Back up open files and databases

Overview

The Code42 agent backs up open files by default so that users don't have to stop working in order to protect their files. Backing up files that are constantly being written to, such as databases or virtual machines, may require more consideration than backing up files that are changed less frequently, such as documents, pictures, or other media files. This article describes best practices for backing up open files and databases.

Considerations

• The Code42 agent backs up open files by default.
• The method used to back up open files varies by operating system.

Best practices for open files and databases

Most files that are constantly being written to require application-specific "hooks" to back up efficiently. Some examples of these types of files:

• Virtual machines
• SQL databases
• Application databases

Rather than relying on application-specific hooks, we recommend backing up application "dumps" (that is, exported or copied versions) to increase the efficiency and consistency of your backups and restores from these types of files. Creating an application dump saves a snapshot of the application's internal files. Then, use the Code42 agent to back up the dumped files.

Update backup interval for application dumps
When backing up large dump files, you may need to increase the backup interval to an hour (or more) to make sure the backup completes before the next scheduled backup starts. If you are backing up to multiple destinations, we highly recommend you make this change.

Application-specific resources

Application-specific links, and information about dumping an application state to a file for backup, are provided below for several common applications.

Non-Code42 products
​Information about products from other manufacturers is intended as a resource to help you get the most out of Code42 products. However, our Technical Support Engineers cannot provide direct assistance for these products. For assistance with products not developed by Code42, contact the product's manufacturer.

Access database

• Backing up an Access Database - from about.com

Act! database

• Dumping an Act! database

Adobe Lightroom

• Backing Up Lightroom's Catalog (Adobe help)

FileMaker Server

• Creating backups with FileMaker Server
• Tips on folders to exclude from backup

SQL databases

SQL Server

• SQL Server Management Studio

PostgreSQL

• pg_dump command - requires scripting
• Automated backup on Windows

MySQL

• MySQL on Linux
• AutoMySQLBackup - may work on Windows with Cygwin
• 10 ways to automatically backup a mysql database

Under the hood

Open file backup behavior varies on each operating system:

• Mac - A non-exclusive read is acquired on the file while backing up.
• Linux - A non-exclusive read is acquired on the file while backing up.
• Windows - Volume Shadow Copy Service (VSS) support can allow backup of open files in Windows. This is the same service that NT Backup uses. A VSS snapshot is created and then the snapshot is read for backup. It is possible that all the files needed for a usable backup are not backed up at the same time.

External resources

• Microsoft TechNet: Volume Shadow Copy Service Technical Reference
• Wikipedia: Shadow Copy

Related topics

• Backup
• How backup works
• Unable to back up files (Windows)