ADSM-L

Re: [ADSM-L] TSM EXPORT NODE TO NODE

2015-03-03 11:14:18
Subject: Re: [ADSM-L] TSM EXPORT NODE TO NODE
From: Matthew McGeary <Matthew.McGeary AT POTASHCORP DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Tue, 3 Mar 2015 10:12:19 -0600
Hello Ricky,

You can do an export node with a mergefilespace=yes option, but I've found that to be problematic when replicating application data.  You could rename the node on the source server first, before exporting, then the node will import with a different name and will not have any disruption to the existing data.

Hope that helps
__________________________

Matthew McGeary
Technical Specialist - Operations
PotashCorp
T: (306) 933-8921
www.potashcorp.com





From:        "Plair, Ricky" <rplair AT HEALTHPLAN DOT COM>
To:        ADSM-L AT VM.MARIST DOT EDU
Date:        03/03/2015 09:57 AM
Subject:        [ADSM-L] TSM EXPORT NODE TO NODE
Sent by:        "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>





Good Morning All,

We have exchange data on an old TSM server that we are trying to decommission. What I need to do is,  export the exchange data that still exists on the old TSM server to our new TSM server that was just built approximately 6 months ago. So my question is, can I export the node from the old TSM server to the new TSM server, even though, the new TSM server already has that node name registered.

In other words,  the node exists on both servers, but the domain are different. If I start the export command will it export the data from the old TSM server to the same node which already exists on the new TSM server.

I appreciate the help

Ricky M. Plair
Storage Engineer
HealthPlan Services
Office: 813 289 1000 Ext 2273
Mobile: 757 232 7258


_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
CONFIDENTIALITY NOTICE: This email message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information and/or Protected Health Information (PHI) subject to protection under the law, including the Health Insurance Portability and Accountability Act of 1996, as amended (HIPAA). If you are not the intended recipient or the person responsible for delivering the email to the intended recipient, be advised that you have received this email in error and that any use, disclosure, distribution, forwarding, printing, or copying of this email is strictly prohibited. If you have received this email in error, please notify the sender immediately and destroy all copies of the original message.

<Prev in Thread] Current Thread [Next in Thread>