ADSM-L

Re: [ADSM-L] TSM server crash

2009-12-28 07:22:31
Subject: Re: [ADSM-L] TSM server crash
From: Grigori Solonovitch <G.Solonovitch AT BKME DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Mon, 28 Dec 2009 15:20:45 +0300
You can try to put in script commands DEFINE LOGVOLUME and EXTEND LOG for 
formatted log volume and run:

DSMSERV runfile <script>

Good luck!



Grigori G. Solonovitch



Senior Technical Architect



Information Technology  Bank of Kuwait and Middle East  http://www.bkme.com



Phone: (+965) 2231-2274  Mobile: (+965) 99798073  E-Mail: G.Solonovitch AT bkme 
DOT com



Please consider the environment before printing this Email





-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
matrixdot
Sent: Monday, December 28, 2009 3:08 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] TSM server crash



Hi All,



OS: W2K3

TSM Version 5.4



My recolvery log ran full and TSM is down at the moment. I only managed to 
format a new logvol and dbvol using dsmfmt.



This is where i am stuck!!



Thanks in advance..



+----------------------------------------------------------------------

|This was sent by jerome.swartz AT computacenter DOT com via Backup Central.

|Forward SPAM to abuse AT backupcentral DOT com.

+----------------------------------------------------------------------



Please consider the environment before printing this Email.

________________________________
"This email message and any attachments transmitted with it may contain 
confidential and proprietary information, intended only for the named 
recipient(s). If you have received this message in error, or if you are not the 
named recipient(s), please delete this email after notifying the sender 
immediately. BKME cannot guarantee the integrity of this communication and 
accepts no liability for any damage caused by this email or its attachments due 
to viruses, any other defects, interception or unauthorized modification. The 
information, views, opinions and comments of this message are those of the 
individual and not necessarily endorsed by BKME."

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