Re: HSM for Windows

Weeks, Debbie wrote: > Yes, and that's exactly the problem as far as I'm concerned. We can > migrate the data to TSM disk, where it will have to stay unless a > migration to tape can be determined by the amount of time the file > has been unused. With the current capabilities we cannot do a smart

Re: Help DELETE VOLHISTORY

Rushforth, Tim wrote: > That sounds similar to a problem we had years ago (APAR IC30429) - have > you tried the "FORCE=YES" option. > I is exactly what I see on one of our servers: tsm: BASKET>q volhist t=dbs Date/TimeVolume TypeBackupBackup Volume Device Clas

Re: Orphaned filespaces

Bill, We too have this problem - the task of identifying 'old' or 'dead' data is made considerably more difficult by the null start and end dates on filespaces. We get round this by querying the latest backup date of any object in each client filespace foreach node from the backups table - as bel

tsm changed DOMAIN statement

TSM users I"m using TSM 5.3 client on an win2000 machine We have 2 backup schedules running on this client. TSM SQL backup sched + a flat file backup. In the flate file backup rather than using "exclude.DIR" to ignore(skip over the SQL data) I have recently updated the DOMAIN statement to po

Re: Orphaned filespaces

Ahh...I hadn't thought of using the backup_date column from the backups table. I'll have to see if I can get away with running a query like this; if so, it'd make my 'cleanup old filespace' processing more thorough. Thanks! Bill Bill Kelly Auburn University OIT 334-844-9917 >>> Ian Smith <[EMAI

TSM backup speed on a Windows server

Hi all I have a little question about backup speed All my servers are force at 100full ... .. I had some issues with a SUN server ... and the solution was to put the SUN server and the switch to AUTO NEGOCIATE ,,, since then the backup is flying ... Is it recommend to set the speed to AUT

Re: TSM backup speed on a Windows server

On Apr 5, 2007, at 10:27 AM, Luc Beaudoin wrote: Is it recommend to set the speed to AUTO-NEGOCIATE on my Windows 2K and 2K3 servers ?? The only recommendation is to use whatever works best. Unfortunately, networking equipment is "all over the place" as to what combination of brands, models,

Re: Orphaned filespaces

On Apr 5, 2007, at 10:21 AM, Bill Kelly wrote: Ahh...I hadn't thought of using the backup_date column from the backups table. I'll have to see if I can get away with running a query like this; if so, it'd make my 'cleanup old filespace' processing more thorough. And then there's ARCHIVE_DATE

having trouble recognized a drive in TSM after being replaced

Hi. Anybody having trouble recognized an IBM LTO2 drive in TSM/IBM 3584-L32/D32after being replaced?? See below for more details. AIX V5.3.5.2 TSM V5.2.7.3 Atape V9.7.5.0 IBM LTO2 drive firmware - 67U1 _ From: Lamb, Charles P. Sent: Thursday,

Re: having trouble recognized a drive in TSM after being replaced

Should not be a problem. However, I have had a case or two. Double that the IBM CE placed this drive back online on the Op Panel after replacing. That is, finished the "Drive Replacement". David Longo >>> "Lamb, Charles P." <[EMAIL PROTECTED]> 4/5/2007 11:56 AM >>> Hi. Anybody having t

Re: having trouble recognized a drive in TSM after being replaced

Charles, Try this. you have to find the actual serial number as just autodetect does not work at times. Upd drive serial=/autodetect. Avy Wong Business Continuity Administrator Mohegan Sun 1 Mohegan Sun Blvd Uncasville, CT 06382 (860) 862-8164 cell (860) 961-6976

Drive error

Hi Could some one please advise me on following errors. 04/05/07 06:11:06 ANR8302E I/O error on drive DRIVE01 (mT1.0.0.4) (OP=READ, Error Number=1117, CC=401, KEY=08, ASC=00, ASCQ=05, SENSE=F0.00.08.00.00.80.00.1E.00.00.00.00.00.05.00.00.00-

Automate UNIX Client Installs

I could have sworn I read about this on here a while ago, but now I can't find any info on it. Search ain't so great anymore... I'm trying to automate the client install, and am stuck on the part where you need to cache the password (with the passwordaccess generate option) Is there a non-intera

Re: Drive error

What kind of drive is this? What was the activity when the error occurred? Have you had this problem with this tape before? Is the error occurring on any tape the drive tries to use? Thanks, Kelly J. Lipp VP Manufacturing & CTO STORServer, Inc. 485-B Elkton Drive Colorado Springs, CO 80907 7

Re: Drive error

Hi Kelly, Thank you for the response. Its LTO3 Drive No activity except a tape was being mounted. (have changed that tape to redo) No problem has been recorded before I made the drive online, it looks fine (It has been half an hour though) Regards, Dinesh Pahari -Original Message-

Re: Drive error

So it's reading/writing correctly now? If so, could be a transient error. One should continue to keep an eye on it. When was the last time the drive was cleaned? Stray quark in the universe. Kelly J. Lipp VP Manufacturing & CTO STORServer, Inc. 485-B Elkton Drive Colorado Springs, CO 80907 7

export node

Hello, I am trying to export the obsolete nodes(filespace and all) so that I can free up some space on tsm server. The problem is I am low on scratch volumes where these nodes reside. Am I correct to think that I better have sufficient scratch volumes available before exporting the obsolete

Re: having trouble recognized a drive in TSM after being replaced

Hi We halted the TSM system and re-started the TSM system. We then could define the library tape drives on the TSM system and define the path on the TSM system for these two TSM replacement LTO2 tape drives. The library tape drive elements must have been hang-up between the IBM 35

Re: export node

Yes - Original Message - From: [EMAIL PROTECTED] <[EMAIL PROTECTED]> To: ADSM-L@VM.MARIST.EDU Sent: Thu Apr 05 12:17:32 2007 Subject: export node Hello, I am trying to export the obsolete nodes(filespace and all) so that I can free up some space on tsm server. The problem is I am

EXPORT order

Is there a specific order that I should export / import? I am trying to merge two TSM 4.2 servers into one by export and import of the policy, and nodes. should I export the nodes, or the policy domain first? Michael Read

Re: EXPORT order

Domains and server information first and then the client data. As another approach consider starting from scratch on your new TSM server rather than sending any data at all from the old servers. You can export/import the server information but then simply have the clients start doing backups to t

Re: EXPORT order

Thanks for your reply Kelly Both these servers are part of our old environment. We have a lot of data that is Freeze-hold / never expire, and are looking at consolidating our older servers, to reduce ongoing maintenance/operating costs. There are no servers actively backing up to these systems.