ADSM-L

Re: NT client with drive that won't back up

2015-10-04 17:46:05
Subject: Re: NT client with drive that won't back up
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
To: ADSM-L AT VM.MARIST DOT EDU
No, that's the strange thing, I get no errors at all, nothing in the
dsmsched.log and nothing in the dsmerror.log.

> -----Original Message-----
> From: Craig Shreve [SMTP:CShreve AT UNIONGAS DOT COM]
> Sent: Wednesday, March 24, 1999 9:46 AM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Re: NT client with drive that won't back up
>
> Is there any error message?  I had this problem once where there were
> corrupt files on the drive.  The rest of the machine backed up
> successfully, but the drive with corrupt files failed with return code
> 4.  I could even back up individual files from the drive via the backup
> client gui.  This was  how I narrowed down to what the corrupt files
> were.  We had to reboot so that a chkdsk could run.  The corrupt files
> were cleared out, end everything returned to normal.
>
> -----Original Message-----
> From: Campbell, Rose [mailto:campbelr AT JNTF.OSD DOT MIL]
> Sent: Wednesday, March 24, 1999 11:19 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: NT client with drive that won't back up
>
>
> All,
>
> I have an NT client that has several drives which need to be backed up
> daily.  One of them is not backing up, this happens to be the most
> important
> of all the drives.  I have opened a pmr with IBM several times on this,
> but
> I am getting nowhere.
>
> Things I have tried are:  putting the drive (I:\) into the include
> exclude
> statement and making the share for that drive a system share.
>
> Has anyone seen this before?  Do you have any suggestions?
>
> Thanks,
> Rose M. Campbell
> Data Storage Manager
> Schriever AFB
> 719-567-8454
> 719-567-8288 (fax)
> rose AT jntf.osd DOT mil
<Prev in Thread] Current Thread [Next in Thread>