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.
| Author |
Topic |
|
pdset
Constraint Violating Yak Guru
310 Posts |
 Posted - 2013-05-09 : 18:22:46
|
| We have 2008 R2 SQL Server built on WINDOWS 2008 R2 Enterprise Edition.We do backups being stored and in the process of TRANSFERRING these .BAK files were unable to get copied across within the Data Centre arena.Moreover the file size of more than 20 GB is also unable to process.The above things were easily done using WINDOWS 2003 Server but this is the latest beauty of Microsoft new invention on 2008 Server.So we have compressed the file to less than 20GB and still while transferring then also it won't copy.Is there any method this can be copied to another server within the same network.Your suggestions much appreciated. |
|
|
srimami
Posting Yak Master
160 Posts |
Posted - 2013-05-10 : 03:26:00
|
| There shouldn't any problem to transfer the .bak files in 2008 env. Please ensure you run with administrative rights, it works. |
 |
|
|
jackv
Master Smack Fu Yak Hacker
2179 Posts |
Posted - 2013-05-10 : 13:57:29
|
| What error message are you getting? Are you trying to copy through SQL Server or from Windows?Jack Vamvas--------------------http://www.sqlserver-dba.com |
|
|
|
pdset
Constraint Violating Yak Guru
310 Posts |
Posted - 2013-05-15 : 19:29:28
|
| Apologies to get back little absent.I was trying to copy the .BAK file from Windows Environment. Though there is enough Disk space for the file and also the file is within the Data Centre arena, after copying it in middle of around 50 - 60 percent and it has got this error.Error 0x8007046A: Not enough Server Storage is available to process this Command.I have verified from the Friendly suggestive pages from the net, and it really didn't helped me either to suppress.Any further suggestions. Thanks all. |
|
|
|
russell
Pyro-ma-ni-yak
5072 Posts |
Posted - 2013-05-15 : 20:24:20
|
| saw this?http://blogs.technet.com/b/markrussinovich/archive/2009/03/26/3211216.aspx |
|
|
|
AJSpruit
Starting Member
3 Posts |
Posted - 2013-05-16 : 09:03:52
|
| I recently had the same issue moving large files on Windows Server 2003. I used 2 methodsScripting option: Check out XCOPY with /Z /J optionsGUI option: I've been using Teracopy for this.Kindest RegardsAJ |
|
|
|
jackv
Master Smack Fu Yak Hacker
2179 Posts |
Posted - 2013-05-17 : 01:51:46
|
| On a nightly job I run i.e copying a 120 GB backup copy - when the server was unnswe menmory pressure - this problem used to occur occassionally. As a workaround - we needed to reboot the server. After a awhile - we doscovered a memory leak on the server. Instead of now using COPY or XCOPY - which are buffer based , I use a utility called ESEUTIL - which I picked up from Microsoft Exchange and is used to copy large mailboxes within Exchange. ESEUTIL used unbuffered IO - and has has halved the amount of time . Using it is very simple. Read some notes on usage http://www.sqlserver-dba.com/2011/02/speed-up-copying-large-files-with-eseutil.htmlJack Vamvas--------------------http://www.sqlserver-dba.com |
|
|
|
|
|
|
Backup File Transfer