Veritas Flex Appliance Getting Started and Administration Guide
- Product overview
- Release notes
- Flex Appliance 2.1 new features, enhancements, and changes
- Flex Appliance 2.1.1 new features, enhancements, and changes
- Flex Appliance 2.1.2 new features, enhancements, and changes
- Flex Appliance 2.1.3 new features, enhancements, and changes
- Flex Appliance 2.1.4 new features, enhancements, and changes
- Supported upgrade paths to this release
- Operational notes
- Flex Appliance 2.1 release content
- Flex Appliance 2.1.1 release content
- Flex Appliance 2.1.2 release content
- Flex Appliance 2.1.3 release content
- Flex Appliance 2.1.4 release content
- Getting started
- Initial configuration guidelines and checklist
- Performing the initial configuration
- Adding a node
- Accessing and using the Flex Appliance Shell
- Accessing and using the Flex Appliance Console
- Managing the appliance from the Appliance Management Console
- Setting the date and time for appliance nodes
- Common tasks in Flex Appliance
- Managing network settings
- Managing users
- Overview of the Flex Appliance default users
- Changing the password policy
- 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
- Importing a remote user or user group to the Flex Appliance Console
- Editing a remote user domain in the Flex Appliance Console
- Changing a local user password in the Flex Appliance Console
- Expiring local user passwords in the Flex Appliance Console
- Removing users from the Flex Appliance Console
- Managing user authentication with smart cards or digital certificates
- Changing the hostadmin user password in the Flex Appliance Shell
- Changing the sysadmin user password in the Veritas Remote Management Interface
- Using Flex Appliance
- Managing the repository
- Creating application instances
- Managing application instances from Flex Appliance and NetBackup
- Managing application instances from Flex Appliance
- Upgrading application instances
- Updating an application instance to a newer revision
- About Flex Appliance upgrades and updates
- Appliance security
- Monitoring the appliance
- Reconfiguring the appliance
- Troubleshooting guidelines
Assigning Fibre Channel ports to an instance
To perform backups over Fibre Channel, you must assign ports to your application instances.
This release supports the following types of backups over Fibre Channel:
VMware SAN transport (initiator)
Tape out (initiator)
SAN client (Fibre Transport target) - supported on NetBackup 9.1.0.1 and later instances
Use the following procedure to assign one or more Fibre Channel ports to an application instance.
To assign Fibre Channel ports to an instance
- From the System topology page of the Flex Appliance Console, navigate to the Application instances section.
- Locate the instance that you want to assign ports to. If it is running, select it and click Stop. You can also wait to stop the instance until the Flex Appliance Console prompts you to if you prefer.
- Click on the instance name to open the instance details page, then navigate to the Fibre Channel tab.
- Click Assign ports and follow the prompts to assign available ports. If you assign a port as an initiator that was previously used as a target, you are prompted to rescan the port before you can continue.
Note:
Depending on the use case you select for the port, only the devices of that storage type are visible to the instance. If you want all devices to be visible to the instance, select all available options from the Used for drop-down menu.
Note the following information:
You can assign an initiator port to multiple instances if the instances belong to the same tenant. You cannot assign a target port to multiple instances.
You can use the same port for both VMware and Tape out backups.
You can assign multiple ports to the same application instance or instances as long as they meet the following guidelines:
Used for VMware SAN transport:
Multiple ports can be assigned to a single or to multiple application instances in any combination.
Used for Tape out or for both Tape out and VMware SAN transport:
Multiple ports can be assigned to a single or to multiple application instances. However, the ports that are connected to the same tape devices must also be connected to the same application instances. The same tape devices cannot be assigned to different instances using different ports.
Used for SAN client:
Multiple ports can be assigned to a single or to multiple application instances in any combination. Once you have assigned the ports, you cannot assign them to additional application instances or use them for another use case unless you unassign the existing instances.
A Fibre Transport (FT) target port can handle data streams from multiple SAN client initiator ports concurrently. However, if you want it to handle streams from more than two SAN client initiator ports, consider changing the following NetBackup primary server setting:
nbftconfig -setconfig -ncp4
Caution:
This setting applies to all FT target ports on all media servers in your NetBackup domain. This setting should only be increased from the default (2) when all of the following conditions exist:
All FT target ports on all media servers are at least eight gBit/s link speeds.
The mix of jobs is such that all of the media servers have unused FT pipes.
A large number of jobs from other SAN clients are waiting for resources.
The back-end storage units have a lot of unused throughput capacity.
If you increase the -ncp setting too high, the load balancing between multiple FT media servers could become highly imbalanced.