Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -105,9 +105,9 @@ Designing an effective backup and restore strategy requires careful planning, im

The accounts that perform backup or restore operations shouldn't be granted more privileges than necessary. Review [backup](../../t-sql/statements/backup-transact-sql.md#permissions) and [restore](../../t-sql/statements/restore-statements-transact-sql.md#permissions) for specific permission details. It's recommended that backups are [encrypted](../security/encryption/transparent-data-encryption.md) and, if possible, [compressed](backup-compression-sql-server.md).

To ensure security, backup files should have extensions that follow proper conventions:
Use consistent file extensions to make backups easier to identify and manage. SQL Server doesn't require or enforce these extensions, but following a convention helps with operational tasks such as configuring antivirus exclusions for backup files. For more information, see [Configure antivirus software to work with SQL Server](/troubleshoot/sql/database-engine/security/antivirus-and-sql-server).

- Database backup files should have the `.BAK` extension
- Database backup files should have the `.BAK` extension.
- Log backup files should have the `.TRN` extension.

### Use Separate Storage
Expand Down