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

Manual backups

You can take a manual backup of the system at any time using the backup command from the CLI. The backup is available in the standard format at /backup/ timestamp/dbcore.zip.

You can backup the semantic datastore using the following command:

getSemanticService getbackupService backupDBs

The backup is available in the standard format in the /backup/ date-timestamp/ date-timestamp_diagnosticfeedback.zip folder. This functionality is also available through Settings -> Backup. The backup mechanism allows for saving the database at any time and restoring it when needed. You can save the history repository or the central database by selecting the type of backup. You have an option to make a diagnostic feedback backup. The diagnostic backup saves the database, the history repository, wiki pages, the config folder, and the config.prop file. This can be kept for later use or downloaded for making a diagnosis about the application.

You can also take a full backup which save all the data, pages, and configuration of the SDS Management Platform.

To take a manual backup

  1. Go to Settings -> Backup.
  2. Select the database that you want to back up from the menu. Select dbmodel if you want to backup the main database where imported and authored triples are stored. Select historymodel if you want to backup the database that stores the historical data that is created by the historical data provider.
  3. Click Backup. The backup of the database is available and can be used in the future to restore the database to the current state or be downloaded as a .trig file.