We use the letter K on all of ours without any problem. I would mention
that you be sure to obtain labels that comply with IBM's latest
specification. The upgraded firmware on these libraries makes the
scanning very snesitive. It causes the library not to read some of the
labels. We have to replac
I do not know of any reasonable limitations.
I have some that are all numerical and some that start
with first char alpha and some first and 2nd alpha.
David B. Longo
System Administrator
Health First, Inc.
3300 Fiske Blvd.
Rockledge, FL 32955-4305
PH 321.434.5536
Pager 321.634.8230
Fax:
TnL2 will work.
Look in the 3584 Intro & Planning guide under "Ultrium Bar Code Label"
for specs.
8 chars must be uppercase alphameric, with the last 2 being L2 (for
LTO2).
So you can use any comb. of letters & numbers you want for the 1st 6.
Pretty colors available.
Additional specs in the b
Are there any limitations to the labels that are used with this LTO2
library? In other words, is it ok to use say a letter T and the rest numbers
on the barcodes of LTO2 tapes or is there a special combination that needs
to be on them?
Thanks,
Geoff Gill
TSM Administrator
SAIC M/S-G1b
(858
Hi all..
A few months back we upgraded to TSM 5.2.6 (AIX) and since then we've
noticed some client sessions "hang" from time to time. These stalls do
not appear to be related to a particular client or proccess. We've seen
similar behaviour on both on WINDOWS and AIX clients, on archives
sessions
Thanks, Joe --
Looks like HA and Prole aren't playing well (at least that's the only
area I can think of that they'd run into each other).
Do you run your backups over HA-controlled networks? I've got a
dedicated non-HA network for backups; that might be another area.
Tom Kauffman
NIBCO, Inc
--
Version = all 64 bit versions of TDP for MySAP are not working with HACMP
5.3.0.0.
The log from TDP is listed below. It is not a very descriptive error.
I was told that a fix might be out in Q1 of 2006, but they did not give
any specifics.
Data Protection for mySAP(R)
Hi,
This message simply means that there is insufficient space in other volumes
in the storage pool..
Is there any other reclamation process running for the same storage pool..
the output of "q stgp" pasted above shows "Reclamation Processes: 1"
but "Reclamation
Threshold: 100" ..
Please check if
What version, and not working in what way?
I'm running AIX 5.3, TDP/R3 (Version 5, Release 3, Modification 0 for
AIX LF 64-bit - Build: 257 compiled on Nov 23 2004) with the 64-bit TSM
api version 5.3.0.0 with HACMP 5.2; I was thinking about moving to HACMP
5.3 early next year. Which one (TDP or
On Nov 22, 2005, at 2:02 PM, Dennis Melburn W IT743 wrote:
...In a previous inquery to this, I was told to basically restore the
corrupted volumes. This has apparently worked, as I no longer get
these
errors. My question is, are these tapes permanently damaged, or were
just the files corrupted
Recently I have had to restore about a dozen tapes that had the
following types of errors:
10/20/2005 11:18:55 ANR1330E The server has detected possible
corruption in an
object being restored or moved. The actual
values for the
incorrect fr
_
physical or virtual tapes?
__
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
Warning to all parties using a 64-bit TDP that is thinking of upgrading to
HACMP 5.3 on AIX systems.
I spent a full day with TSM trying to find why our TDP for mySAP (64 bit)
was not working. Only to discover that the two are not compatable at this
time.
Temporary workaround was to install an ol
==> On Tue, 22 Nov 2005 10:00:36 -0500, Dave Zarnoch <[EMAIL PROTECTED]> said:
> I was attempting to start a reclamation of an offsite copy pool
> update stg EAGLENOTESCOPY reclaim=85
> and rec'd the following message:
> 11/22/05 08:09:54 ANR1086E Space reclamation is ended for volume
>
Hi TSM-ers,
I use subfile backup to save our exchange pst-files to a TSM 5.3.2.0
server (client is 5.3.2.0 on Windows 2000).
On day one TSM subfile backup was not successful because the pst-file
was locked by the user. That's fine.
On day two TSM didn't try to backup the pst-file with subfile but
TSM handling of directory backups, either by default behavior
or with the use of the DIRMC option, has often been a source
of confusion for customers. We in TSM development would like
to better understand how and why our customers use DIRMC. To
that end, we are interested in your answers to the que
Follow-up:
Looks like APAR IC47984 (just opened today) could also be a factor.
Regards,
Andy
Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED]
Internet e-mail: [EMAIL PROTECTED]
IBM Tivoli Storage Manager su
Hi Luc,
Luc Beaudoin schrieb:
I all
Did anyone had to migrate a 3583 to a 3584 library
Is there any documentation regarding that or anyone had done it
We've done it last year. If you use the same drives so that you can
reuse your tapes, it's very simple. Just make sure the name of y
Sorry to hear that you are having problems.
Generally, the "unable to communicate with journal service" means that
the session between the backup client and the journal daemon has
ended for some reason.
Note that this isn't really a "crash" as you mention as the process
doesn't terminate with an
Also, did your ADIC engineer configure the i2000 to talk to your Win2K3
host?
The one time I worked with the i2000, I recall that it has a sort of
reverse LUN masking that the ADIC folks have to set up.
Otherwise the box won't talk to the host.
-Original Message-
From: ADSM: Dist Stor Ma
Did you load the correct device drivers? For non-IBM libraries you must load
the TSM Device Driver for those medium changers and
drives.
Bill Boyer
"Some days you're the bug, some days you're the windshield" - ??
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]
NB: This email and its contents are subject to our email legal notice
which can be viewed at http://www.sars.gov.za/Email_Disclaimer.pdf
Hi,
Corrections to earlier post.Still experiencing same problem.
Problem comes when we define the library within TSM, "define path
servername LTOLIB
You've probably hit the MAXSCRATCH for the storage pool. Increase that value.
UPD STG EAGLENOTESCOPY MAXSCRATCH=
Bill Boyer
"Some days you're the bug, some days you're the windshield" - ??
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Dave
Zarn
Since the LTO3's can read the LTO1's and the 3584 library can handle mixed
media, I would mark my LTO1 tapes as READONLY, put in
lots of LTO3 tapes for scratch and let all the new data go to the LTO3 tapes
and the data on the LTO1's just let expire off. Your
reclamation tasks will take over and r
Thanks Bill
My 3583 is a LTO1 and my new 3584 is LTO3 ...
after putting all my LTO1 tapes in the 3584 .. should I starts some move
data from the LTO1 to the LTO3 tapes ?
Thanks again
Luc Beaudoin
Administrateur Réseau / Network Administrator
Hopital General Juif S.M.B.D.
Tel: (514) 340-8222 ex
I was attempting to start a reclamation of an offsite copy pool
update stg EAGLENOTESCOPY reclaim=85
and rec'd the following message:
11/22/05 08:09:54 ANR1086E Space reclamation is ended for volume
308250.
There is insufficient space in storage pool.
(PROCESS:
Hi
We use z/OS 1.6 Unix (OMVS) and the TSM client version 5.3. We tried to
create an include/exclude list where we specifically want to include
certain directories. All other directories should be excluded.
The content of the root directory:
Type Filename
_ Dir .
_ Dir ..
They are both LTO libraries, right. Unless you're moving up to 3592 drives in
the 3584?
First define a temporary MANUAL library and point your devclass(es) to it.
Def libr temp1 libt=manual
Upd devc libr=temp1
Now delete all your drives/paths library/path for the 3583 in TSM.
Attach the 3584
I all
Did anyone had to migrate a 3583 to a 3584 library
Is there any documentation regarding that or anyone had done it
thanks
Luc Beaudoin
Administrateur Réseau / Network Administrator
Hopital General Juif S.M.B.D.
Tel: (514) 340-8222 ext:8254
Christoph,
I would upgrade first the existing server.
The TSM database on the new server will contain only the server definitions
after the export/import of the server. The metadata of what backups are written
on the tapes must be done by a full export / import of the nodes too.
best regard
Allen S. Rout schrieb:
> ==> On Mon, 21 Nov 2005 11:47:20 +0100, Christoph Martin <[EMAIL PROTECTED]>
> said:
>
>>We currently have out TSM server version 4.2.4 running on a PowerPC with AIX
>>4.3.3. We now want to migrate to new hardware using version 5.3 on a
>>(Debian) Linux server.
>
>>Are the
Hello
I think that Richard Sims is right I have almost the same configuration
here the script I run to define my path for library and drives:
tsm: ADSM>q script adici2000 f=r
UPDATE PATH ADSM I2000LIB SRCTYPE=SERVER DESTTYPE=LIBRARY DEVICE=/dev/lb1
AUTODETECT=YES
UPDATE PATH ADSM I2000DRV1
On Nov 22, 2005, at 1:21 AM, Reuben Pillay wrote:
...
Problem comes when we define the library within TSM, "define drive
servername LTOLIB3 ... device=lbx.x.x.x. online=yes" get error I/O
error accessing library LTOLIB3 RC=15 ...
I should think so. You are attempting to utilize pre-Version5 c
Hello, TSMers !
An admin has just done a hard restart from my tsm server - while
reclamation processes and library where active...sh..happens.
System is up without problems now, and i checked the servers actlog, db and
log; can i realy be happy - i have found no errors !?
Is their anything else i
34 matches
Mail list logo