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
Stopping and starting all mounts
After you restart the Velocity Storage Server or the Velocity physical appliance, the database sources and the sandboxes on the host servers may not be accessible. For example, the appliance restarts when you perform a rollback operation on it, which causes all the mounts to be inaccessible on the host servers on which the Velocity Client is installed.
Before you restart the Velocity Storage Server or physical appliance, you must stop all active sandboxes, and unmount all sandboxes and database sources. After you restart the Velocity Storage Server or physical appliance, you must remount all sandboxes and database sources.
To stop all mounts
- On the host server where the Velocity Client is installed, type the following command to stop each active sandbox:
<mnt path>/tools/scripts/sandbox stop
Perform this step on every host server where the Velocity Client is installed and for every sandbox and database source on each host server.
- If you have an ASM environment, on the host server where the Velocity Client is installed, do the following to unmount the ASM disk group from each database source and sandbox:
Note:
If you do not have an ASM environment, skip step 2 and proceed to step 3.
Log in as a grid infrastructure user on the Oracle database server where the database source is mounted.
From the directory where the database source is mounted, type the following command:
<mnt path>/tools/scripts/asmtasks_grid umountdg
You must unmount the ASM disk group on every host server where the Velocity Client is installed and for every sandbox and database source on each host server.
- On the host server where the Velocity Client is installed, do the following to unmount all sandboxes and database sources:
Type the following command to access the scripts that are available:
cd /opt/veritas/velocity/shutdown
Type the following command to view the list of scripts that are available:
ls
Note:
One script is available for each mount point. The name of the script does not match the name of the mount point.
This step is required on every host server where the Velocity Client is installed and for every sandbox and database source on each host server.
To start all mounts
- On the host server where the Velocity Client is installed, type the following command to view the remount scripts:
cd /opt/veritas/velocity/startup
- Run all of the scripts to mount the sandboxes and database sources.
This step is required on every host server where the Velocity Client is installed and for every sandbox and database source on each host server.
- If you have an ASM environment, on the host server where the Velocity Client is installed, do the following to remount all disk groups:
Log in as a grid infrastructure user on the Oracle database server where the database source is mounted.
From the directory where the database source is mounted, type the following command:
<mnt path>/tools/scripts/asmtasks_grid mountdg
This step is required on every host server where the Velocity Client is installed and for every sandbox and database source on each host server.
- On the host server where the Velocity Client is installed, for each sandbox, type the following command to restart sandboxes:
<mnt path>/tools/scripts/sandbox start
This step is required on every host server where the Velocity Client is installed and for every sandbox and database source on each host server.
Note:
If you have a RAC environment, you only need to run the restart command on one node.
- You must restart the vexecd service on the Velocity Client.
See Ingestions and sandboxes are stuck 'In Progress' after the Velocity Storage Server is restarted.