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.