Microsoft SQL Server

Zmanda Pro empowers you to safeguard your SQL Server databases with ease and efficiency. Here's a breakdown of the key features:

• Broad Compatibility: Backs up SQL Server versions 2005 and later, including the latest 2022 edition.

• Cloud-Optimized VDI Technology: Leverages VDI (Virtual Device Interface) for efficient, cloud-based backups without data spooling to your local disk. This reduces strain on your on-premises infrastructure.

• Simplified Monitoring: Unlike traditional methods, Zmanda Pro provides a streamlined experience. You won't be overwhelmed with progress bars or estimated times during backups, allowing you to focus on other tasks.

Setting Up the Connection

Before you can back up your SQL Server databases, you'll need to provide Zmanda Pro with some connection details:

Local Connections:

Zmanda Pro can only connect to SQL Server instances running on the same machine where you're running the backup software. This local approach ensures efficient data transfer.

Instance Name:

If you have a single instance of SQL Server (the default installation), leave this field blank. If you have multiple named instances of SQL Server, enter the specific instance name you want to back up.

Shared Memory Protocol:

For Zmanda Pro to connect, the "Shared Memory" protocol must be enabled in SQL Server Configuration Manager. This is a common method for local communication within the machine. If you encounter connection issues, verify that "Shared Memory" is enabled.

Advanced Details (Optional):

• Driver Selection: Zmanda Pro automatically prioritizes the optimal driver (MSOLEDBSQL, SQLNCLI11, SQLOLEDB) for your environment, ensuring compatibility. You can view your installed drivers using the methods mentioned in the original document.

• Authentication: Zmanda Pro offers flexibility for connecting to your databases: 1. Windows Authentication: Use your existing Windows credentials or the credentials of the "backup.elevator" service account. 2. SQL Server Authentication: Enter a valid SQL Server username and password.

Multiple Instances:

Zmanda Pro simplifies backing up from multiple SQL Server instances. You can:

Select the desired instance from the dropdown menu populated with available instances. To use the default instance, leave the field empty.

Backup Modes:

Zmanda Pro offers several backup modes to suit your specific needs and database environment. The available options are:

Default Mode: Full Backup (Recommended)

• Zmanda Pro performs a complete copy of the selected databases (BACKUP WITH COPY_ONLY T-SQL equivalent).

• Zmanda Pro's built-in deduplication optimizes storage usage in the cloud by eliminating redundant data across backups.

• This method ensures a full restoration point for your databases in case of data loss.

Advanced Modes (Optional):

These options leverage SQL Server's native backup functionality and require more management overhead. They are suitable for experienced users with specific requirements.

• Differential Backups:

  • Creates smaller backups containing only the changes since the last full backup (BACKUP WITH DIFFERENTIAL T-SQL equivalent).

  • Requires creating separate backup jobs for both full and differential backups.

  • Ensures efficient storage usage but necessitates careful management:

    • Other backup systems shouldn't reset the last base backup.

    • Successful differential backups require recent successful full backups.

    • Regular full backups minimize differential overhead.

    • Retention policies need strict management for complete recovery.

• Log Backups:

  • Captures changes made since the last full backup using SQL Server's transaction log backups (BACKUP LOG T-SQL equivalent).

  • Enables very frequent backups and potentially faster restores.

  • Requires regular full backups and careful retention management for a complete recovery point.

  • The database Recovery Model in SQL Server must be set to "Full" or "Bulk Logged".

Choosing the Right Backup Mode:

• For most users, the default "Full Backup" is the best choice due to its simplicity and reliability.

• Consider differential or log backups only if you have specific performance needs or a deep understanding of managing these advanced options.