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
Recovering an Oracle database
You can recover a database through restore by using a database copy from Velocity, then manually recovering the database. When you restore a database, the data is transferred back to the original host server. You can choose to overwrite the existing database on the original host server or to move the data files to a different location on the original host server.
After Velocity moves the data back to the host server, you must manually run RMAN commands to complete the database recovery. Ensure that you prepare all necessary archive logs to use for recovery.
Note:
Recovery of an Oracle database requires a valid control file. Velocity will not restore the control file. If the original control file is invalid, recreate it or restore from other backups before you continue with this procedure.
To recover an Oracle database
- Start the original Oracle instance into the MOUNTED state.
Note:
If the original database is an Oracle RAC Database, keep the node that will run the recovery in a mount status, and shut down all other Oracle RAC instances on all nodes.
- From the Velocity Cloud Console, in the left pane, click Database Sources.
- On the Database Sources window, choose how you want to find the database copy to use to restore a database.
To select a database copy from a calendar
Do this:
Click +, and then click Create Recovery Sandbox.
Expand a database, and then select the database copy that you want to use for recovery.
Click Next.
To select a database copy from a list of copies
Do this:
Click Details on the row for the database source that contains the database copy that you want to use for recovery.
Select Copies.
Select More, and then select Recovery.
- In Recovery Location, select the location where you want to recover the database.
You can restore the database back to the original location on the host server, which overwrites the existing data, or you can restore the database to a different location on the host server.
To recover the database to a different location, ensure that the destination file folder or the ASM disk group already exists with Oracle user read and write privileges. If the database is an Oracle RAC, the different location should be accessible by all nodes.
For example, for an alternate restore for an ASM disk group, the disk group name could be '+DATA2'.
- In Recovery Sandbox Name, type the name that you want to use to identify this sandbox.
This name will appear in the list of sandboxes on the Sandbox window.
- (Optional) In Description, type a description to help you to identify this sandbox.
The Host Server and the Database Name fields cannot be changed. Velocity fills in those fields automatically based on your selections.
- If you have an Oracle RAC environment, select an Oracle RAC host node to which you want to recover the database.
Velocity shows only the nodes that are registered with the Velocity Client.
- Click Next.
- Review the settings that you selected, and then click Recover Database.
- Read the database recovery warning, and then click Yes, Recover Database.
Go to the Dashboard or to the Sandboxes window to see the progress of the recovery.
After the restore is successful, the Oracle instance is in a MOUNTED state.
- To set up the database, log in to the original instance of the database.
- Run the RECOVER command to perform the Oracle recovery to any point of time later than the time of the database copy backup.
All of the archived logs that are needed for the recovery should be prepared by the DBA. Velocity does not keep these archived logs.
- To open the database, run the ALTER DATABASE OPEN command.
Refer to your Oracle documentation for more information about the options for the RECOVER and ALTER DATABASE OPEN commands.