Re: NTBackup - The device reported an error on a request to write data to media.




"Damon" <enlighten@xxxxxxxxxxxxxxxxx> wrote in message
news:C5591EA6-3203-4C98-B4E3-0F5C306DD20D@xxxxxxxxxxxxxxxx
Hi,

I'm having some problems with NTBackup. We currently have 5 servers which
we have two NTBackup jobs set-up on each server. One backup job for each
server is for backing up system state. The next backup job which runs
after that backs up the files and then the system state backup.

The problem that I am getting is that on some days the backups on
different servers fail, its currently random as to which backup will fail
and on what day. When they fail the error log always contains the
following:

Error: The device reported an error on a request to write data to media.
Error reported: Unknown error.

Then if it was an exchange backup

Error: SERVER\Microsoft Information Store\First Storage Group is not a
valid drive, or you do not have access.

If it was a file backup (the drive letter will change depending on where
the files are being backed up.

Error: E: is not a valid drive, or you do not have access.

If I go and run that schedule task again it will succeed. Because the
backups can run perfectly I think that the error which is being reported
is not correct because obviously the drives are accessible. What I'm
thinking it could be (I'm guessing here) is that maybe this is the error
that you get when doing a backup across the network and maybe the network
connection drops out for a second.

I really need to get this sorted and working, does anyone have any ideas
on what I should do here?

Cheers

Damon


Instead of scheduling ntbackup.exe directly, embed it in a batch
file as below, then examine the contents of c:\test.log after the
next failure.
@echo off
echo Start of job: %date% %time% %UserName% >> c:\test.log
net use >> c:\test.log
copy c:\test.log "{Destination}" 1>>c:\test.log 2>>&1
ntbackup /.. /..
echo End of job: %date% %time% %UserName% >> c:\test.log
echo. >> c:\test.log

Replace {Destination} with the drive\folder that the backup job
itself uses.


.



Relevant Pages

  • Re: 3rd Party Backup Software
    ... You are fully welcome to spend your clients money on a solution that is built into SBS. ... No, it does none of those because it is a simple, cheap, backup method best used for a home user. ... Let us not forget that while SBS only allows for one PDC, this does not have an effect on running multiple servers. ... If you have no experience with true disaster recovery methodology, then I can understand where something as basic as NTBackup would seem like all you need. ...
    (microsoft.public.windows.server.sbs)
  • Re: Backup to external drives
    ... servers for at least 7 months and it is working great on all of them. ... > I am reaching the limits of my tape backup and am considering the following. ... > in a box with a USB 200gb drive on it in one of the external buildings. ... > I could then have NTBackup do a nightly backup to that drive. ...
    (microsoft.public.windows.server.sbs)
  • Re: Next openSUSE
    ... That will not do because I add the new stuff on the backup drive. ... I take pieces (directory trees) and copy them manually. ... I would have had to use free servers of pay for, ... My guess is that CSS or whatever is causing this bug. ...
    (alt.os.linux.suse)
  • Problematic Backup Rate for Exchange 2007
    ... We are currently only getting about 45 MB/min backup speed to disk ... multi-role servers. ... Can someone relate what speeds they are getting? ... We have three Exchange 2007 servers: ...
    (microsoft.public.exchange.admin)
  • Re: Exchange 2003 backup
    ... Veritas, formerly Seagate, formerly Arcada) wrote NTBACKUP. ... The best way to back up Exchange 2003 is using NTBACKUP to back up to a disk ... backup file to tape or whatever. ... I like to know what it the best way to backup Exchg 2003/W2k3 servers? ...
    (microsoft.public.exchange.setup)