Cindy,
Use the Verbose in your DSM.OPT instead of QUIET. Then find out from your
dsmsched.log what's the last file is backed up before it's failed. I had
the similar situation caused by two corrupt files.
Regards,
Jack
CCannam AT genam DOT com on 12/09/98 10:55:58 AM
Please respond to ADSM-L AT vm.marist DOT edu
To: ADSM-L AT vm.marist DOT edu
cc:
Subject: Re: surprise on nt client
OK --- I updated the client code with the latest and greatest yesterday
afternoon as was suggested. The problem didn't go away. Here are the log
results:
SCHEDLOG:
12/08/1998 17:42:26 --- SCHEDULEREC QUERY BEGIN
12/08/1998 17:42:26 --- SCHEDULEREC QUERY END
12/08/1998 17:42:26 Next operation scheduled:
12/08/1998 17:42:26 -------------------------------------------------------
-----
12/08/1998 17:42:26 Schedule Name: CORP_NT_INCR_DAILY
12/08/1998 17:42:26 Schedule Name: CORP_NT_INCR_DAILY
12/08/1998 17:42:26 Action: Incremental
12/08/1998 17:42:26 Objects:
12/08/1998 17:42:26 Options:
12/08/1998 17:42:26 Server Window Start: 04:00:00 on 12/09/1998
12/08/1998 17:42:26 -------------------------------------------------------
-----
12/08/1998 17:42:26 Schedule will be refreshed in 4 hours.
12/08/1998 17:42:26 Schedule will be refreshed in 4 hours.
12/08/1998 21:42:26 Querying server for next scheduled event.
12/08/1998 21:42:26 Node Name: CRPNTTI1
12/08/1998 21:42:27 Session established with server ADSM: MVS
12/08/1998 21:42:27 Server Version 2, Release 1, Level 0.13
12/08/1998 21:42:27 Data compression forced off by the server
12/08/1998 21:42:27 Server date/time: 12/08/1998 21:40:35
Last access: 12/08/1998 17:40:35
12/08/1998 21:42:27 --- SCHEDULEREC QUERY BEGIN
12/08/1998 21:42:27 --- SCHEDULEREC QUERY END
12/08/1998 21:42:27 Next operation scheduled:
12/08/1998 21:42:27 -------------------------------------------------------
-----
12/08/1998 21:42:27 Schedule Name: CORP_NT_INCR_DAILY
12/08/1998 21:42:27 Schedule Name: CORP_NT_INCR_DAILY
12/08/1998 21:42:27 Action: Incremental
12/08/1998 21:42:27 Objects:
12/08/1998 21:42:27 Options:
12/08/1998 21:42:27 Server Window Start: 04:00:00 on 12/09/1998
12/08/1998 21:42:27 -------------------------------------------------------
-----
12/08/1998 21:42:27 Schedule will be refreshed in 4 hours.
12/08/1998 21:42:27 Schedule will be refreshed in 4 hours.
12/09/1998 01:42:27 Querying server for next scheduled event.
12/09/1998 01:42:27 Node Name: CRPNTTI1
12/09/1998 01:42:27 Session established with server ADSM: MVS
12/09/1998 01:42:27 Server Version 2, Release 1, Level 0.13
12/09/1998 01:42:27 Data compression forced off by the server
12/09/1998 01:42:27 Server date/time: 12/09/1998 01:40:35
Last access: 12/08/1998 21:40:35
12/09/1998 01:42:27 --- SCHEDULEREC QUERY BEGIN
12/09/1998 01:42:27 --- SCHEDULEREC QUERY END
12/09/1998 01:42:27 Next operation scheduled:
12/09/1998 01:42:27 -------------------------------------------------------
-----
12/09/1998 01:42:27 Schedule Name: CORP_NT_INCR_DAILY
12/09/1998 01:42:27 Schedule Name: CORP_NT_INCR_DAILY
12/09/1998 01:42:27 Action: Incremental
12/09/1998 01:42:27 Objects:
12/09/1998 01:42:27 Options:
12/09/1998 01:42:27 Server Window Start: 04:00:00 on 12/09/1998
12/09/1998 01:42:27 -------------------------------------------------------
-----
12/09/1998 01:42:27 Command will be executed in 2 hours and 26 minutes.
12/09/1998 01:42:27 Command will be executed in 2 hours and 26 minutes.
12/09/1998 04:08:27
Executing scheduled command now.
12/09/1998 04:08:27 Node Name: CRPNTTI1
12/09/1998 04:08:28 Session established with server ADSM: MVS
12/09/1998 04:08:28 Server Version 2, Release 1, Level 0.13
12/09/1998 04:08:28 Data compression forced off by the server
12/09/1998 04:08:28 Server date/time: 12/09/1998 04:06:36
Last access: 12/09/1998 01:40:35
12/09/1998 04:08:28 --- SCHEDULEREC OBJECT BEGIN CORP_NT_INCR_DAILY
12/09/1998 04:00:00
12/09/1998 04:08:28 Saving registry keys.
12/09/1998 04:08:30 Registry keys saved.
(That's where it appears to simply stop, reporting no more about the backup
than what it prints here.)
There are no entries applicable to the stop in either the DSMERROR.LOG or
the DSIERROR.LOG files.
HOWEVER --- when viewing the same client's filespaces, here's what appears
there: (it's as though the SCHEDLOG
isn't getting the word that the incremental has completed, but the server
is)....
---------------------------------------------------------------------------
---------------------------------------------------------------------------
---------------------------------------------------------------------------
----------------------------
----------------------------
\\crpntti1\c$ CRPNTTI1 WinNT NTFS 2039.5 39.9
\\crpntti1\c$ CRPNTTI1 WinNT NTFS 2039.5 39.9
12/09/1998 04:06:37 <1 12/09/1998 04:08:27 <1
\\crpntti1\d$ CRPNTTI1 WinNT NTFS 6636.2 48.7
12/09/1998 04:08:28 <1 12/09/1998 06:26:55 <1
\\crpntti1\e$ CRPNTTI1 WinNT NTFS 8675.7 0.1
12/09/1998 06:26:55 <1 12/09/1998 06:26:56 <1
\\crpntti1\f$ CRPNTTI1 WinNT NTFS 2039.5 0.2
12/09/1998 06:26:56 <1 12/09/1998 06:26:57 <1
\\crpntti1\g$ CRPNTTI1 WinNT NTFS 6636.2 0.2
12/09/1998 06:26:57 <1 12/09/1998 06:27:16 <1
DSM.OPT file is as follows:
*********************************************************
* IBM Adstar Distributed Storage Manager
* ADSM V3Rx BA Client
* DSM.OPT for 32-Bit Windows Client (Windows NT 4.0)
* *******************************************************
COMMmethod TCPip
COMPRESSION NO
DOMain ALL-LOCAL
*********************************************************
Exclude "?:\...\SYSTEM32\CONFIG\*.*"
Exclude "?:\...\SYSTEM32\CONFIG\...\*"
Exclude "?:\temp\*.*"
Exclude "?:\fullshot\*.bmp"
Exclude "?:\*.tst"
Exclude "?:\*.test"
Exclude "?:\...\tst.*"
Exclude "?:\...\test.*"
Exclude "?:\...\*.swp"
Exclude "?:\...\win386.swp"
Exclude "?:\IBMBIO.COM"
Exclude "?:\IBMDOS.COM"
Exclude "?:\MSDOS.SYS"
Exclude "?:\MSBIO.COM"
Exclude "?:\...\386spart.par"
Exclude "?:\...\*.par"
Exclude "?:\...\dblspace.*"
Exclude "?:\...\ntuser.dat.LOG"
Exclude "?:\...\NTUSER.DAT"
Exclude "?:\pagefile.sys"
Exclude "?:\page*.sys"
Exclude "?:\recover*\*.*"
Exclude "?:\ntsmf*\*.*"
Exclude "?:\restores\*"
Exclude "?:\...\ntsmf*\*.*"
Exclude "?:\...\program file\plus!\microsoft\internet\cache\*.*"
************************************************************************
NODEname crpntti1
SUbdir NO
TCPPort 1500
TCPServeraddress 10.x.x.x
************************************************************************
TCPBUFFSIZE 31
TCPWINDOWSIZE 64
TCPNodelay YES
TXNBYTELIMIT 25600
QUERYSCHEDPERIOD 4
************************************************************************
CHangingretries 2
ERRORLOGRetention 10
RETRYPeriod 5
MAXCMDR 5
SCHEDLOGRETENTION 10
************************************************************************
SCHEDMODE POLLING
SCROLLLines 80
SCROLLPrompt YES
Quiet
Passwordaccess generate
So I'm a little stumped --- having done numerous NT installs with and
without connect agents, this is the 1st time
something has come up that really doesn't give me an indication where the
problem may actually reside. Because these
backups occur during the wee hours of the morning, I'll place a schedule
out there that will query the sessions active
during that time period for tonight's run. In the meantime, any help is
appreciated!
C.L.Cannam
Storage Management/ADSM
GENAM/St. Louis, MO/USA
ccannam AT genam DOT com
Andy Raibeck <storman AT US.IBM DOT COM> on 12/08/98 12:52:34 AM
Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
cc: (bcc: Cindy Cannam/GENAM)
Subject: Re: surprise on nt client
Hello Cindy,
If you are running version 3.1.0.0 of the Win32 client, I
urge you to run (don't walk) to the ADSM FTP site and pull down
and install 3.1.0.6. Problems at the 3.1.0.0 level of code
could possibly explain the trouble you are seeing. Even if
this is not the problem, I still strongly urge you to get to
this level.
When you see the client stop doing anything, does the session
actually stop? What does QUERY SESSION show?
If the 3.1.0.6 code does not resolve this, then it would be
helpful if you could include the entire DSMSCHED.LOG file from
the point where the messages about the next scheduled event
are shown ("Next operation scheduled") through the ending
statistics for that operation. Please also include DSM.OPT.
Best regards,
Andy
Andy Raibeck
IBM Storage Systems Division
ADSM Client Development
e-mail: storman AT us.ibm DOT com
"The only dumb question is the one that goes unasked."
To all:
Just recently an ADSM NT client running V3.1.0.0 began spitting out the
following messages after apparently starting a backup schedule --- it's as
though the schedule starts, the registry is backed up, and then nothing
happens --- sometimes the backup doesn't appear to finish (according to the
schedule log), but with the next day's incremental, the info from the
previous day is posted and appears to be correct and uneventful. Has anyone
else seen this type of behavior on an NT box?
SCHEDLOG message:
12/07/1998 04:07:43
Executing scheduled command now.
12/07/1998 04:07:43 Node Name: NTTMA
12/07/1998 04:07:43 Session established with server ADSM: MVS
12/07/1998 04:07:43 Server Version 2, Release 1, Level 0.13
12/07/1998 04:07:43 Data compression forced off by the server
12/07/1998 04:07:43 Server date/time: 12/07/1998 04:05:01 Last access:
12/07/1998 00:14:01
12/07/1998 04:07:43
Registry Backup Function Invoked.
12/07/1998 04:07:44
Save Registry Key: RootKey 'HKEY_LOCAL_MACHINE', SubKey 'SOFTWARE'
12/07/1998 04:07:44
Save Registry Key: RootKey 'HKEY_LOCAL_MACHINE', SubKey 'SYSTEM'
12/07/1998 04:07:45
Save Registry Key: RootKey 'HKEY_LOCAL_MACHINE', SubKey 'SECURITY'
12/07/1998 04:07:45
Save Registry Key: RootKey 'HKEY_LOCAL_MACHINE', SubKey 'SAM'
12/07/1998 04:07:45
Save Registry Key: RootKey 'HKEY_USERS', SubKey '.DEFAULT'
12/07/1998 04:07:45 ANS1427I Registry Backup function completed
successfully.
ERROR LOG message:
12/07/1998 04:07:58 AltStreamSize(): CreateFile: Win32 RC=32
12/07/1998 04:07:58 AltStreamSize(): CreateFile: Win32 RC=32
12/07/1998 04:07:58 AltStreamSize(): CreateFile: Win32 RC=32
12/07/1998 04:07:58 AltStreamSize(): CreateFile: Win32 RC=32
12/07/1998 04:07:58 AltStreamSize(): CreateFile: Win32 RC=32
Thanks much!
C.L.Cannam
Storage Management/ADSM
GENAM/St. Louis, MO/USA
ccannam AT genam DOT com
|
