Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: VxVM breaking mirror for migrating storage
Top Forums UNIX for Advanced & Expert Users VxVM breaking mirror for migrating storage Post 302895551 by keelba on Tuesday 1st of April 2014 09:24:00 AM
Old 04-01-2014
VxVM breaking mirror for migrating storage
We are in the process of migrating storage from one array to another. I know the commands I would use in LVM but I am not very familiar with VxVM.

The goal is to attach the new LUNs from the new array and add them to the disk group. Then mirror the data online to these new LUNs using VxVM mirroring. Once the mirroring has completed we would break the mirror from the old LUNs and be running on the new storage.

The catch here is that the customer is not 100% sure they want to be on the new array and wants the ability to failback quickly if there are problems, such as performance. There are several terabytes of data so the original sync could be quite time consuming. If, for example, it takes 12 hours and the customer complains about the performance, we want to get back on the old disks as soon as possible, not after waiting another 12 hours.

In LVM, I could do this simply with the lvsplit and lvmerge commands. The lvsplit breaks the mirror into a new lvol and keeps a bitmap of all the changes so that resyncing the mirror happens much more quickly, very similarly to a snapshot. If, after a couple of days, the customer is satisfied, we would completely remove the old LUNs and be done with the project.

Can anyone help me with the commands to do the same in VxVM? I found conflicting answers on Google. One says an exact equivalent to lvsplit/merge is the command vxassist snapshot and vxassist snapback. Antother sites suggests using vxplex detach and vxplex attach. So if anyone has suggestions on the best way to accomplish this, I'd really appreciate it.

One thing I need an answer for, is where the bitmap is stored and how to make sure we do not fill it up and lose it. This is an active database so the delta might be quite large for all we know after a few days.
 

10 More Discussions You Might Find Interesting

1. HP-UX

Breaking Mirror

Can some one point this UNIX newbie to a web site or directions on the steps needed to break a mirror in HP-UNIX to change a bad hard drive. (4 Replies)
Discussion started by: egress1
4 Replies

2. Solaris

Breaking mirror for patches, sun/os 5.9

Hi, Going to be applying patches to Sun prod (dev 1st) boxes soon, I'm going to break the mirror's on 3 file systems on the root disk prior to that (/, /var, /swap),then run 9_Recommended. Then, run it for a day or 2 before re-syncing the mirrors. But, what if I want to backout of this... (1 Reply)
Discussion started by: BG_JrAdmin
1 Replies

3. Solaris

Solaris 10 - breaking of mirror and change new hard disk

Hi, am a newbie at solaris. Need advice and help on this. 1) How do I break the mirror between 2 hard disks. (wish to keep 1 good hard disk as backup) 2) After remove 1 hard disk and put in new hard disk, how do I initialise or fomat the new hard disk? 3) How do I put back the backup... (3 Replies)
Discussion started by: chongkls77
3 Replies

4. 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

5. 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

6. AIX

IBM SAN Storage DS4700 - Copy Mirror Flashcopy

Hello, Does anyone know how to copy SAN Storage logical disks from IBM TotalStorage Software. I have a SAN Logical Disk of 200GB mounted on my AIX LPAR_1 via fibre channel fcs0 I would like to make an exact copy of the SAN Logical Disk from IBM totalStorage and mount it on AIX LPAR_2 ... (4 Replies)
Discussion started by: filosophizer
4 Replies

7. Red Hat

breaking a hard drive mirror

Hey guys i have a machine running redhat enterprise 3.8 (i believe) and it has two hard drives that are mirrored. what would i have to do to get them to act as two seperate hard drives so i have 120gb capacity total as opposed to just 60? also, what would i do if i just wanted to take one of... (4 Replies)
Discussion started by: pacman529
4 Replies

8. Solaris

Unable to boot from mirror disk on x86 server configured under VxVM

Hi, Can you help me on booting x86 server configured under VxVM. Server boots fine normally from both the disks but if I try to boot server from mirror disk without starting veritas, then it does not boot. vxplex -g rootdg dis var-02 vxplex -g rootdg dis swapvol-02 vxplex -g rootdg dis... (2 Replies)
Discussion started by: milindphanse604
2 Replies

9. Red Hat

Migrating an Oracle database storage - REDHAT4

e have a RHEL4 server with an Oracle 10 ( RAC ) are migrating storage bank records. The copy is made by the storage they make a copy of the level of disk all blocks are copied and the file permissions. Problems we had Initially the Cluster service was not rising due to absence of OCR disks... (0 Replies)
Discussion started by: fausto.ncc1701
0 Replies

