Search <book_title>...

Veritas Velocity™ User's Guide

Last Published: 2017-11-28

Product(s): Velocity (2.8)

Getting to know Velocity
1. Introducing Velocity
2. How to access the Velocity Cloud Console
3. About the Velocity Appliance
4. About the Velocity Storage Server administration interfaces
5. Using the Velocity shell menu
Setting up Velocity
1. Velocity administrator's checklist for setting up Veritas Velocity
2. Database administrator's checklist for setting up Veritas Velocity
3. Sandbox user's checklist for setting up Veritas Velocity
4. How to set up the Velocity Storage Server
5. How to set up the Velocity Client
6. Deleting a Velocity Client
7. Configuring a proxy server for Velocity
8. Required and optional ports for Velocity
9. Installing the NetBackup Client on the Velocity Storage Server
Setting up the Velocity on-premises management server
1. How to set up the Velocity on-premises management server
2. Deploying the Velocity on-premises management server image on a virtual machine
3. Configuring the network settings for the Velocity on-premises management server
4. Configuring Active Directory/LDAP settings on the Velocity on-premises management server
5. Adding users to the Velocity on-premises management server
Upgrading Velocity
1. How to upgrade to Velocity version 2.8
2. Finding the Velocity Storage Server and Velocity Client version numbers
3. Downloading and transferring software updates to the Velocity Storage Server
4. Removing previous upgrade files
5. Upgrading the Velocity Storage Server
6. Upgrading the Velocity Client for Linux
7. Upgrading the Velocity Client for Windows
8. Upgrading the Velocity Client for Solaris
Velocity Storage Server
1. About the Velocity Storage Server
2. Viewing physical storage usage on the Velocity Storage Server
3. About reclaiming storage space on the Veritas Velocity Storage Server
4. Increasing meta and data storage capacity on the Velocity Storage Server
5. Deregistering a Velocity Storage Server
6. How to reset the Velocity Storage Server
Users and roles
1. How to configure users and roles in Velocity
2. Adding users
3. Role-based access control
4. Adding roles
5. Deleting roles
6. Viewing details about all users and roles
7. Assigning users to an existing role
8. Removing users from a role
9. Changing the database sources that are assigned to a role
Oracle database ingestion using Velocity
1. How to provide copies of Oracle databases for sandboxes in Velocity
2. Adding an Oracle database to ingest into Velocity
3. Ingesting an Oracle database into Velocity for the first time
4. Ingesting an Oracle database again after the first ingest
5. Canceling an Oracle database ingestion
6. How to use copy preparation to mask or sanitize sensitive data
7. Ingesting an Oracle database into Velocity from the command line
8. About setting custom initialization parameters for a sandbox for an Oracle database copy
9. Editing default options for the ingest method for Oracle databases
Oracle database ingestion using NetBackup CoPilot
1. How to set up NetBackup CoPilot to ingest Oracle databases into Velocity
2. Ingesting an Oracle database with NetBackup CoPilot
Microsoft SQL Server database ingestion using Velocity
1. How to provide copies of SQL Server databases for sandboxes in Velocity
2. Adding a SQL Server database to ingest into Velocity
3. Ingesting a SQL Server database into Velocity
4. Editing default options for SQL Server database ingestion
5. Canceling a SQL Server database ingestion
Database sources and copies
1. About database sources and copies
2. Viewing details of an Oracle database source
3. Viewing details of a SQL Server database source
4. Changing the nickname or description of a database source
5. Deleting a database source from Velocity
6. About scheduling ingestions for a database source
7. Retention periods for database sources and copies
8. Viewing database copies
9. Viewing the number of sandboxes that were created from a database copy
10. Viewing the status of database copies
11. Deleting database copies
Sandboxes
1. About sandboxes
2. Creating a sandbox from an Oracle database copy
3. Starting an Oracle database instance manually
4. Creating a sandbox from a SQL Server database copy
5. Starting a SQL database manually
6. Finding your sandbox
7. Viewing details about your sandboxes
8. Deleting a sandbox
9. Managing sandboxes when you restart the host Oracle Database server
10. Unmounting a sandbox from an Oracle host server
Database recovery
1. Recovering an Oracle database
Alerts and logs
1. Viewing alerts
2. Creating audit log reports
3. Redirecting the syslog messages
4. Viewing the syslog messages on a Red Hat Enterprise Linux computer
5. Viewing the syslog messages on a Windows computer
Managing the Velocity physical appliance
1. Configuring network address settings on the Velocity physical appliance
2. About the Veritas Remote Management Console on the Velocity physical appliance
3. About Velocity physical appliance storage
  1. Configuring the storage on the Velocity physical appliance
  2. Viewing the storage on the Velocity physical appliance
4. About users on the Velocity physical appliance
5. About Velocity physical appliance checkpoints
  1. Creating a custom checkpoint on the Velocity physical appliance
  2. Restoring the Velocity physical appliance from a checkpoint
6. About factory reset on the Velocity physical appliance
  1. Restoring the Velocity physical appliance to a factory state
Monitoring the Velocity physical appliance
1. About Veritas AutoSupport on the Velocity physical appliance
  1. Setting up AutoSupport on the Velocity physical appliance
2. Setting up email notifications on the Velocity physical appliance
3. Setting up SNMP notifications on the Velocity physical appliance
4. Auditing the SDCS logs on the Velocity physical appliance
  1. About SDCS event type codes and severity codes on the Velocity physical appliance
  2. Changing the SDCS log retention settings on the Velocity physical appliance
5. Testing the Velocity physical appliance hardware
Velocity physical appliance security
1. About Velocity physical appliance user account privileges
  1. Velocity physical appliance user name and password specifications
    1. Password encryption and handling on the Velocity physical appliance
