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 |
|
Soumen Dey
Starting Member
20 Posts |
 Posted - 2004-10-12 : 03:20:38
|
| Hi,I maintain two databases , one in NewYork and the other in New Delhi (India). We have a production System where data is entered by the operators. Every day I take a back up (full) of the database in India and transfer the .bak file in zip format by ftp to USA ( We have our own FTP Server) . I enter the US server thru remote desktop and download the file and restore the .bak file there. At that end executives also enter data and I do the same in the reverse way. Now the issue is that the data is progressively getting larger and the .bak file takes a lot of time to get uploaded thru Ftp about 4 hrs , though we have a 512 kbps lease line. I'm really concerned about the huge downtime. Can any one of you suggest me any solution as regarding how to transfer the data ? |
|
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
Posted - 2004-10-12 : 03:32:09
|
| you may want to consider archiving old data so that you can maintain a reasonable db size.or you can divide the data to be transferred, e.g. have a standy database, transfer the "differential" data, and just backup that database instead of the source. so you only handle the changes made.keeping it simple |
 |
|
|
sify
Starting Member
18 Posts |
Posted - 2004-10-12 : 04:04:09
|
| Does you infrastructure allow you replicating between the servers? |
|
|
|
Kristen
Test
22859 Posts |
Posted - 2004-10-12 : 04:20:56
|
| Could you use DIFFERENTIAL backups during the week, and a full backup (say) once a week?Alternatively, you could look into Log Shipping (and Replication as sify mentioned)Kristen |
|
|
|
Soumen Dey
Starting Member
20 Posts |
Posted - 2004-10-12 : 04:46:31
|
quote:
Originally posted by jen
you may want to consider archiving old data so that you can maintain a reasonable db size.or you can divide the data to be transferred, e.g. have a standy database, transfer the "differential" data, and just backup that database instead of the source. so you only handle the changes made.keeping it simple
Thanks for your prompt reply.Look I 've to upload the .bak file from india and download the same and restore in US and need to do the reverse. No matter wheteher I take a differential or transactional log backup , atleast I need to take one full database backup. It is where the time is getting consumed |
|
|
|
hgorijal
Constraint Violating Yak Guru
277 Posts |
Posted - 2004-10-12 : 04:50:13
|
| set up replication to keep both databases in sync; instead of transfering entire database backups every day.Hemanth GorijalaBI Architect / DBA... |
|
|
|
Kristen
Test
22859 Posts |
Posted - 2004-10-12 : 05:36:29
|
| Put an Update date column on each table (enforced with a trigger I suppose), and have some way of "logging" deletions, and then extract those rows and apply at the other end?Or replication (a once-a-day each-way replication should do the trick, but it will be a PITA when it breaks ...)Why not have the N.Y. executives connect to the server in India? (or the other way round if you are based in N.Y. <g>)Kristen |
|
|
|
|
|
|
|
|
Managing Database Size