NetApp



High Level Steps/FlowStep Comments 1dfm options set dpReaperCleanupMode=Never. This is to make sure that during the migration conformance/reaper doesn’t reap any relationship2Validate no active jobs and relationships are idle, and suspend dataset3Relinquish all relationships using DFPM.4Remove all physical resources from the dataset (if the dataset contains multiple relationships, then only remove ones that need migration). 5Relinquish the primary qtrees from the dataset using DFBM.6Migrate the data using technique 1 from NetApp KB 1011499 if you want to migrate the entire volume.Use technique 2 from the same kb if you only want to migrate a qtrees. In this doc the example used is of technique 1 for entire primary volume migration. But irrespective of technique 1 or 2 steps in PM remain the same.7Re-discover the storage controllers in DFM. 8Add the physical resources back to the dfm using the DFBM. 9Import the new relationships into the dataset. 10Resume the dataset and test by doing an on-demand backup job11Revert the option back to orphansdfm options set dpReaperCleanupMode=OrphansDetailed StepsCurrent Environment:Sourcempo-vsim14Snap Vault SourceDestinationmpo-vsim15Snap Vault DestinationNew Sourcempo-vsim16New SnapVault SourceThis is how relationship looks like in Prot Mgr before we start.C:\>dfpm dataset list -m UserHomeId Node Name Dataset Id Dataset Name Member Type Name---------- -------------------- ---------- -------------------- -------------------------------------------------- --------------------------- 1347 Primary data 1344 UserHome volume mpo-vsim14:/UserHome 1367 Backup 1344 UserHome volume mpo-vsim15:/UserHomeC:\> dfpm dataset list -R UserHomeId Name Protection Policy Relationship Id State Status Hours Source Destination ---- --------- ------------------ -------------- ------------ ------- ----- ---------------------------- ----------------------------1344 UserHome Back up 1371 snapvaulted idle 0.0 mpo-vsim14:/UserHome/- mpo-vsim15:/UserHome/UserHome_mpo-vsim14_UserHome1344 UserHome Back up 1373 snapvaulted idle 0.0 mpo-vsim14:/UserHome/adai mpo-vsim15:/UserHome/adai 1344 UserHome Back up 1375 snapvaulted idle 0.0 mpo-vsim14:/UserHome/vsv mpo-vsim15:/UserHome/vsv 1344 UserHome Back up 1377 snapvaulted idle 0.0 mpo-vsim14:/UserHome/amir mpo-vsim15:/UserHome/amir Step 1:This is to make sure that during the migration conformance/reaper doesn’t reap any relationship C:\>dfm options set dpReaperCleanupMode=NeverChanged cleanup mode for relationships managed by protection capability of OnCommand to Never.C:\>Step 2:C:\>dfpm dataset suspend UserHomeSuspended dataset UserHome.C:\>Step 3:Relinquish Relationships using DFPMFrom the DFM ServerC:\>dfpm dataset list -m UserHomeId Node Name Dataset Id Dataset Name Member Type Name---------- -------------------- ---------- -------------------- -------------------------------------------------- --------------------------- 1347 Primary data 1344 UserHome volume mpo-vsim14:/UserHome 1367 Backup 1344 UserHome volume mpo-vsim15:/UserHomeC:\> dfpm dataset list -R UserHomeId Name Protection Policy Relationship Id State Status Hours Source Destination ---- --------- ------------------ -------------- ------------ ------- ----- ---------------------------- ----------------------------1344 UserHome Back up 1371 snapvaulted idle 0.0 mpo-vsim14:/UserHome/- mpo-vsim15:/UserHome/UserHome_mpo-vsim14_UserHome1344 UserHome Back up 1373 snapvaulted idle 0.0 mpo-vsim14:/UserHome/adai mpo-vsim15:/UserHome/adai 1344 UserHome Back up 1375 snapvaulted idle 0.0 mpo-vsim14:/UserHome/vsv mpo-vsim15:/UserHome/vsv 1344 UserHome Back up 1377 snapvaulted idle 0.0 mpo-vsim14:/UserHome/amir mpo-vsim15:/UserHome/amir C:\>dfpm dataset relinquish mpo-vsim15:/UserHome/UserHome_mpo-vsim14_UserHomeRelinquished relationship (1371) with destination UserHome_mpo-vsim14_UserHome (1370).C:\>dfpm dataset relinquish mpo-vsim15:/UserHome/adaiRelinquished relationship (1373) with destination adai (1372).C:\>dfpm dataset relinquish mpo-vsim15:/UserHome/vsvRelinquished relationship (1375) with destination vsv (1374).C:\>dfpm dataset relinquish mpo-vsim15:/UserHome/amirRelinquished relationship (1377) with destination amir (1376).C:\>Step 4: Remove all Resources from Dataset using NMC/CLIFrom the NetApp Management Console Done in the NMC, edit the dataset, remove the physical resources first from the Backup Node, then from the Primary Node. Else do it using cli as followsC:\>dfpm dataset remove -N "Primary data" UserHome mpo-vsim14:/UserHomeDataset dry run results----------------------------------Do: Checking that dataset configuration conforms to its policy.Effect: Conformance checking failed.Reason: Dataset has been manually suspended.Suggestion: Click Resume on the Datasets window to reestablish protection job schedules.Dataset conformance status will be updated after you resume protection of this datasetRemoved volume mpo-vsim14:/UserHome (1347) from dataset UserHome (1344).C:\>dfpm dataset remove -N "Backup" UserHome mpo-vsim15:/UserHomeDataset dry run results----------------------------------Do: Checking that dataset configuration conforms to its policy.Effect: Conformance checking failed.Reason: Dataset has been manually suspended.Suggestion: Click Resume on the Datasets window to reestablish protection job schedules.Dataset conformance status will be updated after you resume protection of this dataserRemoved volume mpo-vsim15:/UserHome (1367) from dataset UserHome (1344).C:\>STEP 5: Relinquish the primary qtrees from the dataset using DFBM. From the DFM Server CLIC:\>dfbm primary dir list 1371ID: 1371Last Backup Status: NormalPrimary Directory: mpo-vsim14:/UserHome/-Secondary Volume: mpo-vsim15:/UserHomeSecondary Volume ID: 1367State: SnapVaultedLag: 29 minsStatus: IdleBandwidth Limit: NoneCustom Script:Run Custom Script As User:C:\>dfbm primary dir relinquish 1371Relinquished control over mpo-vsim14:/UserHome/-.C:\>Repeat this for all relationships.Step6: Migrate the data using technique 1 from NetApp KB 1011499Existing snapvault relationship:Source Destination State Lag Statusmpo-vsim14:/vol/UserHome/- mpo-vsim15:/vol/UserHome/UserHome_mpo-vsim14_UserHome Snapvaulted 00:35:42 Idlempo-vsim14:/vol/UserHome/adai mpo-vsim15:/vol/UserHome/adai Snapvaulted 00:35:42 Idlempo-vsim14:/vol/UserHome/amir mpo-vsim15:/vol/UserHome/amir Snapvaulted 00:35:42 Idlempo-vsim14:/vol/UserHome/vsv mpo-vsim15:/vol/UserHome/vsv Snapvaulted 00:35:42 IdleDesired Snap vault relationshipSource Destination State Lag Statusmpo-vsim16:/vol/UserHome/- mpo-vsim15:/vol/UserHome/UserHome_mpo-vsim14_UserHome Snapvaulted 00:14:41 Idlempo-vsim16:/vol/UserHome/adai mpo-vsim15:/vol/UserHome/adai Snapvaulted 00:13:33 Idlempo-vsim16:/vol/UserHome/amir mpo-vsim15:/vol/UserHome/amir Snapvaulted 00:27:23 Idlempo-vsim16:/vol/UserHome/vsv mpo-vsim15:/vol/UserHome/vsv Snapvaulted 00:16:26 IdleRecipe# Create a new volumepri> vol create newvol aggr0 10gpri> vol restrict newvolpri> snapmirror initialize -S oldvol newvolmpo-vsim16> vol create UserHome aggr1 80mCreation of volume 'UserHome' with size 80m on containing aggregate'aggr1' has completed.mpo-vsim16> vol restrict UserHomeVolume 'UserHome' is now restricted.mpo-vsim16> snapmirror initialize -S mpo-vsim14:UserHome UserHomeTransfer started.Monitor progress with 'snapmirror status' or the snapmirror log.# At time of cutover stop client access to oldvol and continue:pri> snapmirror update -S oldvol newvolpri> snapmirror break newvolmpo-vsim16> snapmirror break UserHomesnapmirror break: Destination UserHome is now writable.Volume size is being retained for potential snapmirror resync. If you would like to grow the volume and do not expect to resync, set vol option fs_size_fixed to off.mpo-vsim16># Resume client access to newvol# Update the SnapVault relationshipsec> snapvault modify -S pri:/vol/newvol/qtree sec:/vol/tradvol/qtreesec> snapvault modify -S pri:/vol/newvol/qtree2 sec:/vol/tradvol/qtree2?If you like not to wait for next update schedule can you update it yourself using the following clisec> snapvault update /vol/tradvol/qtreeAlternatively you can also use start which will do the job of both modify and update.Sec> snapvault start –r –S mpo-vsim16:/vol/UserHome/adai mpo-vsim15:/vol/UserHome/adaimpo-vsim15> snapvault modify -S mpo-vsim16:/vol/UserHome/- mpo-vsim15:/vol/UserHome/UserHome_mpo-vsim14_UserHomempo-vsim15> snapvault modify -S mpo-vsim16:/vol/UserHome/adai mpo-vsim15:/vol/UserHome/adai mpo-vsim15> snapvault modify -S mpo-vsim16:/vol/UserHome/amir mpo-vsim15:/vol/UserHome/amir mpo-vsim15> snapvault modify -S mpo-vsim16:/vol/UserHome/vsv mpo-vsim15:/vol/UserHome/vsv 7 Re-Discover Controllers C:\>dfm host discover mpo-vsim16Refreshing data from host mpo-vsim9.mponbtme.lab.eng.app.in (134) now.C:\>dfm host discover mpo-vsim15Refreshing data from host mpo-vsim10.mponbtme.lab.eng.app.in (135) now.C:\>Wait for svtimestamp to be populated on both source and destination.C:\>dfm detail mpo-vsim15 | findstr /i svTimestamp svTimestamp 2012-08-08 19:15:02.000000STEP8: Add the physical resources back to the dfm using the DFBMFrom the DFM Server CLI C:\>dfbm primary dir add mpo-vsim15:/UserHome mpo-vsim16:/UserHome/-Started job 3608 to create backup relationship between mpo-vsim15:/UserHome and mpo-vsim16:/UserHome/-.C:\>This will not do a rebaseline as the relationship already exists we are only adding the same to dfm.C:\>dfbm job list 3608Job: 3608Status: NormalTime Started: 08 Aug 19:29Description: Importing backup relationship between secondary mpo-vsim15:/UserHome and primary mpo-vsim16:/UserHome/-.Progress: DoneArguments: svsVolume=1367&svpHost=141&svpDir=%2FUserHome%2F-&svThrottle=0C:\>Take careful note of the syntax here. The Secondary / SnapVault volume goes at the beginning, with no qtree. No /vol syntax either. The primary SnapVault source goes last, and includes the qtree.Step 9: Import the new relationships into the dataset. From NetApp Management Console Browse External Relationships and you will find both the new SnapVault. Import them to the correct points in the dataset. PS: You may see this error by nothing to worry.After importing the relationships, the dataset will show a status of Warning. When you investigate the warning, the dataset reports, "no backup history exists".? To clear this warning event, either run an on-demand backup job or wait for the next scheduled backup to occur. Either way, the backup job will force an update of the relationship and create a new backup snapshot. Once the first backup for the imported relationship are succesful, the warning status will go away.10 Resume the Dataset, Protect now, and Review jobs We resume the dataset from the NMC, and hit Protect Now with an hourly job. When reviewing the jobs, we notice a few failed jobs from 30 minutes prior, this may be due to adding the resources back into the dataset (the primary and tertiary) which may have been unnecessaryThings to note as part of this migration.Some of things you should be aware of are the following.We lose the dynamic referencing, and there by auto relationship creation of qtree(for QSM and SV) which are created after the this migration process.We also lose the ability of dynamic secondary sizing of the imported destination volumes as they are not marked dp_managed.(this may not happen in our case as it’s within the same dfm server which one needs to validate)Though this could be overcome using the Secondary Space Management feature by migrating the destination volumes.Old backup version on the primary are lost, as the primary volumes FSid would have changed.The snapshots associated with old backup version before the migration process would only be available via Ops Mgr Ui and not via PM restore wizard.These old snapshot will not be deleted as per retention by PM instead needs to be deleted by users. ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download