urgent help needed - SQL Server Forums

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

SQL Server 2005 Forums

SQL Server Administration (2005)

urgent help needed

Author

Topic

sodeep
Master Smack Fu Yak Hacker

7174 Posts

Posted - 2007-11-01 : 14:15:11

Actually we have already backed up the Very large database(1.1 TB). We are trying to migrate the backup file to other server . But the copy is running really slow because of slow network banwidth. What are best options to transfer terabyte file from one server to other.
Thanks in advance

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2007-11-01 : 14:18:39

Compress the file first.

Check with your network admins on what options you have in your environment.

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

sodeep
Master Smack Fu Yak Hacker

7174 Posts

Posted - 2007-11-01 : 14:20:16

Thanks for reply Tara. Can you please exactly tell me the steps

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2007-11-01 : 14:22:33

1. Compress file on source server
2. Copy compressed file to destination server
3. Uncompress file on destination server

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

sodeep
Master Smack Fu Yak Hacker

7174 Posts

Posted - 2007-11-01 : 14:25:24

Thanks Tara. For compresssing the files i have used WinRar . Can you please tell me any third party tools or any options.

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2007-11-01 : 14:27:33

We use winrar as well. For other options, try googling.

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

Kristen
Test

22859 Posts

Posted - 2007-11-01 : 14:58:55

Sounds like you have taken the original database offline and are trying to get the new server upright in its place, but the file transfers are too slow etc.

For large databases we:

1) transfer a Full backup (in a non-urgent manner)
2) the original database carries on running
3a) We Restore and Test the FULL backup (including sorting out Orphan logins etc)
3b) Restore again, using NORECOVERY
4) Take a DIFF backup, transfer to new server, restore (with NORECOVERY)
5) Transfer and Restore any TLog backups since the DIFF was created
6a) Disable all access "application" to the old database
6b) Take a final transaction backup
7) Transfer and Restore any TLog backups since the earlier TLog backup transfer
8) Use Restore with the RECOVERY option to make the new server database "live"
9) Sort out orphan logins. Most (maybe "all"!) logins will already exist, so relatively easy operation.
10) Point applications at the new server (or "rename" it in place of the original server)

Kristen

Subscribe to SQLTeam.com

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -

Resources