We tryed installing the v3 client. The drive still does not get backed up.
In addition there are no longer any messages in the dsmsched.log about the
drive or any errors. Another strange thing in the log file was no mention of
drive
D: getting backed up even though q filespace showed that the drive was backed
up when the scheduler ran. It appears that the d: drive did not need any files
backed
up so maybe that why it was omitted from the dsmsched.log. But there should
have
been something logged for the failed volume set (E:). As you can see the
v2 client indicated a failed status for the node while the v3 client indicates
success even though the E: drive did not get backed up.
Here is part of the dsmsched.log file showing this:
(Version 2)
01/13/1998 20:00:51 ANS4090E Access to the specified file or directory is denied
01/13/1998 20:00:51 Normal File--> 1,770
C:\WINNT\system32\LLS\LlsUser.LLS Sent
01/13/1998 20:00:51 ANS4638E Incremental backup of 'C:' finished with 6 failure
01/13/1998 20:00:51 Incremental backup of drive 'D:' with label 'BOOT-AREA'
01/13/1998 20:00:52 Successful incremental backup of 'D:'
01/13/1998 20:00:52 ANS4147E Drive E: is an invalid drive specification
01/13/1998 20:00:52 Total number of objects inspected: 2,730
01/13/1998 20:00:52 Total number of objects backed up: 18
01/13/1998 20:00:52 Total number of objects updated: 0
01/13/1998 20:00:52 Total number of objects rebound: 0
01/13/1998 20:00:52 Total number of objects deleted: 0
01/13/1998 20:00:52 Total number of objects failed: 6
01/13/1998 20:00:52 Total number of bytes transferred: 2,759.7 KB
01/13/1998 20:00:52 Data transfer time: 3.09 sec
01/13/1998 20:00:52 Data transfer rate: 892.25 KB/sec
01/13/1998 20:00:52 Average file size: 129.3 KB
01/13/1998 20:00:52 Elapsed processing time: 0:00:23
01/13/1998 20:00:52 ANS4847E Scheduled event 'DAILY-IOS-8PM' failed. Return
code = 4.
01/13/1998 20:00:52 Sending results for scheduled event 'DAILY-IOS-8PM'.
01/13/1998 20:00:52 Results sent to server for scheduled event 'DAILY-IOS-8PM'.
(after upgrade to v3)
01/14/1998 20:01:08 ANS4007E Error processing
'C:\WINNT\Profiles\scheduler1\ntuser.dat.LOG': access to the object is denied
01/14/1998 20:01:08 ANS1802E Incremental backup of 'C:' finished with 4 failure
01/14/1998 20:01:09 Total number of objects inspected: 2,800
01/14/1998 20:01:09 Total number of objects backed up: 12
01/14/1998 20:01:09 Total number of objects updated: 0
01/14/1998 20:01:09 Total number of objects rebound: 0
01/14/1998 20:01:09 Total number of objects deleted: 1
01/14/1998 20:01:09 Total number of objects failed: 4
01/14/1998 20:01:09 Total number of bytes transferred: 2.16 MB
01/14/1998 20:01:09 Data transfer time: 6.95 sec
01/14/1998 20:01:09 Network data transfer rate: 318.99 KB/sec
01/14/1998 20:01:09 Aggregate data transfer rate: 77.17 KB/sec
01/14/1998 20:01:09 Objects compressed by: 0%
01/14/1998 20:01:09 Elapsed processing time: 00:00:28
01/14/1998 20:01:09 Scheduled event 'DAILY-IOS-8PM' completed successfully.
01/14/1998 20:01:09 Sending results for scheduled event 'DAILY-IOS-8PM'.
01/14/1998 20:01:09 Results sent to server for scheduled event 'DAILY-IOS-8PM'.
And finally the q filespace output:
File Space Name Node Name Platform File Space Type Capacity (MB) %Util Last
Backup Start Days Since Last Backup Started Last Backup Completion Days Since
Last Backup Completed
----------------------------------------------------------------------------
------------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------------
SYSTEM-AREA SMSUNIV WinNT NTFS 1757.1 17.5
SYSTEM-AREA SMSUNIV WinNT NTFS 1757.1 17.5
01/14/1998 20:00:41 1 01/14/1998 20:01:08
1
BOOT-AREA SMSUNIV WinNT FAT 305.8 0.4
01/14/1998 20:01:08 1 01/14/1998 20:01:09
1
Data-Area SMSUNIV WinNT NTFS 14276.4 16.4
01/15/1998 08:43:59 <1 01/15/1998 09:26:30
<1
Could someone from IBM please comment on this problem?
Thanks,
Alex Mounayar. SMS
ADSM-L AT VM.MARIST DOT EDU on 01/08/98 09:33:04 AM
Please respond to ADSM-L AT VM.MARIST DOT EDU @ Internet
To: ADSM-L AT VM.MARIST DOT EDU @ Internet
cc:
Subject: Re: ANS4147E invalid device error on nt volume set
Alex,
We have seen this problem, and I have no explanation. I scheduled a
backup of the "bad" drive via a bat file and the NT scheduler service. We
intended to research the problem, but the machine was slated for
upgrade/rebuild and the problem was gone after this was done. I could see
no discrepancy on the drive when looking with performance monitor, srvinfo
or disk administrator.
We have never had a chance to resolve the problem by using the ADSM v3
client. If your server is v2, you can run the v3 client to see if it fixes
the problem, so why not do it?
good luck,
Dan T.
----------
> From: Alex Mounayar <Alex.Mounayar AT SMED DOT COM>
> From: Alex Mounayar <Alex.Mounayar AT SMED DOT COM>
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: ANS4147E invalid device error on nt volume set
> Date: Wednesday, January 07, 1998 3:20 PM
>
> We are having a problem backing up a nt volume set with the
> scheduler. We are running the version 2 nt client on a nt 4.0 intel
machine.
> The following error logs to schedule log:
>
> 12/30/1997 02:16:52 ANS4147E Drive E: is an invalid drive specification
>
> The E: drive is a multi-volume volume set made up of 3 whole disks and
1/2 of
> another disk.
> The ba gui client does not give the error message and backs up the
volume.
>
> Has anyone else seen this problem or have a fix?
>
> Also does anyone know if the v3 nt scheduler would work?
>
> Thanks
>
>
>
> *
*
|
