I really think this is a good set of routines and sp's for a log shipping solution. I ran across it while looking for a solution to keep 235 databases (53 gigs) within 24 hours of snyc at our standby server offsite. Replication wasn't an option as I had to leave the online databases user-changeable (add, delete tables, add, drop databases - as DBA I have no control of that, and I'm not notified so snapshot's really weren't in our business model).
I worked through mod's for Chris's script, and we emailed back and forth some - then decided it wasn't a viable option as I have other restrictions that just make it not possible (only a t-1 line, and only permitted to transfer 50 gigs a month).
If anyone out there has any suggestions as to how to do this, I'm open to them:critenour@imapdata.com
Thanks for your help Chris.
Chris, first let me thank you for this contribution, you have saved me literally days of work and its far better than I could have achieved on my own.
I have one small problem with it though. When gzip is called to zip up the BAK files it occasionally fails to delete the original file and therefore causes and error email to be sent.
I am using a Job running iunder the SQL Server agent and its last step is to also FTP and then MOVE the files. The MOVE command also returns an errorlevel (despite succeeding).
I suspect that this issue is caused by attempting to delete a file (i.e. a backup) that is still open.
Have you come across this problem and/or do you have any suggestions to get around it?
Many Thanks,
Jason
Chris
Excellent work on this! We have been using this for a couple of our databases which run the MSDE flavor and it works great.
Thanks
Ravi
