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 the Velocity on-premises management server
- Upgrading Velocity
- How to upgrade to Velocity version 2.9
- Finding the Velocity component 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
- Automatic ingestion of NetBackup deduplicated backups
- About using NetBackup deduplicated backups to create Velocity sandboxes
- How to set up automatic ingestion of NetBackup deduplicated backups
- Supported Oracle policy options for automatic ingestions of NetBackup deduplicated backups
- Supported SQL Server policy options for automatic ingestions of NetBackup deduplicated backups
- Adding an Oracle database source to automatically ingest NetBackup deduplicated backups
- Adding a SQL Server database source to automatically ingest NetBackup deduplicated backups
- 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
- Velocity REST APIs
- Getting started with Velocity REST APIs
- Authenticate a user for the Velocity REST APIs
- Get Velocity Storage Servers
- Create a share
- Find the share ID
- Find the share location
- Create a snapshot
- Find the snapshot ID
- Create a sandbox
- Find the sandbox ID
- Get a sandbox
- Delete a share
- Delete a snapshot
- Delete a sandbox
- Get templates (shares)
- Get snapshots
- List all sandboxes
- 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
- 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
Upgrading the Velocity on-premises management server
To upgrade the Velocity on-premises management server, you must download and transfer software updates to the management server by using the Velocity shell menu. You download the software update files onto a client computer such as a laptop. Then, you transfer the update files over a local network to the management server by using a CIFS share or an NFS share.
To upgrade the Velocity on-premises management server
- Contact Veritas Technical Support to obtain and download the required upgrade files.
- Use one of the following commands to compute the checksum value for the rpm file:
Windows
Refer to the following article for computing the MD5 checksum on Windows:
UNIX
Run one of the following commands to compute the checksum value for the rpm file:
md5sum <filename> or sha1sum <filename>
Where <filename> is the full name and extension of the update file.
Verify that the checksum value matches the value from the Velocity Support website.
- Log on to the Velocity shell menu.
- From the Main_Menu > Manage > Software view, type the following command:
Share Open
- Map or mount the share directory onto your computer as follows:
Windows CIFS share
\\<management-server-name>\incoming_patches
Where <management-server-name> is the host name or IP address of the Velocity on-premises management server.
UNIX NFS share
mkdir -p /mount/<management-server-name>
mount <management-server-name>:/inst/patch/incoming
/mount/<management-server-name>
Where <management-server-name> is the host name or IP address of the Velocity on-premises management server.
- Copy the rpm file and the tar files to the mount share.
Note:
During the copy process, do not run any commands on the on-premises management server or the copy operation may fail.
- From the Velocity shell menu, go to Support > Maintenance > Elevate.
- Use the mv command to move the tar files from /inst/patch/incoming to /tmp:
- After the file is successfully copied to the on-premises management server, unmap or unmount the network share from your computer.
- On the on-premises management server, from the Main_Menu > Manage > Software view, type the following command:
Share Close
This command moves the update file to the necessary internal upgrade directory and secures the on-premises management server. Always close network shares on the on-premises management server when you have finished using them.
Note:
The following commands also move the update file to the correct internal directory:
List Version
List Details All
List Details Base
Share Open
Share Close
- To ensure that the update file is ready to install, type the following command:
List Downloaded
The command lists the name of the update file.
- Type the following command to run the update file:
Install <update file name>
Where <update file name> is the name of the that is given in the output of the command List Downloaded.
- Follow the prompts to complete the upgrade process.
More Information