PowerProtect Data Manager 19.9 Microsoft Application Agent SQL Server User Guide
- 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 for SQL
- 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 SQL
- Microsoft SQL Server data protection and replication requirements
- Microsoft SQL operational log files for backup and restore operations
- Protecting a stand-alone SQL Server
- Protecting 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
- 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 SQL discovery jobs in host scale-out environments
- Configure the database backup stripe level
- Enable multi-stream backups for SQL protection policy
- Manage the Microsoft application agent for SQL
- Support for existing Microsoft application agent backups with PowerProtect Data Manager
- Microsoft application agent for SQL Server application-aware protection
- Troubleshooting an error about lockbox stable value threshold after major system update
- Troubleshooting an error during configuration of SQL Server application-aware protection
- Troubleshooting self-service T-SQL backups with an I/O error message
- Managing Storage, Assets, and Protection
- Add protection storage
- Enable an asset source
- Delete an asset source
- Setting the sysadmin privilege for Microsoft SQL hosts
- Discover a SQL application host
- Add a protection policy for SQL database protection
- Cancel a SQL application agent protection or restore job
- Add a Service Level Agreement
- Extended retention
- Edit the retention period for backup copies
- Delete backup copies
- 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
- Troubleshoot the 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 Databases
- Performing self-service SQL database backups
- Overview of Application Direct with SQL Server backups
- Best practices to back up SQL Server with Application Direct
- Naming conventions for backups with Application Direct
- Circumstances that promote SQL Server backups to level full
- Scheduling backup jobs
- Scheduling 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 SQL Server
- Scheduling a CmdExec job on multiple SQL Servers
- Configuring primary and target SQL Server Agents
- Running a job on the target servers
- Scheduling a T-SQL job
- Scheduling SQL Server backups by using Windows Task Scheduler
- Scheduling 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 SQL Server with the Application Direct backup command
- Perform backups with T-SQL scripts
- Performing Self-Service Restores of Microsoft SQL Databases
- Restoring a SQL application host
- Best practices to restore SQL Server with Application Direct
- Restoring SQL Server databases
- Performing table-level recovery
- Performing SQL Server disaster recovery
- Performing Centralized Restores of SQL Application Direct Backups
- Centralized restores of SQL Server Application Direct backups
- Considerations for SQL centralized restores
- Centralized restore of SQL system databases
- Centralized restore of a SQL stand-alone database
- Centralized restore of a SQL AAG database
- Centralized restore of multiple SQL databases
- Troubleshooting of SQL centralized restore operations
- Performing Self-Service Restores of SQL Virtual Machine Backups
- Restoring a SQL Server virtual machine backup
- Overview of SQL Server virtual machine restore operations
- Prerequisites
- Restoring SQL Server databases to a virtual machine
- Performing SQL Server table-level recovery to a virtual machine
- Performing an instant access recovery
- Performing Centralized Restores of SQL Virtual Machine Backups
- Centralized restores of SQL Server virtual machine backups
- Considerations for SQL centralized restores
- Centralized restore of SQL system databases
- Centralized restore of a SQL stand-alone database
- Centralized restore of a SQL AAG database
- Centralized restore of multiple SQL databases
- Troubleshooting of SQL centralized restore operations
Loading, Please wait
Troubleshooting self-service T-SQL backups with an I/O error message
When the Microsoft application agent is integrated with the PowerProtect Data Manager, a successful self-service Transact-SQL (T-SQL) backup might display the following error message:
IO error: Permission denied
To prevent this error message during self-service T-SQL backups, ensure that the SQL instance service runs as the OS/SQL user, instead of NT SERVICE\<instance_name>.
Data is not available for the Topic
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: <>()\