NetBackup™ Web UI Microsoft SQL Server Administrator's Guide

Last Published:
Product(s): NetBackup & Alta Data Protection (10.3.0.1, 10.3)
  1. About NetBackup for SQL Server
    1.  
      Overview of NetBackup for SQL Server
    2.  
      Detailed features for NetBackup for SQL Server
  2. Installation and host configuration
    1. Planning the installation of NetBackup for SQL Server
      1.  
        NetBackup server and client requirements
      2.  
        Requirements for using NetBackup for SQL Server in a NetBackup cluster
      3.  
        License for NetBackup for SQL Server
    2. Configuring SQL Server hosts and user permissions
      1.  
        Installing the Veritas VSS provider for vSphere
    3.  
      Configuring the NetBackup services for SQL Server backups and restores
    4.  
      Configure local security privileges for SQL Server
    5.  
      Assign an RBAC role to the SQL Server administrator
    6.  
      Configuring the primary server host name for the SQL Server agent
    7.  
      Configure the number of jobs allowed for backup operations
    8.  
      Configure the Maximum jobs per client setting
  3. Managing SQL Server discovery and credentials
    1. About discovery of SQL Server objects
      1.  
        Discover advanced or basic availability groups on demand
      2.  
        Discover databases on demand
      3.  
        Discover read-scale availability groups
    2. About SQL Server credentials
      1.  
        Add a credential for SQL Server
      2.  
        Select a credential for a SQL Server instance or replica
      3.  
        View the credential name that is applied to an asset
      4.  
        Edit or delete a named credential
    3.  
      Remove SQL Server instances
    4.  
      Manually add a SQL Server instance
  4. Managing protection plans for SQL Server
    1.  
      About protecting SQL Server availability groups
    2. Create a protection plan to protect SQL Server assets
      1.  
        Schedules
      2.  
        Performance tuning and configuration options
    3.  
      Add SQL Server assets to a protection plan
    4.  
      Customize protection settings for a Microsoft SQL Server asset
    5.  
      Remove protection from SQL Server assets
    6.  
      Protect a SQL Server availability group that crosses NetBackup domains
  5. Configuring backup policies with Snapshot Client
    1.  
      About NetBackup Snapshot Client for SQL Server
    2.  
      How SQL Server operations use Snapshot Client
    3.  
      Snapshot methods
    4.  
      Configuration requirements for SQL Server snapshot and Instant Recovery backups
    5.  
      Configure a snapshot policy for SQL Server
    6.  
      Configure a policy for Instant Recovery backups of SQL Server
    7. Using copy-only snapshot backups to affect how differentials are based
      1.  
        Creating a copy-only backup (legacy SQL Server policies)
      2.  
        Creating an Instant Recovery backup that is not copy-only (legacy SQL Server policies)
    8. About SQL Server agent grouped snapshots
      1.  
        Restoring a database backed up in a group
  6. Viewing SQL Server asset details
    1.  
      Browse SQL Server assets
    2.  
      View the protection status of databases, instances, or availability groups
  7. Restoring SQL Server
    1.  
      Requirements for restores of SQL Server
    2.  
      Perform a complete database recovery
    3.  
      Recover a single recovery point
    4.  
      Options for SQL Server restores
    5.  
      Restore a database (non-administrator users)
    6.  
      Select a different backup copy for recovery
    7.  
      Restore a SQL Server availability database to a secondary replica
    8.  
      Restore a SQL Server availability database to the primary and the secondary replicas
  8. Using instant access with SQL Server
    1. Prerequisites when you configure an instant access SQL Server database
      1.  
        Hardware and configuration requirements of instant access
    2.  
      Things to consider before you configure an instant access database
    3.  
      Configure Samba users for SQL Server instant access
    4.  
      Configure an instant access database
    5.  
      View the livemount details of an instant access database
    6.  
      Delete an instant access database
    7.  
      Options for NetBackup for SQL Server instant access
    8.  
      NetBackup for SQL Server terms
    9.  
      Frequently asked questions
  9. Protecting SQL Server with VMware backups
    1. About protecting an application database with VMware backups
      1.  
        Limitations of VMware application backups
    2. Create a protection plan to protect SQL Server data with a VMware backup
      1.  
        Backup options and Advanced options
      2.  
        Exclude disks from backups
      3.  
        Snapshot retry options
    3.  
      Protect SQL Server data with a VMware backup
    4.  
      Restore SQL Server databases from a VMware backup
  10. Performance and troubleshooting
    1.  
      NetBackup for SQL Server performance factors
    2.  
      Troubleshooting credential validation
    3.  
      Troubleshooting VMware backups
    4.  
      SQL Server log truncation failure during VMware backups of SQL Server

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.

How to make Samba shares available to a Windows user
  • 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.

How to make Samba shares available to a SQL Server service
  • If the SQL Server service logs on as a Windows user, refer to the following topic:

    See How to make Samba shares available to a Windows user.

  • 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 Main > Settings > Security > Authentication > LocalUser.

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:

  • If you want, create a new local user with the following commands:

    • #useradd <username>

    • #passwd <username>

    You can also use an existing local user.

  • Run the following commands to create user credentials for Samba and enable the user:

    • smbpasswd -a <username>

    • smbpasswd -e <username>

For Build Your Own (BYO) users

For new users:

  1. Create a Linux user, then add the user to Samba.

    For example, the following commands create a test_samba_user for Samba service only.

    # adduser --no-create-home -s /sbin/nologin test_samba_user

    # smbpasswd -a test_samba_user

  2. Enter a new SMB password.

  3. Enter the new SMB password again.

    The new user is added.

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:

  1. Log in to the MSDP engine pod in a cluster using kubectl.

  2. Run the following command to log in to rshell in the MSDP engine.

    su - msdpadm

  3. Run the following rshell command to add a Samba user.

    setting samba add-user username=[samba user name] password=[samba password]

    For example,

    msdp-16.1] > setting samba add-user username=test_samba_user password=Te@Pss1fg0

    You can use the same command to update the password for an existing user.

    In AKS and EKS cloud platforms, the Samba rshell command configures Samba servers in all MSDP engines in a cluster.

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.