October 21, 2005 at 8:18 am
I would like to implement Log Shipping ( think) but when I started to read up on it, I found that this is available only with Enterprise Edition? Is that True?
If that is the case, Here is my situation.. I have one production SQL Server (2000 Standard Edition) with 20 Production DBs (about 6 gb total) Most of our APPS are 3rd party apps so I maintain a Test SQL Server Instance where I can test/QA any scripts the vendor may send for fixes/enhancements/new versions.
I use Maintenance Plans to do Full Backups nightly and transaction log backups once an hour during business hours (basically 8am - 7pm) of my User Databases and Full weekly Backups of my System Databases.
I recently discovered that the Production DB server has not been backed up in awhile.. YIKES! I immediately changed my Backup Scheme and in addition to my local SQL Backups (above) I now do a FULL backup of ALL databases to a network Share on another Server - and I will continue to do so until I see that our tape backups of the DB Server are reliable again (maybe never)
I guess my question is ... If I can't do log shipping with SQL Server 2000 Standard Edition.. Can anyone tell me how they would handle this situation? Ideally I want to move/restore backups from my production instance to a standby instance for Disaster Recovery purposes.. Can anyone tell me what they would do or point me in the right direction? Thanks!!!!!!
October 21, 2005 at 9:26 am
If you read it, it must be true. You need SQL Enterprise Edition to perform log shipping.
Since you are copying backups to a different server you should be safe, but you should also do t-log backups to the server that holds your backups, so you will you will not lose a day's worth of data. If your saving files only for disaster recovery then this should suffice, (well as long as your getting backups copied offsite also). Log shipping is primarily used for "Warm" standby. Meaning the db is as up to date as the last log file restored, and can quickly be brought online if the primary server fails. If it is critical to the business, or your application that the server is not down for more lets say 15 minutes, then you will probably have to pay the piper and get enterprise edition.
October 21, 2005 at 10:24 am
Thank you for the response.. One more question.. Considering that I use SQL Server Maintenance Plans for my Backups, How can I do transaction log backups to my local server as well as to a network share? I would think that it would mess up the flow (so to speak) Or did you mean that I should copy my xaction log backups to the network share?
October 21, 2005 at 2:25 pm
Yeah, you can't tell a maintenance plan to do a backup in 2 places.
You can probably find/write some code that copies the backups to another drive.
October 24, 2005 at 6:04 am
What I did was make another maintenance plan.... It backs up my DBs to a Network Drive at 8pm every night. Then at 5am i do another full set of Backups (to a local drive on the Server) and at 7am commence with my hourly transaction log backups (7am-7pm) This should work...
October 24, 2005 at 6:06 am
Now I'll just have to figure out how to get them copied off to another Server and restored periodically... yikes!
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply