Veritas NetBackup™ Self Service Configuration Guide

Last Published:
Product(s): NetBackup (8.2)
  1. Licensing
    1.  
      Applying the full License
  2. Configuring a Self Service solution
    1.  
      About configuring a Self Service solution
    2.  
      Self Service scheduled backup
    3.  
      Configuration checklist
  3. Configuring a NetBackup master server
    1.  
      About configuring the NetBackup master server
    2.  
      Enabling communication with a Windows NetBackup master server
    3.  
      Enabling communication with a UNIX NetBackup master server
    4.  
      Enabling communication with a NetBackup appliance
    5.  
      Enabling communication with a NetBackup master server using the REST API
    6.  
      Creating NetBackup Template Policies
  4. Configuring Self Service
    1.  
      About Self Service configuration
    2.  
      Configuring backup servers
    3.  
      Configuring protection
    4.  
      Configuring the Backup Now form
    5.  
      Configuring tenants
    6.  
      Access rights
    7.  
      Registering computers
    8. Configuring the home page
      1.  
        Home page integration settings
  5. Customizing Self Service
    1.  
      Language settings
    2.  
      Creating or customizing a request form
    3.  
      Themes
    4.  
      Notices
  6. User authentication methods
    1.  
      About user authentication methods
    2.  
      Forms based authentication
    3.  
      Windows Authentication
    4.  
      Active Directory Import
    5.  
      Configuring Self Service to use Federated Single Sign-On
  7. Troubleshooting
    1.  
      About troubleshooting
    2.  
      Where to find troubleshooting information
    3.  
      Impersonation of a tenant user
    4.  
      Issues with Remote PowerShell to Windows master servers
  8. Appendix A. NetBackup policy types
    1.  
      List of NetBackup policy types
  9. Appendix B. Dashboard traffic light status and usage
    1.  
      About dashboard traffic light status and usage
    2.  
      Assets with a protection type
    3.  
      Assets without a Protection Type
    4.  
      Usage and Charging
  10. Appendix C. Synchronizing data from NetBackup
    1.  
      About synchronizing data from NetBackup
  11. Appendix D. NetBackup Self Service data caching process
    1.  
      About NetBackup Self Service data caching process
    2.  
      NetBackup Data Synchronization
    3.  
      Backup Now
    4.  
      Protect
    5.  
      Unprotect
  12. Appendix E. Integration settings
    1.  
      About integration settings
    2.  
      NetBackup Adapter
    3.  
      NetBackup Adapter Usage
    4.  
      NetBackup Adapter Access Rights
    5.  
      Action Request Types
    6.  
      vCloud Director import
  13. Appendix F. REST API
    1.  
      About the REST API
  14. Appendix G. Glossary
    1.  
      Glossary

Windows Authentication

To use Windows Authentication, the users must be set up in the database with the user names that match the users' domain names. This format is either DOMAIN_NAME\username or username. The format depends on the system setting.

Configure Remove Domain Name in Admin > Settings > System Configuration. Switch it on if it uses firstname.lastname or switch off if it uses DOMAIN\firstname.lastname.

Once at least one Windows user has access to the Administration area, disable both Anonymous Authentication and Forms Authentication in IIS. Then enable Windows Authentication. This configuration in IIS insures the web.config file is updated and Self Service address is changed accordingly.

You can only use the shipped admin user ID to access the system until Windows Authentication is configured in IIS. After that point, no manual logon is available.

Note:

If you use Active Directory to synchronize users, ensure that at least one user is associated to the Supervisor access profile on initial import. Otherwise, access to the Admin area is compromised.

Note:

These instructions only apply to configuration on initial implementation of the system and are not appropriate for later changes to the logon protocol. This limitation is due to effect on historical data.