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
Creating a sandbox from an Oracle database copy
You can create a sandbox whenever you want a different database copy, or when you want to refresh a database copy.
The database files for the database copy are stored on the Velocity Storage Server, on an NFS export path. When you specify an Oracle Database server as the sandbox host, the sandbox is automatically mounted as an NFS share on that Oracle Database server. Then, the Oracle software can access the database files in the NFS export path and create and start the database for the sandbox.
You are prompted to provide the following information:
The time and date of the database copy that you want to use in the sandbox.
The Oracle Database server that you want to access the sandbox.
Optional configuration details for the sandbox.
Ensure that the following prerequisites are set up before you create a sandbox:
The Velocity Client is configured on the host Oracle Database server.
The Oracle host server is running a supported configuration.
See the Velocity Software Compatibility List at the following URL:
Before you create a sandbox, ensure that the host Oracle Database server has any required patches.
You must create a sandbox on a host server on which a version of Oracle is installed that is the same as the ingested database. Alternatively, to use an existing Oracle home from this host, enter it in the Custom Oracle Home Path field when you create the sandbox.
To create a sandbox from an Oracle database copy
- From the Velocity Cloud Console, in the left pane, click Sandboxes, and then on the Sandboxes dialog, click +.
- On the Choose Database dialog, do one of the following:
To get the latest database copy
Select a database.
To choose a specific date and time of a database copy
Select a database, click the down arrow, and then select a date and time from the calendar.
Note:
The following icon indicates that the database copy contains test data instead of production data:
- Click Next.
- On the Configure Host dialog, specify the details of the Oracle Database server that you want to host the sandbox:
Sandbox Name
Enter a name for the sandbox. The sandbox name is limited to 128 characters.
Description
Enter a description of the sandbox to help you distinguish it from other sandboxes.
Host
Enter the hostname or IP address of the Oracle Database server on which you want to create an Oracle instance to stand up the copy of the database for the sandbox, and then click +.
Copy Preparation Script Path
Enter the path and file name of the script on the sandbox host server that you want to automatically run on the database copy to mask or sanitize data.
After the script runs, a snapshot of the prepared database copy with the masked data is available to sandbox users.
This field is disabled if you clear the Automatically start the database check box.
Automatically start the database
This check box is selected by default to enable Velocity to start the database instance for this sandbox automatically after the sandbox is created. Clear this check box if you do not want Velocity to start the database instance automatically after the sandbox is created. If you clear this check box, the sandbox is created, so you can perform a manual operation, recover data, or manipulate the data. You can choose to start the database instance manually at any time.
Database Name
Enter a new name for the database that you want to set up from your sandbox.
Note:
The database name must start with a letter, can contain only letters and numbers, and cannot exceed eight characters. Refer to your Oracle documentation for other database name requirements.
This field is disabled if you clear the Automatically start the database instance check box.
Database Memory
(Optional) Enter the memory size for the database that you want to run from the sandbox. By default, the allocated memory size is 40% of the available system memory on the computer that hosts the sandbox.
This field is disabled if you clear the Automatically start the database instance check box.
Working Directory
(Optional) Enter the local path on the host of the working directory to which you want to direct all of the input operations and output operations of the database. You can specify the path of the working directory to your local disk to enable better input and output operations.
Input and output files include temp files, online logs, archive logs, audit files, and the Flash Recovery Area (FRA).
The working directory must already exist. You must have permissions to read and write in the new working directory.
Note:
If your environment includes Oracle RAC, ensure that the working directory path exists on all of the RAC nodes.
This field is disabled if you clear the Automatically start the database instance check box.
Custom Oracle Home Path
(Optional) Enter the Oracle home path that you want to use to set up the database from the sandbox. If there are multiple Oracle home paths on a node, the default home path is the first home path in
ContentsXML/Inventory.xml
.The Oracle home path identifies the program group that is associated with a specific home, and the Oracle services that are installed on this home.
The path name must be between 1 and 127 characters, and can include only alphanumeric characters, underscores, and forward slashes.
This field is disabled if you clear the Automatically start the database instance check box.
NFS Mount Path
(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. If you do not enter an NFS mount path, Velocity uses a default path.
- Click Next.
- On the Review Settings dialog, ensure that your selections are correct, and then click Create.
After the sandbox is successfully created, you can start using the database copy from your sandbox.