Veritas Flex Appliance Getting Started and Administration Guide
- Product overview
- Getting started
- Modifying settings
- 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 an Active Directory domain to the Flex Appliance Console
- Importing an Active Directory user or user group to the Flex Appliance Console
- Editing an Active Directory domain in the Flex Appliance Console
- Changing a user password in the Flex Appliance Console
- Removing a user from the Flex Appliance Console
- Changing the hostadmin user password in the Flex Appliance Shell
- Managing NetBackup application instance users
- Using Flex Appliance
- Managing the repository
- Creating application instances
- Managing application instances
- Resizing instance storage
- Editing instance network settings
- Managing application add-ons on instances
- Viewing instance performance metrics
- Running NetBackup commands on an application instance
- Setting environment variables on NetBackup instances
- Storing custom data on a NetBackup instance
- Establishing trust with a NetBackup 7.7.3 master server instance
- Upgrading application instances
- About Flex Appliance upgrades and updates
- Monitoring the appliance
- Reconfiguring the appliance
- Troubleshooting guidelines
Managing application instances
You can manage your application instances from the System topology page of the Flex Appliance Console. To access your existing instances, click on the box on the home page or the icon in the left-side navigation bar, then navigate to the Application instances section.
Under Application instances, you can perform the following tasks:
Create a new instance.
Select an existing instance to:
Relocate it to another node if you have a multi-node appliance.
Stop or start it.
Note:
When you start an instance, Flex Appliance automatically determines which node to start it on for optimal load balancing. Therefore, it may not start on the same node that it was located on when it was stopped. If you want the instance to run on a specific node, you can relocate it after it starts.
Use the drop-down to delete it.
Use the drop-down to resize the storage.
Use the drop-down to upgrade it.
Click on an existing instance to perform the following tasks:
View the instance details.
Edit the network settings, including IP address and interface pairs.
Manage add-ons.
You can also perform the following tasks outside of the Flex Appliance Console:
View live performance metrics of all of the instances on your appliance from the Flex Appliance Shell. See Viewing instance performance metrics.
Run NetBackup commands on a NetBackup master or media server instance from an SSH session.
Set environment variables on NetBackup 8.2 or later master server instances. See Setting environment variables on NetBackup instances.
Modify or disable the
nbdeployutilutility.The
nbdeployutilutility may adversely affect performance of NetBackup applications instances on a Veritas 5150 Appliance. If you do not need this feature or if you determine that it causes performance issues due to high CPU usage, you can modify the configuration or disable it as follows:Log in to the master server instance and create the following nbdeployutil configuration file if it is not present:
/usr/openv/var/global/nbdeployutilconfig.txtRefer to the topic "Scheduling capacity licensing reports" in the NetBackup Administrator's Guide, Volume II for the procedure to use custom values for the capacity licensing report.
Note:
Flex Appliance does not support adding local directories or manually editing most files on application instances. If you create a local directory or manually edit a file and the instance is relocated or stopped for any reason, the changes are not maintained when the instance restarts.
However, if you must store a small amount of critical data on an instance, you can store it in the /mnt/nblogs directory. Note that this directory has 250GB of storage space that cannot be resized. If you use too much storage space, the instance may be affected.
More Information