Hi Christian!
In fact, the user wants to duplicate a production server (SERVER-A), so he
wants SERVER-B to be an exact copy of SERVER-A after the restore. So, we would
like to restore the file level data and all other objects (like the registry
etc.) too.
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
Christian Svensson
Sent: donderdag 25 september 2008 17:07
To: ADSM-L AT VM.MARIST DOT EDU
Subject: SV: Restoring data from another node
Hi Loon,
Can you please explain more what you try to restore.
You can restore another nodes data if you want to. What kind of data do you
want to restore?
Best Regards
Christian Svensson
WW Support: +44-1453-84 7009
U.S. Support: +1-866-832-2267
Cell: +46-70-325 1577
E-mail: Christian.Svensson AT cristie DOT se
Skype: cristie.christian.svensson
________________________________________
Från: ADSM: Dist Stor Manager [ADSM-L AT VM.MARIST DOT EDU] för Loon, EJ
van - SPLXM [Eric-van.Loon AT KLM DOT COM]
Skickat: den 25 september 2008 16:45
Till: ADSM-L AT VM.MARIST DOT EDU
Ämne: 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
**********************************************************************
|
