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
- Automatic ingestion of NetBackup deduplicated backups
- 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
- Velocity REST APIs
- Best practices
- Troubleshooting
- Glossary
- 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
Upgrading the Velocity on-premises management server
To upgrade the Velocity on-premises management server, you must download and transfer software updates to the management server by using the Velocity shell menu. You download the software update files onto a client computer such as a laptop. Then, you transfer the update files over a local network to the management server by using a CIFS share or an NFS share.
To upgrade the Velocity on-premises management server
- Contact Veritas Technical Support to obtain and download the required upgrade files.
- Use one of the following commands to compute the checksum value for the rpm file:
Windows
Refer to the following article for computing the MD5 checksum on Windows:
UNIX
Run one of the following commands to compute the checksum value for the rpm file:
md5sum <filename> or sha1sum <filename>
Where <filename> is the full name and extension of the update file.
Verify that the checksum value matches the value from the Velocity Support website.
- Log on to the Velocity shell menu.
- From the Main_Menu > Manage > Software view, type the following command:
Share Open
- Map or mount the share directory onto your computer as follows:
Windows CIFS share
\\<management-server-name>\incoming_patches
Where <management-server-name> is the host name or IP address of the Velocity on-premises management server.
UNIX NFS share
mkdir -p /mount/<management-server-name>
mount <management-server-name>:/inst/patch/incoming
/mount/<management-server-name>
Where <management-server-name> is the host name or IP address of the Velocity on-premises management server.
- Copy the rpm file and the tar files to the mount share.
Note:
During the copy process, do not run any commands on the on-premises management server or the copy operation may fail.
- From the Velocity shell menu, go to Support > Maintenance > Elevate.
- Use the mv command to move the tar files from /inst/patch/incoming to /tmp:
- After the file is successfully copied to the on-premises management server, unmap or unmount the network share from your computer.
- On the on-premises management server, from the Main_Menu > Manage > Software view, type the following command:
Share Close
This command moves the update file to the necessary internal upgrade directory and secures the on-premises management server. Always close network shares on the on-premises management server when you have finished using them.
Note:
The following commands also move the update file to the correct internal directory:
List Version
List Details All
List Details Base
Share Open
Share Close
- To ensure that the update file is ready to install, type the following command:
List Downloaded
The command lists the name of the update file.
- Type the following command to run the update file:
Install <update file name>
Where <update file name> is the name of the that is given in the output of the command List Downloaded.
- Follow the prompts to complete the upgrade process.
More Information