I have a 20 GB SS2005 database that I would like to be replicated to a dev server for testing purposes. I might have some issues with the firewall blocking ports. I haven't read up on the specifics of how log shipping works yet, but I assume that is the best approach. A daily transfer would suffice.
A few options I am considering:
1. use the built in stuff, but I'm not sure it will work with our security settings, and if the trans logs are large it might be strained.
2. writing a small custom app to zip up the log file then ftp them down to the dev server. This could run nightly.
3. some third party util, such as FolderShare could transfer the log files
Any comments or suggestions?
If it's a dev environment and you are saying a daily transfer would suffice, maybe you want to consider restoring the last full backup from production onto the dev box and just schedule that daily. Log shipping could be an option I guess, depending on what you want to test - If you are testing by reading live data that needs to be fairly current for the testing purpose. But you would generally consider log shipping more for warm standby, reporting server, etc.
-Sue
|||thx for the response, sue.
i was trying to avoid a daily 30 gb download.
|||How about taking a daily differential backup and transferring that?
It should be very much smaller than a full, and proportional to the data churn in your production DB.
No comments:
Post a Comment