DPX Protecting SQL Server: General Considerations

DPX Block Data Protection for SQL Server supports the following:

  • Backing up supported SQL Server databases

  • Backing up several instances installed on one server

  • Backup verification. See Chapter 24: Verifying Application Backups.

  • SQL log truncation after backup.

  • Restoring supported SQL Server databases to original file paths

  • Restoring databases with log files and data files being copied to a new directory

Note. SQL Server does not support restoring databases to new locations for the databases master and model

  • Restoring databases to the original and new SQL Server instance

See also. For the latest system compatibility details regarding supported hardware, file systems, applications, operating systems, and service packs, see the Compatibility Guide

Note the following considerations for SQL Server Protection:

  • Do not install SQL Server on %SystemRoot% (which is usually the C: drive). Doing so may interfere with Block restore and Instant Access.

  • SQL Server 2012 AlwayOn Availability Groups are supported. See Protecting AlwaysOn Availability Groups: Concepts and Considerations.

  • You cannot specify multiple directories as destinations for data files or log files during restore.

  • You cannot restore a database to a new name.

  • For Block backups of SQL Servers:

    • If Backup and Truncate SQL Logs option is set to Yes, SQL Server transaction logs are truncated on the source database server after the backup completes. To find the backed up SQL logs, refer to the message BACKUP LOG <database-instance> TO DISK... in the Job Log or to Event 18265 in the Application Event Log.

    • If Backup and Truncate SQL Logs option is set to No, SQL Server transaction logs are not truncated and will therefore continue to grow on the source database server. To truncate translation logs, run SQL Server maintenance on the source machine. No is the default.

    • Note that Backup and Truncate SQL Logs must be set to Yes to enable Point-in-Time restore.

  • Point-in-Time restore of Block backups for SQL is supported as follows:

    • At least one incremental backup must have been run after the base backup that precedes the point in time. The incremental backup job definition must have had the Backup and Truncate SQL Logs option set to Yes.

    • The Point in Time Restore option must be selected and populated, under Restore Destination Options. The point-in-time must be before the latest (most recent) incremental backup.

    • SQL point-in-time restore is supported for restores to original location only.

    • SQL point-in-time restore is supported only against backups run from DPX 4.5.3 or later.

    • SQL point-in-time restore is not supported for SQL AlwaysOn availability group databases.

  • When restoring to a new location, your original production database is removed from the original disk. For more information, read knowledge base article 41655.

  • During SQL Server restores, the SQL Server Management Studio must be closed.

  • DPX Block Data Protection agents use Microsoft Volume Shadow Copy Service to back up Microsoft SQL Server.

  • DPX Block Data Protection for SQL Server is not supported for client nodes running Windows Server 2012 with ReFS enabled. See Catalogic DPX Block Data Protection.

Last updated