I hope this will help This is my "internal" manual. 5. On source server under network view-other servers- define server <dest_srv_name> with same admin name and password as on dest. server 6. Verify backup on source server; policy domain; policy set; mgmt classes; backup copy group and schedule and association 7. After backup is finished run EXPORT POLICY <pol_dom_name> toserver=<dest_srv_name> 8. Next step is to export customer's data. Run EXPORT NODE <node_name> filedata=backup toserver=<dest_srv_name> mergefilespaces=no 9. Verify on dest_server; client node info and associated pol. Domain; set;class; and backup group; file space name and content; scheduling and associate node with schedule 10. Reconfigure dsm.opt on client to connect to new (destination) server; only change tcp/ip address
11. Run manual test backup or restore to enter new (same) password and encrypt key; purpose of this step is to create new registry entries for new server. 12. Enable schedule on new server to start; schedule has to disabled until step 11 is performed successfully ; otherwise it will fail without encrypt key. Because we have same password on both servers scheduling service doesn't have to be reconfigured. Joe Crnjanski - Partner Infinity Network Solutions Inc. Phone:416-235-0931 x26 Fax:416-235-0265 Cell:416-937-6335 Web: www.infinitynetwork.com E-mail: [EMAIL PROTECTED] -----Original Message----- From: Aldrich, Jamie [ mailto:[EMAIL PROTECTED] Sent: Wednesday, August 13, 2003 8:36 PM To: [EMAIL PROTECTED] Subject: Moving nodes I know that you can EXPORT NODE, and then IMPORT NODE on the new server. But, if you do not have the POLICY set up, it has errors. Does anyone know the correct procedure for moving a client from one server to another? Jamie Aldrich Verizon
