DAG scenario where we've got replicated databases.
BUT, transaction log disk filled up on the server with the active copy and seems to have unmounted the database. Added more space to the trans log disk (luckily, its a VM machine) and DB mounted itself without intervention.
Looking at the times/dates on files in transaction log and they are newer than last backup flagged for these DBs. We've been migrating (from 2007) to this particular server so I'm guessing this is what has caused the extra activity in the logs.
Looking at the manual, it seems enabling circular logging is an option but not if you use VSS enabled backups (which we do) because I guess this will clear down the logs. BUT, I'm thinking if we had this we wouldn't have had this outage today.
What would we lose if we enabled circular logging and logs got overwritten in this way?
Or is it just better to add more disk space to enable more log files to be retained until backup?
Is there a way to manually purge log files without doing backup?