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:
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
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.
If you have a RAC environment, you only need to run the restart command on one node.
Searching...
