Sponsored Content
Full Discussion: Move root disk to new server
Operating Systems Solaris Move root disk to new server Post 71861 by reborg on Monday 16th of May 2005 03:28:15 PM
Old 05-16-2005
Quote:
Originally Posted by VirginiaSA
Thanks. To thicken the issue, I'm running VxVM. I guess I'll need to install the VxVM license at the new site. Do I install the license at the ok prompt prior to the first boot -r command?
No, the root disk will be an encapsulated UFS filesystem, and will boot. You should boot and then apply the license.

Actually, thinking about this further is could be best to unencasulate the disk before moving it and reencapsuleate it at the new site.

Last edited by reborg; 05-16-2005 at 08:32 PM..
 

9 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

Move a disk to Sol. 2.6

I removed an external Sun disk (with data on it) from an old 2.6 system and added the disk to another 2.6 system. The new system seems to recognize the system (verified by the format command). When try to mount I am getting, I got the error: mount: /dev/dsk/c1t1d0s6 is not this fstype. I... (3 Replies)
Discussion started by: sunshine
3 Replies

2. Shell Programming and Scripting

how to move a file from one server to another server using FTP in shell script?

I have a file --> file1.txt i need to copy this file to another server using FTP....the 2 servers are server1 and server2..may i know how to write a script that can do this? thanks in advance! Im a newbie to this... (4 Replies)
Discussion started by: forevercalz
4 Replies

3. Solaris

Move root filesystem to other slice

Hi, df -h display: # df -h Filesystem size used avail capacity Mounted on /dev/dsk/c1t0d0s0 9.8G 8.1G 1.7G 84% / /proc 0K 0K 0K 0% /proc mnttab 0K 0K 0K 0% /etc/mnttab fd 0K 0K 0K 0% /dev/fd swap 1.0G 152K 1.0G 1% /var/run swap 1.1G 24M 1.0G 3% /tmp /dev/dsk/c1t0d0s3 57G 13G 43G 24%... (4 Replies)
Discussion started by: lamoul
4 Replies

4. Red Hat

Best softwareraid for 2 disk root-server

Hi, we have a root-server with 2 Disks, each 750 gb / centos 5.1 we would like to have 4 mirrored data, and 1 mirrored boot-filesystem what do you think is the best solution, I would like to use linux lvm for a raid1-mirror, but I was told the system wont boot in case of a disk failure ... (4 Replies)
Discussion started by: funksen
4 Replies

5. Solaris

Move partition to new disk

Hi, The disks of my servers are getting full and I need to move the /export/home partition on to a new set of disks. I already have 2 mirrored disks and have added 2 more and mirrored them after creating the filesystem on them. Do I just need to edit the /etc/vfstab and point the /export/home... (1 Reply)
Discussion started by: run_time_error
1 Replies

6. Solaris

Lost Root Password on VXVM Encapsulated Root Disk

Hi All Hope it's okay to post on this sub-forum, couldn't find a better place I've got a 480R running solaris 8 with veritas volume manager managing all filesystems, including an encapsulated root disk (I believe the root disk is encapsulated as one of the root mirror disks has an entry under... (1 Reply)
Discussion started by: sunnyd76
1 Replies

7. UNIX for Dummies Questions & Answers

Move os from 1 disk to the other

Hi, I have server with 2 active disk, but disk 1 contain big part of os is falling, how can i move everything to disk 2 and then remove the disk 1? Thanks (4 Replies)
Discussion started by: prpkrk
4 Replies

8. Linux

Move OS to storage disk

Hi We have RHEL 7.3 running from local disk and we want to move it to storage. I am unable to find any proper procedure to do this activity. Please help. (4 Replies)
Discussion started by: powerAIX
4 Replies

9. Solaris

Move root disk to new identical hardware

We have in a couple of occasions moved root disk & flashcard in netra 240 to new identical hardware instead of replacing mb in dead server. Flashcard is to preserve mac adresses and mainly hostid for license stuff. Works without doing anything other than poweron & boot. Now we have a similar... (5 Replies)
Discussion started by: stockhes
5 Replies
vxrootmir(1M)															     vxrootmir(1M)

