Flex Appliance 7.0 new features, enhancements, and changes
The following list describes the new features, enhancements, and changes in the Flex Appliance 7.0 release:
You can configure multiperson authorization to add an extra layer of security by requiring additional authorized reviewers to approve critical operations.
A new two-step update process has been introduced which allows parallel prechecks in multi‑node clusters, reducing downtime and offering greater flexibility during updates.
You can create custom roles with specific permission sets beyond the default options. This flexibility ensures that users have exactly the rights needed for their jobs, reducing unnecessary access and improving security.
You can restrict network access to services running inside application instances. By allowing access only through specified ports and an allowable IP/CIDR list, network access control minimizes attack exposure and ensures that only trusted sources can communicate with NetBackup instances.
You can set resource limits to allocate CPU and memory resources efficiently to ensure optimal application performance.
Lockdown mode can be enabled at the appliance level using the Flex Appliance Console. At the instance level, you can change the lockdown mode.
See About lockdown mode.
You can retain the MAC address of the parent host interface across application stop and start events for an application instance.
You can prevent service disruption caused by inode exhaustion by monitoring the inode usage for all application instance volumes.
After a new installation of Flex Appliance, the dialog will appear at every login until the administrator explicitly enforces or opts out.
The supported ciphers and message authentication codes (MACs) in the Flex Appliance Shell has been updated to improve overall system security.
The supported protocols and cipher suites for Flex Appliance Console access have been updated .
The Flex Appliance Console has been enhanced to consistently use server time instead of client time, improving accuracy and consistency for all time‑based operations across the interface.