Sponsored Content
Top Forums UNIX for Advanced & Expert Users Presenting current LUNs to new OS. RHEL 7, LVM Post 303039868 by hburnswell on Wednesday 16th of October 2019 03:30:37 PM
Old 10-16-2019
Thank you @Peasant for the reply. I wanted to provide an update...

The process was actually much easier than expected. We just needed to:

1. Snapshot the original LUN.
2. Create the same mount point on the new server.
3. Copy the /etc/fstab entry from original server and write it to the /etc/fstab on the new server.
4. Present the snapshot LUN to the new server.
5. Reboot the new server.

This allowed us to to see the original data as expected.

Thanks again for the help..

HB
 

9 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Presenting the user a menu in Bash ...

Hello, I am trying to write a bash script function to present the user a menu of options. The following is what I have so far: function MainMenu { while ] do echo "--------------------------------------------------------------------------------" echo... (4 Replies)
Discussion started by: ckoeber
4 Replies

2. Red Hat

Migrating from RHEL LVM to VxVM

Hiya, Is there a known method from converting LVM data to VxVM data.. ie we have a load of local and SAN (HPDM) mounts on RHEL 4u5/5u1 servers which are now required to be clustered with SFS (VxFS,VxVM,CFS,VCS etc) I've come across the vxvmconvert, but thought that was HP-UX only? Many... (0 Replies)
Discussion started by: itsupplies
0 Replies

3. Filesystems, Disks and Memory

Migrating from RHEL LVM to VxVM

Hiya, Is there a known method from converting LVM data to VxVM data.. ie we have a load of local and SAN (HPDM) mounts on RHEL 4u5/5u1 servers which are now required to be clustered with SFS (VxFS,VxVM,CFS,VCS etc) I've come across the vxvmconvert, but thought that was HP-UX only? Many... (3 Replies)
Discussion started by: itsupplies
3 Replies

4. HP-UX

How to reduce LVM to create another LVM

Hi, I'm new to HP-UX. I have LVM on /var with 92Gig. I would like to reduce it to create another LVM for Oracle client with 800 meg or so. How to do it. I'm running 11.iv3 Thanks (4 Replies)
Discussion started by: lamoul
4 Replies

5. Red Hat

Does RHEL 5 provide a command to collect RHEL system log in single compress file?

Hi, I heard a command that can collect all RHEL 5 log in a single compress file before I forget. Does any body know...What the command is ? Thanks. (4 Replies)
Discussion started by: nnnnnnine
4 Replies

6. UNIX for Dummies Questions & Answers

How to convert non LVM root partition to LVM?

Hi Guys, I m using redhat 6, I have installed root partition as non-LVM . Is there any way i can convert it to LVM? (1 Reply)
Discussion started by: pinga123
1 Replies

7. Red Hat

Error throwing while installing vsftpd package in rhel 6. using rhel 6 dvd.

Hi all, Im studying rhcsa as of now, so yum installation and dependencies are messing me to not workit out. i have dual os, win 7 & rhel 6. i have tried this installation of vsftpd package with rhel 6 dvd in VM rhel 6 in win 7 as well as host rhel 6.still the same issue. below error... (6 Replies)
Discussion started by: redhatlbug
6 Replies

8. Red Hat

How to reduce the LVM Size in RHEL/Centos 7 ?

Hi All, I have one logical volume with size as 900G and it is mounted as xfs file system. Now I want to reduce this partition to 500G. So I followed the below steps. unmount the mount point /home Reduced the volume using the command Now I remounted the partition. But the problem... (3 Replies)
Discussion started by: kalpeer
3 Replies

9. UNIX for Beginners Questions & Answers

Presenting data in column format

I have written a script that that takes file names and breaks them apart. File names are : aal_mock.war.deployed AuroralMockService-1.0.war.deployed consumerProfile.war.deployed EbillMock.war.deployed IAMAOGServices.war.deployed IAMPermission.war.deployed... (5 Replies)
Discussion started by: Junaid Subhani
5 Replies
nfs_manual_setup(7)					 Miscellaneous Information Manual				       nfs_manual_setup(7)