NAME
vxrootmir - create a mirror of a Veritas Volume Manager root disk SYNOPSIS
/etc/vx/bin/vxrootmir [-g diskgroup] [-t tasktag] [-p Pool_1,Pool_2,...] [[-v] [-b] [-R] root_mirror] DESCRIPTION
The vxrootmir command creates mirrors of all of the volumes on a Veritas Volume Manager (VxVM) rootable boot disk, and makes the new disk bootable. A disk to be used as a mirror can be specified either by its VM disk name (disk media name) or by its device name (disk access name). If a disk media name is specified, it is validated to make sure that it exists and that it has been properly initialized. This validation includes making sure that the private region is at the same location and has the same length as the private region on the primary root disk, and that the sum of the lengths of all of the subdisks located on the primary root disk will fit within the available space in the public region of the specified disk. If a disk access name is specified, it is validated to make sure it exists and is not in use, and that the total length of all the subdisks on the primary root disk will fit within the public region. The disk is then initialized to contain a private region with the same offset and length as the private region on the primary root disk. A new disk media name is assigned to the disk formed from the prefix rootdisk followed by the next available number (for example, rootdisk02, rootdisk03, and so on). All volumes that have a subdisk on the primary VxVM root disk are mirrored on the specified disk. When the root volume (rootvol) is mir- rored, the vxassist command executes vxbootsetup to set up the new disk as a boot disk. The -p option allows you to mirror the volumes on the root disk as stripe columns across several disks. The argument to this option is a list of disks that are to be used for the stripe column mirrors. If not enough disks are specified, vxrootmir prints a message to the standard error output, including information on how many disks are required, and then exits. When initialized for VxVM use, these stripe column disks are named with the prefix rootaux followed by the next available number (for example, rootaux01, rootaux02, and so on). OPTIONS
-b If the system was booted from the VxVM root disk that is being mirrored, this option uses the setboot command to set the alter- nate boot disk to the specified mirror. If the system was booted from another root disk (such as an LVM root disk), an alternate root disk is not set. If the -v option is also specified, information is displayed on the current setboot settings, and on whether the alternate boot disk is set to the specified mirror. -g diskgroup Specifies the boot disk group. -p Pool_1,Pool_2,... Specifies the disks that are to be used for stripe column targets when mirroring the VxVM root disk. The disks can be specified either as disk access names, or as disk media names if they have previously been initialized for use with VxVM. If specified as disk access names, the disks are checked for existence, correct size, and availability for use. -R Indicates that only the volumes required to boot successfully from the new mirror are to be mirrored. -t tasktag Marks any tasks that are registered to track the progress of an operation with the tag tasktag. This option is passed to vxas- sist when mirroring volumes, so any child tasks are also tagged with tasktag. -v Displays verbose output including timestamps for operations in progress. This option is useful as mirroring large volumes can take a long time. ARGUMENTS
daname Specifies the disk to be used as a mirror by its disk access name (such as c0t2d0). dmname Specifies the disk to be used as a mirror by its disk media name (such as rootdisk03). EXAMPLES
This example shows the vxrootmir command being invoked in its simpliest form: /etc/vx/bin/vxrootmir c5t1d0 The next example shows how to use the -R option with vxrootmir. # /etc/vx/bin/vxrootmir -v -b -R c5t10d0 vxrootmir: 10:10: Gathering information on the current VxVM root configuration vxrootmir: 10:10: Checking specified disk(s) for usability vxrootmir: 10:10: Preparing disk c5t10d0 as a VxVM disk vxrootmir: 10:10: Adding disk c5t10d0 to rootdg as rootdisk02 vxrootmir: 10:10: Mirroring only volumes required for root mirror boot vxrootmir: 10:10: Mirroring volume standvol vxrootmir: 10:11: Mirroring volume swapvol vxrootmir: 10:18: Mirroring volume rootvol vxrootmir: 10:20: Current setboot values: vxrootmir: 10:20: Primary: 0/4/0/1.11.0 vxrootmir: 10:20: Alternate: 0/4/0/1.13.0 vxrootmir: 10:20: Making c5t10d0 (0/4/0/1.10.0) the alternate boot disk vxrootmir: 10:20: Disk c5t10d0 is now a mirrored root disk The final example shows how to specify a list of disks for use as stripe column mirrors: # /etc/vx/bin/vxrootmir -v -p c5t11d0,c5t12d0,c5t13d0 c5t10d0 vxrootmir: 12:11: Gathering information on the current VxVM root configuration vxrootmir: 12:11: Checking specified disk(s) for usability vxrootmir: 12:11: Preparing disk c5t10d0 as a VxVM disk vxrootmir: 12:11: Adding disk c5t10d0 to rootdg as rootdisk02 vxrootmir: 12:11: Preparing disk c5t11d0 as a VxVM disk vxrootmir: 12:11: Adding disk c5t11d0 to rootdg as DM rootstpm01 vxrootmir: 12:11: Preparing disk c5t12d0 as a VxVM disk vxrootmir: 12:11: Adding disk c5t12d0 to rootdg as DM rootstpm02 vxrootmir: 12:11: Preparing disk c5t13d0 as a VxVM disk vxrootmir: 12:11: Adding disk c5t13d0 to rootdg as DM rootstpm03 vxrootmir: 12:11: Mirroring all volumes on root disk vxrootmir: 12:11: Mirroring volume standvol vxrootmir: 12:12: Mirroring volume swapvol vxrootmir: 12:19: Mirroring volume rootvol vxrootmir: 12:21: Mirroring volume optvol vxrootmir: 12:24: Mirroring volume usrvol vxrootmir: 12:27: Mirroring volume homevol vxrootmir: 12:28: Mirroring volume tmpvol vxrootmir: 12:28: Mirroring volume varvol vxrootmir: 12:36: Disk c5t10d0 is now a mirrored root disk NOTES
If the vxrootmir command aborts for any reason, or if you interrupt the command during execution, an attempt is made to clean up the VxVM objects that had been generated up to the time of the abort or interruption. All mirror plexes that had already been added, or that were in the process of being added when the interruption occurred, are removed. All Data Media (DM) objects that were created are also removed. If a plex or a DM object cannot be removed, an explanatory message is displayed. SEE ALSO
setboot(1M), vxassist(1M), vxbootsetup(1M), vxintro(1M), vxmirror(1M), vxtask(1M) VxVM 5.0.31.1 24 Mar 2008 vxrootmir(1M)
All times are GMT -4. The time now is 03:02 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy