Hi, all.
I've got a client with:
OS: Server 2008 Enterprise SP2 x64
TSM version: 6.1 level 0.02
Java version (32 and 64bit versions installed) 6.15
failing to back up system state to my tsm 5.5.3 server.
We're working a PMR, I wanted to see if anyone else was seeing this?
- Allen S. Rout
Update: The sysadmin removed and re-applied SP2, and the problem went
away. We have attempted to duplicate the problem on a spare system, but
have been unable to do so.
While troubleshooting some client problems, we installed hotfixes 934016
and 940349 on Windows 2003 SP2 x86, as described in the
While troubleshooting some client problems, we installed hotfixes 934016
and 940349 on Windows 2003 SP2 x86, as described in the client
requirements page:
http://www-01.ibm.com/support/docview.wss?rs=663context=SSGSG7uid=swg2
1197133loc=en_UScs=utf-8lang=en
The hot fixes that were actually
meddelande-
Från: Larry Clark [mailto:[EMAIL PROTECTED]
Skickat: den 19 oktober 2007 19:30
Till: ADSM-L@VM.MARIST.EDU
Ämne: Re: schedule to exclude system object
so the single tics are to preserve the double quotes?
- Original Message -
From: Andrew Raibeck [EMAIL PROTECTED]
To: ADSM-L
, October 19, 2007 12:57 PM
Subject: Re: schedule to exclude system object
In this case, I don't see any issue with the quotes (or lack thereof).
options=-domain=-systemobject is valid.
My guess is that this occurs on a system that does not support the
SYSTEMOBJECT domain, such as Windows
so the single tics are to preserve the double quotes?
- Original Message -
From: Andrew Raibeck [EMAIL PROTECTED]
To: ADSM-L@VM.MARIST.EDU
Sent: Friday, October 19, 2007 1:22 PM
Subject: Re: [ADSM-L] schedule to exclude system object
No, you'll need quotes around the domain values
-systemservices
Client doesnt like -systemservices
Tim
- Original Message -
From: Andrew Raibeck [EMAIL PROTECTED]
To: ADSM-L@VM.MARIST.EDU
Sent: Friday, October 19, 2007 12:57 PM
Subject: Re: schedule to exclude system object
In this case, I don't see any issue with the quotes (or lack thereof
12:55 PM
Subject: Re: schedule to exclude system object
Have you done a q sched f=d to see how it displays? Does it display with
the
double quotes?
I know I have run into this situation doing a def/update sched on AIX
- Original Message -
From: Tim Brown [EMAIL PROTECTED]
To: ADSM-L
Subject: Re: [ADSM-L] schedule to exclude system object
Have tried various combinations no luck
Tim
- Original Message -
From: Larry Clark [EMAIL PROTECTED]
To: ADSM-L@VM.MARIST.EDU
Sent: Friday, October 19, 2007 11:45 AM
Subject: Re: schedule to exclude system object
looks like you have
You should not use - before Systemstate and Systemservices.
Thanks
Christian
-Ursprungligt meddelande-
Från: Larry Clark [mailto:[EMAIL PROTECTED]
Skickat: den 19 oktober 2007 19:30
Till: ADSM-L@VM.MARIST.EDU
Ämne: Re: schedule to exclude system object
so the single
It is Windows 2003, doesnt have SYSTEMOBJECT
just systemstate and systemservices
Will try with those
Thanks
Tim
- Original Message -
From: Andrew Raibeck [EMAIL PROTECTED]
To: ADSM-L@VM.MARIST.EDU
Sent: Friday, October 19, 2007 12:57 PM
Subject: Re: schedule to exclude system object
into this situation doing a def/update sched on AIX
- Original Message -
From: Tim Brown [EMAIL PROTECTED]
To: ADSM-L@VM.MARIST.EDU
Sent: Friday, October 19, 2007 12:50 PM
Subject: Re: [ADSM-L] schedule to exclude system object
Have tried various combinations no luck
Tim
- Original
of excellence.
Tim Brown [EMAIL PROTECTED]
Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU
10/19/2007 08:33 AM
Please respond to
ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU
To
ADSM-L@VM.MARIST.EDU
cc
Subject
schedule to exclude system object
Created schedule to exclude system object
quote.
should be -domain=sys
- Original Message -
From: Tim Brown [EMAIL PROTECTED]
To: ADSM-L@VM.MARIST.EDU
Sent: Friday, October 19, 2007 11:33 AM
Subject: [ADSM-L] schedule to exclude system object
Created schedule to exclude system object as described in client admin for
windows guide
Created schedule to exclude system object as described in client admin for
windows guide
update schedule nt nt_daily_fs option=-domain=-systemobject
This is exactly how its coded in the manual
However when client schedule runs I get this error
ANS1107E Invalid option/value: '-domain
Have tried various combinations no luck
Tim
- Original Message -
From: Larry Clark [EMAIL PROTECTED]
To: ADSM-L@VM.MARIST.EDU
Sent: Friday, October 19, 2007 11:45 AM
Subject: Re: schedule to exclude system object
looks like you have a problem with the quotes. It is inserted
21:22
To: ADSM-L@VM.MARIST.EDU
Subject: System Object Files
Hiya,
Does anyone out there have an exclude command that will exclude system
state, system services, and system object files when backing up. I'm
looking for a option or two that I can use in a default dsm.opt file and
it won't make
Hiya,
Does anyone out there have an exclude command that will exclude system
state, system services, and system object files when backing up. I'm
looking for a option or two that I can use in a default dsm.opt file and it
won't make a difference which Windows version is being run.
Thanks
Quick question on windows system object filespace. windows client system
objects don't change everyday so how often and what strategy should I have to
back them up. Is it true that it is very expensive transaction for TSM server.
Ashok Vats
916-845-3767
segment from this.
Leigh
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Thomas Denier
Sent: 24 January 2006 21:25
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] System object restore problem
We just went through a disaster recovery test, using
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Thomas Denier
Sent: 24 January 2006 21:25
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] System object restore problem
We just went through a disaster recovery test, using the following
process
for each
: Wednesday, January 25, 2006 4:54 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: System object restore problem
Thomas,
One other thing. You mention that you have actually managed to complete
this method successfully with 5.1.x.x and 5.2.x.x code. Bear in mind
that there were a number of bugs
Seems like this didn't work the last time I tried it - TSM required the
client to be named EXACTLY the same in order to do a system object
restore, including being in the same domain. We created a segregated
network to test these types of restores.
Steve Schaub
Systems Engineer, WNI
BlueCross
matching the production computer name to a node name
matching the replacement system computer name.
3.Execute 'rename filespace' commands to make the corresponding changes to
computer names embedded in UNC volume names.
4.Restore the C drive.
5.Restore the system object.
6.Restore the remaining
]
Sent by: ADSM: Dist Stor Manager
ADSM-L@VM.MARIST.EDU
09/06/2005 09:53 AM
Please respond to
ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU
To
ADSM-L@VM.MARIST.EDU
cc
Subject
Re: [ADSM-L] system object
backup fails
Test with:
C:\Progra~1\Tivoli\TSM\baclient\dsmc
Regards
: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Dksh Cssc
Sent: 19. september 2005 04:44
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] system object backup fails
Hi all,
My problem recurs.
I have tried various ways to backup this machine but it fails every now
and then.
I
Manager ADSM-L@VM.MARIST.EDU
09/02/2005 09:10 PM
Please respond to
ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU
To
ADSM-L@VM.MARIST.EDU
cc
Subject
Re: [ADSM-L] system object backup fails
Hello Callie,
I have no explanation for how the command you have specified works on
other Windows machines
Stor Manager ADSM-L@VM.MARIST.EDU
09/06/2005 09:53 AM
Please respond to
ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU
To
ADSM-L@VM.MARIST.EDU
cc
Subject
Re: [ADSM-L] system object backup fails
Test with:
C:\Progra~1\Tivoli\TSM\baclient\dsmc
Regards
- Original Message -
From
Andrew Raibeck [EMAIL PROTECTED]
Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU
09/02/2005 01:13 AM
Please respond to
ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU
To
ADSM-L@VM.MARIST.EDU
cc
Subject
Re: [ADSM-L] system object backup
.
Andrew Raibeck [EMAIL PROTECTED]
Sent by: ADSM: Dist Stor Manager
ADSM-L@VM.MARIST.EDU
09/01/2005 10:22 AM
Please respond to
ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU
To
ADSM-L@VM.MARIST.EDU
cc
Subject
Re: [ADSM-L] system object
backup fails
Callie, it would help
.
Andrew Raibeck [EMAIL PROTECTED]
Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU
09/01/2005 10:22 AM
Please respond to
ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU
To
ADSM-L@VM.MARIST.EDU
cc
Subject
Re: [ADSM-L] system object backup fails
Callie, it would help to have a little
Dear all,
Anyone encounter problem backing up system objects as I did?
Well,I have a command schedule for XP machine systems object backup :(
dsmc backup systemobject) .However it always fails.
08/29/2005 22:28:27 ANS1909E The scheduled command failed.
08/29/2005 22:28:28 ANS1512E Scheduled
: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On
Behalf Of Dksh Cssc
Sent: Wednesday, August 31, 2005 8:32 PM
To: ADSM-L@VM.MARIST.EDU
Subject: system object backup fails
Dear all,
Anyone encounter problem backing up system objects as I did?
Well,I have a command schedule for XP machine
@VM.MARIST.EDU
cc
Subject
Re: [ADSM-L] system object backup fails
What kind of ID are you running the scheduled backup under?
--
Mark Stapleton ([EMAIL PROTECTED])
IBM Certified Advanced Deployment Professional
Tivoli Storage Management Solutions 2005
IBM Certified Advanced Technical
Callie, it would help to have a little more information about the problem;
in particular, the dsmsched.log and dsmerror.log info that corresponds to
the scheduled event where the system object backup failes.
Mark's question about the ID refers to the NT user account under which the
scheduler
If you include the System Object for Windows 2000 and the
systemstate/systemservices for Windows 2003, will you backup the registry
and SAM of the server? According to the TSM Windows Client documentation
it is recommended that the system32\config directory be excluded, why?
Isn't this where
Yes, the registry and SAM are included in the System Object/System State
backup.
Those files can't be backed up as files, because Windows puts an
exclusive lock on them.
So if you try to include system32/config, you just get errors, anyway.
In fact, for Win2K and Win2K3, if you start the command
Why would you need to restore system object if you used Christie. With Christie
is, like you said, cloned system, so there is no need to restore system object.
Joe Crnjanski
Infinity Network Solutions Inc.
Phone: 416-235-0931 x26
Fax: 416-235-0265
Web: www.infinitynetwork.com
Hello
I've done a cloning of a winnt system to a new system with ITSM and
Christie.
I can restore all files from the C and D drives to the new system, but I
can't reach the System Objects. If I look on the backup of the system
objects on the original system i see objects. But I don't see any
Good Morning.
Is there a way to delete old SYSTEM OBJECT files that are backed up?
What we currently do is, do an incremental backup on the entire machine
including the SYSTEM OBJECT nightly and keep for 90 days. What I'd like to
do is delete some of the old SYSTEM OBJECT files that are old
manual for the syntax:
include systemobject all mgmtclassname
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Jones, Eric J
Sent: Wednesday, January 26, 2005 7:21 AM
To: ADSM-L@VM.MARIST.EDU
Subject: SYSTEM OBJECT question
Good Morning
Hi,
We are running a 5.1.6.2 TSM server and 5.1.6.2 Client. Up to now we have
only backed up NT4 and windows 2000 Clients.
We have just begun deploying Windows 2003 Active Directory and Windows 2003
servers. I am researching the level of support in TSM 5.1.6.2 for Windows
2003.
It would appear
)
LESTAR.IESubject: Windows 2003 client, system
object and TSM server 5.1.x.x
Sent by:
ADSM: Dist
Stor Manager
[EMAIL PROTECTED]
IST.EDU
2004-09-30
10
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On
Behalf Of Doyle, Patrick
We have just begun deploying Windows 2003 Active Directory and
Windows 2003 servers. I am researching the level of support in
TSM 5.1.6.2 for Windows 2003.
It would appear that Windows 2003 IS supported.
a major headache!!! Check
your IBM fixes bulletin!!!
Best Regards
Tony Morgan
FBUK
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Doyle, Patrick
Sent: 30 September 2004 09:39
To: [EMAIL PROTECTED]
Subject: Windows 2003 client, system object and TSM
For now, at the 5.1.5 client level, it might be easier to put the
following in your include/exclude list:
exclude.systemobject frs
This should cause systemobject backups to skip the FRS object, and avoids
the batch file method you mentioned.
Thanks. That worked perfectly, and was a lot
statement allow the piecemeal backups of system objects
to work as expected? Would the TSM server place the files from the
piecemeal backups in a 'SYSTEM OBJECT' filespace? Would this approach
require changes in bare metal restore procedures? Is there a better way
to support operating system recovering
the
piecemeal backups in a 'SYSTEM OBJECT' filespace? Would this approach
require changes in bare metal restore procedures? Is there a better way
to support operating system recovering without a crippling performance
penalty?
We are preparing to migrate to a 5.2.2 TSM server under mainframe Linux
I dunno if that will eliminate all your problems.
But I thought there were known issues with the TSM client not handling the
Win2K3 System Object correctly until you get to 5.2.3.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Thomas Denier
Sent
.
But I thought there were known issues with the TSM client not handling the
Win2K3 System Object correctly until you get to 5.2.3.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Thomas Denier
Sent: Wednesday, September 15, 2004 12:03 PM
To: [EMAIL
One of our Windows clients sent an 18 gigabyte system object backup
last night. Results from 'query occ' commands suggest that it has been
doing this for the last five nights. I ran a 'query content' command
against one of the volumes holding the lastest backup and got a list of
files like
Very strange...
You should open up a problem with IBM support if you have not already done
so.I don't know under what system object component these files are
falling, but you might try running:
dsmc query systeminfo sfp
and examining the resulting dsminfo.txt file to see if these are somehow
Is this a replicated filesystem?
At 11:07 AM 9/14/2004 -0400, you wrote:
One of our Windows clients sent an 18 gigabyte system object backup
last night. Results from 'query occ' commands suggest that it has been
doing this for the last five nights. I ran a 'query content' command
against one
enough is the enemy of excellence.
ADSM: Dist Stor Manager [EMAIL PROTECTED] wrote on 09/14/2004
09:47:00:
Is this a replicated filesystem?
At 11:07 AM 9/14/2004 -0400, you wrote:
One of our Windows clients sent an 18 gigabyte system object backup
last night. Results from 'query occ
FWIW,
5.00 is Win2K
5.01 is WinXP
5.02 is Win2003 server
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Andrew Raibeck
Sent: Tuesday, September 14, 2004 12:35 PM
To: [EMAIL PROTECTED]
Subject: Re: Huge system object
Very strange...
You should
All,
I am seeing unusual behavior on my Windows XP backup, wherein ASR and
SYSTEM OBJECT do not backup by default, either from the command dsmc i or
on the scheduler. There are no domain, include/excludes, just barebones
defaults in my config file:
PASSWORDACCESS GENERATE
TCPPORT 1506
]
Subject: Re: Separating Windows System Object Backup from the File
system Backups
Fantastic! That worked just Great! Makes sense as the TSM Server
Scheduler contacts the TSM Client API which should know what Dir its in...
Dahhh!
Thanks !
-Original Message-
From: ADSM: Dist Stor Manager
We've been having issues with the log being pinned by Win2k Sysobj's The Tivoli tech
support had me create two schedules (One for File system only and one set of Scheds
for Sysobj.) If anyone has any ideas that would be great! We want to do this from
the server side as we have hundreds of
a difference.
Wanda Prather
I/O, I/O, It's all about I/O -(me)
-Original Message-
From: Hart, Charles [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 01, 2004 4:33 PM
To: [EMAIL PROTECTED]
Subject: Separating Windows System Object Backup from the File system
Backups
We've been having
that the who path with spaces causes problem in general.
Best Regards,
Charles
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
Prather, Wanda
Sent: Tuesday, June 01, 2004 4:03 PM
To: [EMAIL PROTECTED]
Subject: Re: Separating Windows System Object
To: [EMAIL PROTECTED]
Subject: Separating Windows System Object Backup from the File system
Backups
We've been having issues with the log being pinned by Win2k Sysobj's The
Tivoli tech support had me create two schedules (One for File system only
and one set of Scheds for Sysobj.) If anyone has any ideas
PROTECTED]
Sent: Tuesday, June 01, 2004 5:11 PM
To: [EMAIL PROTECTED]
Subject: Re: Separating Windows System Object Backup from the File system
Backups
I there's go to be an issue with the C:\Program File\ folder having a space.
When I run the c:\program files\tivoli\tsm\baclient\dsmc backup system
Good point, I can ask'm.
Thanks!
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
Prather, Wanda
Sent: Tuesday, June 01, 2004 4:17 PM
To: [EMAIL PROTECTED]
Subject: Re: Separating Windows System Object Backup from the File
system Backups
It can't
, 2004 4:13 PM
To: [EMAIL PROTECTED]
Subject: Re: Separating Windows System Object Backup from the File
system Backups
We've done similar things in the past (registry backups, event log backups)
without specifying a path at all on the schedule.
Have you tried just dsmc backup systemobject
Hi !
I have a problem with some of my clients.
Lately, some of them are unable to backup the systemobject !
When doing a manual backup, I find out that it is the system files that
cause the application to die.
(It doesn't hang, it just terminates and disappears !)
When running as a Scheduler
Furnes [mailto:[EMAIL PROTECTED]
Verzonden: dinsdag 9 september 2003 17:26
Aan: [EMAIL PROTECTED]
Onderwerp: Win32 baclient dies when backing up system object !?
Hi !
I have a problem with some of my clients.
Lately, some of them are unable to backup the systemobject !
When doing a manual backup, I
-
From: Kjetil Furnes [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 09, 2003 11:26 AM
To: [EMAIL PROTECTED]
Subject: Win32 baclient dies when backing up system object !?
Hi !
I have a problem with some of my clients.
Lately, some of them are unable to backup the systemobject !
When doing
-
From: Kjetil Furnes [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 09, 2003 11:26 AM
To: [EMAIL PROTECTED]
Subject: Win32 baclient dies when backing up system object !?
Hi !
I have a problem with some of my clients.
Lately, some of them are unable to backup the systemobject !
When doing
to ADSM: Dist Stor Manager
To: [EMAIL PROTECTED]
cc:
Subject:Win32 baclient dies when backing up system object
!?
Hi !
I have a problem with some of my clients.
Lately, some of them are unable to backup the systemobject !
When doing a manual backup, I find out
, but there is a problem when I try to backup the system object.
Tthe client 'disappears' (i.e. ends with no message and clears from the
screen)
Messages like the one below are in dsmerror.log:
06/13/2003 08:44:56 File not found
06/13/2003 08:44:56 File not found
06/13/2003 08:45:39 The file is being
Tnx for answers Matt Wanda.
//Henrik
---
The information contained in this message may be CONFIDENTIAL and is
intended for the addressee only. Any unauthorised use, dissemination of the
information or copying of this message is
) terminated connection with client severed.' at almost the
same time the client starts to backup SYSTEM OBJECT.
Any ideas?
//Henrik
---
The information contained in this message may be CONFIDENTIAL and is
intended
to you. I also renamed the System Object at the TSM server for
the node, and then was able to do a fresh backup of the system object.
This was a hassle when I could, whenever possible, just update the client
code. You will just have to remember to go back and get rid of that renamed
system object
fixed it by upgrading
these machines to 5.1.6.0.
-Original Message-
From: Henrik Wahlstedt [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 11, 2003 8:20 AM
To: [EMAIL PROTECTED]
Subject: 4.2.2.0 client crach rc=4, System object?
Hi,
I have a w2k sp3 client with TSM 4.2.2.0. TSM
/ip!
3. (optional) stop all unnecessary netbios-related serverces
4. rename the server to original name. it is now netbios blind and will
not complain :-)
5. perform restore as usual - files, system object and reboot
6. upon restart the system will complain about name conflict and/or
ip-address
]
cc:
Subject:Re: Restore of System Object
Any plans for removing this restriction?
We have a few users that want to clone a production machine to do
testing.
And they want to use TSM to do it. Becuasue of this limitation we use MS
Backup to backup system state to disk
: Restore of System Object
Dist Stor
Manager ADSM-
[EMAIL PROTECTED
I'm trying to restore the System Object of one Win2K server to another
Win2K server. Kind of a disaster recovery test.
TSM Client Version on source machine is 4.2.0, TSM Client Version on
destination machine is 4.2.2. Copied the dsm.opt file from the source
machine to the destination machine
Brad,
TSm will not restore a SYSTEM OBJECT to a different machine.
Now it can be a physically different machine, but it must have the same
hostname, and it must have identical hardware, as you are restoring the
registry, which includes hardware information.
-Original Message-
From
It is not permitted to restore the system object to a machine with a
different name. The computer name of the restore target much match that of
the original machine.
You can find more info in the IBM redbook SG24-6141 Deploying the Tivoli
Storage Manager Client in a Windows 2000 Environment
-alone test network or change
computer specific information.
Thanks,
Tim Rushforth
City of Winnipeg
-Original Message-
From: Andrew Raibeck [mailto:[EMAIL PROTECTED]
Sent: Friday, March 28, 2003 3:07 PM
To: [EMAIL PROTECTED]
Subject: Re: Restore of System Object
It is not permitted
PROTECTED]
EDU cc:
Sent by: ADSM: Dist Stor Subject: Re: Restore of System
Object
Manager
[EMAIL PROTECTED]
03/28/2003 04:05 PM
Please
Environment
TSM Server: AIX 4.3.3 / TSM 4.2.2.10
TSM Client: Windows 2000 Server (5.00.2195) / TSM 5.1.5.9
We have Roaming User Profiles stored in one Windows Server and replicate
this partition to another Windows Server. On both servers we experience
long running backups of System Object
of excellence.
James R Owen [EMAIL PROTECTED]
Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED]
03/14/2003 15:25
Please respond to ADSM: Dist Stor Manager
To: [EMAIL PROTECTED]
cc:
Subject:can a mgmtclass be specified for SYSTEM OBJECT sysfiles?
Andy
Have you tried include.systemobjectALL expiring?
Have in mind IBM/Tivoli call this System Object while Microsoft calls it
System State and it is not a path (that you can access using 'dir
System State' :-)
Zlatko Krastev
IT Consultant
James R Owen [EMAIL PROTECTED]
Sent by: ADSM
Andy,
Is it possible to specify a mgmtclass for SYSTEM OBJECT sysfiles?
We have tested and successfully implemented
exclude.systemobject sysfiles
for 350 Win2K/XP clients [no active/inactive sysfile backups remain
for these clients], but we have an additional 650 Win2k/XP clients
The adsm.sys dir contains a copy of your registry. This is not the same as
the files going into the SYSTEM OBJECT filespace. These files are needed to
maintain a consistent system state. Some info from the help files:
Backing up system objects
Certain Windows NT, 2000, and XP system objects can
OBJECTS are stored.
-Original Message-
From: Fred Johanson [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 25, 2003 11:41 AM
To: [EMAIL PROTECTED]
Subject: Binding SYSTEM OBJECT
About half the machines in our central server domain are small and bound to
a small server management class
About half the machines in our central server domain are small and bound to
a small server management class by an option set. It looks like
0 include ?:* smallserver
1-37 exclude the usual suspects
38 include c:\adsm.sys\...\* smallserver
39 dirmc smallserver.
Sequence #s 0 and 39 do the right
Hart, Charles [EMAIL PROTECTED]
Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED]
31.01.2003 21:02
Please respond to ADSM: Dist Stor Manager
To: [EMAIL PROTECTED]
cc:
Subject:Re: System Object / Mgmt. Classes / Policy Sets / Backup
Groups - -
What's the best
Environment:
TSM Server 5.1.1.6 on AIX 4.3.3 ML10
Client: 5.1.5.9 on Win 2k SP2
I am getting the following error when it tries to backup the system object:
01/30/2003 20:32:24 ANS1228E Sending of object 'C:' failed
01/30/2003 20:32:24 ANS1931E An error saving one or more eventlogs.
Has anybody
01/30/2003 20:32:24 ANS1228E Sending of object 'C:' failed
01/30/2003 20:32:24 ANS1931E An error saving one or more eventlogs.
Has anybody seen this before?
A search of the ADSM-L archives shows prior reports, but no feedback
from the affected users as to resolution, unfortunately.
Perchance,
that if I
go through the GUI and backup each piece of the System Object separately we
die on the system files. All of the other pieces of the system object backup
fine if I do them individually ???
Any one have any thoughts?
Curt Magura
Lockheed Martin EIS
Orlando, Fla.
321-235-1203
-Original
/2003 06:32
Please respond to ADSM: Dist Stor Manager
To: [EMAIL PROTECTED]
cc:
Subject:Re: System Object backup problem
Bruce - Started seeing this on one client about a week ago. Difference is
Server is at 5.1.1.1 client is at 5.1.1.0. Machine was backing up
-
From: Andrew Raibeck [mailto:[EMAIL PROTECTED]]
Sent: Friday, January 31, 2003 8:50 AM
To: [EMAIL PROTECTED]
Subject: Re: System Object backup problem
Get the latest client code (5.1.5.9). There are two crash problems fixed at
the 5.1.5.x level, IC33354 and IC34160. This will most likely address
[mailto:[EMAIL PROTECTED]]
Sent: Friday, January 31, 2003 8:31 AM
To: [EMAIL PROTECTED]
Subject: Re: System Object backup problem
01/30/2003 20:32:24 ANS1228E Sending of object 'C:' failed 01/30/2003
20:32:24 ANS1931E An error saving one or more eventlogs.
Has anybody seen this before?
A search
: System Object backup problem
Get the latest client code (5.1.5.9). There are two crash problems fixed
at the 5.1.5.x level, IC33354 and IC34160. This will most likely address
what you are seeing.
Regards,
Andy
Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes
Hmmm I may have misconstrued Curtis's comments. When he said die on
the sysfiles, I was thinking crash, which is what my response
addressed.
What happens when you try to back up the individual system object
components as Curtis tried? What works, and what fails? Any messages in
dsmerror.log
/2003 07:22
Please respond to ADSM: Dist Stor Manager
To: [EMAIL PROTECTED]
cc:
Subject:Re: System Object backup problem
Thanks Andy. I'm in the process of going through our internal change
control
process to start a client upgrade cycle across the company
This is the error I get when I try to backup only the event logs through the
GUI: 01/31/2003 07:43:59 ANS5205E An error saving one or more eventlogs
I can backup ALL parts of the system object except the event logs!
NO crashes! This is our payroll system
1 - 100 of 194 matches
Mail list logo