10. AIX

Migrating LUNs to new storage array

All, I have a AIX server with multiple volumes and I need to move them from a legacy storage SAN to a new SAN. We are concerned because to use mirrorvg as we would have to run on a single HBA (one on the old SAN and one on the new). Our other option is to use an appliance to do a block... (3 Replies)
Discussion started by: bkchicago
3 Replies

LEARN ABOUT HPUX

vxbrk_rootmir

vxbrk_rootmir(1M)														 vxbrk_rootmir(1M)

NAME

       vxbrk_rootmir - break off a mirror of a VxVM root disk to create a separate root disk generation

SYNOPSIS

       /etc/vx/bin/vxbrk_rootmir [-g diskgroup] [-v] [-b]     [-t tasktag] {daname|dmname}

DESCRIPTION

       The  vxbrk_rootmir  command  creates  a mirror of a Veritas Volume Manager (VxVM) rootable boot disk, breaks the mirror, and then makes the
       broken-off mirror into a completely separate root disk that is suitable for booting by itself.

       Except the specified target disk, the bootdg should not contain any disks other than valid root mirror disks.  A  valid	root  mirror  disk
       should have mirrors of all volumes in the bootdg. Thus, all disks must be exactly identical in terms of the volumes contained.

       The  given disk access name, daname, or disk media name, dmname, is first checked to see if it is already a valid root disk mirror.  If so,
       the mirror is broken off from the current VxVM root disk, and regenerated into a unique VxVM root disk.	If the specified  disk	is  not  a
       valid  root disk mirror, and is unused for other purposes, the vxrootmir command is first called to mirror the specified disk from the cur-
       rent VxVM root disk.  After the mirroring operation is complete, the mirror is then broken off, and regenerated into  a	unique	VxVM  root
       disk.

OPTIONS

       -b   Uses  the  setboot	command  to set the alternate boot disk to the specified disk.	If the -v option is also specified, information is
	    displayed about the current setboot settings.

       -g diskgroup
	    Specifies the disk group into which the newly broken-off mirror is to be placed. The disk group is created	if  it	does  not  already
	    exist.   If  the  disk group already exists, the broken-off mirror is added to it.	If this option is not specified, the disk group of
	    the broken-off mirror is set to the current default disk group. However, the generation number is made different from the default disk
	    group to prevent the mirror from being automatically imported.

       -t tasktag
	    Marks  any tasks that are registered to track the progress of an  operation with the specified tag, tasktag.  This option is passed to
	    vxrootmir if it is necessary first to mirror the specified disk that is to be broken off.

       -v   Displays verbose output, including timestamps for operations that are in progress.	This option is passed to vxrootmir if it is neces-
	    sary first to mirror the specified disk that is to be broken off.

ARGUMENTS

       daname	 Specifies the disk to be used as the broken off mirror by its disk access name (such as c0t2d0).

       dmname	 Specifies the disk to be used as the broken off  mirror by its disk media name (such as rootdisk03).

