The following conditions must be met to use TSM to duplicate a windows server:
The source and target nodes cannot be on the same network
The source and target nodes cannot communicate with the AD at the same time
The target must have the same name as the source to begin the restore of the
system.
When we have done this in the past we would connect the target node to an
unused NIC on the server so that we had a private network. Once on a private
network we would rename the node and do the restore. Be sure to not allow the
source node to interact with the TSM server during the restore.
If you are unable to place the target node on a private network then how where
you going to resolve the duplicate name on the network problem after the
restore?
Andy Huebner
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Howard Coles
Sent: Thursday, September 25, 2008 10:40 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Restoring data from another node
Yea, that's why I inserted the " (if you can) " part.
See Ya'
Howard
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
> Of Loon, EJ van - SPLXM
> Sent: Thursday, September 25, 2008 10:20 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: [ADSM-L] Restoring data from another node
>
> Hi Howard!
> This is not an option, because then you would end-up with two Windows
> boxes with the same machine name on the network and, as far as I know,
> that's not allowed within a domain.
> And shutting down or renaming the original server is not an option too
> since it's running a production application.
> Kindest regards,
> Eric van Loon
> KLM Royal Dutch Airlines
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
> Of
> Howard Coles
> Sent: donderdag 25 september 2008 16:57
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: Restoring data from another node
>
> You can't restore systemstate to another node, from my understanding.
>
> The best way to do this (if you can) is to rename the node you want to
> do the restore on to match that of the original box. Then you can
> restore everything, and when you're done you can rename it back. Just
> make sure not to do any backups while using the original node name or
> everything gets fouled up.
>
> See Ya'
> Howard
>
>
> > -----Original Message-----
> > From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On
Behalf
> > Of Loon, EJ van - SPLXM
> > Sent: Thursday, September 25, 2008 9:46 AM
> > To: ADSM-L AT VM.MARIST DOT EDU
> > Subject: [ADSM-L] Restoring data from another node
> >
> > Hi *SM-ers!
> > One of my customers is trying to restore a complete node (lets say
> > NODE-A) to a new node (lets say NODE-B) .
> > We tried both the VIRTUALNODENAME parameter and the "access another
> > nodes data" method, but we are running into the same problem.
> > When we start the BAclient on SERVER-B and select \\SERVER-A\c$ for
a
> > restore to the original location, TSM tries to restore the data to
> > SERVER-A and thus the replace files pop-up appears. Of course we can
> > specify another location for the file level restore (to the c: drive
> of
> > the SERVER-B machine itself), but how about the system state?
> > Could somebody please help us out here?
> > Thank you very much for your reply in advance!
> > Kindest regards,
> > Eric van Loon
> >
> **********************************************************************
> > For information, services and offers, please visit our web site:
> > http://www.klm.com. This e-mail and any attachment may contain
> > confidential and privileged material intended for the addressee
only.
> > If you are not the addressee, you are notified that no part of the
> > e-mail or any attachment may be disclosed, copied or distributed,
and
> > that any other action related to this e-mail or attachment is
> strictly
>
> > prohibited, and may be unlawful. If you have received this e-mail by
> > error, please notify the sender immediately by return e-mail, and
> > delete this message.
> >
> > Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries
and/or
> > its employees shall not be liable for the incorrect or incomplete
> > transmission of this e-mail or any attachments, nor responsible for
> > any delay in receipt.
> > Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal
> > Dutch Airlines) is registered in Amstelveen, The Netherlands, with
> > registered number 33014286
> >
> **********************************************************************
> **********************************************************************
> For information, services and offers, please visit our web site:
> http://www.klm.com. This e-mail and any attachment may contain
> confidential and privileged material intended for the addressee
> only. If you are not the addressee, you are notified that no part
> of the e-mail or any attachment may be disclosed, copied or
> distributed, and that any other action related to this e-mail or
> attachment is strictly prohibited, and may be unlawful. If you have
> received this e-mail by error, please notify the sender immediately
> by return e-mail, and delete this message.
>
> Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries
> and/or its employees shall not be liable for the incorrect or
> incomplete transmission of this e-mail or any attachments, nor
> responsible for any delay in receipt.
> Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal
> Dutch Airlines) is registered in Amstelveen, The Netherlands, with
> registered number 33014286
> **********************************************************************
This e-mail (including any attachments) is confidential and may be legally
privileged. If you are not an intended recipient or an authorized
representative of an intended recipient, you are prohibited from using, copying
or distributing the information in this e-mail or its attachments. If you have
received this e-mail in error, please notify the sender immediately by return
e-mail and delete all copies of this message and any attachments.
Thank you.
|
