Let’s face it, if it’s Oracle, DB2, or anything along those lines, I can snap a copy and back it up with my eyes closed.
MSSQL, being a pretend database, has me stumped.Â I’m so used to archive logs that I’m not even sure how to use TF/Snap to back up the database.
This is my understanding.Â MSSQL doesn’t do “Archive Logging” in the traditional sense.
In a “REAL” database system the process is as follows:
1.Â You put the database into “Hot Backup” mode.Â In Oracle this quiesces the data files and writes all changes to the transaction log.Â (When you take the database out of backup mode, the transactions in the log are then played into the database)
2.Â When the above is complete, you can issue a command in one form or another to switch out the last transaction log, which closes one file and opens the next one, and then back up the database files along with the closed transaction log files via whatever file level backup process you have in place, whether it be TimeFinder or just having NetBackup pull the files from that server.
At Disney we did just that, with DB2, and moved in the neighborhood of 250+ Terabytes to tape every night.
At a number of other sites I’ve done the exact same processÂ with Oracle.
Enter MSSQL, a Playschool excuse for an RDBMS, and I’m stumped.Â See – the problem is there is never more than one “database.LDF” file for logging.Â How am I supposed to quiesce writes to a logfile when it never closes it?
Then add that to the process for rolling transaction log backups forward in MSSQL is dependent on the idea that you used the MS Backup process to back it up.Â It seems to be completely unaware of file level backups of the database.
I’m at a loss here – any ideas?