I have a customer with TSM 4.1 in an NT server.
They are using a 3494 library with 3590 SCSI tapes and have the
IBMatl.4.0.1..0.exe driver installed.
They are now installing additional 3590 tapes fibre channel connected.
Is there any new driver required to be able to use the new tapes? I can not
The way TSM works in its database backups is to use an exclusive tape for
each backup version.
You can not have two backups in the same tape.
For incrementals you could use a FILE device class on disk to save scratch
tapes.
Regards
Maria
- Original Message -
From: PINNI, BALANAND (SBCSI)
You can find the mtlib command in the following book:
IBM SCSI Tape Drive, Medium Changer, and Library Device Drivers:
IBM_scsi_tape_iug.pdf
from ftp://ftp.software.ibm.com/storage/devdrvr/
Regards
Maria
For example, if I have 'Version Data Exists' as 90 and 'Retain Extra
Versions' as 60, would it keep 75th file version if it is older then 60
days?
No. I should be deleted as soon as 60 days have passed.
Version Data Exists = 90 means to keep a maximun of 90 versions, but they
all have to be
I do not understand quite well what you try to accomplish. But anyhow,
cached data on disk only remains until a new backup needs the space. In the
tape you will have all the data from the different versions you are keeping.
So it is normal that you have much more data on tape than on disk.
If you
The most probable mistake is that the node name should be in capital
letters.
You have to write exactly what TSM has in its database.
Do a query nodes to find out
Regards
Maria
- Original Message -
From: Shekhar Dhotre [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, March 01, 2001
Did you also give the command: extend log 162?
This is required after you define a new log file in order for *SM to use it
Maria
- Original Message -
From: Wolfgang Herkenrath [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, February 14, 2001 7:19 AM
Subject: Antw: Re: define
I have done this migration today, every thing worked except the creation of the new
TSM server service in Windows NT V4.
Is there any experience of the service not being created?
I could start the new server with the old database with the dsmserv command, but the
service was not created.
We
Mi advise is not to install a 3494 without the convenience I/O station.
There is no much to to understand about it but you can find information in
the
following redbook:
IBM Magstar Tape Products Family: A Practical Guide , SG24-4632-03
Regards
Maria
- Original Message -
From: Saad
The problem with speed in the admin web interface could be related to your
proxy,
if you have one.
We have a similar problem in a customer, the administrative web interface
was very slow,
and when we removed for the TSM server address to go thought the proxy,
the response time was much much
Address of past questions to the forum in internet: http://www.adsm.org
For anyone else trying to figure out how to search the archives, you can
manually search the log files at Marist with
http://vm.marist.edu/htbin/wlvindex?ADSM-L
It is not easy to find anything in the archived questions
PROTECTED]; 'Maria Paz Gimeno ' [EMAIL PROTECTED]
Sent: Thursday, November 09, 2000 1:37 PM
Subject: RE: BACKUPSET DELETE PROBLEM
By the way, you mentionned impossible to schedule a script -
a small 'astuce' if you want to schedule a script in TSM, just schedule
an administrative command under
I would also like to have a copy.
Send it to [EMAIL PROTECTED]
Thanks
Maria
- Original Message -
From: Tom Melton [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, November 09, 2000 7:50 PM
Subject: Re: find a file in tivoli
I converted the file and have it available in pdf
I use MOVE MEDIA for this operation both ways, out and in the library.
With CHECKOUT you have to provide the volume labels of the tapes you want
to remove from the library, while with "move media" you can select by
stgpool. I am not sure if the "checkout" changes the access to offsite but
"Move
is
looking what backupset will expire, to call the tape back from off-site,
check it in with PRIVATE status and then make the backupset expire. That
way, it is ok but the MAIN condition is to have the tape in the library
before running the expire process.
--
From: Maria Paz Gimeno
These are two selects from previous entries in this forum, the first one is
more specific, the second more simple.
I have not used them, see if they help.
Regards
Maria
select filespace_name,volume_name from volumeusage where node_name='' -
and copy_type='backup' and
I have been reading the new redbook:
SG24-6110-00 Tivoli Storage Manager Version 3.7.3 4.1: Technical Guide
and I am very much worried to read that the lan free backup is only supported for TDP
exchange and SAP r3.
We have installed this tsm 4.1 version in a customer who is using a san
We do a checkin with search=yes because we have an script prepared for that,
this way I do not need to check the volume label, and I can use the same
script every day.
Maria
- Original Message -
From: Lawrence Clark [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, September 29,
In my customer they also move DB backup tape to offsite everyday.
We expire the cartridges for db backup after 7 days.
We have created an script with a query volhistory to know the label of the
cartridge to return to the library.
This is important because once you delete a version from
In previous queries to this forum somebody posted the following answer to
your question.
I have collected them and I am now sending here to you. Hope it helps.
Regards
Maria
Here is the one we use to show us nodes not backed up in two or more days:
/* */
/* macro file to select filespaces that
You need to define the server option EXPINTERVAL to 0
A value of 0 means that expiration must be started with the EXPIRE INVENTORY
command. The default is 24.
otherwise the expiration will start every 24 hours after the server is
initialized.
Regards
Maria
- Original Message -
From:
My system is HP-UX 11.0
TSM server 3.7.3
TSM client 3.7.0
The clients are all of them hp-ux in same or different machine
When performing the incremental backup in one system, no problem with most of them, we
receive the following errors:
PID 1223 killed due to trashed stack
PID 1223 was killed
I have this script defined:
MOVE MEDIA STGPOOL=COPIABACKUP WHERESTATE=EMPTY WHERESTATUS=OFFLINE
CHECKIN LIBVOLUME SILO * SEARCH=YES CHECKLABEL=NO STATUS=SCRATCH
The library is a 3494 and the volumes that the move media will recall are already
inserted in the library, we do first a select
I send this message yesterday, I was told to do an audit on the tape. The audit didn't
detect any error on the tape. I send the error messages again in case someone know of
a known apar o ptf.
I have asked the customer to open an incident with IBM but if you know will be much
faster than IBM
24 matches
Mail list logo
