NetBackup™ for Microsoft SQL Server Administrator's Guide
- About NetBackup for SQL Server
- Installation
- Host configuration and job settings
- Installing the Veritas VSS provider for vSphere
- Configuring RBAC for SQL Server administrators
- Managing SQL Server assets and their credentials
- About discovery of SQL Server objects
- About registering SQL Server instances and availability replicas
- Configuring backups with SQL Server Intelligent Policy
- Performance tuning and configuration options
- Protecting SQL Server availability groups
- Protecting SQL Server availability groups with intelligent policies
- Protecting SQL Server availibility groups with batch file-based policies
- About protecting the preferred replica in a SQL Server availability group (batch file-based policies)
- About protecting a specific node in a SQL Server availability group (batch file-based policies)
- About protecting the preferred replica in a SQL Server availability group (batch file-based policies)
- Protecting SQL Server with VMware backups
- About protecting an application database with VMware backups
- Create a protection plan to protect SQL Server data with a VMware backup
- Configuring backup policies with Snapshot Client
- Using copy-only snapshot backups to affect how differentials are based
- About SQL Server agent grouped snapshots
- Protecting SQL Server in a cluster environment
- Managing protection plans for SQL Server
- Restoring SQL Server with the NetBackup web UI
- Using instant access with SQL Server
- Prerequisites when you configure an instant access SQL Server database
- Configuring batch-file based policies for SQL Server backups
- Requirements to use batch files with NetBackup for SQL Server
- Schedule properties for SQL Server batch file-based policies
- Configure a batch file-based policy for a user-directed backup of read-only filegroups
- Performing backups and restores with the NetBackup MS SQL Client
- Redirect a SQL Server database to a different host (NetBackup MS SQL Client)
- Restoring multistreamed SQL Server backups
- Using NetBackup for SQL Server with multiple NICs
- Performance and troubleshooting
- About debug logging for SQL Server troubleshooting
- About disaster recovery of SQL Server
- Appendix A. Other configurations
- About SQL Server backups and restores in an SAP environment
- About NetBackup for SQL Server with database mirroring
- Appendix B. Register authorized locations
Configure Samba users for SQL Server instant access
A NetBackup client may need Samba user credentials to access Samba shares. You can configure Samba local users for SQL Server instant access on the corresponding storage server.
If the Samba service on a storage server is part of Windows domain, the Windows domain users can be used as Samba users.
For Azure Kubernetes Service (AKS) and Amazon Elastic Kubernetes Service (EKS) cloud platforms, only Samba local user can access Samba share. You must add Samba users to access the Samba share.
During SQL Server instant access, the SQL Server service needs to access the Samba share. If a Windows user is specified to start the instant access database, that Windows user also needs to access the Samba share.
If the Windows user is a domain user and is in the same domain as the storage server:
The Windows user can directly access the Samba share and no configuration is required.
If the Windows user is not a domain user, or is not in the same domain as the storage server:
Save the Samba user credentials for the Windows user by running the following command and enter the Samba account password:
cmdkey /add:<Samba hostname> /user:<Samba account username> /pass
The Windows user accesses the Samba share using the credentials.
If the SQL Server service logs on as a Windows user, refer to the following topic:
If the SQL Server service logs on as a service account (for example, NT Service\MSSQLSERVER)
If the SQL Server Windows host is in the same domain as the storage server:
SQL Server service is authenticated as the domain host and no configuration is required.
If the SQL Server Windows host is not in any domain and Samba guest access is not disabled, the SQL Server service can access the share as guest and no configuration is required.
For all other scenarios, create a Samba session for the SQL Server service account by running following SQL statement:
xp_cmdshell 'net use \\<Samba hostname>\<sharename> <Samba account password> /user:<Samba account username>'
The SQL Server service accesses the Samba share using the provided Samba user credentials. The share name must be a share that is available on the storage server. If there is no share at the time, you must create one.
The Samba session is valid until the next restart. You must run the command again after restart to get Samba access.
If xp_cmdshell is not enabled for the SQL Server, use the following commands to enable or disable xp_cmdshell.
-- enable xp_cmdshell EXEC sp_configure 'show advanced options', '1' RECONFIGURE EXEC sp_configure 'xp_cmdshell', '1' RECONFIGURE
-- disable xp_cmdshell EXEC sp_configure 'show advanced options', '1' RECONFIGURE EXEC sp_configure 'xp_cmdshell', '0' RECONFIGURE
The following table describes how to add or manage Samba users if the Samba service is not part of Windows domain.
Table: Steps to add or manage Samba users
User | Steps |
---|---|
For NetBackup Appliance users | For NetBackup Appliance, local users are also Samba users. To manage local users, logon to CLISH and select .The Samba password is the same as the appliance local user's logon password. |
For Flex Appliance users | For a Flex Appliance application instance, log in to the instance and add any local user to Samba, as follows:
|
For Build Your Own (BYO) users | For new users:
For existing users: If you want to add an existing user to the Samba service, run the following command: smbpasswd -a test_samba_user |
For AKS and EKS platform users | For new users:
|
To automatically start the SQL Server database, ensure that you can access the share when you log on with the instance credentials from the web UI.
For the cloud platforms such as AKS and EKS, add the Samba user and each MSDP engine host name in Windows credential manager. This action allows the NetBackup client can connect to the Instant Access Samba share automatically.