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 that are already ingested
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.
When you enable copy preparation for an ingested database, the setting applies to all database copies from all database sources that are of the same database.
See How to use copy preparation to mask or sanitize sensitive data.
To mask sensitive data manually in database copies that are already ingested
- From the Velocity Cloud Console, in the left pane, click Database Sources.
- Select the row that the database appears on, and then click Details.
- Click Edit.
- Select Enable Copy Preparation, and then when prompted, click Enable Copy Preparation again, and then click Save.
If there are multiple database copies for this database source, or if there are multiple databases sources for a database, you are prompted to enable copy preparation on all of the copies.
All of the available database copies are hidden from the sandbox users that have access to the database. These database copies appear with the following icon:
- From the Velocity Cloud Console, in the left pane, click Sandboxes, and then click +.
- Select the database for which you enabled copy preparation.
- 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 made changes to 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.