DB Backup file copy error

Question

Post reply

DB Backup file copy error

Summer90

SSC-Dedicated

Points: 32891
More actions
January 28, 2010 at 5:00 am

#96215

We have a prod and a test Win2003 servers running SQL 2000 SP4. I backup the prod db to the local HD and then file copy it to the test server then on the test server I restore the db. This has worked great until the last three weeks. There is over 2 gig of memory free and all drives have plenty of free space too. Has anyone ran accross this issue? It doesn't make the job fail nor does it write anything to the server log as an error.
I backup/copy a 19 gig db file just fine, the one that fails is 97 gig.
Executed as user: xxxxxx\xxxxxx. G:\bcksql\xxxprod_db.BAKFile creation error - Insufficient system resources exist to complete the requested service. 0 File(s) copied. Process Exit Code 0. The step succeeded.
This is the command:
xcopy G:\bcksql\xxxprod_db.BAK \\servertest\H$\bcksql\ /d /c /y

Viewing 8 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic. Login to reply

vstitte SSCarpal Tunnel Points: 4475 More actions · Answer 1

Are you doing this manually or is it part of a script and you have it scheduled in SQL Server Agent?

Chandra Sekhara Vyas Dhara SSChampion Points: 10207 More actions · Answer 2

Is it a job scheduled? If so please check the agent log for error.

Summer90 SSC-Dedicated Points: 32891 More actions · Answer 3

Yes it is scheduled through SQLAgent. The job says it is successfull but when you go into the job and look at the steps they all say successfull but the output has the message I posted about insufficient resources.

Chandra Sekhara Vyas Dhara SSChampion Points: 10207 More actions · Answer 4

It should be problem with target machine where u copying the file. Check is there any change in that target mechine

Summer90 SSC-Dedicated Points: 32891 More actions · Answer 5

I looked at it and found nothing. I had the server engineer group look at it and they found nothing. I even rebooted it and did the file copy again and it failed.

vstitte SSCarpal Tunnel Points: 4475 More actions · Answer 6

Did you check the account SQL Server Agent is running under? Hopefully you have already checked that.

I had a related issue where the jobs stopped running and found out someone had reset the service to use Local System Account.

Summer90 SSC-Dedicated Points: 32891 More actions · Answer 7

It is not that. This job has several steps and it backs up two dbs and file copies the backup files to the non production server. The other db file copy works but it is under 20 gig. The one that fails is 95 gig. That is really the only difference.