Please enter search query.
Search <book_title>...
NetBackup™ Snapshot Manager Install and Upgrade Guide
Last Published:
2022-09-08
Product(s):
NetBackup & Alta Data Protection (10.1)
- Introduction
- Section I. NetBackup Snapshot Manager installation and configuration
- Preparing for NetBackup Snapshot Manager installation
- Deploying NetBackup Snapshot Manager using container images
- Deploying NetBackup Snapshot Manager extensions
- Installing the Snapshot Manager extension on a VM
- Installing the Snapshot Manager extension on a managed Kubernetes cluster (AKS) in Azure
- Installing the Snapshot Manager extension on a managed Kubernetes cluster (EKS) in AWS
- Installing the Snapshot Manager extension on a managed Kubernetes cluster (GKE) in GCP
- NetBackup Snapshot Manager cloud plug-ins
- NetBackup Snapshot Manager application agents and plug-ins
- Installing and configuring Snapshot Manager agent
- Configuring the Snapshot Manager application plug-in
- Microsoft SQL plug-in
- Oracle plug-in
- NetBackup protection plan
- Protecting assets with NetBackup Snapshot Manager's agentless feature
- Volume Encryption in NetBackup Snapshot Manager
- NetBackup Snapshot Manager security
- Preparing for NetBackup Snapshot Manager installation
- Section II. NetBackup Snapshot Manager maintenance
- NetBackup Snapshot Manager logging
- Upgrading NetBackup Snapshot Manager
- Uninstalling NetBackup Snapshot Manager
- Troubleshooting NetBackup Snapshot Manager
Microsoft SQL plug-in configuration requirements
Before you configure the plug-in, ensure that your environment meets the following requirements:
This plug-in is supported in Microsoft Azure, Google Cloud Platform and Amazon AWS environments.
A supported version of Microsoft SQL server is installed on the Windows instance.
The SQL server instances that you want to protect must be running on a non-system drive.
Snapshot Manager also does not support SQL server instances that are installed on a mount point.
Snapshot Manager uses the Microsoft Volume Shadow Copy Service (VSS).
Ensure that you configure VSS to store shadow copies on the same drive (the originating drive) where the database resides.
See Configuring VSS to store shadow copies on the originating drive.