Veritas Flex Appliance Getting Started and Administration Guide
- Product overview
- Release notes
- Flex Appliance 4.0 new features, enhancements, and changes
- Flex Appliance 4.1 new features, enhancements, and changes
- Flex Appliance 4.2 new features, enhancements, and changes
- Supported update paths to this release
- Operational notes
- Flex Appliance 4.0 release content
- Flex Appliance 4.1 release content
- Flex Appliance 4.2 release content
- Getting started
- Managing network settings for instances
- Managing users
- Overview of the Flex Appliance default users
- Managing Flex Appliance Console users and tenants
- Adding a tenant
- Editing a tenant
- Removing a tenant
- Adding a local user to the Flex Appliance Console
- Connecting a remote user domain to the Flex Appliance Console
- Editing a remote user domain in the Flex Appliance Console
- Importing a remote user or user group to the Flex Appliance Console
- Managing single sign-on (SSO)
- Managing identity providers (IDPs)
- Importing a single sign-on user or user group to the Flex Appliance Console
- Managing user authentication with smart cards or digital certificates
- Changing a local user password in the Flex Appliance Console
- Expiring local user passwords in the Flex Appliance Console
- Unlocking a user account in the Flex Appliance Console
- Removing users from the Flex Appliance Console
- Changing the password policy
- Changing the hostadmin user password in the Flex Appliance Shell
- Changing the sysadmin user password in the Veritas Remote Management Interface
- Managing multifactor authentication
- Using Flex Appliance
- Managing the repository
- Creating application instances
- Managing application instances from Flex Appliance and NetBackup
- Managing application instances from Flex Appliance
- Resizing instance storage
- Editing instance network settings
- Assigning Fibre Channel ports to an instance
- Unassigning Fibre Channel ports from an instance
- Managing application add-ons on instances
- Viewing instance performance metrics
- Clearing a configuration error status on an application instance
- Deleting an application instance
- Upgrading application instances
- Updating an application instance to a newer revision
- About Flex Appliance updates
- Remote replication
- About remote replication
- Pairing appliances for remote replication
- Creating a replica
- Managing remote replication
- Remote replication best practices
- Monitoring remote replication
- Editing the replication network
- Repairing a lost connection between paired appliances
- Pausing and resuming replication
- Resolving discrepancies between an active and a replica instance
- Changing the replication role of an instance
- Unlinking active and replica instances
- Forgetting a paired appliance
- Appliance security
- Monitoring the appliance
- Registering an appliance
- Configuring alerts
- Monitoring the appliance from the System Health Insights portal
- Viewing the hardware status
- Viewing hardware faults
- Viewing system data
- Clearing the hardware status
- Forwarding logs
- Providing access for external monitoring
- Revoking access for external monitoring
- Reconfiguring the appliance
- Reconfiguring the appliance network
- Changing DNS or Hosts file settings
- Shutting down the appliance
- Performing a factory reset
- Performing a reimage
- Recovering storage data after a factory reset or a reimage
- Performing a storage reset
- Removing a node
- Viewing or resetting the storage shelf order on a Veritas 52xx Appliance
- Troubleshooting guidelines
Upgrading application instances
Use the following procedure to upgrade an existing instance in Flex Appliance.
To upgrade an instance
- Make sure that the new version of the application is located in the repository. See Managing the repository.
Note:
If the instance that you want to upgrade has a replica, make sure that the new version of the application is also located in the repository on the paired appliance.
- From the System topology page of the Flex Appliance Console, navigate to the Application instances section.
- Locate the instance that you want to upgrade. If it is stopped, click Actions > Start before you begin the upgrade so that the upgrade precheck can run.
- Stop all current backup operations on the instance.
- From the Application instances section, click Actions > Upgrade instance.
- Select the version that you want to upgrade to and click Precheck.
- If the precheck passes, click Next to continue. If the application needs any additional configuration parameters, you are prompted to enter them. Enter the parameters and click Next. Then verify the selection summary and click Upgrade to begin the upgrade process.
If the precheck returns with any error messages, resolve the issues before continuing with the upgrade.
If the upgrade fails for any reason, the instance automatically rolls back to the previous version. You can find more detailed information on the failure in the Activity Monitor. Resolve any issues before restarting the upgrade procedure.
- If your application does not support rollback, the upgrade is now complete.
If your application does support rollback, the instance version remains in a pending state for the next 24 hours. You must decide within that time period whether you want to commit to the new version or roll back to the previous version. Note that some operations are restricted until you commit or roll back. Complete the rest of this procedure to restore full functionality.
Warning:
Performing a rollback may lead to inconsistencies between the NetBackup catalog and the media servers for all jobs that ran after the upgrade. These inconsistencies can affect future backups.
To commit or roll back the instance version, navigate to the System topology > Application instances section and do one of the following:
To commit to the new version, locate the instance and click Actions > Upgrade instance > Commit. You can also click on the instance name to open the instance details page, then click Commit at the top of the screen.
To roll back to the previous version, stop all current backup operations on the instance. Then locate the instance and click Actions > Upgrade instance > Roll back. You can also click on the instance name to open the instance details page, then click Roll back at the top of the screen.
Warning:
Before you roll back the version of a primary server instance, check the versions of all media servers and clients that are used with it. The version of the primary server after rollback must be equal to or later than the versions of the connected hosts, including media server instances.
Caution:
If you do not commit or roll back within 24 hours of the upgrade, the new instance version is committed automatically.