Hi Goran,
Yes, you need to do label libvolume on new tapes. You can use volume without
sticky label in TSM, but not without magnetic label on tape. I think that
error you got during labeling is not TSM problem, it seems like drive-tape
comaptibility problem. What is element 261, is it drive? If
right now :-|
- Original Message -
From: Tomás Hrouda [EMAIL PROTECTED]
To: ADSM-L@VM.MARIST.EDU
Sent: Wednesday, September 07, 2005 11:07 AM
Subject: Re: LTO3 tapes problem !
Hi Goran,
Yes, you need to do label libvolume on new tapes. You can use volume
without
sticky label in TSM
I think you only need install License files as part of TSM server
installation package from original base (4.1.0) CD, which are not part of
downloadable server patches and updates. Don't install other server code
from CD, but licenses only. I had never installed HPUX TSM server, but I
think that
Curtis,
yesterday we succesfuly restored DB from STK9310 through manual library
setting as you wrote. It seems like it is only way to use Gresham controled
library in TSM server standalone mode for restore DB.
Many thanks.
Tomas
-Original Message-
From: ADSM: Dist Stor Manager
OK, with percentages, I think it depends on setting of estimate capacity in
deviceclass. I tried to set it as near as possible to real utilization, when
tape goes full, to better gues real tape utilization during filling process.
Some time ago I has 200G estimated and when I re-count percentages
My definitions of drive devices are OK, TSM server was already in production
and I use mtx.x.x.x as usual in W2K.
Tomas
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]
Behalf Of Michael Swinhoe
Sent: Monday, June 09, 2003 4:35 PM
To: [EMAIL PROTECTED]
Of course my library definition in devconfig is EXTERNAL, because we use
Gresham to control library. Could you exactly describe how to set up this
library as manual in devconfig please?
Thanks
Tomas
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]
Behalf Of
That's life, now I saw you are true, but I didn't presume problems like
this, so I didn't check the list. :-))
Tom
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Zlatko Krastev/ACIT
Sent: Friday, January 10, 2003 9:49 AM
To: [EMAIL PROTECTED]
Thanks Daniel,
I'll try to contact him (if any exists :-)). But I have one more question
... is any redbook or documentation about backing up DB2 database with TSM
available? I would like to do some plans and pre-studying steps to
accomplish this workaround.
Thanks
-Original Message-
Many many thanks Davide.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Davide Giacomazzi
Sent: Wednesday, December 11, 2002 2:13 PM
To: [EMAIL PROTECTED]
Subject: R: DB2 backup on AIX
Hi Tom`s, you can find a redbook concerning db2 backup using
Did you try to use group by nodes.contact?
I tried you command (only without section filespace_name like '%\c$' -
it didn't work)
select substr(nodes.contact,1,1) as SERVERTYP,sum (filespaces.capacity),sum
(filespaces.capacity*pct_util/100) from nodes,filespaces where
Hi Markus,
by my opinion you must not make extra schedules for simple clients, because
files are migrated form diskpool per node at the time. If several
migrations occured during backups, I thing your diskpool is too small. It
will be better to increase its size to achieve one migration process
... or maybe some stuffy, frustrated and down in the dumps Legato or
Arcserve administrator :-)))
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
McMullen David E
Sent: Tuesday, July 23, 2002 9:37 PM
To: [EMAIL PROTECTED]
Subject: Re: unsubscribe
I had tryied it now on my test W2K TSM 4.2.0.0 server with filedevice class
DB snapshot ... without success.
delete volhistory type=dbsnapshot tod=06/24/2002 force=yes
0 sequential volume history entries were succesfully deleted
Was FORCE=YES parameter applied only in 4.1.5 version?
(My
I have these files if you want to send it, write you email address ...
it's about 3MB ...
Tom
[EMAIL PROTECTED]
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Jacques Butcher
Sent: Monday, May 13, 2002 6:59 AM
To: [EMAIL PROTECTED]
Subject:
Sorry to all, I was wrong ... Q SEss is right command ... but with different
result in dsmc otherwise to dsmadmc.
Tom
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Tomas Hrouda
Sent: Friday, May 10, 2002 10:28 AM
To: [EMAIL PROTECTED]
Subject:
Gerald,
I mean you cannot generally use all administrative commands (like q sess)
from DSMC client (B-A). There is DSMADMC (administrative) client designed to
do it. You can use restricted set of query commands by DSMC, you can find
them in Using B-A clients manuals. In your case q sess was
Try to increase MESSAGEINTERVAL parameter in you server option file. You
need recycle your TSM server than because off change take effect.
Tom
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Gerald Wichmann
Sent: Monday, May 06, 2002 11:29 PM
To:
Hi Dirk,
I know this commands, but I need more info about database, that I mentioned
here. I built my own excel table with database tables and columns structure,
but that's not enough for me. I'd tried to connect to DB through ODBC and
got a lot of tables with particular data, but some kind of
Many thanks Stefano.
Tom
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
ProtoTipo srl
Sent: Monday, April 22, 2002 3:00 PM
To: [EMAIL PROTECTED]
Subject: Rif: Error on SAP redologs backup
Your log reports the following error:
BR372E File
Hi Jan,
you are completely right. As you mentioned, possible (and I mean correct
too) way is 1. change retention periods to reflect your new policy
requirements, 2. validate policy set, 3. activate policy set, 4. run
expiration on TSM server manually (command EXPIRE INVENTORY) and 5. reclaim
free
Hi Tor,
if problem with memory overflow appears at start of backup, so I think I
know what is your problem ... I have similar one on AIX client which backs
up tons of files through NFS. Try to include parameter MEMORYEFFICIENBACKUP
YES into your dsm.opt file (or check this switch through client
I think your mt2 drive is offline due any reason, this keyword is seen in
your error message (OP=OFFL). See your library operation guide for detailed
error description. Try also Q DR command to ensure that TSM detects your
drive ONLINE.
Hi, TOM
-Original Message-
From: ADSM: Dist Stor
Hi,
I think there is good idea to keep DBbackups on disks (sequential file
device class), when much disk space is available, and copy them to other
machines in case of TSM server disaster. This will save some space in
library for data and lower tape operations. I am using this way for example
in
24 matches
Mail list logo
