Veritas NetBackup™ Flex Scale Administrator's Guide
- Product overview
- Viewing information about the NetBackup Flex Scale cluster environment
- NetBackup Flex Scale infrastructure management
- User management
- Considerations for managing NetBackup Flex Scale users
- Adding users
- Changing user password
- Removing users
- Modifying user roles
- Considerations for configuring AD/LDAP
- Configuring AD server for Universal shares and Instant Access
- Configuring AD/LDAP servers for NetBackup services
- Configuring additional AD/LDAP servers for managing NetBackup services/Universal Shares/Instant Access
- Configuring AD/LDAP servers on clusters deployed with only media servers
- Directory services and certificate management
- Region settings management
- About NetBackup Flex Scale storage
- About Universal Shares
- Cloud bucket support for NetBackup Flex Scale
- Backing up data to Data Domain storage
- Node and disk management
- NetBackup Flex Scale network cabling
- Adding a node to the cluster using the NetBackup Flex Scale web interface
- Adding a node using the REST APIs
- Replacing a node in a cluster
- Starting and stopping nodes
- Rebooting a node
- Adding an excluded node to the cluster
- Replacing a disk
- Adding an excluded disk to the cluster
- Viewing the disk sync status
- Viewing disk details
- Viewing node details
- Switching management console to another cluster node
- License management
- Stopping NetBackup service containers
- Starting NetBackup service containers
- Managing the Fibre Channel ports
- Requirements
- Enabling BOM (Bill of Materials) configuration for Fibre Channel
- Assigning Fibre Channel ports
- Discovering attached devices
- Rescanning Fibre Channel cards
- Cleaning Fibre Channel ports
- Unassigning Fibre Channel ports
- Viewing details about the Fibre Channel ports
- Disabling BOM (Bill of Materials) configuration for Fibre Channel
- Managing hardware vendor packages
- Updating credentials for HPE iLO administrator users
- User management
- NetBackup Flex Scale network management
- About network management
- Modifying DNS settings
- Configuring MTU on public interfaces
- Configuring the console FQDN
- About bonding Ethernet interfaces
- Bonding operations
- Configuring NetBackup Flex Scale in a non-DNS environment
- Data network configurations
- Choosing the correct input method for data network configuration
- Network configuration on plain device (eth5)
- Network configuration on VLAN (eth5)
- Network configuration on bonded interfaces (bond0 on eth5 and eth7)
- VLAN on bond of eth5 and eth7 (bond0)
- Network configuration on management interface (eth1)
- Network configurations for adding a partial data network
- Support for multiple VLAN when disaster recovery is configured
- Configuring static routes on a NetBackup Flex Scale cluster
- NetBackup Flex Scale infrastructure monitoring
- Resiliency in NetBackup Flex Scale
- EMS server configuration
- Site-based disaster recovery in NetBackup Flex Scale
- About site-based disaster recovery in NetBackup Flex Scale
- Configuring disaster recovery using GUI
- Clearing the host cache
- Automated NetBackup SLP management
- DNS key management
- Managing disaster recovery using GUI
- Performing disaster recovery using RESTful APIs
- Active-Active disaster recovery configuration
- NetBackup optimized duplication using Storage Lifecycle Policies
- NetBackup Flex Scale security
- About the security meter
- STIG overview for NetBackup Flex Scale
- FIPS overview for NetBackup Flex Scale
- Managing the login banner
- Changing the password policy
- Support for immutability in NetBackup Flex Scale
- Authenticating users using digital certificates or smart cards
- About system certificates on NetBackup Flex Scale
- Deploying external certificates on NetBackup Flex Scale
- Configuring isolated recovery environment (IRE)
- Configuring multifactor authentication
- About multifactor authentication
- Considerations before configuring multifactor authentication
- Configuring multifactor authentication for your user account
- Disabling multifactor authentication for your user account
- Enforcing multifactor authentication for all users
- Configuring multifactor authentication for your user account when it is enforced in the cluster
- Resetting multifactor authentication for a user
- Single Sign-On (SSO)
- Appendix A. Maintenance procedures for HPE servers
- Replacement procedure for a chassis fan
- Replacement procedure for power supply
- Replacement procedure for a single OS disk
- Replacement procedure for both OS disks on a non- management console node
- Replacement procedure for NVMe disks (SSDs)
- Replacement procedure for RAID controller
- Replacement procedure for an Integrated Lights-Out (iLO) port
- Replacement procedure for quad-port NIC
- Procedure for memory expansion (DIMMs)
- Replacement procedure for memory (DIMMs)
- Replacement procedure for Mellanox port
- Replacement procedure for SFP port
- Replacement procedure for chassis
- Replacement procedure for a hard disk drive
- Replacement procedure for a Fibre Channel card for a cluster node
- Replacement procedure for a Fibre Channel card for a node that is not in a cluster
- Appendix B. Configuring NetBackup optimized duplication
- Appendix C. Disaster recovery terminologies
- Appendix D. Configuring Auto Image Replication
About lockdown modes
Lockdown mode is one of the features of ransomware protection. The lockdown mode protects your cluster data from internal and external threats by securing all the external endpoints from unauthorized access. Access to all the services is protected and authenticated.
NetBackup Flex Scale lockdown mode offers additional security levels to protect your appliance and data, in addition to the hardened, secure operating environment that comes out of the box.
Lockdown mode provides the following benefits:
It prevents unauthorized access or modification to the underlying operating system (OS). Once the lockdown mode is enabled, administrators cannot make changes to the OS or the internal components. If you need access to the OS for emergency operations, you must contact Veritas Technical Support to obtain a Support Key and temporarily unlock the appliance. This functionality prevents unauthorized changes even if a malicious user gains access to stolen credentials.
It gives the appliance users options for managing WORM (Write Once Read Many) data. Your data is protected from being encrypted, modified, and deleted using WORM properties.
Different lockdown modes provide different level of granularity for WORM and retention. The NetBackup Flex Scale appliance support three lockdown modes.
Normal mode:
This is the default mode of the cluster if the lockdown mode is not specified during installation.
In this mode, WORM and retention capabilities are disabled. User cannot create worm STU in this mode.
Enterprise mode:
In this mode, WORM and data retention features are enabled.
User can choose to create WORM-enabled STU.
User has the option to remove the retention locks and expire image data.
User can extend the retention period but cannot reduce the retention period.
The retention time period can be extended from the NetBackup primary container only if the user has the NetBackup administrator role.
Retention can be disabled or retention lock can be removed using the MSDP Restricted Shell only if the user has the appliance administrator role.
After removing the images retention locks from the MSDP Restricted Shell, the user still cannot expire images from the NetBackup Administration Console, but can expire the images from the NetBackup primary server using the following command:
/usr/openv/netbackup/bin/admincmd/bpexpdate -backupid n155-h201.cdc.veritas.com_1631842421 -d 0 -copy 1 -try_expire_worm_copy
Compliance mode:
In this mode, WORM and data retention features are enabled.
The user can extend the retention period.
The user does not have the option to remove retention locks and expire image data before the predefined time.
Once appliance lockdown mode is set to compliance, user does not have the option to delete data until it is expired.
Veritas strongly recommends that you enable enterprise lockdown mode to prevent unauthorized access to the OS, even if you do not plan to create WORM storage instances.