NAME
nfs_manual_setup - Describes how to manually set up the Network File System (NFS) DESCRIPTION
This reference page describes how to manually set up the Network File System (NFS). Setting up NFS includes configuring the following: Servers Clients, using /etc/fstab Clients, using Automount or AutoFS Setting Up Servers Use the following procedure to set up an NFS server: Create the /etc/exports file and add the appropriate entries to it. The entries that you add are site-specific but their syntax should be as follows: pathname [-root=0] [-root=hostlist [-anon=uid] [-rw=hostlist [-ro] identifier_1 ... identifier_n You can use the number sign (#) as a delimiter to add comments. For more informa- tion, see the exports(4) reference page and the Network Administration manual. Add the following information to the /etc/rc.con- fig.common file by using the /usr/sbin/rcmgr command, which has the following syntax: /usr/sbin/rcmgr set variable value Indicate that this system is a server, by entering the following command: # /usr/sbin/rcmgr set NFSSERVING 1 (A zero (0) in place of the 1 indicates that this system is not a server.) Specify the number of nfsd server threads you want to run on the system. Separate symbols are used for UDP threads and TCP threads. For example, to run 8 TCP threads and 4 UDP threads, enter the following commands: # /usr/sbin/rcmgr set NUM_TCPD 8 # /usr/sbin/rcmgr set NUM_UDPD 4 You can run up to 128 server threads for both transports combined. Although 8 server threads for each transport is usually adequate, if NFS client performance is slow, a possible solution is to increase the number of server threads. Set the NONROOTMOUNTS parameter. Setting this parameter to 0 specifies that only root users on the client systems can mount file systems. Setting it to 1 specifies that anyone on the client systems can mount file systems. The following command specifies that users must be running as root to mount file systems from the server: # /usr/sbin/rcmgr set NONROOTMOUNTS 0 Specify whether you want to run the PC-NFS daemon. PC-NFS software provides personal computers on your network with the same capabilities as NFS. PC-NFS is based on the client/server model. The client software runs on the per- sonal computer. The server software runs on the Tru64 UNIX server. Instructions for setting up the PC-NFS client software is pro- vided with the PC-NFS software documentation. To specify that you want to run the PC-NFS daemon, enter the following command: # /usr/sbin/rcmgr set PCNFSD 1 You must then export the directories you want to mount on the PC client to the client. Also, you must export the /usr/spool/pcnfs directory to the PC client for the client to be able to utilize network printing. For information on exporting directories, see the Network Administration manual. Specify whether you want to run the NFS locking service to allow clients to set advisory record locks on files exported to them. To specify that you want to run the NFS locking service, enter the following command: # /usr/sbin/rcmgr set NFSLOCKING 1 Note, by default, 7 nfsiod daemons are run on all NFS systems. To turn this client service off, enter the following command: # /usr/sbin/rcmgr set NUM_NFSIOD 0 The /usr/sbin/rcmgr command appends the information to the end of the /etc/rc.config.common file. For more information on the rcmgr utility, see the rcmgr(8) reference page. Make sure that one of the following is true for client systems to which you are exporting file systems: They have an entry in the /etc/hosts file of the server. Their host information is in the hosts database, if the network is serving host information with NIS or DNS. The server specifies the client's Internet address instead of its host name in its /etc/exports file and the mountd daemon is not configured to run with Internet address checking turned on. Start the NFS daemons by entering the following command: # /sbin/init.d/nfs start # /sbin/init.d/nfsmount start To stop the NFS daemons, enter the following command: # /sbin/init.d/nfs stop Using the /etc/fstab File to Set Up Clients Use the following procedure to set up an NFS client, using the /etc/fstab file: Edit the /etc/fstab file. Unless you are using an automatic mounting service, such as Automount or AutoFS, edit the /etc/fstab file to contain an entry for each file system that you want to mount on your system if you want it mounted automatically. Specify the file system you are mount- ing, the server you are mounting it from, the permissions with which it is mounted, and the local mount point for it. The syntax for entries in the /etc/fstab file is as follows: fs_spec@server fs_file fs_vfstype fs_mntopts fs_freq fs_passno For more information, see fstab(4). The following is a sample /etc/fstab file: /usr/dist@host1 /usr/dist nfs ro,bg 0 0 share/man@host2 /usr/share/man nfs ro,bg 0 /usr/staff/h0@host3 /nfs/host3/usr/staff/h rw,bg 0 /usr/staff/h1@host3 /nfs/host3/usr/staff/h1 nfs rw,bg 0 0 Create a local mount point for each remote file system that you specified in the /etc/fstab file. The local mount points must correspond exactly to the fs_file field in the /etc/fstab file. In the preceding example, the client system uses the /etc/fstab file to mount the remote file system /usr/share/man from host2. The /etc/fstab entry specifies that the local mount point is also called /usr/share/man on the client system. While this is the easiest way to name the local mount point, it can have any name. To create the /usr/share/man mount point, enter the following command: # mkdir /usr/share/man Make sure that one of the following is true for server systems from which you are importing file systems: They have an entry in the /etc/hosts file of the client. Their host information is in the hosts database, if the network is serving host information with NIS or DNS. Edit the /etc/rc.config.common file by using the /usr/sbin/rcmgr utility. Add the following information to the /etc/rc.config.common file: Whether this system is an NFS server (a system can be both a client and a server). The number of nfsiod daemons that you want the system to run. To specify that you want this system to run 7 nfsiod daemons, enter the following command: # /usr/sbin/rcmgr set NUM_NFSIOD 7 You can run up to 64 nfsiod daemons. Although 7 nfsiod daemons is usually adequate, if NFS read and write performance is slow, you can increase the number of nfsiod daemons. Optionally, you can turn on the NFS locking service, if you want to be able to set advi- sory record locks on NFS-mounted files. To do this, enter the following command: # /usr/sbin/rcmgr set NFSLOCKING 1 Note that the NFS locking service must also be running on the server. The /usr/sbin/rcmgr command appends the information to the end of the /etc/rc.config.common file. For more information on the rcmgr utility, see rcmgr(8). Start the NFS daemons by entering the following command: # /sbin/init.d/nfs start # /sbin/init.d/nfsmount start If you are using Automount or AutoFS on this system, you should complete the steps in the Network Administration manual before starting the NFS daemons. If you need to stop the NFS daemons, enter the following command: # /sbin/init.d/nfs stop Administering Automount and AutoFS Maps You can customize Automount and AutoFS maps to suit your environment and either administer them locally, distribute them using NIS, or both. For information on creating and administering Automount and AutoFS maps, see the Network Administration manual. RELATED INFORMATION
Commands: autofsd(8), automount(8), mountd(8), nfsconfig(8), nfsd(8), nfsiod(8), rpc.lockd(8), rpc.statd(8) Files: advfs(4), cdfs(4), fstab(4) Network Information: nfs_intro(4) Network Administration, Technical Overview delim off nfs_manual_setup(7)
All times are GMT -4. The time now is 10:53 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy