ADSM-L

Re: [ADSM-L] Restoring data from another node

2008-09-25 11:40:56
Subject: Re: [ADSM-L] Restoring data from another node
From: Howard Coles <Howard.Coles AT ARDENTHEALTH DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 25 Sep 2008 10:39:38 -0500
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
> **********************************************************************

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