February 10, 2010 at 5:02 pm
how to copy the database (backup) from one server to another server.
i mean directly how to copy into another server.
February 10, 2010 at 5:09 pm
charipg (2/10/2010)
how to copy the database (backup) from one server to another server.i mean directly how to copy into another server.
I am not sure if I understood your question completely.. Lemme quote all options on top of my head..
Attach/Detach (offline)
Copy Database (can be online)
Use Backup of the existing database and copy it to target server and restore it there.
Script the entire database and use SSIS to move the data..
Blog -- LearnSQLWithBru
Join on Facebook Page Facebook.comLearnSQLWithBru
Twitter -- BruMedishetty
February 10, 2010 at 6:19 pm
Best bet would be a SAN mirror or use third party utilities (i.e. Double Take) - mirror the drive you're doing you backups on, at the block level with checksum (hardware level). Of course, assuming you have these in place...
I'm replicating 3/4 TB production databases (for reporting pourposes ) in minutes - they all sit on EMC/NetApp SAN storage, multiple spindles LUNs, etc...
Double Take works with local storage also.
Hope this helps
February 10, 2010 at 7:16 pm
$3cur1ty (2/10/2010)
Best bet would be a SAN mirror or use third party utilities (i.e. Double Take) - mirror the drive you're doing you backups on, at the block level with checksum (hardware level). Of course, assuming you have these in place...I'm replicating 3/4 TB production databases (for reporting pourposes ) in minutes - they all sit on EMC/NetApp SAN storage, multiple spindles LUNs, etc...
Double Take works with local storage also.
Hope this helps
This, of course, works if you have (can afford) Double Take. If you don't have it, you have to use the tools and processes availble which is what Bru provided.
February 10, 2010 at 8:39 pm
Just an add:
If you are trying to move only the backup files/folders you can use ROBOCOPY tool or simply you can use XCOPY from command prompt. Which move faster than the copy paste to network server.
command Line:
XCOPY \\<Source server>\<drive>\<File.bak\back.rar\.zip> \\<destination server>\<drive>\<File.bak\back.rar\.zip>
Cheers,
- Win.
" Have a great day "
February 10, 2010 at 9:23 pm
The most important variable is the size of the "backup" file (as stated) he wants to move and the connection between the servers:
> .bak file only = xcopy with -v option (corruption may occur while moving the file over the wire)
> When you get into 100s GB = DB should be on SAN and LUNs configured and carved up appropriate
I would't attempt to move a 300-400 GB file over the wire and restore from it (would take hours). I've done it in the past on 2 GB Full connection, both servers in the same data center and it's just painfull...
Again, the size of the file is unknown... and in emergencies you work with what you have...
FYI - Double Take is ~3-4k per server license. 😎
February 10, 2010 at 9:42 pm
winslet (2/10/2010)
Just an add:If you are trying to move only the backup files/folders you can use ROBOCOPY tool or simply you can use XCOPY from command prompt. Which move faster than the copy paste to network server.
command Line:
XCOPY \\<Source server>\<drive>\<File.bak\back.rar\.zip> \\<destination server>\<drive>\<File.bak\back.rar\.zip>
Something I learned this week, XCOPY has been depreciated in Windows Server 2008. They tell you to use ROBOCOPY. I have no idea when XCOPY will actually be removed from Windows Server.
February 10, 2010 at 9:44 pm
$3cur1ty (2/10/2010)
The most important variable is the size of the "backup" file (as stated) he wants to move and the connection between the servers:> .bak file only = xcopy with -v option (corruption may occur while moving the file over the wire)
> When you get into 100s GB = DB should be on SAN and LUNs configured and carved up appropriate
I would't attempt to move a 300-400 GB file over the wire and restore from it (would take hours). I've done it in the past on 2 GB Full connection, both servers in the same data center and it's just painfull...
Again, the size of the file is unknown... and in emergencies you work with what you have...
FYI - Double Take is ~3-4k per server license. 😎
Also dependent on version of the OS you are running. Our shop has Double Take, but they can only install it on Standard Edition OS's. Can't run it on the sservers running Enterprise or Data Center editions.
February 10, 2010 at 9:54 pm
Since DT supports these versions, is there a reason why? I have it on Enterprise x64 for over a year...
February 10, 2010 at 10:06 pm
$3cur1ty (2/10/2010)
Since DT supports these versions, is there a reason why? I have it on Enterprise x64 for over a year...
Just going by what our Network people say. They are responsible for the server hardware and os. I just install and support SQL Server and provide database support for the LOB which are supported by others in the same department I work.
The tech support for Double Take tried telling our network people we needed shared storage to run SQL Server Database Mirroring and that we would still need Double Take. Sorry, wrong. I have database mirroring up and running in our new PeopleSoft environment.
Have to say, cool beans (so far).
Where we are using Double Take, it works great. We have it supporting failover for our Student Information System. It is NOT setup for automatic failover. I was told they did it that way so that things could be checked and verified before doing a failover. I was also told by network services 4.5 years ago that it was tested, but a member of my time constantly says it was never tested.
It did hang the primary system once shortly after I started working here. But that was the only problem with it.
February 10, 2010 at 10:17 pm
Lynn - this sounds familiar and just happened to me two weeks ago:)
If you're looking @ Page Faults and watching other ocounters on the source server when the full mirror starts (required for full server failover and based on the version), it goes trough the roof and hangs the SQL instance running on the same server or in best case scenario, just "impacts performance".
They're certain Registry changes to be made and tune DT to prevent this -
Thank you
February 10, 2010 at 10:25 pm
$3cur1ty (2/10/2010)
Lynn - this sounds familiar and just happened to me two weeks ago:)If you're looking @ Page Faults and watching other ocounters on the source server when the full mirror starts (required for full server failover and based on the version), it goes trough the roof and hangs the SQL instance running on the same server or in best case scenario, just "impacts performance".
They're certain Registry changes to be made and tune DT to prevent this -
Thank you
The problem we had many years ago was that it locked a part of the database. When a co-worker came and talked to me and told me the errors that users were getting, i even said that it sounded like a record lock of some sort. He blew me off, and about an hour or so later he came back and told me what the problem was and that I was correct. I just didn't know what was causing the lock.
To fix the problem, they had to restart Double Take. If they made any config changes at the time, I have no idea as network services is responsible for Double Take.
Viewing 12 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply