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
How to use copy preparation to mask or sanitize sensitive data
Velocity provides an option that lets you prepare an Oracle database copy for data masking, data sanitizing, or any other data manipulation methods before sandbox users can access the database copies. Masking or sanitizing the data lets you hide the actual data but still provide usable data for test and development purposes. For example, you may want to remove any personal data or sensitive data and insert test data instead.
When you add a database source for ingestion, you can select the option. Then, after the database is ingested, only the database owner can view it in the list of database copies. The database owner is the person who ran the database ingestion. This restricted view prevents sandbox users from selecting a database copy before you have the opportunity to prepare the data.
To change the data in the database copy, create a sandbox for the ingested database on a secure server on which you want to mask or sanitize the data. You can mask or sanitize the data by doing one of the following:
Run your masking script automatically on the database copy when you create the sandbox.
Velocity automatically runs the script when the sandbox is created. After the script runs and the data is masked or sanitized, Velocity runs a snapshot application to make the new database copy with the masked data available to sandbox users, in Sandboxes.
Use your data preparation tools after you create the sandbox.
To change the data in the database copy, create a sandbox for the ingested database on a secure server on which you want to run your data preparation tools. When you have finished preparing the data, Velocity provides a snapshot application for you to run that makes the prepared database copy available for sandbox users.
If you make changes to the database copy in the sandbox, you can run the snapshot application again to make a new copy of the database copy. Sandbox users can then create a sandbox from the prepared database copy that contains the changes.
Sandbox users can create sandboxes only from the prepared database copy. Only the database owner has access to both the original database copy and the prepared database copy.
Note:
Prepared database copies do not expire. You can set a retention date and specify the amount of time to keep the database copy. When the retention period ends, the expired prepared database copy is automatically deleted from the server.
You can disable or enable copy preparation at any time for all of the database copies from a database source, even after the database has been ingested.
All database copies for which copy preparation is enabled are displayed with the following icon:
To mask or sanitize data in a database copy, you must have:
The Velocity administrator role or the Velocity database administrator role.
Root access on the server on which you run the snapshot application if you mask sensitive data manually.
See Masking sensitive data manually in database copies.
See Masking sensitive data in database copies by using a script.
See Masking sensitive data manually in database copies that are already ingested.
See Masking sensitive data by using a script in database copies that are already ingested.