2. About the Velocity physical appliance intrusion detection system
  1. Reviewing SDCS events on the Velocity physical appliance
3. About Velocity physical appliance operating system security
  1. Vulnerability scanning of the Velocity physical appliance
  2. Disabled service accounts on the Velocity physical appliance
4. About data security on the Velocity physical appliance
5. About data integrity on the Velocity physical appliance
6. About the Velocity physical appliance ports
7. Recommended IPMI settings on the Velocity physical appliance
  1. Replacing the default IPMI SSL certificate on the physical appliance
Best practices
1. Improving the performance of Veritas Velocity for Oracle Database
2. Stopping and starting all mounts
3. Protecting the Velocity on-premises management server
Troubleshooting
1. NFS export paths where ingested Oracle Database sources are stored are inaccessible
2. NFS export path is not created during a database ingestion
3. Database ingestion fails with the Oracle error 'diskgroup {xx} space exhausted'
4. After restart of the vpfsd service, links to the applications are broken
5. Sandbox creation fails on an Oracle Database server
6. Sandbox creation fails for a SQL Server database copy
7. Sandbox creation fails after you use the --adGroups argument when you configure the Velocity Client for Windows
8. Sandbox creation may take longer than usual on Oracle Database 12c
9. A sandbox cannot be deleted from an Oracle Database server because the mount point is busy
10. Error occurs when registering the Velocity Client; provide the Oracle DBA with access to the Velocity registration files
11. Error occurs when a new sandbox name has the same name as a deleted sandbox
12. Ingestions and sandboxes are stuck 'In Progress' after the Velocity Storage Server is restarted
Glossary
1. Glossary terms for Velocity
Context-sensitive topics
1. Create Sandbox - Choose Database
2. Create Sandbox - Configure Host
3. Create Sandbox - Review Settings
4. Create Sandbox - Choose Database
5. Create Sandbox - Configure Host
6. Create Sandbox - Review Settings
7. Sandboxes window
8. Sandbox details
9. Sandbox details for an Oracle database copy
10. Sandbox details for a SQL Server database copy
11. Role Wizard - Select User Type
12. Role Wizard - Select Users
13. Role Wizard - Select Sources
14. Role Wizard - Review
15. Copies dialog
16. Database source details
17. Database Sources dialog
18. How to set up the Velocity Client
19. Schedule dialog
Section I. Velocity shell menu commands
1. Introduction
  1. About Velocity commands
2. Appendix A. Main > Manage > Storage
  1. Manage > Storage > Configure
  2. Manage > Storage > Show
3. Appendix B. Main > Manage > Cloud
  1. Main > Manage > Cloud
4. Appendix C. Main > Manage > Software
5. Appendix D. Main > Monitor
6. Appendix E. Main > Network
7. Appendix F. Main > Settings
8. Appendix G. Main > Support

Adding a Certificate Authority signed certificate to the Velocity Storage Server

By default, the Velocity Storage Server uses a self-signed certificate that Veritas provides. You can, however, replace the certificate with your own Certificate Authority (CA) signed certificate. To use your own certificate, you must create a new keystore file, install the certificate chain, and reference the new chain using the appropriate keystore alias.

Adding your own CA-signed certificate helps to ensure that your Oracle Database servers communicate only with the Velocity Storage Server.

To add a Certificate Authority signed certificate to the Velocity Storage Server

Log on to your Velocity Storage Server.
Type the following command to change the directory:
cd /opt/apache-tomcat/security
Type the following command to create a new keystore file with a self-signed certificate and private key:
keytool -genkey -alias tomcat -keyalg RSA -keystore keystore.tomcat-velocity -keysize 2048
Note:
The private key that is generated is part of the CA signing request. It is important to save a copy of this file in a secure location for future use.
Make a note of the alias from the command. You must use the same value for the "-alias" flag throughout this procedure. In this example, the alias is "tomcat".
Answer the questions with information about your organization and provide a password for the keystore.
Type the following command on the newly created keystore file to produce the certificate request text file. The certificate request text file is used for the certificate signing request:
keytool -certreq -keyalg RSA -alias tomcat -file certreq.csr -keystore keystore.tomcat-velocity
Use the text that is included in the certreq.csr file to request a certificate from your certificate authority. The FQDN that you use for the Subject Alternative Name (SAN) field must be fully resolvable in your network's DNS namespace.
Warning:
You must use the correct FQDN in the SAN field. If you do not use the correct FQDN, the procedure fails.
Once you have received the issued certificate chain, save the text in the following file:
/opt/apache-tomcat/security/cert.p7b
Use the following command to change the directory to the original keystore work location:
cd /opt/apache-tomcat/security
Import the new certificate chain into the newly generated keystore using the following command:
keytool -import -alias tomcat -trustcacerts -file cert.p7b -keystore keystore.tomcat-velocity
Where "file cert.p7b" is the certificate chain text that was issued from your CA and that you saved in step 7.
Type the following command to save a copy of the file named keystore to keystore.orig:
cp keystore keystore.orig
Type the following command to import the new keystore file, which now contains your CA-issued certificate chain, into the existing keystore:
keytool -importkeystore -deststorepass appliance -destkeypass appliance -destkeystore keystore -srckeystore keystore.tomcat-velocity -srcstorepass appliance -alias tomcat
Note:
You may need to update the passwords in the command to match the commands that were used earlier in this procedure.
When you are prompted to overwrite the existing alias, select Yes.
Type the following command to restart Velocity tomcat:
service tomcat-velocity restart
Log on to the Oracle server as root.
Navigate to /opt/veritas/velocity/etc/controller.conf and change the following values:
Change the "verifyhost" value from "false" to "true".
Change the "verifypeer" value from "false" to "true".
Type the following command to restart the Velocity Client:
service vexecd restart