Veritas Access Solutions Guide for Software-Defined Storage (SDS) Management Platform

Last Published:
Product(s): Access (7.4.2)
Platform: Linux
  1. Introduction
    1.  
      About Veritas Access
    2.  
      About the SDS Management Platform
  2. Deploying the SDS Management Platform with Veritas Access
    1.  
      Deploying the SDS Management Platform
  3. Using the SDS Management Platform interface
    1.  
      Using the SDS Management Platform launchpad
    2.  
      Using the Infrastructure application
    3.  
      Using the Long Term Retention Storage (LTR) application
    4.  
      Operation icons on the SDS Management Platform interface
  4. Setting up SSL in the SDS Management Platform
    1.  
      About setting up SSL in the SDS Management Platform
    2.  
      Generating and installing a new certificate
    3.  
      Creating and upgrading a trust store
  5. Performing authentication
    1.  
      Authentication modules
    2.  
      Certificate-based client authentication
  6. System backup and restore
    1.  
      About system backup and restore
    2.  
      Automatic backups
    3.  
      Manual backups
  7. Troubleshooting
    1.  
      Log locations
    2.  
      Diagnostic reports
    3.  
      Java Virtual Machine (JVM) parameters
    4. SDS Management Platform known issues
      1.  
        If multiple bucket creation requests with different inputs for attributes such as size and layout are in progress in parallel, then a bucket can get created with incorrect attributes
      2.  
        When editing a storage resource or backup server, an Advanced button is available that shows options that you should not change
      3.  
        If you add a Veritas Access cluster where the host includes the protocol (such as, https://10.20.30.40), the provider gets added and collects data but running the LTR workflow fails
      4.  
        When you create a bucket, the status of the task appears as DONE, even though the creation is still in progress
      5.  
        Clicking on a non-mapped Veritas Access cluster directs you to an empty wiki page which shows a table and some data
      6.  
        If you restart the operating system, the SDS Management Platform does not start automatically
      7.  
        When you add a storage resource or backup server, the added resource is not automatically visible
      8.  
        After the SDS log is rotated, the log messages from either Veritas Access or the SDS plugin go to the rotated file instead of the new file
      9.  
        Some of the storage resources may appear as faulted and a warning sign appears next to the cluster IP address in the Infrastructure> Storage Resources page
      10.  
        Creation of STU fails if the S3 user is changed
    5.  
      Software limitations

Diagnostic reports

You can trigger the diagnostic report from Settings ->Diagnostic Information. It is a general-purpose tool that streamlines the interaction with the SDS Management Platform support. The backend service runs within a Java Virtual Machine (JVM), that in turn runs within a service wrapper which ensures that the JVM is kept running. The service is normally started and stopped using the Windows services.msc or by a Linux service init script. If the service has completely stopped responding, first attempt to connect to the service using the Command Line Interface (CLI) and, if this is possible, produce a diagnostic feedback zip file (which causes the in-memory DB to be persisted) with the following command:

# getDiagnosticService createDiagnosticFeedback -addMemoryDump false

The diagnostic zip file is written to the /webapps/ROOT/diag folder and is named diag+ timestamp.zip. This causes the in-memory DB and the RDF triple store to be written to disk. Then, try to restart the service within the CLI using the restartService command. If all else fails, shutdown the operating system cleanly and restart. The database is always written in a consistent way, so it should always be readable.