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
Ingestions and sandboxes are stuck 'In Progress' after the Velocity Storage Server is restarted
When the Velocity Storage Server is restarted, the Velocity Client may no longer communicate with the Velocity Storage Server. Additionally, some permissions on the NFS export path or CIFS path may have changed.
On the Dashboard on the Velocity Cloud Console, all data ingestions and sandbox creations may continuously display the status 'In Progress'. If you try to cancel the ingestion or the sandbox creation, the status may change to 'Canceling in progress' but it never resolves.
Also, on the Clients window on the Velocity Cloud Console, the Velocity Client status may appear as 'Not Connected'.
To solve this issue, restart the vexecd service on the Velocity Client. If that does not fix the issue, then try to reset the permissions.
To restart the vexecd service on the Velocity Client for Solaris
- Log on to the Solaris host server as root.
- In a terminal window, type the following command:
svcadm restart vexecd
To restart the vexecd service on the Velocity Client for Linux
- Log on to the Linux host server as root.
- In a terminal window, type the following command:
service vexecd restart
To restart the vexecd service on the Velocity Client for Windows
- On the host Windows server, right-click the taskbar, and then click Task Manager.
- Go to the Services tab
- Right-click vexecd, and then click Restart.
If the issue is not resolved, try the following steps to reset the permissions.
To reset the permissions
- From the Velocity shell menu, go to the Main Menu > Support > Maintenance view, type the following command, and then press Enter.
elevate
- Type the following command, and then press Enter.
chmod 777 /mnt/vpfs_shares/*/*
More Information