Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 General SQL Server Forums
 New to SQL Server Administration
 Backup file copy error from one server to another

Author  Topic 

gangadhara.ms
Aged Yak Warrior

549 Posts

Posted - 2010-07-26 : 23:47:48
Dear All,

I need to do a DB refresh from PRODUCTIOn to DEV server.I have a full backup file with size of 46 GB.When copying from production server to DEv server i am getting the following error.If any body face the issue earlier can somebody pls help me.

Error:
"Cannot Copy"filename:Insufficient system resources exist to complete the required service.

Thanks in Advance
Gangadhar

slimt_slimt
Aged Yak Warrior

746 Posts

Posted - 2010-07-27 : 00:25:19
seems like you are running out of space on your disk?

how do you copy this file?
Go to Top of Page

gangadhara.ms
Aged Yak Warrior

549 Posts

Posted - 2010-07-27 : 00:42:57
Hi,
Thanks for the reply..

I have nearly 180GB of free space in the destination server but still i do get this error.

I am shared the backup file in PRODUCTION server
and in destination i am accessing \\productionserver\backupfile

Please help me
Go to Top of Page

gangadhara.ms
Aged Yak Warrior

549 Posts

Posted - 2010-07-27 : 01:47:29
The Source server is

Windows server 2003 Enterprise Edition with SP3
Go to Top of Page

gangadhara.ms
Aged Yak Warrior

549 Posts

Posted - 2010-07-27 : 02:03:57
Hi All,

IS there any way to do the Db refresh apart from taking backup and restore.

I need to do this DB refresh like any other way..

Database size is 40GB
Go to Top of Page

GoldenSQL
Starting Member

3 Posts

Posted - 2010-07-28 : 14:58:03
quote:
Originally posted by gangadhara.ms

Hi All,

IS there any way to do the Db refresh apart from taking backup and restore.

I need to do this DB refresh like any other way..

Database size is 40GB



Hi,

Create a linked server on your DEV server with sa access and run your script to refresh the DEV database by Production way. This is the simplest way

SQL Guru 4 U
Go to Top of Page

russell
Pyro-ma-ni-yak

5072 Posts

Posted - 2010-07-28 : 15:43:27
sounds more like RAM problem to me
Go to Top of Page

Kristen
Test

22859 Posts

Posted - 2010-07-29 : 01:48:17
"I have a full backup file with size of 46 GB.

Database size is 40GB
"

Seems a bit unlikely (DB smaller than backup file)?

Note that, whatever the size of the Backup file, RESTORE will create the Database files to the size of the original database files - so if the original database had lots of free space so will the new database, after restore (potentially it could even be bigger than your 180GB disk). I expect that isn't the case, but perhaps worth checking on the original machine?
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2010-07-29 : 01:53:35
quote:
Originally posted by GoldenSQL


Create a linked server on your DEV server with sa access and run your script to refresh the DEV database by Production way. This is the simplest way



No that's one of the hardest ways to move a database to another server. The easiest way is backup/restore or detach/attach. Next easiest is the GUI's copy wizard. Linked server is probably the hardest way actually.

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog
Go to Top of Page

russell
Pyro-ma-ni-yak

5072 Posts

Posted - 2010-07-29 : 14:02:42
if it's disk space issue, error will say "Insufficient Disk Space" since it says "resources" I think it's memory issue.

can try copying bak file to local machine and restore locally
Go to Top of Page

Kristen
Test

22859 Posts

Posted - 2010-07-30 : 05:37:43
quote:
Originally posted by russell

if it's disk space issue, error will say "Insufficient Disk Space" since it says "resources" I think it's memory issue.



Yes, I agree, but sometime the errors cascade and you wind up with a seemingly unrelated message. The Database may be WAY larger than the backup file itself (which might put even more pressure on RAM perhaps?)
Go to Top of Page
   

- Advertisement -