- Notes, cautions, and warnings
- Preface
- PowerProtect Data Manager Appliance for Microsoft Application Agent Overview
- PowerProtect Data Manager Appliance overview
- Introducing the Microsoft application agent
- Microsoft SQL Server application agent and File System agent coexistence
- VM Direct limitations
- Prerequisites
- Supported Internet Protocol versions
- Encryption in-flight
- PowerProtect Data Manager Appliance new deployment overview
- PowerProtect Data Manager Appliance existing deployment overview
- Security configuration
- Enabling the Microsoft Application Agent for Microsoft SQL Server
- Microsoft SQL Server data protection and replication requirements
- Microsoft SQL Server operational log files for backup and restore operations
- Protecting a stand-alone Microsoft SQL Server
- Protecting Microsoft SQL Server clustered environments
- Install, update, and uninstall the application agent
- Prerequisites
- Install the Microsoft application agent with the wizard
- Install the Microsoft application agent with a silent installation
- Update the Microsoft application agent
- Update the application agent in the PowerProtect Data Manager Appliance UI
- Uninstall the Microsoft application agent with the setup file
- Uninstall the Microsoft application agent with a silent uninstallation
- Required privileges for Application Direct backup and recovery
- Configure prerequisites for backups and restores of Always On availability groups
- Stagger Microsoft SQL Server discovery jobs in host scale-out environments
- Configure the database backup stripe level
- Enable multi-stream backups for Microsoft SQL Server protection policy
- Manage the Microsoft application agent
- Configurable ports for Microsoft SQL Server
- Support for existing Microsoft application agent backups with PowerProtect Data Manager Appliance
- Microsoft application agent for application-aware protection
- Managing Storage, Assets, and Protection
- Enable an asset source
- Delete an asset source
- Disable the Microsoft application agent
- Reinstall the Microsoft application agent
- Setting the sysadmin privilege for Microsoft SQL Server hosts
- Discover a Microsoft SQL Server application host
- Protection policies for Microsoft SQL Server database protection
- Supported protection policy purposes
- Supported protection policy objectives
- Replication triggers
- Roadmap for planning a Microsoft SQL Server database protection policy
- Before you add a protection policy for Microsoft SQL Server database protection
- Add a protection policy
- Asset-level configuration for protection policies
- Protection rules
- Cancel a Microsoft SQL application agent protection or restore job
- Edit the retention period for backup copies
- Delete backup copies
- Host CPU throttling
- Enable the use of pre-scripts and post-scripts with backups
- Migration between Application Direct and VM Direct configurations
- Enable the Microsoft application agent after Internet Protocol change
- Enable the Microsoft application agent after Microsoft SQL Server hostname change
- Enable the Microsoft application agent after Microsoft SQL Server host IP address change
- Reregister the agent after a PowerProtect Data Manager Appliance hostname or IP address change
- Enable the Microsoft application agent after reusing IP address from a different host
- Enable the Microsoft application agent after migration to a different Microsoft SQL Server host
- Enable the Microsoft application agent after Microsoft SQL Server upgrade
- Enable the Microsoft application agent after operating system upgrade
- Manage the PowerProtect agent service
- About the PowerProtect agent service
- Start, stop, or obtain the status of the PowerProtect agent service
- Troubleshooting PowerProtect agent service installations
- Troubleshooting PowerProtect agent service operations
- Register the PowerProtect agent service to a different server address on Windows
- Recovering the PowerProtect agent service from a disaster
- Manage the cloud tier operations with PowerProtect Data Manager Appliance for application agents
- Performing Self-Service Application Direct Backups of Microsoft SQL Server Databases
- Performing self-service Microsoft SQL Server database backups
- Overview of Application Direct with Microsoft SQL Server backups
- Best practices to back up Microsoft SQL Server with Application Direct
- Naming conventions for backups with Application Direct
- Circumstances that promote Microsoft SQL Server backups to level full
- Scheduling backup jobs
- Scheduling Microsoft SQL Server backups by using SQL Server Agent
- Configuring the SQL Server Agent to schedule jobs
- Changing the SQL Server Agent service login credentials
- Creating a proxy for the CmdExec subsystem
- Scheduling a CmdExec job
- Scheduling a CmdExec job on a single Microsoft SQL Server
- Scheduling a CmdExec job on multiple Microsoft SQL Servers
- Configuring primary and target SQL Server Agents
- Running a job on the target servers
- Scheduling a T-SQL job
- Scheduling Microsoft SQL Server backups by using Windows Task Scheduler
- Scheduling Microsoft SQL Server backups by using SQL Server Agent
- Performing manual backups
- Perform backups with the Microsoft app agent for Application Direct SSMS plug-in
- Back up Microsoft SQL Server with the Application Direct backup command
- Perform backups with T-SQL scripts
- Performing Self-Service Application Direct Restores of Microsoft SQL Server Databases
- Restoring a Microsoft SQL Server application host
- Best practices to restore Microsoft SQL Server with Application Direct
- Restoring Microsoft SQL Server databases
- Performing table-level recovery
- Performing Microsoft SQL Server disaster recovery
- Performing Centralized Restores of Application Direct Backups
- Centralized restores of Microsoft SQL Server Application Direct backups
- Considerations for centralized Microsoft SQL Server Application Direct restores
- Centralized restore of Microsoft SQL Server system databases
- Centralized restore of a Microsoft SQL Server stand-alone database
- Centralized restore of a Microsoft SQL Server AAG database
- Centralized restore of multiple Microsoft SQL Server databases
- Quick recovery for server DR
- Performing Self-Service Restores of Virtual Machine Backups
- Restoring a Microsoft SQL Server virtual machine backup
- Overview of Microsoft SQL Server virtual machine restore operations
- Prerequisites
- Restoring Microsoft SQL Server databases to a virtual machine
- Performing Microsoft SQL Server table-level recovery to a virtual machine
- Performing an instant access recovery
- Performing Centralized Restores of Virtual Machine Backups
- Centralized restores of Microsoft SQL Server virtual machine backups
- Considerations for centralized Microsoft SQL Server application-aware restores
- Centralized restore of Microsoft SQL Server system databases
- Centralized restore of a Microsoft SQL Server stand-alone database
- Centralized restore of a Microsoft SQL Server AAG database
- Centralized restore of multiple Microsoft SQL Server databases
- Protecting Virtual Machines Using the Transparent Snapshots Data Mover
- Overview of Transparent Snapshots Data Mover
- vSphere Installation Bundle monitoring and management
- Transparent snapshots data mover system requirements
- Prerequisites to virtual machine protection with the Transparent Snapshots Data Mover
- Configuring Microsoft SQL Server application-aware protection with TSDM
- Troubleshooting and limitations for SQL application aware policies with TSDM
- Migrating assets to use the Transparent Snapshots Data Mover
- Microsoft SQL Server Best Practices and Troubleshooting
- Glossary
PowerProtect Data Manager Appliance 5.16.0.0 Microsoft SQL Server User Guide
Prerequisites
Ensure that your environment meets the requirements for a new deployment or update of PowerProtect Data Manager Appliance.
Requirements:
NOTE:The most up-to-date software compatibility information for the
PowerProtect Data Manager Appliance software and the application agents is provided by the
E-Lab Navigator.
- A list of hosts that write backups to DD systems is available.
- DDOS version 6.2 or later and the
PowerProtect DD Management Center are required. All models of
DD systems are supported.
NOTE:PowerProtect DD Management Center is required with a DDOS version earlier than 6.1.2. With DDOS version 6.1.2 or later, you can add and use a DD system directly without PowerProtect DD Management Center.
- License: A trial license is provided with the PowerProtect Data Manager Appliance software. Customers can contact Customer Support for assistance with a permanent PowerProtect Data Manager Appliance license.
- Large environments require multiple PowerProtect Data Manager Appliance instances. Contact Champions.eCDM@dell.com for assistance with sizing requests.
- The
PowerProtect Data Manager 5500 Appliance download file requires the following:
- ESXi version 7.0 U3c or later.
- 10 vCPUs, 40 GB RAM, one 100 GB disk, and one 500 GB disk.
- The latest version of the Google Chrome browser to access the PowerProtect Data Manager Appliance UI.
- TCP port selected as the
PowerProtect Data Manager Appliance communications port from the supported port ranges 7000 to 7009 and 7012 to 7020. The selected port is open between
PowerProtect Data Manager Appliance and the application agent host.
NOTE:If a port is not selected from the port ranges, then the default port 7000 is used as the PowerProtect Data Manager Appliance communications port. VM Direct supports only the default port 7000.
- VMware ESXi server that hosts
PowerProtect Data Manager Appliance meets the following minimum system requirements:
- 10 CPU cores
- 40 GB RAM for PowerProtect Data Manager Appliance
- Seven disks with the following capacities:
- Disk 1—100 GB
- Disk 2—500 GB
- Disk 3—10 GB
- Disk 4—10 GB
- Disk 5—5 GB
- Disk 6—5 GB
- Disk 7—5 GB
- One 1-GB NIC
- Each Microsoft SQL Server host meets the following minimum system requirements:
- In a scaled environment:
- 8 CPU cores
- 16 GB of RAM
- In a stand-alone environment:
- 4 CPU cores
- 4 GB of RAM
- Microsoft SQL Server host must not have been previously registered to
PowerProtect Data Manager Appliance using a different protection type, either Application Direct or
VM Direct.
For example, if the Microsoft SQL Server host was previously registered to PowerProtect Data Manager Appliance with Application Direct during the Microsoft application agent installation, the protection type for that host may not be changed to VM Direct, even if the Microsoft application agent is uninstalled.
NOTE:It is recommended to use stripes only for large databases.
For performing a backup of 100 databases on a Microsoft SQL Server host, it is recommended to use 32 GB of RAM and the default stream count values of 4 for full and differential backups and 1 for log backups.
- In a scaled environment:
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\