I am just a little confused (okay- it's perpertual...)
Wanda & Tim, I only have to worry about RSM problems if the TSM server is NT/2K?
(Isn't RSM a service that runs on the NT/2k platform only?)
With an AIX TSM server at 3.7.4.0, the "only" problems I would have with going
4.1.2.X client code on NT/2K would be the inclexcl problem, the problem with
silent installs not distributing the custom dsm.opt file (apar IC29440),
incorrect return codes for events that actually fail, and compression?
Geesh, after all that, wouldn't it be safer to go 3.7.2.17 client level??
thank
lisa
|--------+------------------------------>
| | "Rushforth, Tim" |
| | <[EMAIL PROTECTED]|
| | PEG.MB.CA> |
| | |
| | 01/30/2001 03:07 PM |
| | Please respond to |
| | "ADSM: Dist Stor |
| | Manager" |
| | |
|--------+------------------------------>
>----------------------------------------------------------------------------|
| |
| To: [EMAIL PROTECTED] |
| cc: (bcc: Lisa Cabanas/SC/MODOT) |
| Subject: Re: Which client version is best for a Win2000-server ? |
>----------------------------------------------------------------------------|
Excellent list Wanda. I will add:
One problem with failed schedules showing up as completed successfully is
fixed in 4.12. Not sure if this is the same one you mention for RSM. We
have experienced this on 3.7 and 4.1 - an example is Server out of Storage
Space, - schedules show as completed successfully. I believe this applies
to all platforms. Try this out, if the schedule shows as completed
successfully you had better be checking the local schedule and error logs.
4.11
- APAR IC27728 - if backing up with compression=yes and compressalways=no,
the backup of system ojbects is not complete. Bypass - use compressalways=no
if using compression.
4.12
- APAR IC29368 - User Abort on Backup (all 4.12 clients)
- Client displays User Abort when error detected instead of displaying
proper error message, it is sometimes easy to determine what the real error
is, somtimes not so easy.
- APAR IC29356 - Different number of system ojbects backed up via web
client than GUI or cmd line, pretty minor but make sure you don't rely on a
backup of the System Objects made with the Web Client.
Just started doing some "Bare Metal Restores" of W2K with 4.12 client, have
experineced Dr. Watson errors when restoring System Objects, appears related
to RSM. Dsmerror log shows - NTRestoreRsmDB(): error importing the RSM
database files. Win32 RC=4312. The backup of the RSM database did run
successfully.
Tim Rushforth
City of Winnipeg
-----Original Message-----
From: Prather, Wanda [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 30, 2001 2:26 PM
To: [EMAIL PROTECTED]
Subject: FW: Which client version is best for a Win2000-server ?
I have been wrestling with this question myself, and it's difficult.
Below is the information I have collected from THIS LIST on the various
client levels for Win2K. You have to be CAREFUL what you are doing
here, as there are problems with all available versions, some with very
ugly consequences.
If anyone else has information to add below, or finds I am mistaken,
PLEASE UPDATE and REPOST it, I think it will help everyone. I would
like very much to hear that I am WRONG about these outstanding problems!
Most of the problems below only affect those who are backing up via the
scheduler.
++++++++++++++
Level 3.7.2.01
- There is a VERY SERIOUS BUG in this level that affects only some
people. On both Win2K server and Win2K PRO, you can get "export of RSM
data base fails" error during scheduled bacukp. At that point the
scheduler stops and no backups are done, but it REPORTS SUCCESS BACK TO
THE SERVER. We had one office with 4 WIn2k PRO machines that went
without backups over a month because of this error. (That office no
longer uses TSM!) YOU CAN"T BE SURE whether you are getting backups of
your Win2K machines or not without checking the scheduler log.
This should be posted as a HIPER problem on the Tivoli web site as it is
a MAJOR INTEGRITY problem to report failed backups as OK. Search the
archives at www.adsm.org for "EXPORT RSM" to see the entries. If you
don't need registry backups, you can avoid the problem by using the
BACKUPREG NO option. One person reported correcting the problem by
setting the RSM service to MANUAL start.
- Our old favorite the Daylight Savings time bug has returned in the
3.7.2.01 client, it takes a full backup when it should not.
+++++++++++++++
Level 3.7.2.17
- This level has the fix for the Daylight Savings Time bug.
+++++++++++++++
Level 4.1.1
- One person has reported the RSM EXPORT error as in the 3.7.2.01 client
above.
- At Level 4.1.1, the scheduler does not give you backups of the system
objects, you must create your own .bat files to back them up with
commands.
- Level 4.1.1 also has the Daylight Savings Time bug.
++++++++++++++++
Level 4.1.1.16
- This level has the fix for the Daylight Savings Time bug.
++++++++++++++++
Level 4.1.2
- This level has only been available since December. No reports so far
of the EXPORT RSM bug. This level also backs up system objects
automatically, except for the two following cases:
- Your server must be at 3.7.4 at least, or the client will not back up
the registry, even though earlier versions of the client did so.
- The 4.1.2 client has changed the structure for registry backups so
that a system32\config subdirectory is created in \adsm.sys to store
part of the registry backup. However, the 4.1.2 client has an EXCLUDE
statement that prevents these files in system32\config from being sent
to the server. Current older TSM clients that will be upgraded in place
also, in MANY INSTALLATIONS, have this EXCLUDE statement that will
prevent registry backups from being saved.
So you must ALTER your include/exclude lists to add:
include *:\adsm.sys\...\* , and you must PREVENT YOUR USERS from
installing the 4.1.2 clients until you have done so. FOR TIVOLI TO
DISTRIBUTE THE CLIENT IN THIS FASHION IS APPALLING, and the person who
thought this is a good idea is a dork. This is something else that
should be reported as a HIPER problem on the Tivoli Web site, as having
someone simply install the 4.1.2 client over an older client will CREATE
AN INTEGRITY PROBLEM that they will never be aware of until they try to
do a restore. THIS PROBLEM AFFECTS WINNT as well as WIN2K. Search
www.adsm.org for "REGISTRY EXCLUDED" to see the entries.
So, pick your poison. And I hope somebody out there can tell me I am
WRONG about many of these problems!
-----Original Message-----
From: Gunnar Uhr
To: [EMAIL PROTECTED]
Sent: 1/22/01 5:41 AM
Subject: Which client version is best for a Win2000-server ?
Hello !
I have seen some time ago that some of You had opinions about some
client-versions on a Win2000-server.
I think it had to do with backing up the registry or some other part of
the "System Objects" and that it didn't function ok.
This far I have only used ADSM 3.1.x on backing up Win2000-server and
ofcorse it's limitations.
(The most nodes I back up is WinNT4.0)
Now I want to change to a TSM-client (4.x ?) and want to make the most
out of it.
Which client version is best for a Win2000-server ?
Is the 4.1.20 allright ?
Do You have any other "tips and hints" and/or configuration features
that is useful on that operation system and would like to share it with
me I would be very grateful.
Thanks in advance
Gunnar
--
****************************************************************
Gunnar Uhr Tel. 08-517 76440
IT-Service
KAROLINSKA SJUKHUSET Fax. 08-314899
171 76 STOCKHOLM e-mail [EMAIL PROTECTED]
