If the backup file was restored to a different server, where a “bad actor” was a sysadmin, they now have complete access to all of the data within that database (except for databases where TDE was enabled or where the data was encrypted within the database itself).
You have a bigger problem that file extension naming. “what if a backup file… due to an unrecognized extension the file was deleted” This entry was posted in SQL Server Administration and tagged Database Backups by Brumedishetty. Being a DBA is to plan for the most unexpected disaster to happen and still be able to get everything covered.ĭo you like this site? Like our FB page \LearnSQLWithBru so that, you know when there is a new blog post. May be that might be the only backup copy and that was deleted… trn, it would not run a virus check, in order to save the disk read / write overhead and the processor usage on the server.įinally, what if a backup file saved with extension “.jkl” and due to an unrecognized extension the file was deleted by one of your team members.
#Quicken file extension backup file software#
To give you another reason, usually there are exceptions added in your server Anti Virus software so that as soon as it sees certain files with extensions, such as.
You would not want to waste time by running a restore command against a backup file and then the see a message that this is not the kind of backup the SQL Server is waiting for. diff, you know, ok this is my differential backup file. So when you are trying to restore you database from your backups, you would want to know what kind of backup is that backup file just by looking at the extension. The first reason is to quicken you restores, yes the ultimate goal of a backup is to restore your data in case of a failure (user, hardware or a natural disaster). Why it should be named using a certain extensions, the reasons are many. If the backup was completed successfully, you can use that file to restore without any issues. sql or any funny extension as you wish and write the backup information into that file. You can name your backup as db_full.zip or. SQL Server does not have problem with the file extension as long as the file is a valid file. Doing this way, it would be easier across your team (of 2 or 20) to recognize what is the backup type by looking at the file extension.
TRN for transactional (Upper case is not a must, only to highlight the file extension). Most of the time I had worked, seen or heard, it was a general industry wide accepted extension of. One of the answers is, for our convenience to remember what type of backup is stored with what type of extensions. What should be the extensions for backup files? So I thought why not I write a blog post on this. This looks like a simple question, but I had often seen in many forums this question being asked, I happened to answer a question on as recently as last week.