FYI:
Hi Mike,
APAR IC34853 has been taken top correct this problem.
It's still open.
I'll monitor it for closure and let you know.
APAR= IC34853 SER= IN INCORROUT
TSM BACKUP OF WIN 2000 ACTIVE DIRECTORY SYSTEM OBJECT CAN REPORT
SUCCESS DESPITE FAILURE DURING BACKUP ATTEMPT.
STAT= OPEN FESN0909258- CTID= SJ0291 ISEV= 2
ERROR DESCRIPTION:
TSM client backup of the Windows 2000 active directory (AD)
system object can report success even though the backup of the
AD never occurs.
.
Recreate steps:
1. On the Win2k Domain Controller, revoke the Administrative
share privilages at the drive level for the drive where the
AD files (ntds.dit, etc) reside.
2. Run a backup of the AD system object using TSM:
dsmc backup activedirectory
3. The following statistics and result reported:
Backup System Object: 'Windows NT Directory Services'.
.
Selective Backup processing of 'Windows NT Directory
Services' finished without failure.
Total number of objects inspected: 1
Total number of objects backed up: 2
Total number of objects updated: 0
Total number of objects rebound: 0
Total number of objects deleted: 0
Total number of objects expired: 0
Total number of objects failed: 0
Total number of bytes transferred: 0 B
Data transfer time: 0.00 sec
Network data transfer rate: 0.00 KB/sec
Aggregate data transfer rate: 0.00 KB/sec
Objects compressed by: 0%
Elapsed processing time: 00:00:04
.
None of the AD system object data is ever sent to the TSM server
but the above messages indicate no failure in this attempt. A
service trace indicates the following error:
fioGetAttrib(\\machinename\c£\WINNT\NTDS\NTDS.DIT): Entry.
fioGetAttrib(\\machinename\c£\WINNT\NTDS\NTDS.DIT) failed.
fioGetAttrib(): FindFirst: Share path name
\\machinename\c£\WINNT\NTDS\NTDS.DIT is no longer exists
TransWin32RC(): Win32 RC 67 from fioGetAttrib():FindFirstFile
TransWin32RC(): Translated Win32 RC 67 to RC 264
.
It is also noted that backup of the drive data succeeds without
failure, even though the Administrative share privilages have
been revoked. There is no clear reason why the AD backup fails
and the regular client file backup succeeds. The particular
point of failure appears to indicate a specific call
FindFirstFile() is used only for AD backups, and not normal file
backups. It is this call that causes the failure, since it
uses the UNC name as shown in the above trace segment.
Initial Impact: Med
LOCAL FIX:
Do not revoke Administrative Share access at the drive level.
*****************************
Best Wishes, Nigel.
Nigel Bentley
IBM Certificated Software Services Specialist
Tivoli Certificated TSM Consultant
IBM UK - ITS Technical Support
EMEA Back Office Support for TSM
---------------------------------------------------------------
e-mail: nigel_bentley AT uk.ibm DOT com
---------------------------------------------------------------
Need help with Tivoli Software?
http://www.ibm.com/software/sysmgmt/products/support/
Log a problem online at:
http://www.ibm.com/software/support/probsub.html
Regards,
Michael Swinhoe
Storage Management Group
Zurich Financial Services
E-mail: mailto:Mike.Swinhoe AT UK.Zurich DOT com
Andrew
Raibeck To: ADSM-L AT VM.MARIST DOT EDU
<[email protected] cc:
BM.COM> Subject: Re: Two Windows backup
questions (repost)
Sent by:
"ADSM: Dist
Stor Manager"
<ADSM-L AT VM DOT MA
RIST.EDU>
09/12/2002
16:34
Please
respond to
"ADSM: Dist
Stor Manager"
Which problem and which APAR are you referring to?
Regards,
Andy
Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.eyebm DOT com (change eye to i to reply)
The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.
Michael Swinhoe <mike.swinhoe AT UK.ZURICH DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
12/09/2002 08:44
Please respond to "ADSM: Dist Stor Manager"
To: ADSM-L AT VM.MARIST DOT EDU
cc:
Subject: Re: Two Windows backup questions (repost)
There is a APAR currently for this problem. However in the mean time we
use NTBackup to backup the System State to a flat file kicked off by a VB
script, which we run as a preschedulecmd in the dsm.opt file.
Regards,
Michael Swinhoe
Storage Management Group
Zurich Financial Services
E-mail: mailto:Mike.Swinhoe AT UK.Zurich DOT com
Andrew
Raibeck To: ADSM-L AT VM.MARIST DOT EDU
<[email protected] cc:
BM.COM> Subject: Re: Two Windows
backup questions (repost)
Sent by:
"ADSM: Dist
Stor Manager"
<ADSM-L AT VM DOT MA
RIST.EDU>
09/12/2002
15:39
Please
respond to
"ADSM: Dist
Stor Manager"
Microsoft does not support the "system state" concept on Windows NT 4.0,
and so TSM can't support it, either. On NT 4.0, it is correct that all you
see is the registry and event log in the "SYSTEM OBJECT" file space. In
sum, Windows NT 4.0 support is as it always has been: TSM backs up regular
files, registry, and event log.
Regards,
Andy
Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.eyebm DOT com (change eye to i to reply)
The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.
"Loon, E.J. van - SPLXM" <Eric-van.Loon AT KLM DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
12/09/2002 08:26
Please respond to "ADSM: Dist Stor Manager"
To: ADSM-L AT VM.MARIST DOT EDU
cc:
Subject: Re: Two Windows backup questions (repost)
Hi Alexander!
Unfortunately that doesn't say that all files are backed up. My Windows NT
machine also has a SYSTEM OBJECT filespace on the TSM server. However, it
only contains the registry files and the event log. The presence of the
SYSTEM OBJECT filespace does not guarantee that it contains all system
object files.
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines
-----Original Message-----
From: Alexander Verkooyen [mailto:alexander AT SARA DOT NL]
Sent: Monday, December 09, 2002 15:14
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Two Windows backup questions (repost)
Hi Eric,
We did some tests on Windows XP (not 2000). When we
did an incremental backup on a system without a
DOMAIN statement in dsm.opt a file space of
the type "SYSTEM OBJECT" would appear on the
TSM server for this node.
So I think one can assume that the system object
is included by default.
Best regards,
Alexander
"Loon, E.J. van - SPLXM" wrote:
>
> Hi Alexander!
> I know the registry files are included by default, but are the system
> objects on Windows 2000?
> Kindest regards,
> Eric van Loon
> KLM Royal Dutch Airlines
>
> -----Original Message-----
> From: Alexander Verkooyen [mailto:alexander AT SARA DOT NL]
> Sent: Monday, December 09, 2002 14:16
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: Two Windows backup questions (repost)
>
> "Loon, E.J. van - SPLXM" wrote:
> >
> > Hi *SM-ers!
> > This is a repost because I did not receive any answer about a week
ago.
> > I have two Windows related questions:
> >
> > 1) When running an incremental, TSM backs up the registry files by
> default.
> > We are soon going to add several Windows 2000 client which use Active
> > Directory. I read in the manual that Active Directory is part of the
> System
> > Objects which can be backed up using the BACKUP SYSTEMOBJECT command.
So,
> if
> > I'm reading things correctly one has to issue both commands ('dsmc i'
and
> > 'dsmc backup systemobject') for a complete backup?
>
> In my experience the system object is included
> in the incremental backup by default
> as long as no DOMAIN is specified in dsm.opt
>
> Regards,
>
> Alexander
> --
> -----------------------------------------------
> Alexander Verkooijen (alexander AT sara DOT nl)
> Senior Systems Programmer
> SARA High Performance Computing
>
> **********************************************************************
> For information, services and offers, please visit our web site:
http://www.klm.com. This e-mail and any attachment may contain confidential
and privileged material intended for the addressee only. If you are not
the
addressee, you are notified that no part of the e-mail or any attachment
may
be disclosed, copied or distributed, and that any other action related to
this e-mail or attachment is strictly prohibited, and may be unlawful. If
you have received this e-mail by error, please notify the sender
immediately
by return e-mail, and delete this message. Koninklijke Luchtvaart
Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be
liable for the incorrect or incomplete transmission of this e-mail or any
attachments, nor responsible for any delay in receipt.
> **********************************************************************
--
-----------------------------------------------
Alexander Verkooijen (alexander AT sara DOT nl)
Senior Systems Programmer
SARA High Performance Computing
___________________________________________________________________________
The information contained in this message is confidential and may be
legally privileged. If you are not the intended recipient, please do not
read, copy or otherwise use it and do not disclose it to anyone else.
Please notify the sender of the delivery error and then delete the
message from your system.
Any views or opinions expressed in this email are those of the author
only.
Communications will be monitored regularly to improve our service and for
security and regulatory purposes.
Thank you for your assistance.
___________________________________________________________________________
|
