I did try client autodeployment in the lab and, frankly, found it rather
disappointing - tricky to troubleshoot and no way of automating it from the
command line that we could work out. Didn't experience any random reboots
because we couldn't get the damn thing to work!
/David Mc
Sent from my
Hi David,
what phases of the deployment steps were you trying to automate via the
command line and did not work for you -- Scheduling the deployment ?
Observing the results?
So we can help you with that.
Regards/Pozdravi, Gergana
| | ~\\ ! //~
| | ( ( 'o . o' ) )Imagination can
We are in the process of migrating from a TSM 5.5.4.0 server under
mainframe Linux to a pair of TSM 6.2.2.0 servers, also under mainframe
Linux. Our organization has an application running under SCO Open Server
3.2.5. The SCO system uses TSM 3.1.0.8 client code (the highest client
level that was
I have tried the autodeploy feature and like it. Yes it has been problems,
mostly because IBM failed to keep the ftp-server compatible with the autodeploy
feature (wrong case in a file name and later a corrupt xml-file), but now it
works.
I recommend everyone to try it. It is easy to setup
Has anyone had a Windows 2008 client backup fail with the following error?
ANS1417W Protected system state file is backed up
to the drive file space, not system state file space.
4/05/2011 00:06:19 ANS1417W Protected system state file
'C:\Windows\System32\xmllite.dll' is backed up
to the
Timothy,
This message does not actually cause the backup to fail. However, it does
merit attention. Go to the link in my sig and search on the message number
(ANS1417W) and you will find an important flash about this issue (which was
also posted to the list a couple or so weeks ago).
Best
Thanks Andy,
I will take a look and also find out why the backup is actually failing if this
is not causing it. This is the only message I saw I will check again though.
Best regards
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Andrew
Timothy,
The ANS1417W is a warning message, which would cause the backup to end with
a status of successful and return code 8. This return code means that
TSM was able get through the backup operation, but one or more warning
messages were issued which should be investigated. It can also mean
We purchased an STK SL500 tape library with 4 LTO4 drives in it a few years ago
and we have had nothing but problems with it, almost from the beginning. It is
fully loaded with LTO4 cartridges (about 160) and seems to randomly just crash
and take all of the drives offline to TSM. We also have a
What brand of LTO4 drives are in your STK library?
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Dury,
John C.
Sent: Tuesday, April 05, 2011 6:11 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] nightmares with a STK SL500 tape library
We
I had similar issues with an STK L180 library, and it came down to bad firmware
on the library. Have you checked to make sure you're running the same level on
both libraries? It should be viewable on the front panel.
What are the symptoms when it goes offline? Is the front panel still
I've never working with this library, but have some questions/ideas.
1. Are both libraries identical and do they have same firmware for library
and drives?
How about configuration on the library?
2. They are both connected to same TSM server you say. Do they use the same
HBA's
on the TSM
What have people done regarding Open Systems VTL's?
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Prather, Wanda
Sent: Tuesday, April 05, 2011 7:04 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] nightmares with a STK SL500 tape library
We have two SL3000s (one all LTO4 and one all LTO5) and have had some
issues with the older one, but none with the newer one. After talking
with a Sun (or was it Oracle?) engineer, it appeared that there were
some firmware bugs with the HP LTO4 drives that caused them to be overly
sensitive to
14 matches
Mail list logo
