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
After restart of the vpfsd service, links to the applications are broken
The vpfsd service manages all the data of the NFS export path where the backups of the source Oracle Database are stored. Each export path on the Velocity Storage Server contains a link to the applications that are required to run database ingestion and sandbox creation. If the vpfsd service on the Velocity Storage Server fails, the links to the applications are broken.
Note:
For normal restarts of the Velocity Storage Server, you do not need to reestablish the links to the applications.
To reestablish the links to the applications, you must restart the vagentd service after you restart the vpfsd service.
To reestablish application tool links after you restart the vpfsd service
- To verify if the vpfsd for an export path is running, on the Velocity Storage Server, type the following command
ps aux|grep <export path>
For example:
# ps aux|grep asm4
The output is similar to the following:
root 8079 1 1 Mar30 ? 00:50:37
/opt/veritas/velocity/vpfs/bin/vpfsd
--mount _point /mnt/mount_out/asm4/asm4 --meta_dir/vs_meta/meta_dir
--source_id asm4 --share_name asm4 --log_level information
--config_path /vs_data/vo10/etc/velocity/vpfsd_config.json
--allow_other
If vpfsd is not in the output, the vpfsd service of that export path may have failed.
- To restart the vpfsd service, 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 Velocity Storage Server, as a root user, type the following command to restart the vpfsd service:
/opt/veritas/velocity/etc/vpfs.mnt/<mount point_name>.sh
For example:# /opt/veritas/velocity/etc/vpfs.mnt/asm4.sh
To verify that the vpfsd service has started correctly, as a root user type the following command:
ps aux|grep <export_path>
For example:# ps aux|grep asm4
- To restart the vagentd service, type the following command on the Velocity Storage Server:
service vagentd restart