Important Update: Cohesity Products Documentation
All Cohesity product documentation are now managed via the Cohesity Docs Portal: https://docs.cohesity.com/HomePage/Content/home.htm. Some documentation available here may not reflect the latest information or may no longer be accessible.
NetBackup™ SAN Client and Fibre Transport Guide
- Introducing SAN Client and Fibre Transport
- Planning your deployment
- Planning your SAN Client deployment
- SAN Client operational notes
- About SAN Client storage destinations
- How to choose SAN Client and Fibre Transport hosts
- About NetBackup SAN Client support for agents
- About NetBackup SAN Client support for clustering
- About NetBackup SAN Client support for Windows Hyper-V Server
- About NetBackup SAN Client unsupported restores
- About Fibre Transport throughput
- Converting a SAN media server to a SAN client
- Preparing the SAN
- Preparing the SAN
- About zoning the SAN for Fibre Transport
- About zoning the SAN for Fibre Transport for a 16-gigabit target mode HBA support
- About HBAs for SAN clients and Fibre Transport media servers
- About the 16-gigabit target mode HBAs for SAN clients and Fibre Transport media servers
- When selecting the HBA ports for SAN Client
- About supported SAN configurations for SAN Client
- Licensing SAN Client and Fibre Transport
- Configuring SAN Client and Fibre Transport
- Overview of configuring SAN Client and Fibre Transport
- Configuring a Fibre Transport media server
- About the target mode driver
- About nbhba mode and the ql2300_stub driver
- About FC attached devices
- How to identify the HBA ports
- About HBA port detection on Solaris
- About Fibre Transport media servers and VLANs
- Start nbhba mode
- Mark the Fibre Transport media server HBA ports
- Configure the media server Fibre Transport services
- Configure the media server Fibre Transport services for a 16-gigabit target mode HBA support
- Display the FTMS state for a 16-gigabit target mode HBA support
- Identify the HBA ports for a 16-gigabit target mode HBA support
- Configuring SAN clients
- Configuring SAN clients in a cluster
- About configuring Fibre Transport properties
- Configure Fibre Transport properties
- Fibre Transport properties
- Configure SAN client usage preferences
- SAN client usage preferences
- Managing SAN clients and Fibre Transport
- Disabling SAN Client and Fibre Transport
- Troubleshooting SAN Client and Fibre Transport
- About troubleshooting SAN Client and Fibre Transport
- SAN Client troubleshooting tech note
- View the Fibre Transport logs
- About unified logging
- Stop and start the Fibre Transport services
- Stop and start the Fibre Transport services for a 16-gigabit target mode HBA support
- Backups failover to LAN even though Fibre Transport devices available
- Kernel warning messages when Cohesity modules load
- SAN client service does not start
- SAN Client Fibre Transport Service validation
- SAN client does not select Fibre Transport
- Media server Fibre Transport device is not active
- No Fibre Transport devices discovered
- Appendix A. AIX specific configuration details
- AIX Reference Information
- Before you begin configuring NetBackup on AIX
- About AIX persistent naming support
- About configuring robotic control device files in AIX
- About device files for SAN Clients on AIX
- About non-QIC tape drives on AIX
- About no rewind device files on AIX
- Create AIX no rewind device files for tape drives
- Disable the AIX dynamic tracking
SAN Client tape storage limitations
The following limitations exist for tape as a SAN Client storage destination:
Only FT backups from the same client are multiplexed in a particular MPX group.
FT backups from different clients are not multiplexed together in the same MPX group.
You cannot multiplex different SAN clients to the same tape. Different clients can still be backed up to the same FT media server, but they are written to different tape drives in different MPX groups.
FT and LAN backups (from the same client or different clients) are not multiplexed together in the same MPX group.
SAN Client does not support Inline Tape Copy over Fibre Transport; Inline Tape Copy jobs occur over the LAN. The SAN Client features is designed for very high speed backup and restore operations. Therefore, SAN Client excludes backup options (such as Inline Tape Copy) that require more resources to process and manage.