![]() I am taking a quick trans backup followed by a truncate log size. Strikes, you’re going to instantly bring up another server with no Theyīelieve you’ve got everything under control, and that when disaster Right now, all of your users believe your RPO and RTO is zero. #Backup scheduler down avamar full#Just bear in mind that under SIMPLE recovery, you will only be able to recover back to the last FULL or FULL/DIFF.Ĭheck out The 9 Letters That Get DBAs Fired. If that is the case, you should just change your recovery model to SIMPLE and then you won't need to worry about taking your transaction log backups. Since you are basically throwing away the transaction log backups you're taking, you are obviously not interested in being able to restore to a given point in time. You would need to take into consideration small problems (server went down) to big problems (the building just exploded). RTO basically is the maximum time allowed to get things back to 'normal' or at least functioning. RPO basically is, how much data could we 'possibly' lose should a bad problem happen? 5 minutes, 1 hour, 1 day, NONE? The absolute FIRST thing you need to do is identify your Recovery Point Objective (RPO) and Recovery Time Objective (RTO). ![]() ![]() When was the last time a FULL or DIFF backup was taken? Even if you weren't deleting the transaction log backups you're taking, it would take you a VERY long time to restore your latest FULL backup (assuming you still have it) and DIFF and ALL of the transaction logs to get you close to where you want to be in a recovery situation. By deleting the transaction log backup file, you just made it impossible to recover to any point after that (unless you are taking additional FULL or DIFF backups). You also say that Avamar only takes transaction log backups once per day. You say Avamar handles the whole backup and recovery and yet, you're doing things (deleting transaction log backups) behind its back. Reading your question makes me wonder if you've actually attempted to restore these databases as proof of your backup strategy (either by naming the databases something different on the current server or restoring them to another server). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |