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
Resolving discrepancies between an active and a replica instance
An active instance and its replica instance should always have the same configuration. However, discrepancies can occur between them in the following scenarios:
You upgrade or update the active instance, but the newer version or revision is not in the repository on the appliance where the replica is located.
You install a new add-on on the active instance but do not install it on the replica instance.
You update an add-on on the active instance, but the newer revision is not in the repository on the appliance where the replica is located.
You update the replica instance to a newer revision.
You install or update an add-on on the replica instance
To avoid these scenarios, adhere to the following best practices:
Always make sure that the required application and add-ons are available in the repositories on both appliances.
If you install an add-on on the active instance, also install it on the replica instance. Alternatively, you can make sure the add-on is in the repository on the appliance where the replica is located and then pause and resume replication.
Do not perform operations on the replica instance unless they are required to match the configuration of the active instance.
You can verify the configurations of the active and the replica instances from the Remote replication page. Locate the instance that you want to check and click . The window that appears displays discrepancies if any exist, along with instructions on how to resolve them.