| Author |
Topic |
|
rternier
Starting Member
44 Posts |
 Posted - 2009-07-03 : 19:26:30
|
| I have a good number of large databases I need to move from 1 server to another.These servers are not behind the same firewall.moving them by FTP would take 15 hours. Moving by flash drive takes 2 hours. We don't want that much downtime.Are there any alternative ways of doing this?I was thinking SQL Server Replication might work. Turn it on to replicate the DB's on both DB Servers and then turn it off and move the IP address to look to the new server.Any thoughts?----Killer ASP.NET ninja coding monkeys do exist![url]http://weblogs.asp.net/rternier[/url] |
|
|
tripodal
Constraint Violating Yak Guru
259 Posts |
Posted - 2009-07-06 : 11:03:17
|
| Perhaps you could take a full backup on your main server.Then transfer a differential / tlog backup to make both databases equivalent as you switch over the databases.Depending on that activity that backup may be much smaller and timly over ftp.Someone will correct me if im wrong.:) |
 |
|
|
rternier
Starting Member
44 Posts |
Posted - 2009-07-06 : 13:18:02
|
| Main DB server contains 200 DB's, all heavily used. i need to move about 10 of them to a new server. But those 10 can't be down for a long time because they deal with public safety.----Killer ASP.NET ninja coding monkeys do exist![url]http://weblogs.asp.net/rternier[/url] |
|
|
|
ahmad.osama
Posting Yak Master
183 Posts |
Posted - 2009-07-09 : 03:45:48
|
quote:
Originally posted by rternier
Main DB server contains 200 DB's, all heavily used. i need to move about 10 of them to a new server. But those 10 can't be down for a long time because they deal with public safety.----Killer ASP.NET ninja coding monkeys do exist![url]http://weblogs.asp.net/rternier[/url]
well...identify the off hours and use flash drives... |
|
|
|
Gyto
Posting Yak Master
144 Posts |
Posted - 2009-07-09 : 07:25:20
|
| Could you do this:1) Take a full copy of each database2) Restore them onto the new server while leaving the live version operational3) Take a database offline and copy the transaction log file over to the new server4) Replay the log file against the copy to get it up to date and them bring the new version online5) Repeat 3-4 for each databaseJust thinking that the log file would be much easier to move quickly than the database itself?Like tripodal....I'm sure someone will correct me if I'm wrong....! |
|
|
|
ahmad.osama
Posting Yak Master
183 Posts |
Posted - 2009-07-09 : 09:48:19
|
quote:
Originally posted by Gyto
Could you do this:1) Take a full copy of each database2) Restore them onto the new server while leaving the live version operational3) Take a database offline and copy the transaction log file over to the new server4) Replay the log file against the copy to get it up to date and them bring the new version online5) Repeat 3-4 for each databaseJust thinking that the log file would be much easier to move quickly than the database itself?Like tripodal....I'm sure someone will correct me if I'm wrong....!
in any case u need to have full backup of databases..i think the guy wants to avoid fullbackup..... |
|
|
|
Gyto
Posting Yak Master
144 Posts |
Posted - 2009-07-09 : 09:51:34
|
quote:
Originally posted by ahmad.osama
quote:
Originally posted by Gyto
Could you do this:1) Take a full copy of each database2) Restore them onto the new server while leaving the live version operational3) Take a database offline and copy the transaction log file over to the new server4) Replay the log file against the copy to get it up to date and them bring the new version online5) Repeat 3-4 for each databaseJust thinking that the log file would be much easier to move quickly than the database itself?Like tripodal....I'm sure someone will correct me if I'm wrong....!
in any case u need to have full backup of databases..i think the guy wants to avoid fullbackup.....
I just thought it would reduce downtime because you could leave the systems operational while you take/restore the backups. |
|
|
|
ahmad.osama
Posting Yak Master
183 Posts |
Posted - 2009-07-09 : 10:01:51
|
quote:
Originally posted by Gyto
quote:
Originally posted by ahmad.osama
quote:
Originally posted by Gyto
Could you do this:1) Take a full copy of each database2) Restore them onto the new server while leaving the live version operational3) Take a database offline and copy the transaction log file over to the new server4) Replay the log file against the copy to get it up to date and them bring the new version online5) Repeat 3-4 for each databaseJust thinking that the log file would be much easier to move quickly than the database itself?Like tripodal....I'm sure someone will correct me if I'm wrong....!
in any case u need to have full backup of databases..i think the guy wants to avoid fullbackup.....
I just thought it would reduce downtime because you could leave the systems operational while you take/restore the backups.
hmm...yes it will that's what tripodal suggested... |
|
|
|
Gyto
Posting Yak Master
144 Posts |
Posted - 2009-07-09 : 10:08:20
|
| Oh yes, so he did....don't know how I missed that! Sorry! |
|
|
|
|
moving very large databases between servers