July 25, 2008 at 6:45 am
Hi,
I have some DB copy jobs going on in PROD server to DR. They map the drive to the DR Server and copy the latest backups from PROD to DR.
When the job tries to copy larger files like (18GB), it fails after sometime with the following error.
Executed as user: XXXXXX\sqladmin. Not enough server storage is available to process this command. 0 file(s) copied. Process Exit Code 1. The step failed.
I tried to copy the file manually also several times, but the same result. The network share does have lot space to occupy this file.
Pls help me out as this is very critical since my DR isnt uptodate.
Thnx in Adv
July 25, 2008 at 8:50 am
What OS are you running? Google "Not enough server storage is available to process this command." It returns a lot of hits, some from MS pointing to changing reg values, some pointing to anti-virus software running. Just a bunch of stuff but hopefully something that may be applicable to your environment. It's not SQL related.
-- You can't be late until you show up.
July 25, 2008 at 11:10 am
How are the copies made as well?
July 25, 2008 at 10:46 pm
I saw the options in google..but some places i have seen users complaining that the registry stuffs also ddnt work out..So i ddnt wanted to try those directly in my registry of prod.
Also, the backup copy has been scheduled in jobs via t-sql commands..
first, map n/w drives, then copy the files and then disconnect the n/w drives..
thats how its implemented..
July 25, 2008 at 10:49 pm
and the OS on both machine is:
Windows Server 2003 R2 Enterprise Edition
August 15, 2008 at 2:55 am
Also, most of the time, the backups goes well...but sometimes it fails with the error I gave. After that, if i try to copy manually also, same error comes.
August 15, 2008 at 6:15 am
Are you sure there is no issue with network connectivity? From the message, it doesn't seem to indicate that but if you have space and proper rights, I'm not sure where else to go with this....Did you google the message and check out the hits to see if anything may apply to your situation?
-- You can't be late until you show up.
August 15, 2008 at 6:22 am
I tried google first...it suggested some registry stuff..But i saw some users complaning abt the registry thing too..so i ddnt wanted to try that in prod server.
Network is fine as the copying goes fine most of the time and even on the day where we have issue, file is copied to the DR till the last min and then it throws the same error, whether its manual or by job.
August 15, 2008 at 1:05 pm
I read somwhere that disabling and enabling network adapters also helps sometimes.
MJ
August 15, 2008 at 11:00 pm
Thanks MJ..
I will talk to my WIN team regarding this and let me c if i can try this..
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply