Re: continuous restore from multiple cartridges

On Apr 6, 2010, at 2:34 AM, Mehdi Salehi wrote: > Hi all, > A client is to restore something from multiple cartridges (regardless of > being collocated or not). Server mounts the first cartridge and the > restoration process starts . Does TSM server prepare (mount) the next > cartridge before it i

Re: continuous restore from multiple cartridges

>> On Tue, 6 Apr 2010 07:14:52 -0400, Richard Sims said: > On Apr 6, 2010, at 2:34 AM, Mehdi Salehi wrote: >> A client is to restore something from multiple cartridges >> (regardless of being collocated or not). Server mounts the first >> cartridge and the restoration process starts . Does TSM

Archive completed but not big enough.

Hello all, We did a Archive and it only Archived 18.15GB it should have Archived 76.6 GB, I am going to delete the Archive and try again. Question - By deleting the filespace via command line or GUI that should get rid of the data that was archived correct? Thanks 99 DELETE FILESPACE Dele

Re: Archive completed but not big enough.

Yes. On 06/04, Timothy Hughes wrote: > Hello all, > > We did a Archive and it only Archived 18.15GB it should have Archived > 76.6 GB, I am going to delete the Archive and try again. > > Question - By deleting the filespace via command line or GUI that should > get rid of the data that was archive

Re: Archive completed but not big enough.

Am I correct in that below it looks like you've performed a `DEL FILESPACE ADOCGWC_10-16-09 *`? This will remove *all* of the data that you've either backed-up or archived belonging to this node. /DMc London, UK -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu

Re: Archive completed but not big enough.

You can get finer-grain control by doing a "UPDATE NODE ARCHDEL=YES" on the server side and then using "DELETE ARCHIVE" on the client. On 04/06/10 06:39, Timothy Hughes wrote: Hello all, We did a Archive and it only Archived 18.15GB it should have Archived 76.6 GB, I am going to delete the Arc

Re: Archive completed but not big enough.

The product provides the 'dsmc delete archive' command to dispose of a single Archive object.

Re: Archive completed but not big enough.

Hi km, Thanks the first try didn't seem to get rid of everything had to redo it and all data has been delete Tim km wrote: Yes. On 06/04, Timothy Hughes wrote: Hello all, We did a Archive and it only Archived 18.15GB it should have Archived 76.6 GB, I am going to delete the Archive and

Re: Archive completed but not big enough.

Thanks Skylar for the command. Thanks again Richard, David and Km for your responses! I'm Still learning about this archive part of TSM. Tim Skylar Thompson wrote: You can get finer-grain control by doing a "UPDATE NODE ARCHDEL=YES" on the server side and then using "DELETE ARCHIVE" on t

Re: Archive completed but not big enough.

F.Y.I - We are re-doing the archive again I will let you know how it goes. Timothy Hughes wrote: Thanks Skylar for the command. Thanks again Richard, David and Km for your responses! I'm Still learning about this archive part of TSM. Tim Skylar Thompson wrote: You can get finer-grain c

Re: Archive completed but not big enough.

Hi David, Thanks for your rely, This node along with others we are creating are just being used to hold "Archived data only" they are not being backed up. No backup data involved. Tim David McClelland wrote: Am I correct in that below it looks like you've performed a `DEL FILESPACE ADOCGWC_1

Sql query help

Tsm server 5.5.4 running on suse 9 linux under zvm 5.3. Trying to create a query which will give me the count of volumes in a storage pool, and its maxscratch setting on a single line. Nice to watch for filling pools which need a larger maxscratch value. Query follows: --- select a

Failed to backup DB on Linux TSM 6.2

Hi All, For some reason I'm unable to backup my TSM DB on Linux (TSM Server 6.2.0.0, TSM Client 6.2.0.0). I get the infamous message: ANR2968E Database backup terminated. DB2 sqlcode: -2033. DB2 sqlerrmc: 106. ANR0985I Process 1 for DATABASE BACKUP running in the BACKGROUND completed with

Re: Sql query help

There is a field in the stgpools table that shows how many tapes are used, so I don't think you need a join. select MAXSCRATCH, NUMSCRATCHUSED from stgpools The way I monitor maxscratch is with this: select STGPOOL_NAME, MAXSCRATCH, NUMSCRATCHUSED from stgpools where MAXSCRATCH is not null and

SV: Failed to backup DB on Linux TSM 6.2

What does DB2Diag.log tell you? Best Regards Christian Svensson Cell: +46-70-325 1577 E-mail: christian.svens...@cristie.se Skype: cristie.christian.svensson Supported Platform for CPU2TSM:: http://www.cristie.se/cpu2tsm-supported-platforms Från: Richard

Re: Archive completed but not big enough.

Tim, Was there an error to indicate why the archive failed? Or did it seem to complete successfully? If so, is it possible that you have compression turned on at the client, through the client setting, or the client options? If so, it is not too surprising that a 76GB file could compress down

Re: Sql query help

Thanks Shawn. That did it. Don't know how I missed that field. 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 Shawn Drew Sent: Tuesday, April 06, 2010 3:18 PM T

Re: Archive completed but not big enough.

It probably doesn't help you in this case, but DELETE FILESPACE has a TYPE=ARCHIVE argument you can give it, so it will only remove archive data. On 04/06/10 10:29, Timothy Hughes wrote: Hi David, Thanks for your rely, This node along with others we are creating are just being used to hold "Ar

Changing DNS name of node - made server mad

We discovered that a new client node was getting an incorrect DNS name resolution, from the TSM server, due to someone reassigning the IP but not removing the DNS entry and the TSM server doing reverse-lookups. So we removed the DNS entry, thus making the TSM server mad (see errors below). It spe

SV: Changing DNS name of node - made server mad

Hi, Take a look in dsm.sys / dsm.opt and see if you are using TCPClientAddress. Best Regards Christian Svensson Cell: +46-70-325 1577 E-mail: christian.svens...@cristie.se Skype: cristie.christian.svensson Supported Platform for CPU2TSM:: http://www.cristie.se/cpu2tsm-supported-platforms __

Re: Archive completed but not big enough.

Skylar Thanks, that command is good to know, I may need to use it sometime. I appreciate it. Thanks Skylar Thompson wrote: It probably doesn't help you in this case, but DELETE FILESPACE has a TYPE=ARCHIVE argument you can give it, so it will only remove archive data. On 04/06/10 10:29, Timo

Re: Archive completed but not big enough.

Hi John, Thanks for your reply Yes, checking through the server log we found this error ANR0530W Transaction failed for session 175494 for node ADOCGWC_10-16-09 (NetWare) - internal server error detected. ANR0530W Transaction failed for session 175490 for node ADOCGWC_10-16-09 (NetWare) - inter

Backupset/Export pain

Hi All I have a customer that thinks he wants a monthly backup kept forever: cites legislative requirements and will not be disuaded. Current implementation is to use a series of backupsets. The issue with this is that the backupset generation can only be started when a drive is available - it