Veritas Velocity™ User's Guide
- Getting to know Velocity
- Setting up Velocity
- Velocity administrator's checklist for setting up Veritas Velocity
- Database administrator's checklist for setting up Veritas Velocity
- Sandbox user's checklist for setting up Veritas Velocity
- How to set up the Velocity Storage Server
- Deploying the Velocity Storage Server image on a virtual machine
- Velocity Appliance initial configuration requirements
- Configuring network and storage settings for the Velocity Storage Server in a virtual environment
- Registering the Velocity Storage Server
- Joining the Velocity Storage Server to the Active Directory domain
- Adding a Certificate Authority signed certificate to the Velocity Storage Server
- How to set up the Velocity Client
- Deleting a Velocity Client
- Configuring a proxy server for Velocity
- Required and optional ports for Velocity
- Installing the NetBackup Client on the Velocity Storage Server
- Setting up the Velocity on-premises management server
- How to set up the Velocity on-premises management server
- Deploying the Velocity on-premises management server image on a virtual machine
- Configuring the network settings for the Velocity on-premises management server
- Configuring Active Directory/LDAP settings on the Velocity on-premises management server
- Adding users to the Velocity on-premises management server
- Upgrading Velocity
- How to upgrade to Velocity version 2.8
- Finding the Velocity Storage Server and Velocity Client version numbers
- Downloading and transferring software updates to the Velocity Storage Server
- Removing previous upgrade files
- Upgrading the Velocity Storage Server
- Upgrading the Velocity Client for Linux
- Upgrading the Velocity Client for Windows
- Upgrading the Velocity Client for Solaris
- Velocity Storage Server
- About the Velocity Storage Server
- Viewing physical storage usage on the Velocity Storage Server
- About reclaiming storage space on the Veritas Velocity Storage Server
- Increasing meta and data storage capacity on the Velocity Storage Server
- Deregistering a Velocity Storage Server
- How to reset the Velocity Storage Server
- Users and roles
- Oracle database ingestion using Velocity
- How to provide copies of Oracle databases for sandboxes in Velocity
- Adding an Oracle database to ingest into Velocity
- Ingesting an Oracle database into Velocity for the first time
- Ingesting an Oracle database again after the first ingest
- Canceling an Oracle database ingestion
- How to use copy preparation to mask or sanitize sensitive data
- Masking sensitive data manually in database copies
- Masking sensitive data in database copies by using a script
- Masking sensitive data manually in database copies that are already ingested
- Masking sensitive data by using a script in database copies that are already ingested
- Disabling copy preparation for Oracle database copies
- Ingesting an Oracle database into Velocity from the command line
- About setting custom initialization parameters for a sandbox for an Oracle database copy
- Editing default options for the ingest method for Oracle databases
- Oracle database ingestion using NetBackup CoPilot
- Microsoft SQL Server database ingestion using Velocity
- Database sources and copies
- About database sources and copies
- Viewing details of an Oracle database source
- Viewing details of a SQL Server database source
- Changing the nickname or description of a database source
- Deleting a database source from Velocity
- About scheduling ingestions for a database source
- Viewing the ingestion schedule for a database source
- Adding an ingestion schedule to a database source
- Editing the ingestion schedule for a database source
- Deleting the ingestion schedule for a database source
- Restarting scheduled database ingestions after changing the system time or time zone on the Velocity Storage Server
- Retention periods for database sources and copies
- Viewing database copies
- Viewing the number of sandboxes that were created from a database copy
- Viewing the status of database copies
- Deleting database copies
- Sandboxes
- About sandboxes
- Creating a sandbox from an Oracle database copy
- Starting an Oracle database instance manually
- Creating a sandbox from a SQL Server database copy
- Starting a SQL database manually
- Finding your sandbox
- Viewing details about your sandboxes
- Deleting a sandbox
- Managing sandboxes when you restart the host Oracle Database server
- Unmounting a sandbox from an Oracle host server
- Database recovery
- Alerts and logs
- Managing the Velocity physical appliance
- Configuring network address settings on the Velocity physical appliance
- About IPv4-IPv6-based network support on the Velocity physical appliance
- About NIC1 (eth0) port usage on the Velocity physical appliance
- Creating a network interface bond (NIC bond) on the Velocity physical appliance
- VLAN tagging on the Velocity physical appliance
- Configuring static routes on the Velocity physical appliance
- Configuring DNS and host name mapping on the Velocity physical appliance
- Setting the host name for the Velocity physical appliance
- Using a proxy server with the Velocity physical appliance
- About WAN optimization on the Velocity physical appliance
- About the maximum transmission unit size on the Velocity physical appliance
- Setting the date and time on the Velocity physical appliance
- About the Veritas Remote Management Console on the Velocity physical appliance
- About Velocity physical appliance storage
- About users on the Velocity physical appliance
- About Velocity physical appliance checkpoints
- About factory reset on the Velocity physical appliance
- Configuring network address settings on the Velocity physical appliance
- Monitoring the Velocity physical appliance
- Velocity physical appliance security
- About Velocity physical appliance user account privileges
- About the Velocity physical appliance intrusion detection system
- About Velocity physical appliance operating system security
- About data security on the Velocity physical appliance
- About data integrity on the Velocity physical appliance
- About the Velocity physical appliance ports
- Recommended IPMI settings on the Velocity physical appliance
- Best practices
- Troubleshooting
- NFS export paths where ingested Oracle Database sources are stored are inaccessible
- NFS export path is not created during a database ingestion
- Database ingestion fails with the Oracle error 'diskgroup {xx} space exhausted'
- After restart of the vpfsd service, links to the applications are broken
- Sandbox creation fails on an Oracle Database server
- Sandbox creation fails for a SQL Server database copy
- Sandbox creation fails after you use the --adGroups argument when you configure the Velocity Client for Windows
- Sandbox creation may take longer than usual on Oracle Database 12c
- A sandbox cannot be deleted from an Oracle Database server because the mount point is busy
- Error occurs when registering the Velocity Client; provide the Oracle DBA with access to the Velocity registration files
- Error occurs when a new sandbox name has the same name as a deleted sandbox
- Ingestions and sandboxes are stuck 'In Progress' after the Velocity Storage Server is restarted
- Glossary
- Context-sensitive topics
- Create Sandbox - Choose Database
- Create Sandbox - Configure Host
- Create Sandbox - Review Settings
- Create Sandbox - Choose Database
- Create Sandbox - Configure Host
- Create Sandbox - Review Settings
- Sandboxes window
- Sandbox details
- Sandbox details for an Oracle database copy
- Sandbox details for a SQL Server database copy
- Role Wizard - Select User Type
- Role Wizard - Select Users
- Role Wizard - Select Sources
- Role Wizard - Review
- Copies dialog
- Database source details
- Database Sources dialog
- How to set up the Velocity Client
- Schedule dialog
- Section I. Velocity shell menu commands
- Introduction
- Appendix A. Main > Manage > Storage
- Appendix B. Main > Manage > Cloud
- Appendix C. Main > Manage > Software
- Appendix D. Main > Monitor
- Appendix E. Main > Network
- Network > Configure
- Network > Date
- Network > DNS
- Network > Gateway
- Network > Hostname
- Network > Hosts
- Network > IPv4
- Network > IPv6
- Network > NetStat
- Network > NTPServer
- Network > LinkAggregation
- Network > VLAN
- Network > WANOptimization
- Network > Ping
- Network > Proxy
- Network > SetProperty
- Network > Show
- Network > TimeZone
- Network > TraceRoute
- Network > Unconfigure
- Appendix F. Main > Settings
- Appendix G. Main > Support
Testing the network path for Oracle communications
Velocity uses NFS to export and mount file systems so that it can access data. When you install and register the Velocity Client, you have to know the appropriate network path so that the Velocity Storage Server can communicate with any Oracle host servers.
You may find it helpful to complete the following procedure if you have a complicated network configuration, for example if you use more than one network card on your Oracle server. Completing these steps before you register the Velocity Client can help eliminate potential issues with the way Velocity uses NFS. It can also help you to determine the integrity of the network configuration.
To test the network path for Oracle communications
- On the Velocity Storage Server, from the Velocity shell menu, select Support > Support > Maintenance.
- When prompted, enter the Velocity Storage Server password, and then type the following command:
elevate
Root access is enabled.
- Type the following command to create a test directory:
mkdir /testexport
- Type the following command to create a test file in the directory:
touch /testexport/test
- Modify /etc/exports to add the following line:
/testexport <hostname/IP>(ro)
Where <hostname/IP> is the hostname or IP address of the Oracle host server that you want to use with Velocity.
Note:
If you already attempted this procedure, but you were unable to view the test file, you should use a new hostname or IP address. The new hostname or IP address should represent a different network card on the Oracle host server.
- Save /etc/exports.
Type the following commands to export the file that you created:
exportfs -rav
Ensure that "/testexport" appears as having been exported to the intended Oracle host server.
Note:
You may receive a message that says "exportfs: Failed to resolve <oracle host>", where <oracle host> is the hostname of the Oracle server that you are using for the test. If you receive this message, you have entered a server hostname that is not able to be resolved on the network. Go back to step 5 and try a new hostname or modify your network name resolution configuration so that the hostname is resolvable to an IP address.
exportfs
Ensure that "/testexport" is listed in the output.
- Log on to the Oracle host server as root.
- Type the following command to create a test directory mount point on the Oracle host server:
mkdir /testmount
Note:
If you already created this test directory to test a hostname or IP address, you can skip this step. At the end of this procedure, when you have successfully identified the hostname or IP address to use with Velocity, you will remove the test directory.
- Type the following command to mount the exported test directory from the Velocity Storage Server:
mount -o vers=4 <storage host/IP>:/testexport /testmount
Where <storage host/IP> is the hostname or IP address of the Velocity Storage Server.
- Type the following command to ensure that the test file can be seen in the mounted directory:
ls -l /testmount/test
- Were you able to view the test file?
If you were able to view the test file:
The mount succeeded.
Proceed to step 13 to remove the testmount directory that you created.
If you were not able to view the test file:
If the mount failed or pauses or if the directory does not show the test file, then the network path is incorrect. You must repeat the test using a different host server hostname or IP address in /etc/exports to determine the correct network path.
For each test, you must unmount the testmount on the host server before you modify /etc/exports on the Velocity Storage Server and retry the mount:
Type the following command on the Oracle host server to unmount the test directory:
umount /testmount
On the Velocity Storage Server, from the Velocity shell menu, select Support > Support > Maintenance.
When prompted, enter the Velocity Storage Server password, and then type the following command:
elevate
Root access is enabled.
Return to step 5 to repeat the procedure. You should use a new hostname or IP address that represents a different network card on the Oracle host server.
- On the Oracle host server, type the following command to unmount the test directory:
umount /testmount
- Type the following command to remove the local test directory mount point:
rmdir /testmount
- On the Velocity Storage Server, from the Velocity shell menu, select Support > Support > Maintenance.
- When prompted, enter the Velocity Storage Server password, and then type the following command:
elevate
Root access is enabled.
- Edit the /etc/exports file and remove the /testexport entry.
- Run the following command:
exportfs -rav
- Type the following command to remove the /testexport directory:
rm -fr /testexport
You have completed this procedure. You can use the hostname or IP address that you tested for the host server when you register the Velocity Client.