Re: Adding drives to a TS3500

2010-04-16 Thread Mehdi Salehi
Thanks all

Backupset removal from Volhistory

2010-04-16 Thread Mario Behring
Hi list, I have a backupset entry in VOLHISTORY that I want to delete. The QUERY BACKUPSET command does not show this volume, so I cannot use the DEL BACKUPSET command. How can I remove this particular backupset entry from VOLHISTORY? Mario

Re: Backupset removal from Volhistory

2010-04-16 Thread Bob Levad
DELETE VOLHISTORY type=backupset volume=xx force=yes todate=today -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Mario Behring Sent: Friday, April 16, 2010 10:03 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Backupset removal from Vo

Tcp/ip address not correctly associated to cluster node

2010-04-16 Thread Lee, Gary D.
Microsoft windows 2008, tsm client 6.2 tsmserver 5.5.4. under suse sles9 under zvm 5.3. We have a two node cluster with clustername sqltestcluster. There is one group (win 2008 no longer refers to them as groups) called sqltsmcluster. Cluster nodes are called sqltestcl01 and sqltestcl02. Sqltes

Linux Client failing with ANS1999E error

2010-04-16 Thread James Choate
Has anyone seen this error? I can't figure out whats going on and the messages guide isn't to helpful in resolving this error. Below are the client OS, BA client version, Server version, dsm.sys from the client, error in the dsmsched.log, dsmerror.log and a snippet from the srvr actlog file.

Re: Tcp/ip address not correctly associated to cluster node

2010-04-16 Thread Dwight Cook
If you want to force it to use the cluster ip for the cluster node, set the tcpclientaddress in the dsm.opt file used by the cluster node client acceptor & scheduler... but if those follow the cluster OK, it really shouldn't matter if they use the cluster address or the address of the server curren

Re: Linux Client failing with ANS1999E error

2010-04-16 Thread Richard Sims
Jim - The backup log doesn't match timewise with the other logs, but I'll assume they are from multiple attempts of the same thing. It looks like the /public/proval-old object is bad in some way, and needs examination. If that system hasn't had fsck's in a while, it may be time. I'd code an Exc

Re: Tcp/ip address not correctly associated to cluster node

2010-04-16 Thread Lee, Gary D.
Thanks dwight. Don't know why I didn't see that. Must be time to go home. Think the brain needs a recharge. Gary Lee Senior System Programmer Ball State University phone: 765-285-1310 -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Dwight

Re: Linux Client failing with ANS1999E error

2010-04-16 Thread Len Boyle
I have not seen this error message before. I think that if you remove the following line from the opt file your errors will go away. VIRTUALMOUNTPOINT / len -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of James Choate Sent: Friday, April 16,

Re: Tcp/ip address not correctly associated to cluster node

2010-04-16 Thread Rick Adamson
Am I missing something, If it uses the node that actively owns the cluster instance for the shared resource backups don't you risk duplicating backup data? Since the shared data could actually be stored by each node when they own the instance. At least that has been my experience, I use a separate