ADSM-L

Re: Client upgrade to 5.2.3.1

2004-11-04 13:20:57
Subject: Re: Client upgrade to 5.2.3.1
From: Andrew Raibeck <storman AT US.IBM DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 4 Nov 2004 11:19:58 -0700
Bill,

OK, next step is to look at the APAR's suggestion to use SHRSTATIC
serialization.

What serialization do you currently use? Generally SHRSTATIC is what I
would recommend, unless there is compelling reason to use another
serialization technique.

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.ibm DOT com

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.

"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 11/04/2004
09:34:46:

> Andrew,
>
> I have now added EXCLUDE.DIR C:\ADSM.SYS to my DSM.OPT.
> It adsm.sys backup failure is occuring during backup of the system
state.
> This are the last few lines of dsmshed.log :-
>
> 4-11-2004 05:17:15 Normal File-->             4,562
> \\s2321\c$\ADSM.SYS\ASR\asr.sif [Sent]
> 04-11-2004 05:17:15 Normal File-->            13,913
> \\s2321\c$\ADSM.SYS\ASR\asrpnp.sif [Sent]
> 04-11-2004 05:17:15 Normal File-->             1,984
> \\s2321\c$\ADSM.SYS\ASR\tsmasr.cmd [Sent]
> 04-11-2004 05:17:15 Normal File-->             4,354
> \\s2321\c$\ADSM.SYS\ASR\tsmasr.opt [Sent]
> 04-11-2004 05:17:15 Normal File-->            28,752
> \\s2321\c$\ADSM.SYS\ASR\waitforevent.exe [Sent]
> 04-11-2004 05:17:16 Successful incremental backup of 'Automated System
> Recovery'
>
> 04-11-2004 05:17:22 Normal File-->        16,776,968
> \\s2321\c$\WINDOWS\repair\Backup\ServiceState\EventLogs\AppEvent.Evt
> [Sent]
> 04-11-2004 05:17:22 Normal File-->        16,776,888
> \\s2321\c$\WINDOWS\repair\Backup\ServiceState\EventLogs\SecEvent.Evt
> [Sent]
> 04-11-2004 05:17:22 Normal File-->         7,116,784
> \\s2321\c$\WINDOWS\repair\Backup\ServiceState\EventLogs\SysEvent.Evt
> [Sent]
> 04-11-2004 05:17:24 Directory-->                   0
> \\s2321\c$\WINDOWS\system32\wbem\Repository [Sent]
> 04-11-2004 05:17:24 Normal File-->                20
> \\s2321\c$\WINDOWS\system32\wbem\Repository\$WinMgmt.CFG [Sent]
> 04-11-2004 05:17:24 Directory-->                   0
> \\s2321\c$\WINDOWS\system32\wbem\Repository\FS [Sent]
> 04-11-2004 05:17:24 Normal File-->         1,335,296
> \\s2321\c$\WINDOWS\system32\wbem\Repository\FS\INDEX.BTR [Sent]
> 04-11-2004 05:17:24 Normal File-->                 4
> \\s2321\c$\WINDOWS\system32\wbem\Repository\FS\MAPPING.VER [Sent]
> 04-11-2004 05:17:24 Normal File-->             3,816
> \\s2321\c$\WINDOWS\system32\wbem\Repository\FS\MAPPING1.MAP [Sent]
> 04-11-2004 05:17:24 Normal File-->             3,816
> \\s2321\c$\WINDOWS\system32\wbem\Repository\FS\MAPPING2.MAP [Sent]
> 04-11-2004 05:17:24 Normal File-->         6,275,072
> \\s2321\c$\WINDOWS\system32\wbem\Repository\FS\OBJECTS.DATA [Sent]
> 04-11-2004 05:17:25 Directory-->                   0 C:\adsm.sys Changed
> 04-11-2004 05:17:25 ANS1228E Sending of object 'C:\adsm.sys' failed
> 04-11-2004 05:17:25 ANS4037E File 'C:\adsm.sys' changed during
processing.
>  File skipped.
> 04-11-2004 05:17:25 Normal File-->             1,612
> C:\adsm.sys\xml.state\COMPDB.xml [Sent]
> 04-11-2004 05:17:25 Normal File-->             4,638
> C:\adsm.sys\xml.state\REGISTRY.xml [Sent]
> 04-11-2004 05:17:25 Normal File-->           430,984
> C:\adsm.sys\xml.state\SYSFILES.xml [Sent]
> 04-11-2004 05:17:25 Normal File-->             1,724
> C:\adsm.sys\xml.state\tsm.xml [Sent]
> 04-11-2004 05:17:25 Directory-->                   0 C:\adsm.sys [Sent]
> 04-11-2004 05:17:25 Directory-->                   0
C:\adsm.sys\EVENTLOG
> [Sent]
> 04-11-2004 05:17:25 Normal File-->             2,326
> C:\adsm.sys\EVENTLOG\EVENTLOG.xml [Sent]
> 04-11-2004 05:17:25 Normal File-->               828
> C:\adsm.sys\EVENTLOG\EVENTLOG_tsm.xml [Sent]
> 04-11-2004 05:17:25 Directory-->                   0 C:\adsm.sys [Sent]
> 04-11-2004 05:17:25 Directory-->                   0 C:\adsm.sys\WMI
> [Sent]
> 04-11-2004 05:17:25 Normal File-->             1,416
> C:\adsm.sys\WMI\WMI.xml [Sent]
> 04-11-2004 05:17:25 Normal File-->               814
> C:\adsm.sys\WMI\WMI_tsm.xml [Sent]
> 04-11-2004 05:17:26 --- SCHEDULEREC STATUS BEGIN
> 04-11-2004 05:17:26 Total number of objects inspected:   22,376
> 04-11-2004 05:17:26 Total number of objects backed up:        0
> 04-11-2004 05:17:26 Total number of objects updated:          1
> 04-11-2004 05:17:26 Total number of objects rebound:          0
> 04-11-2004 05:17:26 Total number of objects deleted:          0
> 04-11-2004 05:17:26 Total number of objects expired:         51
> 04-11-2004 05:17:26 Total number of objects failed:      22,376
> 04-11-2004 05:17:26 Total number of bytes transferred:     1.56 GB
> 04-11-2004 05:17:26 Data transfer time:                   28.29 sec
> 04-11-2004 05:17:26 Network data transfer rate:        58,077.68 KB/sec
> 04-11-2004 05:17:26 Aggregate data transfer rate:      7,271.08 KB/sec
> 04-11-2004 05:17:26 Objects compressed by:                    0%
> 04-11-2004 05:17:26 Elapsed processing time:           00:03:46
> 04-11-2004 05:17:26 --- SCHEDULEREC STATUS END
> 04-11-2004 05:17:26 --- SCHEDULEREC OBJECT END S2321 04-11-2004 05:00:00
> 04-11-2004 05:17:26 Scheduled event 'S2321' completed successfull
>
>
> Thanks
>
> Bill
>
>
>
>
>
>
>
>
> Andrew Raibeck <storman AT US.IBM DOT COM>
> Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
> 01/11/2004 16:23
> Please respond to "ADSM: Dist Stor Manager"
>
>
>         To:     ADSM-L AT VM.MARIST DOT EDU
>         cc:
>         Subject:        Re: Client upgrade to 5.2.3.1
>
>
> Bill, I recommend trying the EXCLUDE.DIR for adsm.sys first, after which
> the problem might very well go away. I have a sneaking suspicion that
the
> adsm.sys backup failure is occurring during backup of the C: drive, not
> during backup of the system state. The system state backup captures
> adsm.sys automatically, so backup of adsm.sys during C: drive backup is
> redundant and unnecessary.
>
> Without knowing anything about your TSM environment, it's tough for me
to
> say whether you need a new management class with SHRSTATIC, but my
"shoot
> from the hip" response would be to suggest updating the existing
> management class copy groups instead. Serialization is not directly
> selected the client, but indirectly selected through the choice of
> management class in your INCLUDE statements.
>
> For that matter, I'm not even sure how well the "use SHRSTATIC"
> recommendation really applies (I was just summarizing the APAR). What is
> the current serialization that you use? Generally I would recommend
> SHRSTATIC anyway. Also, what is your CHANGINGRETRIES option set to (this
> would be on the client).
>
> Again, though, I'd try just
> before worrying about changing management classes.
>
> 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.ibm DOT com
>
> The only dumb question is the one that goes unasked.
> The command line is your friend.
> "Good enough" is the enemy of excellence.
>
> "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 11/01/2004
> 07:56:50:
>
> > Andrew,
> >
> > Thanks for reply.
> >
> >  Does it mean I need to create a separate Management Class
> >  with SHRSTATIC serialization.) for this one client ?
> > Or is there a option that I can add to the DSM.OPT ?
> >
> > Thank you
> >
> > Bill
> >
> >
> >
> >
> >
> >
> >
> >
> > Andrew Raibeck <storman AT US.IBM DOT COM>
> > Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
> > 29/10/2004 16:17
> > Please respond to "ADSM: Dist Stor Manager"
> >
> >
> >         To:     ADSM-L AT VM.MARIST DOT EDU
> >         cc:
> >         Subject:        Re: Client upgrade to 5.2.3.1
> >
> >
> > Bill,
> >
> > This looks like APAR IC41440 which was introduced in version 5.2.2.9.
A
> > fix is not yet available.
> >
> > I suggest adding
> >
> >    exclude.dir c:\adsm.sys
> >
> > to your options file and restartnig the scheduler.
> >
> > The circumvention documented in the APAR also recommends makeing sure
> you
> > are usint SHRSTATIC serialization.
> >
> > 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.ibm DOT com
> >
> > The only dumb question is the one that goes unasked.
> > The command line is your friend.
> > "Good enough" is the enemy of excellence.
> >
> > "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 10/29/2004
> > 07:42:40:
> >
> > > Mark,
> > >
> > > Thankyou for your reponse.
> > >
> > > QUEIT option not in use.....hundreds of files were backed up...
> > > the log file is too long...nothing unusual appears..
> > >
> > > Extracts:-
> > >
> > > Executing scheduled command now.
> > > 29-10-2004 13:58:33 Node Name: S2321
> > > 29-10-2004 13:58:33 Session established with server TSM1: Windows
> > > 29-10-2004 13:58:33   Server Version 5, Release 2, Level 2.0
> > > 29-10-2004 13:58:33   Server date/time: 29-10-2004 13:59:35  Last
> > access:
> > > 29-10-2004 13:34:17
> > >
> > > 29-10-2004 13:58:33 --- SCHEDULEREC OBJECT BEGIN S2321_ONE_OFF
> > 29-10-2004
> > > 13:35:00
> > > 29-10-2004 13:58:33 Incremental backup of volume '\\s2321\c$'
> > > 29-10-2004 13:58:33 Incremental backup of volume '\\s2321\d$'
> > > 29-10-2004 13:58:33 Incremental backup of volume 'SYSTEMSTATE'
> > > 29-10-2004 13:58:33 Backup System State using shadow copy...
> > > 29-10-2004 13:58:37 Backup System State: 'System Files'.
> > >
> > > 29-10-2004 13:58:37 Backup System State: 'Registry'.
> > >
> > > 29-10-2004 13:58:37 Backup System State: 'COM+ Database'.
> > >
> > > 29-10-2004 13:58:37 Incremental backup of volume 'SYSTEMSERVICES'
> > > 29-10-2004 13:58:37 Backup System Services using shadow copy...
> > > 29-10-2004 13:58:39 Backup System Service: 'WMI Database'.
> > >
> > > 29-10-2004 13:58:39 Backup System Service: 'Event Log'.
> > >
> > > 29-10-2004 13:58:39 ANS1898I ***** Processed     1,000 files *****
> > > 29-10-2004 13:58:39 Directory-->                   0 \\s2321\c$\
> [Sent]
> > > 29-10-2004 13:58:39 Directory-->                   0
> \\s2321\c$\ADSM.SYS
> > > Changed
> > > 29-10-2004 13:58:39 Retry # 1  Directory-->                   0
> > > \\s2321\c$\ [Sent]
> > > 29-10-2004 13:58:39 Directory-->                   0
> > > \\s2321\c$\ADSM.SYS\xml.state [Sent]
> > > 29-10-2004 13:58:39 Directory-->                   0
> > \\s2321\c$\Documents
> > > and Settings\Administrator.DMN [Sent]
> > > 29-10-2004 13:58:39 ANS1228E Sending of object '\\s2321\c$\ADSM.SYS'
> > > failed
> > > 29-10-2004 13:58:40 ANS4037E File '\\s2321\c$\ADSM.SYS' changed
during
> > > processing.  File skipped.
> > > .
> > > .
> > > .
> > > .
> > > .
> > > .
> > >
> > > 29-10-2004 13:59:20 Directory-->                   0 \\s2321\d$\
> [Sent]
> > > 29-10-2004 13:59:20 Directory-->                   0
> > > \\s2321\d$\Registration [Sent]
> > > 29-10-2004 13:59:20 Directory-->                   0
\\s2321\d$\System
> > > Volume Information [Sent]
> > > 29-10-2004 13:59:21 ANS1898I ***** Processed    11,000 files *****
> > > 29-10-2004 13:59:21 Normal File-->               354
> > > \\s2321\d$\Interface\Adverts.txt [Sent]
> > > 29-10-2004 13:59:22 Directory-->                   0
> > > \\s2321\d$\Lotus\Domino\Data [Sent]
> > > 29-10-2004 13:59:23 ANS1898I ***** Processed    11,500 files *****
> > > 29-10-2004 13:59:23 Normal File-->             7,378
> > > \\s2321\d$\Lotus\Domino\notes.ini [Sent]
> > > 29-10-2004 13:59:23 Directory-->                   0
> > > \\s2321\d$\Lotus\Domino\Data\A&L SIP's & SAR's.ft [Sent]
> > > 29-10-2004 13:59:23 Directory-->                   0
> > > \\s2321\d$\Lotus\Domino\Data\gtrhome [Sent]
> > > 29-10-2004 13:59:23 Directory-->                   0
> > > \\s2321\d$\Lotus\Domino\Data\IBM_TECHNICAL_SUPPORT [Sent]
> > > 29-10-2004 13:59:23 Directory-->                   0
> > > \\s2321\d$\Lotus\Domino\Data\LeaverNotify.ft [Sent]
> > > 29-10-2004 13:59:23 Directory-->                   0
> > > \\s2321\d$\Lotus\Domino\Data\log.ft [Sent]
> > > 29-10-2004 13:59:23 Directory-->                   0
> > > \\s2321\d$\Lotus\Domino\Data\mail [Sent]
> > > 29-10-2004 13:59:24 Directory-->                   0
> > > \\s2321\d$\Lotus\Domino\Data\names.ft [Sent]
> > > 29-10-2004 13:59:24 Directory-->                   0
> > > \\s2321\d$\Lotus\Domino\Data\PersonInfo.ft [Sent]
> > > 29-10-2004 13:59:24 Directory-->                   0
> > > \\s2321\d$\Lotus\Domino\Data\PrintRequests.ft [Sent]
> > > 29-10-2004 13:59:24 Directory-->                   0
> > > \\s2321\d$\Lotus\Domino\Data\ShipReqSys.ft [Sent]
> > > 29-10-2004 13:59:24 Normal File-->             2,010
> > > \\s2321\d$\Lotus\Domino\Data\admindata.xml [Sent]
> > > 29-10-2004 13:59:24 Normal File-->               201
> > > \\s2321\d$\Lotus\Domino\Data\diagindex.nbf [Sent]
> > > 29-10-2004 13:59:24 Normal File-->             6,564
> > > \\s2321\d$\Lotus\Domino\Data\fault_recovery.hst [Sent]
> > > 29-10-2004 13:59:24 Normal File-->           713,425
> > > \\s2321\d$\Lotus\Domino\Data\fault_recovery.log [Sent]
> > > 29-10-2004 13:59:24 Normal File-->                26
> > > \\s2321\d$\Lotus\Domino\Data\ini.nbf [Sent]
> > > 29-10-2004 13:59:24 Normal File-->             1,542
> > > \\s2321\d$\Lotus\Domino\Data\JOBSCHED.NJF [Sent]
> > > 29-10-2004 13:59:24 Normal File-->               408
> > > \\s2321\d$\Lotus\Domino\Data\loadmon.ncf [Sent]
> > > 29-10-2004 13:59:24 Normal File-->         2,883,584
> > > \\s2321\d$\Lotus\Domino\Data\Motiva.BAD [Sent]
> > > 29-10-2004 13:59:24 Normal File-->               100
> > > \\s2321\d$\Lotus\Domino\Data\nsd.ini [Sent]
> > > 29-10-2004 13:59:24 Normal File-->             2,680
> > > \\s2321\d$\Lotus\Domino\Data\nsdsysinfo.idx [Sent]
> > > 29-10-2004 13:59:24 Normal File-->               140
> > > \\s2321\d$\Lotus\Domino\Data\pid.nbf [Sent]
> > >
> > > .
> > > .
> > > .
> > > .
> > > .
> > > .
> > > 9-10-2004 14:04:24 Directory-->                   0 C:\adsm.sys
> Changed
> > > 29-10-2004 14:04:24 Directory-->                   0
> > C:\adsm.sys\xml.state
> > > [Sent]
> > > 29-10-2004 14:04:25 ANS1228E Sending of object 'C:\adsm.sys' failed
> > > 29-10-2004 14:04:25 ANS4037E File 'C:\adsm.sys' changed during
> > processing.
> > >  File skipped.
> > > 29-10-2004 14:04:25 Normal File-->             1,612
> > > C:\adsm.sys\xml.state\COMPDB.xml [Sent]
> > > 29-10-2004 14:04:25 Normal File-->             4,638
> > > C:\adsm.sys\xml.state\REGISTRY.xml [Sent]
> > > 29-10-2004 14:04:25 Normal File-->           430,984
> > > C:\adsm.sys\xml.state\SYSFILES.xml [Sent]
> > > 29-10-2004 14:04:25 Normal File-->             1,724
> > > C:\adsm.sys\xml.state\tsm.xml [Sent]
> > > 29-10-2004 14:04:25 Directory-->                   0 C:\adsm.sys
> [Sent]
> > > 29-10-2004 14:04:25 Directory-->                   0 C:\adsm.sys\WMI
> > > [Sent]
> > > 29-10-2004 14:04:25 Normal File-->             1,416
> > > C:\adsm.sys\WMI\WMI.xml [Sent]
> > > 29-10-2004 14:04:25 Normal File-->               814
> > > C:\adsm.sys\WMI\WMI_tsm.xml [Sent]
> > > 29-10-2004 14:04:25 Directory-->                   0 C:\adsm.sys
> [Sent]
> > > 29-10-2004 14:04:25 Directory-->                   0
> > C:\adsm.sys\EVENTLOG
> > > [Sent]
> > > 29-10-2004 14:04:25 Normal File-->             2,326
> > > C:\adsm.sys\EVENTLOG\EVENTLOG.xml [Sent]
> > > 29-10-2004 14:04:25 Normal File-->               828
> > > C:\adsm.sys\EVENTLOG\EVENTLOG_tsm.xml [Sent]
> > > 29-10-2004 14:04:26 --- SCHEDULEREC STATUS BEGIN
> > > 29-10-2004 14:04:26 Total number of objects inspected:   22,734
> > > 29-10-2004 14:04:26 Total number of objects backed up:        0
> > > 29-10-2004 14:04:26 Total number of objects updated:          1
> > > 29-10-2004 14:04:26 Total number of objects rebound:          0
> > > 29-10-2004 14:04:26 Total number of objects deleted:          0
> > > 29-10-2004 14:04:26 Total number of objects expired:         33
> > > 29-10-2004 14:04:26 Total number of objects failed:      22,734
> > > 29-10-2004 14:04:26 Total number of bytes transferred:     1.59 GB
> > > 29-10-2004 14:04:26 Data transfer time:                   19.09 sec
> > > 29-10-2004 14:04:26 Network data transfer rate:        87,603.71
> KB/sec
> > > 29-10-2004 14:04:26 Aggregate data transfer rate:      4,737.23
KB/sec
> > > 29-10-2004 14:04:26 Objects compressed by:                    0%
> > > 29-10-2004 14:04:26 Elapsed processing time:           00:05:53
> > >
> > > Thanks
> > >
> > > Bill
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > "Stapleton, Mark" <mark.stapleton AT BERBEE DOT COM>
> > > Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
> > > 29/10/2004 15:03
> > > Please respond to "ADSM: Dist Stor Manager"
> > >
> > >
> > >         To:     ADSM-L AT VM.MARIST DOT EDU
> > >         cc:
> > >         Subject:        Re: Client upgrade to 5.2.3.1
> > >
> > >
> > > From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On
> > > Behalf Of Bill Dourado
> > > >I have just upgraded a client from 5.2.2.0 to 5.2.3.1 as
> > > >recommended by IBM and this list,  to get over a problem.
> > > [snip]
> > >
> > > What does the rest of the dsmsched.log say? (If you have the QUIET
> > > option in your dsm.opt file, remark it out, and let the scheduled
> backup
> > > run again.)
> > >
> > > --
> > > Mark Stapleton (stapleton AT berbee DOT com)
> > > Berbee Information Networks
> > > Office 262.521.5627

<Prev in Thread] Current Thread [Next in Thread>