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 Console accounts for API automation
- 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
Flex Appliance 5.0 new features, enhancements, and changes
The following list describes the new features, enhancements, and changes in the Flex Appliance 5.0 release:
You can now assign new user roles on the Flex Appliance Console, including an observer base role and newly introduced extended roles.
This release introduces two new features that you can use to manage or monitor your appliances through API automation: personal API tokens and service accounts.
See Using Flex Appliance Console accounts for API automation.
You can now view and sign out of open Flex Appliance Console sessions. Each user can manage their own open sessions, and security administrators can manage all open sessions.
You can now gather the logs for a single application instance. This option provides a faster way to collect the logs for a specific instance only. It is available for NetBackup primary and media server instances on version 10.3.0.1 or later and on NetBackup WORM storage server instances on version 20.4 or later.
See Gathering logs.
The tokens that were previously called "API access tokens" have been renamed and are now called "predefined API tokens."
Starting with this release, the hostadmin account becomes locked for 15 minutes after three sign-in attempts with incorrect multifactor authentication codes.
The following APIs are no longer available:
PUT /v1/network/bonds/{bond-name}
Use
PUT /v1/networks/{interface}
instead.PUT /v1/users/local/{username}/password
Use
PUT /v2/users/{uid}/password
instead.DELETE /v1/users/active-directory
Use
DELETE /v1/user-domains
instead.POST /v1/applications/{package-name}
Use
POST /v1/applications
orPOST /v1/add-ons
instead.
Check Veritas SORT for more information on the APIs.
All inbound connections to the appliance now support TLS anonymous authentication version 1.3. Version 1.3 is used by default, while version 1.2 is available for backwards compatibility.
When a remote replication alert is resolved, you no longer receive an email alert to notify you that it has been resolved. You can see the latest alert status from the Remote replication page.