I want to automate the process of DR mirror and then Vault/backup using the Protection manager. But, the dataset in the protection manger require that the luns be in the qtree. I had a session on Oncommand and they said we can make it work by unflagging an option in the dfm.
But my client here want to go with moving the luns into the qtree as the best practice. So, I would like to know if there is a way in moving these luns into a qtree (by creating a new qtree)?? I have attached a snapshot of my environment. Some are in the qtree but some are not.
So how do I move them into a newly created qtree in the same volume? Is it necessary to take the luns offline? DOT 8.0.1 is used
The lun move command will move and/or rename a lun. As long as in the same volume the command works to rename or move between qtrees or in or out of a qtree. lun move /vol/lun1.lun /vol/qtree/lun1.lun for example... I haven't tried it hot so would be good to test out with a test lun while writing/reading it... it shouldn't have an outage for the command but worth testing or opening a case to make sure.
SnapDrive may get confused though so worth testing to see if a rescan picks up the new path. The host won't mind since the same lun has the same mapping after the move but the container path will have to be refreshed or fixed possibly (ideally it picks it up when you test it on a test lun).
From the Block Access Management Guide.. on lun move..what I suspected which is good news. You can change the lun name and path (or just name or path) with the lun move command to move into a qtree. The only question to me is snapdrive container refreshing..
Note: This process is completely nondisruptive; it can be performed while the LUN is online and serving data.
The process is non-disruptive, must be done using the 'lun move' command as Scott pointed out. I have done this many times with live data. SnapDrive for Windows doesn't care and will update appropriately. Just make sure that a SnapManager is not currently performing a backup and/or verify while you use the 'lun move' command.
Snapmirror Vsm will make the target match the source on next update and will transfer the block changes. You can create a manual snapdrive snapshot to test snaps. Then you can snap delta that snap to the last snapmirror snap and see the estimated size of the next transfer.