Veritas Velocity™ User's Guide
- Getting to know Velocity
- Setting up Velocity
- How to set up the Velocity Storage Server
- How to set up the Velocity Client
- Setting up the Velocity on-premises management server
- Upgrading Velocity
- Velocity Storage Server
- Users and roles
- Oracle database ingestion using Velocity
- How to use copy preparation to mask or sanitize sensitive data
- Oracle database ingestion using NetBackup CoPilot
- Microsoft SQL Server database ingestion using Velocity
- Database sources and copies
- About scheduling ingestions for a database source
- Retention periods for database sources and copies
- Sandboxes
- Database recovery
- Alerts and logs
- Managing the Velocity physical appliance
- Configuring network address settings on the Velocity physical appliance
- About WAN optimization 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
- Recommended IPMI settings on the Velocity physical appliance
- Best practices
- Troubleshooting
- Glossary
- Context-sensitive topics
- 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
- Appendix F. Main > Settings
- Appendix G. Main > Support
Masking sensitive data manually in database copies
When you enable copy preparation for an Oracle database source, you can mask or sanitize the data manually in the ingested database before sandbox users can access the database copies. Masking or sanitizing the data lets you hide the real 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.
To mask sensitive data in database copies manually
- From the Velocity Cloud Console, in the left pane, click Database Sources.
- Click +, and then click Add Database to Ingest.
- Select Ingest Oracle to ingest an Oracle database source into Velocity, select whether you want to use Velocity or NetBackup to ingest this database source, and then click Next.
- Enter the hostname or IP address of the Oracle database server that you want to add to Velocity.
- Click + to add the server name or IP address to the Added Hosts list.
- (Optional) To specify a database in a RAC environment, enter each node name or IP address one at a time. Then, click + to add each node to the Added Hosts list.
- For the option Enable Copy Preparation, click Yes.
- Enter the name of the Oracle database that you want to add to Velocity as a source.
Note:
The database name must start with a letter, can contain only letters, numbers, underscores (_), number signs (#), and dollar signs ($), and cannot exceed 30 characters. Refer to your Oracle documentation for other database name requirements.
- (Optional) Enter a user-friendly name for the configured ingest job.
- (Optional) Enter a description of the Oracle database that is meaningful to you or makes it easy to remember.
- (Optional) Enter an NFS mount path, if you do not want to use the default path.
The NFS mount path is the path on the host server where the NFS share is mounted. The default path is /mnt/velocity.
- Click Next.
- (Optional) To create a recurring schedule for the ingestion, configure the scheduling options, and then click Next.
If you do not want to create a recurring schedule, click Skip.
Note:
You may have to upgrade your Velocity Storage Server to enable scheduling.
- (Optional) Select the amount of time you want to retain this database source and all of its subsequent copies.
Note:
After the retention period ends, this database source and all of its copies are removed from the Velocity Storage Server.
If you want to save this database source and its subsequent copies indefinitely, click Skip.
- Click Ingest.
- To create a sandbox, from the Velocity Cloud Console, in the left pane, click Sandboxes, and then click +.
- Select the database for which you enabled copy preparation. By default, Velocity selects the most recent copy of the database that you selected. However, you can browse for older database copies. The date of the selected database copy is circled and highlighted on the calendar.
- Click Next.
- Enter the information as prompted to create the sandbox. Use the IP address of the secure server on which you want to run your data preparation tools.
See Creating a sandbox from an Oracle database copy.
Note:
The Velocity Client must be configured on the server on which you want to create a sandbox.
- Use your data preparation tools to mask or sanitize the data.
- After you have changed the data, on the NFS mount path for the sandbox for the database copy, run the following snapshot application:
/tools/scripts/sandbox snapshot
- After the snapshot application has completed, type the following command to restart the sandbox:
/tools/scripts/sandbox start
A new database copy with the masked data is available to sandbox users, in Sandboxes. The sandbox users who have access to the database source can create a sandbox from the database copy with the masked or sanitized data.
- (Optional) If you make changes to the database copy in the sandbox, run the snapshot application again to make a new copy of the database copy.
Sandbox users can then create a sandbox from the new database copy that contains changes.
The Copy Preparation Date displays the date and time that a copy of the database copy was created.
See How to use copy preparation to mask or sanitize sensitive data.