mike 57299 (12/10/2012)
Yes, the data in a writable state is a must. That is why mirroring and log shipping won't work.Mike
It wasn't stated hence my question, now that we have that cleared up let's go back to your original post.
mike 57299 (12/8/2012)
They have daily backup and 30 min transaction log backps. Unfortunately, because we are charged for bandwidth at the location, I can't pull daily backups from the site to me.
Problem here is if you want fresh writable copy each day you'll need to pull one backup per week and all logs. At 30 min intervals after a couple of days you'll have a truck load of log backups.
mike 57299 (12/8/2012)
I was thinking that I could have a server here at the office. Load a backup. Copy all the transaction logs each day. Then restore the transaction logs to my copy of the data and I would have current data to use for testing, off-site backup, etc.
Why don't you have your dev server on the live site then restores won't cross the network link. It will also prove how robust the application is.
mike 57299 (12/8/2012)
Does this sound workable? Does anyone have any scripts that would help automate the restore process? Any other ideas?Thanks!
Mike
Apart from above the only other option is replication. Bear in mind a re initialisation of the subscription will result in a full backup making its way across the network.
Best to have the dev server local to the live server.
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