![]() ![]() ![]() Not because one was better than the other but because I needed to fullfil some specific requirements for the developers i help take care of. Take this with a grain of salt, but I switched from using veeam to the built in sql backups. ![]() There would be some work setting this up and I’d have to make sure there is disk space on the SQL server for backups and all….īTW - the SQL server is part of an HA availability group. I would configure a SQL maintenance plan to handle SQL backups and transaction log backups locally instead. I’m considering changing the process, where I remove the SQL application processing from the Veeam backup job. This puts the SQL database in read-only mode - not good. While this is the situation, the transaction log continues to grow and eventually fills the disk. In this instance, our backup repository experienced a hardware fail and is offline. This is all fun and dandy until there is an issue that causes the backup job to fail. For the Veeam backup job of our SQL server, the job backs up the SQL application and truncates the SQL Transaction logs. Just looking for opinions on best practices. We use Veeam to backup our systems and mostly happy. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |