I am middle of setting up the Co-Location Server and stuck with transfering the DB Backup file acrosss the VPN.
We have one dedicated VPN channel over 20MB Broadband with 3.5MB Upload Speed. A plan is before I setup for the Log shipping, I want to test a copy of Full Backup Transfer over night and restore onto Co-Location Server. I have 6 production servers with handfull of Databases. For Instanse - one backup DB size is **30GB** (After Compressed backup through ENT Edt..) and it will takes ages to transfer to Co-Lo Site. It might takes days to transfer.
I don't think it works over 3.5MB upload speed internet. What do you do if you are in the same situation like me? I can try another way. I have another secondary server in my office. I can Backup and Restore onto Secondary Server first then run the script below to remove the unuse space (to cut down the DB Size) (that query might took 3 hours) and backup again on Secondary with compressed backup and transfer to Co-Lo site. --Shrink DB with left 10% of free space DBCC SHRINKDATABASE ([TMS-ManagementData], 10); GO Do you think that will work? I checked my DB log by using DBCC SQLPERF (LOGSPACE) it come up with 99887.43 (Log Size MB) / 0.024 (Log Space Used %) So I am pretty sure I can cut down nearly 100GB of unused space. Any suggestion? Thanks in advanced.
The size of the backup doesn't necessarily tally with the size of a database. You can have a database of 100TB, but if you only have 1MB of data in it, then the backup will be approx 1MB. When I originally moved my databases from internal to an external data centre, it was quicker to burn the backups to DVD, drive to the data centre and copy them directly onto the server!
How far apart are these data centres? As the old saw says, "never underestimate the bandwidth of a stationwagon loaded with mag tape driving at 50mph..." I'm looking at doing just that, albeit as a belt-and-braces backup plan...
I would try other compression methods. RedGate's [SQLBackup] will compress files better than zip/rar in my experience. It took 30m off my transfer time using the top level compression - we had a 2MB line over which I had to set up mirroring. Try zipping the compressed file, SQLBackup,sitting on it, anything to make it as small as possible. Then test it. Then consider driving it to the other site... :