Veritas Flex Appliance Getting Started and Administration Guide
- Product overview
- Release notes
- Getting started
- Managing network settings for instances
- Managing users
- Managing Flex Appliance Console users and tenants
- Managing multifactor authentication
- Using Flex Appliance
- Managing the repository
- Managing application instances from Flex Appliance
- Managing application add-ons on instances
- Upgrading application instances
- About Flex Appliance updates
- Remote replication
- Managing remote replication
- Appliance security
- Monitoring the appliance
- Configuring alerts
- Viewing the hardware status
- Reconfiguring the appliance
- Troubleshooting guidelines
Updating an application instance to a newer revision
Periodically, new revisions of applications are released to address security updates. When a new revision is released, it is posted on the Download Center with a new file name that includes the revision number after the version.
For example, the file VRTSflex-netbackup-9.1.0.1-0043x86_64.rpm
indicates that the application version is 9.1.0.1, and the revision number is 0043.
Use the following procedure to update an application instance to a newer revision.
Note:
The Flex Appliance Console does not currently show the revision numbers of your application instances. To determine the current revision of an instance, log in to the Flex Appliance Shell and run the following commands:
support shell
docker inspect flex.io/netbackup/main:<version> --format='{{index .Config.Labels "image.revision"'}}
Where <version> is the version number of the application instance.
To update an instance to a newer revision
- Add the new revision of the application to the repository.
Note:
If the instance that you are updating has a replica, make sure that the new revision is also in the repository on the remote appliance.
- Restart the instance.
Note:
If you have more than one instance of the application, they all get updated to the newer revision the next time they are restarted of if you change the replication role for remote replication.