ADSM-L

[ADSM-L] Problem with NFS mounted FILE storage pool

2010-10-27 04:02:35
Subject: [ADSM-L] Problem with NFS mounted FILE storage pool
From: Grigori Solonovitch <Grigori.Solonovitch AT AHLIUNITED DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 27 Oct 2010 10:59:24 +0300
I have FILE copy storage pool for NFS-mounted file system from Disaster Site 
via 1Gb Ethernet.
Everything is working fine, but I faced problem during Disaster Site testing, 
when NFS file system is unavailable.
TSM Server is hanging after disconnection of Ethernet network due to problems 
with NFS in spite of fact that remote copy pool is not used.
I have found workaround:
- stop TSM server before Disaster Site activation;
- unmount NFS file system;
- start TSM server;
- stop TSM Server after completion Disaster Site testing;
- mount NFS file system;
- start TSM Server.
This workaround is very painful.
Maybe somebody can propose some better solution?
Thank you very much in advance.


Grigori G. Solonovitch

Senior Technical Architect

Information Technology  Ahli United Bank Kuwait http://www.ahliunited.com.kw

Phone: (+965) 2231-2274  Mobile: (+965) 99798073  E-Mail: Grigori.Solonovitch 
AT ahliunited DOT com<mailto:Grigori.Solonovitch AT ahliunited DOT com>

Please consider the environment before printing this Email


________________________________
CONFIDENTIALITY AND WAIVER: The information contained in this electronic mail 
message and any attachments hereto may be legally privileged and confidential. 
The information is intended only for the recipient(s) named in this message. If 
you are not the intended recipient you are notified that any use, disclosure, 
copying or distribution is prohibited. If you have received this in error 
please contact the sender and delete this message and any attachments from your 
computer system. We do not guarantee that this message or any attachment to it 
is secure or free from errors, computer viruses or other conditions that may 
damage or interfere with data, hardware or software.

Please consider the environment before printing this Email.

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