"Backing up the files of a SQL database while it's active is not a good way to back the database up."
If you're referring to the tape backups, those are done at 3:00 am when users are off the system. We are not a 24/7 shop (fortunately!)
Doesn't matter. There being no users doesn't mean that the database IO is quiesced. That is a BAD way to do backups and it's possible that those files will be useless if you need to recover with them. I've seen cases where 'backups' like that are used and either the files won't attach at all or they attach and the database is suspect.
There are tools which allow that but they specifically request SQL to quiesce the database before copying the files
Backup the SQL databases using SQL's native backup before 3am and let the file-system backup copy those to tape, not the mdf and ldf files.
Thanks so much for the response. If I schedule a one-time maintenance job to shrink the database and then rebuild indexes, does that sound reasonable?
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)SQL In The Wild
: Discussions on DB performance with occasional diversions into recoverability
We walk in the dark places no others will enter
We stand on the bridge and no one may pass