EXAMPLES

       This example shows the vxbrk_rootmir command being executed on a disk that already contains a valid root mirror:

       /etc/vx/bin/vxbrk_rootmir -g brkdg -vb c4t15d0
       VxVM vxbrk_rootmir INFO V-5-2-4023 17:47:
	 Checking specified disk(s) for presence and type
       VxVM vxbrk_rootmir INFO V-5-2-4025 17:47:
	 DA c4t15d0s2, DM rootdisk06 is a valid root mirror
       VxVM vxbrk_rootmir INFO V-5-2-4052 17:47:
	 Saving configuration data for later restoration
       VxVM vxbrk_rootmir INFO V-5-2-4022 17:47:
	 Breaking off root mirror on DA c4t15d0s2
       VxVM vxbrk_rootmir INFO V-5-2-4054 17:47:
	 Setting broken off mirror on c4t15d0s2 as unique root disk
       VxVM vxbrk_rootmir INFO V-5-2-2566 17:47:
	 Preparing disk c4t15d0s2 as a VxVM root disk
       VxVM vxbrk_rootmir INFO V-5-2-4046 17:47:
	 Patching devnodes, fstab and volboot file in new Root FS
       VxVM vxbrk_rootmir INFO V-5-2-4045 17:47:
	 Patching /stand/bootconf file to contain new root disk
       VxVM vxbrk_rootmir INFO V-5-2-2462 17:48:
	 Current setboot values:
       VxVM vxbrk_rootmir INFO V-5-2-4048 17:48:
	 Primary:   0/0/2/0.2.0
       VxVM vxbrk_rootmir INFO V-5-2-4010 17:48:
	 Alternate: 0/2/1/0.8.0.255.2.5.0
       VxVM vxbrk_rootmir INFO V-5-2-4042 17:48:
	 Making c4t15d0s2 (0/2/1/0.8.0.255.1.15.0) the alternate boot disk
       VxVM vxbrk_rootmir INFO V-5-2-4028 17:48:
	 Disk c4t15d0s2 is now a broken off root disk

       The  next  example  shows  the  command being executed on a disk that does not contain a valid root mirror, and which requires vxrootmir be
       called to mirror the root disk first:

	      /etc/vx/bin/vxbrk_rootmir -g brkdg -vb c5t5d0
	      VxVM vxbrk_rootmir INFO V-5-2-4023 16:25:
		Checking specified disk(s) for presence and type
	      VxVM vxbrk_rootmir INFO V-5-2-4043 16:25: Mirroring root disk
	      VxVM vxrootmir INFO V-5-2-2501 16:25:
		Gathering information on the current VxVM root configuration
	      VxVM vxrootmir INFO V-5-2-2441 16:25:
		Checking specified disk(s) for usability
	      VxVM vxrootmir INFO V-5-2-2566 16:25:
		Preparing disk c5t5d0 as a VxVM root disk
	      VxVM vxrootmir INFO V-5-2-3766 16:25:
		Disk c5t5d0 is now EFI partitioned disk c5t5d0s2
	      VxVM vxrootmir INFO V-5-2-2410 16:25:
		Adding disk c5t5d0s2 to brkdg as DM rootdisk03
	      VxVM vxrootmir INFO V-5-2-1646 16:25:
		Mirroring all volumes on root disk
	      VxVM vxrootmir INFO V-5-2-1648 16:25: Mirroring volume standvol
	      VxVM vxrootmir INFO V-5-2-1648 16:26: Mirroring volume swapvol
	      VxVM vxrootmir INFO V-5-2-1648 16:30: Mirroring volume rootvol
	      VxVM vxrootmir INFO V-5-2-1648 16:31: Mirroring volume homevol
	      VxVM vxrootmir INFO V-5-2-1648 16:31: Mirroring volume tmpvol
	      VxVM vxrootmir INFO V-5-2-1648 16:31: Mirroring volume usrvol
	      VxVM vxrootmir INFO V-5-2-1648 16:34: Mirroring volume optvol
	      VxVM vxrootmir INFO V-5-2-1648 16:36: Mirroring volume varvol
	      VxVM vxrootmir INFO V-5-2-1616 16:40:
		Disk c5t5d0s2 is now a mirrored root disk
	      VxVM vxbrk_rootmir INFO V-5-2-4052 16:40:
		Saving configuration data for later restoration
	      VxVM vxbrk_rootmir INFO V-5-2-4022 16:40:
		Breaking off root mirror on DA c5t5d0s2
	      VxVM vxbrk_rootmir INFO V-5-2-4054 16:40:
		Setting broken off mirror on c5t5d0s2 as unique root disk
	      VxVM vxbrk_rootmir INFO V-5-2-2566 16:40:
		Preparing disk c5t5d0s2 as a VxVM root disk
	      VxVM vxbrk_rootmir INFO V-5-2-4046 16:41:
		Patching devnodes, fstab and volboot file in new Root FS
	      VxVM vxbrk_rootmir INFO V-5-2-4045 16:41:
		Patching /stand/bootconf file to contain new root disk
	      VxVM vxbrk_rootmir INFO V-5-2-2462 16:41: Current setboot values:
	      VxVM vxbrk_rootmir INFO V-5-2-4048 16:41:
		Primary:   0/0/2/0.2.0
	      VxVM vxbrk_rootmir INFO V-5-2-4010 16:41:
		Alternate: 0/2/1/0.8.0.255.2.0.0
	      VxVM vxbrk_rootmir INFO V-5-2-4042 16:41:
		Making c5t5d0s2 (0/2/1/0.8.0.255.2.5.0) the alternate boot disk
	      VxVM vxbrk_rootmir INFO V-5-2-4028 16:41:
		Disk c5t5d0s2 is now a broken off root disk

SEE ALSO

       vxbootsetup(1M), vxdg(1M), vxintro(1M), vxrootmir(1M), vxtask(1M)

VxVM 5.0.31.1							    24 Mar 2008 						 vxbrk_rootmir(1M)
All times are GMT -4. The time now is 02:46 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy