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
NFS export paths where ingested Oracle Database sources are stored are inaccessible
Vpfsd is the service that manages all the data of the NFS export path where the backups of the source Oracle Database are stored. Each NFS export path has a corresponding vpfsd service. The NFS export path becomes inaccessible if its vpfsd service fails.
To troubleshoot NFS export paths where ingested Oracle Database sources are stored
- On the Velocity Storage Server, to verify if the vpfsd for an NFS export path is running, type the following command:
ps aux|grep <NFS export path>
For example: # ps aux|grep asm4
root 8079 1 1 Mar30 ? 00:50:37 /opt/veritas/velocity/vpfs/bin/vpfsd
--mount_point /mnt/vpfs_shares/asm4/asm4 --meta_dir /vs_meta/meta_dir
--source_id asm4 --share_name asm4 --log_level information
--config_path /vs_data/vol0/etc/velocity/vpfsd_config.json --allow_other
If vpfsd is not in the output, the vpfsd service of that NFS export path may have failed.
- From the Velocity shell menu, select Support > Support > Maintenance.
- When prompted, enter the Velocity Storage Server password, and then type the following command:
elevate
Root access is enabled.
- On the source database server, as a root user type the following command to unmount the NFS mount path:
umount <NFS_mount_path>
For example:# umount /nfs/backup
Do not shut down the Oracle instance.
- On the Velocity Storage Server, as a root user, type the following commands to stop the network share and unmount the NFS mount point:
exportfs -u <oracle_host>:<NFS_mount_point>
umount -If <NFS_mount_point>
Where
<oracle_host> is the source database server that mounts the NFS mount point.
For example:
# exportfs -u 1.2.3.4:/mnt/vpfs_shares/asm4/asm4
# umount -If /mnt/vpfs_shares/asm4/asm4
Note:
You may receive a message that the mount point is not mounted. This message is expected.
- On the Velocity Storage Server, as a root user type the following command to restart vpfsd:
/opt/veritas/velocity/etc/vpfs.mnt/<NFS mount point_name>.sh
For example:# /opt/veritas/velocity/etc/vpfs.mnt/asm4.sh
To verify that vpfsd has started correctly, as a root user type the following command:
ps aux|grep <NFS_export_path>
For example:# ps aux|grep asm4
root 8079 1 1 Mar30 ? 00:50:37 /opt/veritas/velocity/vpfs/bin/vpfsd
--mount_point /mnt/vpfs_shares/asm4/asm4 --meta_dir /vs_meta/meta_dir
--source_id asm4 --share_name asm4 --log_level information
--config_path /vs_data/vol0/etc/velocity/vpfsd_config.json --allow_other
- On the Velocity Storage Server, as a root user type the following command to start the network share of the NFS export path:
exportfs <oracle_host>:<NFS_mount_point>
For example:
# exportfs 1.2.3.4:/mnt/vpfs_shares/asm4/asm4
- On the source database server, type the following command to mount the NFS export path (as a root user):
mount -o rw,bg,hard,nointr,rsize=1048576,wsize=1048576,tcp,actimeo=0,vers=4,timeo=600 <velocity_server>:<mount_point> <NFS mount_path>
For example:
# mount -o rw,bg,hard,nointr,rsize=1048576,wsize=1048576,tcp,actimeo=0,vers=4,timeo=600 1.2.3.4:/mnt/vpfs_shares/asm4/asm4 /nfs/backup
To start the ingest again (as an Oracle user) type the following command:
$ /nfs/backup/tools/bin/ingest_dba
Note:
When you ingest an Oracle database on ASM, the
ingest_dba
application attaches the disk group to ASM automatically.
After the vpfsd service is restored, the NFS export path becomes available again and you can proceed with ingesting an Oracle database.