- Notes, cautions, and warnings
- Preface
- PowerProtect Data Manager for Microsoft Application Agent Overview
- PowerProtect Data Manager overview
- Supported Internet Protocol versions
- Introducing the Microsoft application agent
- VM Direct limitations
- Prerequisites
- Firewall and port considerations
- Role-based security
- Data-in-flight encryption
- PowerProtect Data Manager new deployment overview
- PowerProtect Data Manager existing deployment overview
- 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 and configure 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 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
- 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
- Support for existing Microsoft application agent backups with PowerProtect Data Manager
- Microsoft application agent for application-aware protection
- Managing Storage, Assets, and Protection
- Add protection storage
- Enable an asset source
- Delete an asset source
- Recommission the Microsoft application agent
- Setting the sysadmin privilege for Microsoft SQL Server hosts
- Discover a Microsoft SQL Server application host
- Replication triggers
- Add a protection policy for Microsoft SQL Server database protection
- Cancel a Microsoft application agent protection or restore job
- Add a service-level agreement
- Extended retention
- Edit the retention period for backup copies
- Delete backup copies
- Enable the Microsoft application agent after hostname change
- 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
- Performing Self-Service 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 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
- 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
- Microsoft SQL Server Best Practices and Troubleshooting
- Troubleshooting configuration issues
- Troubleshooting storage units
- Troubleshooting PowerProtect Data Manager UI display of localhost.localdomain hostname
- Troubleshooting agent registration
- Troubleshooting PowerProtect agent service installations
- Troubleshooting PowerProtect agent service operations
- Troubleshooting an error about lockbox stable value threshold after major system update
- Troubleshooting an asset discovery failure in an FCI environment
- Troubleshooting an error during configuration of Microsoft SQL Server application-aware protection
- Troubleshooting an issue with trailing spaces in Microsoft SQL Server database names
- Troubleshooting incorrect database size in PowerProtect Data Manager UI
- Multiple virtual networks (MVLANs) for Microsoft SQL Server application-aware protection
- Troubleshooting backup issues
- Troubleshooting backup failures when credentials include a backslash character (\)
- Troubleshooting memory or paging issues during Microsoft SQL Server backups
- Troubleshooting application-aware backup failure with msagentcon message
- Troubleshooting application-aware backup failure with persisted settings message
- Troubleshooting application-aware backup failure in multiple VLAN environment
- Troubleshooting application-aware backup failure after software update
- Troubleshooting a missing duration value for centralized backup
- Troubleshooting TLOG backup issue with mirrored database configuration
- Troubleshooting self-service T-SQL backups with an I/O error message
- Troubleshooting expired onboarded backup copies that are not deleted
- Troubleshooting backup failure during FCI cluster failover
- Troubleshooting Microsoft SQL Server databases skipped during virtual machine transaction log backup
- Troubleshooting Microsoft SQL Server application-aware backup error about disk.EnableUUID variable
- Troubleshooting restore issues
- Troubleshooting unprotected asset issue after disaster recovery
- Troubleshooting errors in the restore window after updating from PowerProtect Data Manager 19.8 or earlier
- Troubleshooting restores of multiple databases from multiple policies
- Troubleshooting centralized Microsoft SQL Server Application Direct restore operations
- Troubleshooting centralized Microsoft SQL Server Application Direct restore of backup tiered to the cloud
- Troubleshooting centralized Microsoft SQL Server virtual machine restore operations
- Troubleshooting virtual machine log restore failure with AAG named instances from SSMS UI
- Troubleshooting centralized Microsoft SQL Server virtual machine restore failure after VM Direct update
- Troubleshooting centralized Microsoft SQL Server virtual machine restore failure to Windows or CIFS shared path
- Troubleshooting VM Direct SSMS restore failure after PowerProtect Data Manager server update
- Troubleshooting VM Direct SSMS restore of replicated log backup
- Troubleshooting SSMS UI crash after switch from table restore to database restore tab
- Troubleshooting configuration issues
PowerProtect Data Manager 19.11 Microsoft SQL Server User Guide
Troubleshooting an asset discovery failure in an FCI environment
If reverse DNS lookup is not configured for the Microsoft SQL Server virtual server name used in a Failover Cluster Instance (FCI), asset discovery can fail and leave the assets unprotected.
As a workaround, configure the reverse DNS lookups for the Microsoft SQL Server virtual server names used in all Failover Cluster Instances.
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: <>()\