Since you said these are not trivial-size nodes, here are some tricks I've used:
a) Don't lock the node, let it continue backing up to the old server. b) Do your export in chunks. Exports that run a gazillion hours seems to always cause problems and end up failing. I cut down the size of each export by using fromdate/todate on the export, like fromdate = 01/01/2010 todate=12/31/2010. When that's finished, do it again, pick up another later date range, then another and another until you get current. c) Then every morning do: export node filedata=all fromtime=now-24 totime=now merge=yes (always use merge=yes). You can even put this in as an admin schedule that keeps your V6 server up to date and in sync, until you can coordinate with the client owner to switch it over to point to the V6 server for backup. This way you don't have to fight scheduling issues, or worry about it for a day when you get distracted by that pesky pager. You just get the 2 servers in sync for that client a bit at a time, then cut it over when convenient. Wanda -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Vandeventer, Harold [BS] Sent: Monday, August 27, 2012 5:13 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Export node to new server Thanks Wanda,... I owe you sumthin! I'll confirm the domains/mgmt classes/retention rules first. Thanks again. ------------------------------------------------ Harold Vandeventer Systems Programmer State of KansasĀ - Office of Information Technology Services harold.vandeven...@ks.gov (785) 296-0631 -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Prather, Wanda Sent: Monday, August 27, 2012 3:58 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Export node to new server >>Do I follow the "virtual volumes" setup process? No, use the "enterprise configuration" form. You won't be creating any virtual volumes. When you export client data, it will land in the appropriate domain/mgmt. class, and get put into the storage hierarchy of the target server. Woe be unto you if you have domains/mgmt. classes with the same names, but different retention rules, when you start the export/import. >>Then, define the node manually on the target; Not necessary, it will get created with the import. Then: >>1: Lock the node. Not really necessary. >>2: EXPORT NODE <nodename> TOSERVER=<target> FILEDATA=BACKUP >>EXPORTIDENTIFIER=<a value> Suggest adding MERGE =YES as standard practice. Wanda [Confidentiality notice:] *********************************************************************** This e-mail message, including attachments, if any, is intended for the person or entity to which it is addressed and may contain confidential or privileged information. Any unauthorized review, use, or disclosure is prohibited. If you are not the intended recipient, please contact the sender and destroy the original message, including all copies, Thank you. ***********************************************************************