Veritas Access Solutions Guide for NetBackup

Last Published:
Product(s): Appliances (Version Not Specified)
Platform: 3340
  1. Veritas Access integration with NetBackup
    1.  
      About Veritas Access
    2.  
      About Veritas Access as a NetBackup client
    3.  
      About Veritas Access as backup storage for NetBackup
    4.  
      Use cases for long-term data retention
  2. System requirements
    1.  
      Supported configurations and versions for NetBackup with Veritas Data Deduplication
    2.  
      Supported configurations and versions for NetBackup with CloudCatalyst
  3. Configuring Veritas Data Deduplication with Veritas Access
    1.  
      About Veritas Data Deduplication
    2.  
      Add-on license for using Veritas Data Deduplication
    3.  
      Benefits of using Veritas Data Deduplication with Veritas Access
    4.  
      Configuring Veritas Data Deduplication using the GUI
    5.  
      Configuring Veritas Data Deduplication using the Veritas Access command-line interface (CLI)
    6.  
      Configuring a Veritas Data Deduplication storage unit on NetBackup
    7.  
      Configuring global deduplication using the Veritas Data Deduplication storage server across the domain
  4. Migrating the NetBackup images from existing storage to Veritas Data Deduplication storage
    1.  
      Migrating the NetBackup image from OpenDedup/CloudCatalyst/S3 to Veritas Data Deduplication storage
  5. Configuring Veritas Access as a cloud storage server with NetBackup CloudCatalyst
    1.  
      Creating an S3 bucket on Veritas Access for storing deduplicated backup data from NetBackup
    2.  
      Creating a Media Server Deduplication Pool (MSDP) for primary backup using NetBackup
    3.  
      Configure Veritas Access as a cloud storage server on NetBackup server using CloudCatalyst
    4.  
      Enabling SSL on Veritas Access
  6. Configuring backup and restore using NetBackup policies
    1.  
      Storage Lifecycle Policies
    2.  
      Backup and restore
    3.  
      Running a backup policy manually
    4.  
      Restoring backed up files
  7. Configuring Veritas Access with the NetBackup client
    1.  
      Prerequisites for configuring the NetBackup client
    2.  
      About the NetBackup Snapshot Client
    3.  
      About NetBackup snapshot methods
    4.  
      Enabling or disabling the NetBackup SAN client
    5.  
      Workflow for configuring Veritas Access for NetBackup
    6.  
      Registering a NetBackup master server or adding an optional media server
    7.  
      Displaying the excluded files from backup
    8.  
      Displaying the included and excluded files for backups
    9.  
      Adding or deleting patterns to the list of files in backups
    10.  
      Configuring or resetting the virtual IP address used by NetBackup
    11.  
      Configuring the virtual name of NetBackup
    12.  
      Displaying the status of NetBackup services
    13.  
      Configuring backup operations using NetBackup or other third-party backup applications
    14.  
      Performing a backup or restore of a Veritas Access file system over a NetBackup SAN client
    15.  
      Performing a backup or restore of a snapshot
    16.  
      Installing or uninstalling the NetBackup client
    17.  
      Configuring Veritas Access for NetBackup cloud storage
  8. Troubleshooting
    1.  
      Unmounting the SDFS volume before restarting Veritas Access or the NetBackup media server
    2.  
      Upgrading SDFS from earlier versions to 7.4.2
    3.  
      Log locations for troubleshooting
    4.  
      Changing log levels
    5.  
      Additional resources
    6.  
      Generating Veritas Access S3 server keys using the helper script
    7.  
      OpenDedup tuning recommendations
  9.  
    Index

Changing log levels

The logging framework for SDFS is updated to log4j2. For SDFS 7.4.1 and later releases, changing the log levels using the volume.xml is not effective. You have to update the /etc/sdfs/log4j2.xml file.

To change the log level:

  • Edit the /etc/sdfs/log4j2.xml file.

  • Go to the Loggers section.

  • Search for Logger name="sdfs"

  • Set the level to an appropriate parameter.

For example:

<Loggers>
<Logger name="sdfs" additivity="false" level="debug">
<appender-ref ref="sdfsLog" />

The following log levels are available:

  • trace

  • debug

  • info

  • warn

  • error

  • fatal

You can find more details about the log42.xml parameters at https://logging.apache.org/log4j/log4j-2.2/manual/configuration.html.