Re: Offsite copypool question

2012-01-19 Thread Paul_Dudley
> -Original Message- > From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of > Xav Paice > > - "Paul_Dudley" wrote: > > On the SQL servers I have included the SQL database folder in the > > Exclude-Include configuration of the normal TSM backup setup. (these > > data

Re: Low level tape drives for TSM

2012-01-19 Thread Grigori Solonovitch
Thank you very much for information. You are right, IBM proposed us 3592 libraries as a solution, but we found this proposal too expensive for daily amount less than 1TB. I will check ts1120 as an alternative solution. Maybe it will be more suitable for us. __

Re: LTO4 Tape Volumes with diferent Estimated Capacity

2012-01-19 Thread Rick Adamson
Tiago, Generally speaking hardware compression (tape drive) will always yield better results than software based compression. I would only use the client compression when bandwidth issues come into play, like remote offices with limited WAN bandwidth or a slow congested LAN segment. In these cases

Re: Drive and Path Definition

2012-01-19 Thread Shawn Drew
The only other option to restarting the library manager is removing and redefining all drives, library and paths. This would technically leave the TSM server up and would still reprobe the library. The Audit libr command never worked for me on a scsi library for these updates. Regards, Shawn ___

Re: Drive and Path Definition

2012-01-19 Thread Richard Rhodes
"ADSM: Dist Stor Manager" wrote on 01/19/2012 08:42:26 AM: > > ... > > Our libraries are 3584 scsi libraries, which are different animals from > > 3494 libraries. Sorry, I should have said that. > > > > Any time we have changed the physical library it has required us to bounce > > TSM so the new

Re: EXPORT command help

2012-01-19 Thread Hughes, Timothy
Thanks Rick, I think I will try the merge=yes command (see below) export node Bovsrv3cc filedata=all toserver=tsmcore4 merge=yes Hopefully It will only get the 1 file that is missing. Fyi- the Node on the source server actually hasn't been backing up for awhile but we need to move the data

Re: EXPORT command help

2012-01-19 Thread Rick Adamson
If you want ALL data that is stored by the target node use the option filedata=all, allactive would only export the latest versions of each file the node has in storage. If you want to re-run the export I would add the "merge=yes" option which should only update the data on the target TSM server

Re: Re: Drive and Path Definition

2012-01-19 Thread Howard Coles
I'm with Allen. In 10 years of TSM work with both SCSI and FC Libraries and drives, I've never had to restart TSM on AIX to add drives and paths one by one. I also don't mess with TSM Devices since TSM 4.2 on AIX either. I just run cfgmgr, then define the drives and paths. I have used an Exab

Re: Drive and Path Definition

2012-01-19 Thread Allen S. Rout
On 01/19/2012 01:37 AM, Roger Deschner wrote: Pay attention to the fact that typically rmtN, mtN, and TSM driveN device numbers will be different. Make sure the serial numbers in TSM Q DRIVE F=D are correct. ... This, a whole bunch.I'll drop a few scripts here I use to automate the proces

Re: EXPORT command help

2012-01-19 Thread Hughes, Timothy
Thanks Rick, What happen was this node was exported from one TSM server to another and 1 file apparently did go over but wait can't afford to lose 1 file from this node so I just need to get that 1 file. Will the filedata=allactive command just get that 1 file only? TSMSERVER A BOVSRV3CC Bku

Re: EXPORT command help

2012-01-19 Thread Hughes, Timothy
This is probably why, notice it does say the export was a success however there is a ONE file difference 01/18/12 19:30:03 ANR0673W EXPORT NODE: Data storage retrieve or restore failed - error detected. (SESSION: 782588, PROCESS: 75573) 01/19/12

Re: Re: Drive and Path Definition

2012-01-19 Thread Allen S. Rout
On 01/18/2012 06:28 PM, David Bronder wrote: Richard Rhodes wrote: In the past we've never had to restart TSM to add a new drive. As long as the drive was discovered and available at the AIX layer, we could define the new drive. Has this changed with v6.2.x? Seriously? Is this behavior du

Re: EXPORT command help

2012-01-19 Thread Rick Adamson
You could use "filedata=allactive" which would only export the active (most recent) versions of each file. ~Rick -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Hughes, Timothy Sent: Thursday, January 19, 2012 8:40 AM To: ADSM-L@VM.MARIST.EDU

Re: Drive and Path Definition

2012-01-19 Thread Richard Sims
On Jan 19, 2012, at 8:19 AM, Richard Rhodes wrote: > ... > Our libraries are 3584 scsi libraries, which are different animals from > 3494 libraries. Sorry, I should have said that. > > Any time we have changed the physical library it has required us to bounce > TSM so the new slots EA and/or dri

Re: EXPORT command help

2012-01-19 Thread Hughes, Timothy
I believe I am missing something the command syntax is coming up invalid From: Hughes, Timothy Sent: Thursday, January 19, 2012 8:24 AM To: ADSM-L@VM.MARIST.EDU Subject: EXPORT command help Hi, I am trying to export only Newer files (should be only one) is this command correct? export node Bovs

EXPORT command help

2012-01-19 Thread Hughes, Timothy
Hi, I am trying to export only Newer files (should be only one) is this command correct? export node Bovsrv3cc filedata=all toserver=tsmcore4 -IFNewer Thanks

Re: Drive and Path Definition

2012-01-19 Thread Richard Rhodes
"ADSM: Dist Stor Manager" wrote on 01/18/2012 06:28:41 PM: > > > In the past we've never had to restart TSM to add a new drive. As > > > long as the drive was discovered and available at the AIX layer, we > > > could define the new drive. Has this changed with v6.2.x? > > > > It's my experience

Re: compression

2012-01-19 Thread Lee, Gary
I always use compression at the drive level. No need to have the client doing all that work. However, if you have particularly slow network connections, client compression might be useful. Gary Lee Senior System Programmer Ball State University phone: 765-285-1310 -Original Message-

Re: Low level tape drives for TSM

2012-01-19 Thread Lee, Gary
Sounds like you are looking for something in the 3592 class. We are using ts1120 drives. 300 gB uncompressed, fibrechannel connection 2 gb, tsm 5 and 6 support them, usable in a manual library. Don't know about the AIX questions, but don't know why they wouldn't be supported. Gary Lee Seni

Ang: Low level tape drives for TSM

2012-01-19 Thread Daniel Sparrman
Hi I'm taking it as if you'd like to have standalone tape drive which are connected through your SAN/network environment. Most standalone tape drives I know of use SAS or LVD interfaces. FC is most commonly used in tape libraries since FC is aimed at larger, centralized environments. I dont kn

Low level tape drives for TSM

2012-01-19 Thread Grigori Solonovitch
Hello Everybody, We are using disk pools at Head Office and Disaster Site connected by fiber optics links (DS8100 online mirroring and 1GB Ethernet). We are using SCSI tape drives 3590 only for out-of-country copies with daily amount less than 1TB. We need to replace 3590 drives by something newe

Re: LTO4 Tape Volumes with diferent Estimated Capacity

2012-01-19 Thread Botelho, Tiago (External)
Hello all Thank you for your all answers. Regarding to your experience what is more efficiency regarding to tape usage capacity (increase tape amount of data stored)? Compression on client or compression on Drive(HW)? Cumprimentos / Best regards Tiago Botelho -Original Message- Fro