This post is more than 5 years old
25 Posts
0
2804
Can Open Replicator be used to migrate Solaris 5.10 with SVM?
Can Open Replicator be used to migrate Solaris 5.10 using Solaris Volume Manager from USP1100 to DMX3( Model DMX3-24, Microcode Version: 5771, Microcode Patch Level:105, FBA Geometry Emulation: Native).
Each Source(USP1100) device size is 40.70GB. Available dev sizes in the target array are 33.72GB and 8.43GB. So I guess a 5-way meta with 8.43GB can be formed of 42.15GB as the target device to migrate the data.
I know that a Solaris using VXVM can be migrated using Open Replicator, but I am not sure about if Solaris using Solaris Volume Manager can be migrated using Open Replicator.
Thx in Advance
Each Source(USP1100) device size is 40.70GB. Available dev sizes in the target array are 33.72GB and 8.43GB. So I guess a 5-way meta with 8.43GB can be formed of 42.15GB as the target device to migrate the data.
I know that a Solaris using VXVM can be migrated using Open Replicator, but I am not sure about if Solaris using Solaris Volume Manager can be migrated using Open Replicator.
Thx in Advance
stcba
6 Posts
0
July 31st, 2009 15:00
I will assume you know how to get the OR-specific plumbing set up and will address just the SVM-specific issues. Here's the process in a nutshell.
Let's take an example where I have several filesystems, each on a soft partition. To keep it simple, all the soft partitions are carved out of an SVM metadevice called d100. Further, metadevice d100 is built using 2 luns on your USP1100. OR will be used to do a hot pull to DMX devices emcpower1a and emcpower2a.
1) capture the existing SVM config
metastat -p >> /etc/lvm/md.tab
cp /etc/lvm/md.tab /etc/lvm/md.tab.new
2) create your OE pairing file on some other host that has symcli and OR licensing
3) edit md.tab.new and replace the references to the USP devs with the emcpower1a and emcpower2a. It's important to replace the correct USP lun with its partner in a way that is consistent with your OR pairing file. Also, verify that any lines referencing a soft partition comes AFTER the line for d100. For example, if soft partition d101 comes before metadevice d100 in md.tab.new, then move the d101 line below d100. This is important for when you import (metainit) the devices later.
4) unmount all filesystems relating to metadevice d100
5) remove soft partitions and metadevice d100
metaclear -p d100
metaclear d100
6) shutdown the host
shutdown -y -g 0
7) Remove USP devices from the host by unmasking or unzoning, whichever you prefer
8) Start OR session
symrcopy -file -hot -pull -copy create
symrcopy -file activate
symrcopy -file set pace 0
Wait for copy to complete or just move on. Doesn't matter with a hot pull.
9) Boot the host
boot
10) Verify host only sees DMX luns
syminq
11) Import SVM devices
cp -p /etc/lvm/md.tab /etc/lvm/md.tab.
cp -p /etc/lvm/md.tab.new /etc/lvm/md.tab
metainit -a
12) Verify soft partitions are there and mount filesystems
metastat -p
mountall
Good luck!
dynamox
2 Intern
2 Intern
•
20.4K Posts
0
April 7th, 2009 07:00
RRR
1 Rookie
1 Rookie
•
5.7K Posts
0
April 7th, 2009 07:00
But with OR you can migrate anything, since OR only looks at the blocks on the symdevs, not on the filesystems.
Ah... I now see I missed some crucial words.... the data is coming from a USP. I'd ask EMC about this or consult the elab navigator. I think you should ask EMC, since the OR needs to be installed by EMC anyway, so they are involved anyway, right ?
Message was edited by:
RRR
SPC3
25 Posts
0
April 7th, 2009 08:00
I am just curious to know about Solaris using Solaris Volume Manager
SPC3
25 Posts
0
April 7th, 2009 08:00
It is SunOS Generic_125100-10 sun4u sparc SUNW,Sun-Fire.
Thx
SPC3
25 Posts
0
April 7th, 2009 08:00
Message was edited by:
SPC
dynamox
2 Intern
2 Intern
•
20.4K Posts
0
April 7th, 2009 10:00
http://docs.sun.com/app/docs/doc/816-4520
SPC3
25 Posts
0
April 7th, 2009 12:00
Vajinap
47 Posts
0
August 12th, 2009 08:00
SPC3
25 Posts
0
August 12th, 2009 08:00
Anonymous
5 Practitioner
5 Practitioner
•
274.2K Posts
0
August 13th, 2009 13:00
Thanks!
stcba
6 Posts
0
August 24th, 2009 10:00
In order to access the add'l capacity, you will need to take the following steps in an outage.
1) use "powerformat" to re-label the luns so that the SunOS recognizes the larger size. Just as an experiment, look at the output of "format" immediately after the Open Rep session is completed and you'll see that SunOS thinks the target lun is the same size as the smaller source, even though in reality, the target is larger. This is because Open Rep copies EVERY TRACK, including the disk label, from the source. "powerformat" updates the label to reflect reality.
2) The tricker step is to get SVM to recognize the add'l space after "powerformat" is complete. This takes a combination of metaclear and metainit.
Note that Step 2 bears quite a bit of risk. I've had mixed success with the Step 2 in our lab. If risk mitigation is an objective (and of course it is, since the application is clustered), then I recommend creating target luns that are equal to or slightly larger than the source.
Anonymous
5 Practitioner
5 Practitioner
•
274.2K Posts
0
October 13th, 2009 12:00
I am currently doing a project where we are replacing an HDS with a V-Max. There are quite a few Solaris servers using SVM.
My question is on the step where we use metaclear -p d# to delete all of the soft partitions and then metaclear d# to delete the metadevice.
The question is, is this step necessary? Will the metaclear remove the specified d# from the md.tab file? I guess I am unsure as to what this will do.
This is the procedure I have, and please add any comments if you have them.
//Update md.tab
1. metastat -p > md.tab
cp -p /etc/lvm/md.tab /etc/lvm/md.tab.new
//Verify State Replica Databases are on Local Disk
2. metadb -i
3. Unmount file systems
4. Comment out file systems in vfstab using HDS luns.
5. Reboot and come up with V-Max luns
6. Edit md.tab.new with emcpower devices replacing HDS luns
7. Update Solaris label with powerformat
8. Import SVM devices.
metainit -n -a
metainit -a
9. Verify metadevices and soft partitions
metastat -p
metastat | more
10. mount filesystems
11. Uncomment vfstab
Message was edited by:
spwvol1978
stcba
6 Posts
0
November 11th, 2009 11:00
The procedure you wrote looks sound but I'd investigate a couple of things first. Without the metaclear, I'm not sure that SVM will allow you to do the metainit in step 8. If this works for you, please post!
Secondly, you may want to move the powerformat in step 7 to the end, after you've successfully migrated the data, or maybe not use it at all. We ran into an issue using it when trying to get SVM to metainit a lun after powerformat was run. I didn't commit a ton of time to investigate it but I think it is caused by how SVM defines its soft partitions. It works like a casette tape. You remember those, don't you? It basically says start at a certain sector number and go forward for so many sectors and this becomes your size. Well imagine if you started out with a 10GB lun and 2 soft partitions, each partition is 5 GB. When you used up that 10GB and had to grow, you added another 10GB. So the first soft partition has been told to start at 0 and go forward 5GB. The 2nd partition was told start at 5GB and go to 10GB. After adding the 2nd 10GB lun and expanding the first partition, then the first soft partition definition is something like "start at 0 and go 5GB, then start at 10GB and go another 5GB". Now, introduce the powerformat and LUN expansion in the middle of that. What I think is, the specifications given to the soft partitions are no longer valid. If the first partition follows its directions of starting at 0 and using 5GB but then starting at 10GB and using 5 more, then it will not find it's data when it gets to the 10GB milepost because that 10GB milepost is no longer in the same place as before. Milepost 10GB may be somewhere in the whitespace of the first LUN, which is now larger. In any event, that's how I reconcile the lun expansion problem. For those soft partitions that never grew to another lun, we tested out powerformat and it worked fine. But for those that were a little more complicated, the model breaks down. Hope this helps.
Anonymous
5 Practitioner
5 Practitioner
•
274.2K Posts
0
March 7th, 2010 17:00
Thanks stcba. The powerformat will only be used to update the solaris label, and not to recognize the extra space.
Thanks!