Home > Storage > Data Storage Essentials > AppSync > Dell AppSync Integration with Microsoft SQL Server > Overview
Every SQL Server database has a transaction log. AppSync supports SQL Server transaction log backups.
AppSync writes the log backups to the SQL Server default backup directory by default. It can be customized in the service plan menu. For database log backups in a failover cluster environment, use shared storage or a network share so the log backups are written to the same location.
Transaction log backups can be used during the recovery of a production database, or when making a copy of a production database. Depending on the database recovery model, the transaction log volume can become full. In order to prevent the accumulation of logs, regularly run transaction log backups with the Truncate the logs option enabled.
AppSync can also back up transaction logs in Always On Availability Group (AAG) environments. AppSync can backup the primary or secondary database copy. When truncation is enabled, initiate the truncation process by backing up either the primary or secondary database transaction log.
Transaction log backups are supported using streaming backup only - they are not supported using VSS hardware snapshot technology. AppSync backs up transaction logs to a file. The file can be written to a local volume or network share using a UNC path; specified in the Backup path option.
Note: AppSync Supports UNC Paths on a network share only if both machines are in the same domain.
Configure AppSync to enable transaction log backups for a SQL Server service plan. Select the Enable log backup checkbox on the Create the Copy options page. The Transaction Log Backup Options dialog box is enabled as depicted in the following figure, where the Truncate the logs option is selected. Several other options to customize are available based on the environment.
Note: Transaction log backups always run sequentially.