ADSM-L

Re: showing another servers filespaces.

2004-08-25 06:52:59
Subject: Re: showing another servers filespaces.
From: "Loon, E.J. van - SPLXM" <Eric-van.Loon AT KLM DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 25 Aug 2004 12:54:03 +0200
Hi Christopher!
Yes you can. Checkout the EXPORT NODE command for details.
If the target node hasn't backed up yet, a rename node (and an additional
rename filespace for Wintel nodes) would do the trick.
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines


-----Original Message-----
From: Christopher Zahorak [mailto:chris AT UWINDSOR DOT CA]
Sent: Wednesday, August 25, 2004 12:07
To: ADSM-L AT VM.MARIST DOT EDU
Subject: showing another servers filespaces.


I was wondering if there was a way to export a particular servers
filespaces/archives and make them available to another server for restoring
if needed.

This would be used where data on a server is moved to another server and
the first server is taken out of service.

Thanks,
Chris.


Christopher S. Zahorak, BCS
Sr. AIX and Tivoli Administrator

University of Windsor
IT Services, Rm 203
401 Sunset Avenue
Windsor, Ontario
N9B 3P4
P: (519)253-3000 ext. 2762
F: (519)973-7083
email: chris AT uwindsor DOT ca


**********************************************************************
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.
**********************************************************************

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