Follow

This guide seeks to help Infinidat customers who own InfiniGuard, and who also use NetBackup get the most out of their investment. It is also intended to help Infinidat field sales teams by providing guidance to enhance the installation and integration of NetBackup with InfiniGuard systems. This guide includes advice and best practices for using InfiniGuard systems with NetBackup.

Introduction

How to use this guide

This document assumes that the reader has basic expertise with NetBackup, as well as basic networking and SAN experience. It also assumes that the reader has an InfiniGuard system installed in a working NetBackup environment and provides key recommendations and useful information for quickly setting up InfiniGuard DDEs with NetBackup.

The InfiniGuard system is a fully optimized frame assembly for high density and extreme backup performance. InfiniGuard includes four, high density, disk-drive enclosures with 60, 6TB or 12 TB drives in each. It also includes 3 controllers, 2 FC switches, 3 deduplication engines (DDEs), and supporting ATS and BBUs, conveniently managed via an included customer patch panel. Customers will simply cable up InfiniGuard and begin configuring devices and policies to use the high speed, space efficient, enterprise backup solution. 

NetBackup interfaces with the Data Deduplication Engines (DDEs), so throughout this document they will be referred to as InfiiniGuard DDE or just DDE.

This document is organized according to the various storage target access methods to be employed with NetBackup. The InfiniGuard DDE can appear as a Storage Device using OpenStorage (OST), as a Virtual Tape Library (VTL) storage device over Fibre Channel (FC) and as Network Attached Storage device (NAS) over NFS and/or CIFS.

These access methods are discussed in the following order:

  • DDE OST (OpenStorage Technology) and NetBoost
  • DDE VTL
  • DDE NAS – NFS and/or CIFS

Documentation and reference

Infinidat InfiniGuard 3.0 Documentation Center

InfiniGuard 3.0 User Guide

Veritas NetBackup Documentation Center

NetBackup Administrator Guide
NetBackup Command Reference Guide
NetBackup Operating System Software Compatibility List
NetBackup Enterprise Server and Server
Hardware and Cloud Storage Compatibility List (HCL)

Summary of Tuning Parameters for NetBackup

For backup administrators who are well versed on NetBackup and InfiniGuard systems, the following table offers a summary of suggested parameters/values. As with any modifications to a system that impacts performance and/or tuning, your results may vary and are not guaranteed.

Parameter, or OptionSettings
CompressionDo not enable NetBackup's Compression feature (available within the NetBackup policy).
While NetBackup supports compression, to obtain effective deduplication performance rates, you should NOT compress your backup data before sending it to a DDE appliance.
EncryptionDo not enable NetBackup's encryption feature.
While NetBackup supports encryption, for best deduplication performance utilize the hardware encryption provided by the DDE.
DeduplicationDo not enable NetBackup's deduplication feature (available within the NetBackup policy).
To obtain effective deduplication rates, you should NOT deduplicate your backup data before sending it to a DDE appliance (as the DDE will provide best space reduction at the target on ingest).
OST options
Max connections300
LSU images250,000
VTL options
Virtual Library Emulation

Infinidat IBA B4260 DDE (DXi6900)

For AIX configurations see,  Medium changer configuration options for AIX below

Virtual Drive Emulation

On Windows, Linux and Solaris OS:   Emulate as per the NetBackup HCL: IBM or HP LTO virtual tape drives

On AIX OS:  Use HP LTO drive emulations

On HP-UX:   Use IBM LTO drive emulations

SCSI ReserveVeritas recommends using SCSI Persistent Reservation (SPR) if all the hardware in the device path supports it; otherwise use the default SPC-2 SCSI reserve and release method.
Miscellaneous
Server Name

Use only standard ANSI characters for the computer name of the computer on which you want to install NetBackup.

You may receive errors if you install NetBackup on a computer with a name that uses non-standard characters. Windows users must access the NetBackup server by logging in through their Windows domain or the Local account, depending on where it is installed.

Veritas Buffer SettingsDue to the complexity of each enterprise backup environment it is almost impossible to recommend an optimal configuration which fits all.  So Infinidat recommends keeping the default settings unless you are comfortable with Veritas suggestions as outlined here and in the Veritas Tech Notes linked below.
TCP/IP Network Buffer SizeNET_BUFFER_SZ = 262144
Refer to NetBackup KB Article TECH1724 for additional information.
Data Buffer Size and Number of Data Buffers

Most cases:

SIZE_DATA_BUFFER = 262144

NUMBER_DATA_BUFFER = 16

10GB Single Stream Performance:

SIZE_DATA_BUFFER = 1048576

NUMBER_DATA_BUFFER = 16

Refer to NetBackup KB Article TECH1724 for additional information
Windows OS Options
Network

On a heavily utilized system consider increasing TCP/IP timeout on NetBackup Media Server.

Reference: Adjusting the TCP KeepAliveTime parameter: 

https://www.veritas.com/content/support/en_US/article.100028680.html

Users may also reference Microsoft articles on TcpMaxDataRetransmissions

http://support.microsoft.com/kb/170359

NetBoost Resources

Minimum requirements:

  • CPU - Greater than 2.2 GHz processor with at least 2 cores (4 cores recommended)
  • Memory - 2 GB RAM or greater

Note:  Minimum requirements often do not reflect Best Practice, as such Infinidat recommends consideration of designing your systems using greater than minimum requirements.

Configuring NetBackup with InfiniGuard DDE OST

The integration of OpenStorage (OST) API initiative with InfiniGuard, disk backup, deduplication, and replication solutions provides end users with a highly optimized solution for managing backup data across multiple locations and storage tiers. The DDEs OST support allows users to set up Storage Servers and Logical Storage Units (LSUs) on the DDE units, and to use NetBackup to duplicate data between DDE- based LSUs in different locations, providing disk-to-disk DR protection, while leveraging the DDEs deduplication technology to dramatically reduce network bandwidth requirements.

The DDE systems can copy data from one system to another (replication). NetBackup uses this capability to initiate an optimized duplication of backup images between these appliances. The duplication operation of NetBackup triggers the duplication function in the OST Disk Appliance, if both the source and destination volumes for the copy are OST LSUs. OST optimized duplication reduces the workload on the NetBackup Media Server because the replication is performed by the DDE. Duplication is done in the background and is faster because it uses InfiniGuard data deduplication capabilities to reduce the copy bandwidth. Duplication is still initiated, managed, and controlled by the NetBackup Media Server, while the actual data movement process is off-loaded to gain the maximum benefits from the InfiniGuard replication capabilities. OST optimized duplication can be used for duplication from or to a DDE, as disk backup targets.

Veritas's NetBackup OST (OpenStorage) allows NetBackup to seamlessly integrate with InfiniGuard. Once the OST plugin is installed and configured, NetBackup can manage the backups through the DDE and take advantage of the system's capabilities, such as data deduplication and replication minimizing space and network traffic.

Installing and Configuring OpenStorage (OST) Plug-ins

The OST presentation requires the Veritas NetBackup host application and the OST Plug-in client installation on the media server.  Plug-in clients are host operating system dependent and are supplied by Infinidat. To use the InfiniGuard DDE in OST mode, you must configure an OST storage server and LSUs on the DDE. You must also map the LSUs on the NetBackup Media Server so that NetBackup can perform backups and restore from them. Additionally, policies for optimized duplication (OST replication) need to be set on the NetBackup server.

Additional Documentation

This document provides InfiniGuard installation and configuration for OST with Veritas NetBackup.  For additional information see Documentation and reference for links to InfiniGuard and Veritas documentation

InfiniGuard OST configuration is organized in the following major sections.  

OST Plug-In Compatibility Information

The OST plug-in is based on Veritas OpenStorage API specification Version 9.4.2 and 11.1. The following components are required for OST operation with the InfiniGuard:

  • Veritas NetBackup 7.5 or later
  • Veritas NetBackup 52xx Appliance version 2.7.1 or later
  • Veritas NetBackup 53xx Appliance version 2.7.1 or later

Operating System Support

The InfiniGuard OST plug-in contains support for the following systems:

  • Windows support:
    • Windows 2008 R2 64-bit
    • Windows 2012 64-bit
    • Windows 2012 R2 64-bit
    • Windows 2016 64-bit
    • Windows 2019 64-bit
  • Linux support:
    • RedHat Linux 6 x86 64-bit
    • RedHat Linux 7 x86 64-bit
    • RedHat Linux 8 x86 64-bit
    • SUSE11 Linux x86 64-bit
    • SUSE12 Linux x86 64-bit
    • SUSE15 Linux x86 64-bit
  • Appliance Support:
    • Veritas NBU 52xx/53xx Appliance RedHat Linux (2.7.1 or later)

General OST plugin guidelines

The following list provides general guidelines for OST Plug-in:

  • A host can only have a single OST plug-in installed at a time. (Multiple hosts with different installed plug-in versions are supported.)
  • It is required to use the InfiniGuard OST plug-in with InfiniGuard systems for backups and optimized duplication.
  • Refer to the release notes for your InfiniGuard version for more information on replication, OST, and optimized duplication compatibility.

OST and NetBoost data encryption Files

The InfiniGuard Software requires the certificate and key files to be installed on the InfiniGuard and media servers if any encryption method is selected (AES 128, AES 256, or TLS with AES 256).
OST and InfiniGuard NetBoost data encryption options are available at Configuration > System > Security > Data Encryption page on the InfiniGuard DDE.

  • You can install new certificate and key files at any time, as long as there are no active network connections between the OST media server and the InfiniGuard.
  • Upon the selection of any of the available encryption types (AES 128, AES 256, TLS with AES 256), all OST data streams will be encrypted.
  • If no encryption option is selected, neither InfiniGuard NetBoost or OST data will be encrypted.

Installing the OST Plug-in

The following sections provide instructions for installing the OST plug-in on each operating system.            

Download the OST Client Plug-in

To download the NetBoost for NetBackup OST Plug-in: from the InfiniGuard Admin console, click  Infinidat support site>InfiniGuard plug-ins and download the NetBoost OST plug-in for the operating system of the Media Server it will be installed on.

Install the OST Plug-in for RedHat Linux 64-bit

Uninstall older OST plug-ins if already installed. See, Uninstalling the OST Plug-In.
To install the plug-in:

  1. Stop the NetBackup processes.

  2. Create a temporary directory, such as /usr/tmp/INFINIDATplugins.

  3. Move or download INFINIDATOSTPluginxR_x86.64.tar to /usr/tmp/INFINIDATplugins.

  4. Extract the files using /bin/tar xvf INFINIDATOSTPluginlinuxR_x86.64.tar.

  5. Move the plug-in using:
    mv libstspiINFINIDAT.so /usr/openv/lib/ost-plugins/
    mv libstspiINFINIDATMT.so /usr/openv/lib/ost-plugins/

  6. Move the configuration file using: /bin/mkdir -p /usr/INFINIDAT; /bin/mv INFINIDATPlugin.conf /usr/INFINIDAT

Certificate files for encryption must be installed when any method of encryption is used. Move the certificate files using the following commands:

It is recommended that custom certificate files be installed to provide maximum encryption security. Use of the default certificate files provided by Infinidat is not recommended. It is recommended to back up any previous files that may be found on these directories. The certificate files should be the same as the certificate files installed on the InfiniGuard using the Configuration > System > Security > Data Encryption

/bin/mv cacert.pem /usr/INFINIDAT
/bin/mv cert.pem /usr/INFINIDAT
/bin/mv key.pem /usr/INFINIDAT

8. (Optional) Delete the temporary directory created in step 2. In this example it is: rm -rf /usr/tmp/INFINIDATplugin

9. Restart the NetBackup processes to initiate backups and restores.

The OST Plug-in is installed.

Install the OST Plug-in for SUSE Linux 64-bit

If older OST plug-ins are already installed, you must uninstall them first. See, Uninstalling the OST Plug-In.
To install the plug-in:

  1. Stop the NetBackup processes.
  2. Create a temporary directory, such as /usr/tmp/INFINIDATplugins.
  3. Move or download INFINIDATOSTPluginlinuxS_x86.64.tar to /usr/tmp/INFINIDATplugins.
  4. Extract the files using /bin/tar xvf INFINIDATOSTPluginlinuxS_x86.64.tar.
  5. Move the plug-in using:
    mv libstspiINFINIDAT.so /usr/openv/lib/ost-plugins/
    mv libstspiINFINIDATMT.so /usr/openv/lib/ost-plugins/
  6. Move the configuration file using:
    /bin/mkdir -p /usr/INFINIDAT; /bin/mv INFINIDATPlugin.conf /usr/INFINIDAT
  7. Certificate files for encryption must be installed when any method of encryption is used. Move the certificate files using the following commands: 

It is recommended that custom certificate files be installed to provide maximum encryption security. Use of the default certificate files provided by Infinidat is not recommended. It is recommended to back up any previous files that may be found on these directories. The certificate files should be the same as the certificate files installed on the InfiniGuard using the Configuration > System > Security > Data Encryption

/bin/mv cacert.pem /usr/INFINIDAT
/bin/mv cert.pem /usr/INFINIDAT
/bin/mv key.pem /usr/INFINIDAT

8. (Optional) Delete the temporary directory created in step 2. In this example it is:  rm -rf /usr/tmp/INFINIDATplugins

9. Restart the NetBackup processes to initiate backups and restores.

The OST Plug-in is installed.

Install the OST Plug-in for Windows 2008/2012/2016/2019

If older OST plug-ins are already installed, you must uninstall them first.  See, Uninstalling the OST Plug-In


Caution

  • Installing a new plug-in on Windows overwrites the existing C:\libstspiINFINIDAT.iniconfiguration file. If you have made custom changes to the original file, please make a copy of the file prior to installing the new plug-in.
  • After installing the plug-in, you must manually reconfigure your custom settings in the new plug-in .ini file. You can use the older .ini file as a reference to do this. However, do not overwrite the new plug-in .ini file with the older file.

To install the plug-in:

  1. Run INFINIDATOSTPluginWinX64.msi (64-bit).
    Follow the instructions given by the installation wizard to complete the installation.
  2. During installation, the Infinidat default certificate files are installed on the InfiniGuard %WINDIR\INFINIDAT directory. These files are needed if the TLS with AES 256 encryption option for NetBoost is enabled.
    If you want to use custom certificates, first make a backup of the default certificates located in the %WINDIR\INFINIDAT directory. Then copy the custom certificates into this directory.

The OST Plug-in is installed.

Install the OST Plug-in on NetBackup 52xx/53xx Appliance (2.7.1 and later)

If older OST plug-ins are already installed, you must uninstall them first. See, Uninstalling the OST Plug-In
To install an OST plug-in on a Veritas NetBackup™ 52xx/53xx Appliance, please refer to the Veritas NetBackup™ Appliance Administrators Guide at https://www.veritas.com/support/en_US.html

Uninstalling the OST Plug-In

Uninstalling Linux OST Plug-in

To uninstall the OST Plug-in:

  1. Wait until all NetBackup jobs are finished and then stop the NetBackup processes.
  2. Remove older plug-ins by running the following commands:
    • /bin/rm /usr/openv/lib/ost-plugins/libstspiINFINIDAT*
    • /bin/rm /usr/INFINIDAT/INFINIDATPlugin.conf
    • /bin/rm /usr/INFINIDAT/*.pem

Uninstalling the Windows OST Plug-in

To uninstall the Windows OST NetBackup Plug-in:

A note on preparing for un-installation:

Uninstalling the OST Plug-in removes the existing certificates, and installing a new OST Plug-in installs the factory default certificates.
Before uninstalling the plug-in, make a copy of any custom certificates in the %WINDIR\INFINIDAT directory, then restore the custom certificates to this location after installing a new plug-in.

  1. Wait until all the NetBackup jobs are finished, then stop NetBackup processes.
  2. Go to Start > Control Panel > Add/Remove Programs and select Infinidat OST Plug-in for Windows.
  3. Click Remove to start the un-installation process.

Uninstall NetBackup 52xx/53xx Appliance Plug-in

To uninstall an OST plug-in on a Veritas NetBackup™ 52xx/53xx Appliance, please refer to the Veritas NetBackup™ Appliance Administrators Guide at https://www.veritas.com/support/en_US.html.


Configuring InfiniGuard DDEs for OST


To use the InfiniGuard DDE in OST mode, you must configure an OST storage server and LSUs on the DDE. You must also map the LSUs on the NetBackup Media Server so that NetBackup can perform backups and restore from them. Additionally, policies for optimized duplication (OST replication) need to be set on the NetBackup server.

Configuring the OST Authentication

To authenticate the OST storage servers on a media server, you must create local OST user credentials. After you create the OST user credentials, enter them in the backup application to authenticate OST devices on the media server.

Note

Authentication between the OST Plug-in and InfiniGuard DOES NOT USE Active Directory. Instead, you must add new OST user credentials on the InfiniGuard and the media server

To create OST user credentials:

  1. Log in to the InfiniGuard management console.
  2. Navigate to the Configuration > System > Manage Users page.
  3. Click Add.
  4. Specify the Username and New Password that will be used to authenticate the storage servers on the media server.
    Note: For username, alphanumeric characters are allowed, as well as underscores ( _ ) and hyphens ( - ). For password, alphanumeric characters are allowed, as well as the following special characters: ` ~ ! @ # $ % ^ & * ( ) - _ = + [ { ] } \ | ; : ' “ , < . > / ? 
    Provide the same credentials on the media server. Do not include the domain name in the username.
  5. Click Apply.
  6. On the NetBackup management console, add credentials for the Storage Server, making sure to use the same OST username and password you entered on the InfiniGuard.

Configuring OST Backup and Replication Environment

The OST page allows you to configure the InfiniGuard to present its storage capacity as storage servers using OpenStorage (OST) technology. You can add one or more Logical Storage Units (LSUs) to a storage server. Storage servers and LSUs are compatible with backup applications that support OST, such as Veritas NetBackup. In addition, OST data can be duplicated (replicated) between InfiniGuard systems using NetBackup (see OST Data Replication).

To access the OST page, click the Configuration menu, and then click the OST tab.

The OST page contains the following tabs

Configuring Storage Servers

The Storage Servers page allows you to manage OST storage servers on the InfiniGuard DDE. You can view information about existing storage servers, add or edit storage servers, and delete storage servers.

To access the Storage Servers page, on the OST page, click the Storage Servers tab.

Storage Servers Page

Tasks

Use the Storage Servers page to perform the following tasks:

Storage Server List

The Storage Server List displays the following information for all storage servers on the InfiniGuard DDE:

Storage Servers

The number of storage servers that have been added to the system.

Maximum Storage Servers

The maximum number of storage servers that can be added to the system.

LSUs

The number of logical storage units (LSUs) that have been added to the system (see LSU).

OST Service

The status of the OST service. OST settings can be configured in Ready, Stopped, or Verifying state. The OST server is available for backup only in Ready state.

Name

The name of the storage server.

LSUs

The number of LSUs that have been added to the storage server.

Max Connections

The maximum number of connections allowed to the storage server.

Active Connections

The number of currently active connections to the storage server.

Backup Images

The number of backup images on the storage server.

Concurrent Optimized Duplication

The status of Concurrent Optimized Duplication for the storage server (Enabled or Disabled), as well as the configured targets (if any).

Description

A brief description of the storage server (if available).

Additional Information

  • Click a column heading to sort the rows in the table by that column. Click the column heading again to reverse the sort order.
  • The connections of a storage server that are used equals the data streams plus one for each LSU polling. A backup job may generate more than one data stream if the data can be read in parallel. For example, a policy that is backing up A, B, C, and D drives of a Windows system can generate four data streams in parallel.

Adding a Storage Server

Add a storage server to present the storage capacity of the InfiniGuard as LSUs that are compatible with backup applications that support OST. You can add up to 100 storage servers. When adding a storage server, you must also add an LSU to the storage server. (For more information about LSUs, see LSU)

Note

Data on storage servers is always deduplicated.

To add a storage server:

  1. Click Add.

The Add Storage Server page displays.

Add Storage Server Page

2. Under Add Storage Server, enter information about the storage server:

Name

Enter the name of the storage server.

Caution: Do not use an underscore ( _ ) in the name of the storage server.

Note: OST storage server names are not case-sensitive. For example, if you create a storage server named ost1, you cannot create another storage server named OST1 because the system considers the names to be the same.

Description

(Optional) Enter a brief description of the storage server.

Max Connections

Enter the maximum number of connections allowed to the storage server. To disable OST, enter 0 connections. To enable OST, enter 3 to 65536 connections.

Note: Infinidat recommends setting Max Connections to 300.

Enable Concurrent
Optimized Duplication

Select the check box to enable optimized duplication during OST ingest.

Concurrent Optimized Duplication is disabled by default. If enabled, as data is written to the storage server, it is simultaneously replicated to the target InfiniGuard DDE. When optimized duplication or Automatic Image Replication subsequently occurs, the operation is more efficient because a portion of the required data has already been replicated to the target storage server.


Note: To configure the target DDE, (see Adding a Replication Target).

Note: When Concurrent Optimized Duplication is enabled, all data on the storage server is duplicated, not just the specified images.

3. Select the check box for each optimized duplication target you want to duplicate the storage server to. When the storage server is duplicated, its data will be sent to all selected targets.

4. Under Logical Storage Unit, select the type of LSU to add to the new storage server:

Available Capacity

 (Recommended for best performance) Select this option to add an LSU that uses the available capacity on the system.
You cannot add an available capacity LSU to a storage server that already contains an LSU. Also, if you add an available capacity LSU to a storage server, you cannot add additional LSUs to that same storage server.

Note: After you add an LSU that uses the Available Capacity option, you cannot change the LSU to use the Specific Capacity option. Instead, you must delete the LSU, then add a new LSU and choose the Specific Capacity option (see Deleting an LSU).

Specific Capacity

Select this option to specify the physical capacity of the LSU, and then enter the following information.

  • LSU Name - Enter the name of the LSU.
  • Physical Capacity - Enter the physical capacity of the LSU (1 to 1048576 GB).

Note: Infinidat recommends setting LSUs to maximum size (1048576 GB) because spanning them on a backup is not possible.

5. (Optional) In the Description box, enter a brief description of the LSU.

6. (Optional) Select the Enable Automatic Image Replication check box to automatically replicate (duplicate) data on the LSU to a remote LSU on another InfiniGuard DDE.

Automatic Image Replication (AIR) is disabled by default. If enabled, data on an LSU is automatically replicated to a remote LSU that resides on a DDE in a different NetBackup domain. The timing of the duplication, as well as the backup images that are duplicated, are determined by the storage lifecycle policies (SLPs) configured in NetBackup.
OST AIR requires NetBackup 7.6 or higher.

Note

You must configure at least one remote user before you can enable Automatic Image Replication (see Manage Remote Users).

7. If Automatic Image Replication is enabled, select the replication target you want to replicate images to. (You can select only a single target.) When images are replicated, data will be sent to the selected target.

8. If Automatic Image Replication is enabled, specify the following information:

Remote Storage Server Name

The name of the remote storage server (on the target DDE) to replicate data to. The source DDE and target DDE must reside in different NetBackup domains.

Note: To configure the target InfiniGuard DDE, see Replication Send.

Remote LSU NameThe name of the LSU in the remote storage server that will receive the replicated data.
Remote UserThe OST user credentials to use for authentication of the remote (target) DDE. The selected remote user must match a local user on the Configuration > System > Manage Users page on the target DDE (see Manage Users).

9. Click Apply.

Editing a Storage Server

Edit a storage server to change the description of the storage server or the maximum number of allowed connections.

To edit a storage server:

  1. Select the storage server and click Edit.

The Edit Storage Server page displays.

Edit Storage Server Page

2. Enter information about the storage server:

Note

If you are editing a storage server, the Name option cannot be changed.


Description

(Optional) Enter a brief description of the storage server.

Max Connections

Enter the maximum number of connections allowed to the storage server (3 to 65536).

The maximum number of connections cannot be changed if the storage server has more than zero currently active connections. The number of active connections is displayed on the OST page (see Storage Server List).

Note: Infinidat recommends setting Max Connections to 300.

Enable Concurrent Optimized Duplication

Select the check box to enable optimized duplication during OST ingest.

Concurrent Optimized Duplication is disabled by default. If enabled, as data is written to the storage server, it is simultaneously replicated to the target DDE. When optimized duplication or Automatic Image Replication subsequently occurs, the operation is more efficient because a portion of the required data has already been replicated to the target storage server.

Additional Information:

    • To configure the target DDE, (see Replication Send).
    • When Concurrent Optimized Duplication is enabled, all data on the storage server is duplicated, not just the specified images.

3. Select the check box for each optimized duplication target you want to duplicate the storage server to.

When the storage server is duplicated, its data will be sent to all selected targets.

4. Click Apply.

Deleting a Storage Server

Delete a storage server if it is no longer needed. When you delete a storage server, all data stored on the storage server is lost.

Note

If you deleted the storage server from Veritas NetBackup, you must wait several minutes before deleting the storage server from the InfiniGuard DDE.

To delete a storage server:

1. Select the storage server in the Storage Server List.

You cannot delete a storage server if it has more than zero currently active connections. The number of active connections is displayed on the OST page (see Storage Server List). Also, you cannot delete a storage server if it contains LSUs. Before deleting the storage server, you must first delete any LSUs it contains (see Deleting an LSU).

Note

  You can select multiple storage servers to delete at once.

2. Click Delete.

Configuring LSUs - Logical Storage Units

The LSU page allows you to manage the logical storage units (LSUs) contained on OST storage servers on the InfiniGuard DDE. You can view information about existing LSUs, add or edit LSUs, and delete LSUs.

To access the LSU page, on the OST page, click the LSU tab.

LSU - Logical Storage Unit List page

Tasks

Use the LSU page to perform the following tasks:

Logical Storage Unit List

The Logical Storage Unit List displays the following information for all LSUs on the InfiniGuard DDE:

OST Service

The status of the OST service. OST settings can be configured in Ready, Stopped, or Verifying state. The OST server is available for backup only in Ready state.

LSU Name

The name of the LSU.

Storage Server

The storage server that contains the LSU.

Physical Capacity

The physical storage capacity of the LSU.

Automatic Image Replication

The status of Automatic Image Replication (AIR) for the LSU (Enabled or Disabled), as well as the configured targets (if any).

Note: To view details about the remote LSU if AIR is enabled, use the Edit Logical Storage Unit page (see Editing an LSU).

Active Connections

The number of currently active connections to the LSU.

Backup Images

The number of backup images on the LSU.

Description

A brief description of the LSU (if available).


Additional Information

Click a column heading to sort the rows in the table by that column. Click the column heading again to reverse the sort order.

The connections of a storage server that are used equals the data streams plus one for each LSU polling. A backup job may generate more than one data stream if the data can be read in parallel. For example, a policy that is backing up A, B, C, and D drives of a Windows system can generate four data streams in parallel.

Adding an LSU

Add an LSU to a storage server to present the storage capacity of the InfiniGuard DDE as an LSU that is compatible with backup applications that supports OST. You can add an LSU with a specific capacity, or you can add an LSU that uses the available capacity of the DDE.

Note

You must create a storage server before you can add an LSU (see Adding a Storage Server).

To add an LSU to a storage server:

1. Click Add.

The Add Logical Storage Unit page displays.

Add Logical Storage Unit Page

2. Enter information about the LSU.

Storage Server

Select the storage server that will contain the new LSU.

Available Capacity

(Recommended for best performance) Select this option to add an LSU that uses the available capacity on the system.

You cannot add an available capacity LSU to a storage server that already contains an LSU. Also, if you add an available capacity LSU to a storage server, you cannot add additional LSUs to that same storage server.

Note: After you add an LSU that uses the Available Capacity option, you cannot change the LSU to use the Specific Capacity option. Instead, you must delete the LSU, then add a new LSU and choose the Specific Capacity option (see Deleting an LSU).

Specific Capacity

Select this option to specify the physical capacity of the LSU, and then enter the following information.

  • LSU Name - Enter the name of the LSU.
  • Physical Capacity - Enter the physical capacity of the LSU (1 to 1048576 GB).

Note: Infinidat recommends setting LSUs to maximum size (1048576 GB) because spanning them on a backup is not possible.

3. (Optional) In the Description box, enter a brief description of the LSU.

4. (Optional) Select the Enable Automatic Image Replication check box to automatically replicate (duplicate) data on the LSU to a remote LSU on another InfiniGuard DDE.

Automatic Image Replication (AIR) is disabled by default. If enabled, data on an LSU is automatically replicated to a remote LSU that resides on an InfiniGuard DDE in a different NetBackup domain. The timing of the duplication, as well as the backup images that are duplicated, are determined by the storage lifecycle policies (SLPs) configured in NetBackup.
OST AIR requires NetBackup 7.6 or higher.

Note

You must configure at least one remote user before you can enable Automatic Image Replication (see Manage Remote Users).

5. If Automatic Image Replication is enabled, select the replication target you want to replicate images to. (You can select only a single target.) When images are replicated, data will be sent to the selected target.

6. If Automatic Image Replication is enabled, specify the following information:

Remote Storage Server Name

The name of the remote storage server (on the target DDE) to replicate data to. The source DDE and target DDE must reside in different NetBackup domains.

Note: To configure the target InfiniGuard DDE, (see Replication Send).

Remote LSU NameThe name of the LSU in the remote storage server that will receive the replicated data.
Remote User

The OST user credentials to use for authentication of the remote (target) DDE. The selected remote user must match a local user on the Configuration > System > Manage Users page on the target DDE (see Manage Users).

7. Click Apply.

Editing an LSU

Edit an LSU to change its capacity, description, or automatic image replication settings.

To edit an LSU:

  1. Select the LSU and click Edit.

The Edit Logical Storage Unit page displays.

Edit Logical Storage Unit page

2. Enter information about the LSU:

Note

If you are editing an LSU, the Name option cannot be changed.


Physical Capacity

(Specific capacity LSUs only) Enter the physical capacity of the LSU (1 to 1048576 GB).

The physical capacity cannot be changed if the LSU has more than zero currently active connections. The number of active connections is displayed on the LSU page (see Logical Storage Unit List).

Note: The physical capacity on the LSU can be changed, but cannot be resized to lower than the current used capacity on the LSU.

Description

(Optional) Enter a brief description of the LSU.

3. (Optional) Select the Enable Automatic Image Replication check box to automatically replicate (duplicate) data on the LSU to a remote LSU on another InfiniGuard DDE.

Automatic Image Replication (AIR) is disabled by default. If enabled, data on an LSU is automatically replicated to a remote LSU that resides on an InfiniGuard DDE in a different NetBackup domain. The timing of the duplication, as well as the backup images that are duplicated, are determined by the storage lifecycle policies (SLPs) configured in NetBackup.

OST AIR requires NetBackup 7.6 or higher.

Note

You must configure at least one remote user before you can enable Automatic Image Replication (see Manage Remote Users).

4. If Automatic Image Replication is enabled, select the replication target you want to replicate images to. (You can select only a single target.) When images are replicated, data will be sent to the selected target.

5. If Automatic Image Replication is enabled, specify the following information:

Remote Storage Server
Name

The name of the remote storage server (on the target DDE) to replicate data to. The source DDE and target DDE must reside in different NetBackup domains.

Note: To configure the target InfiniGuard DDE, (see Replication Send ).

Remote LSU Name

The name of the LSU in the remote storage server that will receive the replicated data.

Remote User

The OST user credentials to use for authentication of the remote (target) InfiniGuard DDE. The selected remote user must match a local user on the Configuration > System > Manage Users page on the target InfiniGuard DDE (see Manage Users).

6. Click Apply.

Deleting an LSU

Delete an LSU if it is no longer needed. When you delete an LSU, all data stored on the LSU is lost.

Note

If you deleted the LSU from Veritas NetBackup, you must wait several minutes before deleting the LSU from the InfiniGuard DDE.

To delete an LSU:

  1. Select the LSU in the Logical Storage Unit List.

You cannot delete an LSU if it has more than zero currently active connections. The number of active connections is displayed on the LSU page (see Logical Storage Unit List).

Note

You can select multiple LSUs to delete at once.

2. (Optional) Select the Force Delete LSU check box to delete LSUs that are not empty.

Normally, you cannot delete an LSU if it contains existing backup images. If for some reason you cannot remove files from the LSU, selecting the Force Delete LSU check box allows you to delete the LSU even though it is not empty.

3. Click Delete.

Manage Remote Users

The Manage Remote Users page allows you to create and manage remote users for use with OST
Automatic Image Replication (AIR). You must configure at least one remote user before you can enable
Automatic Image Replication for an LSU (see Adding an LSU). When using OST Automatic Image Replication (AIR), the remote user credentials specified on the source InfiniGuard DDE must match the local user credentials on the target (remote) InfiniGuard DDE.

To access the Manage Remote Users page, on the OST page, click the Manage Remote Users tab.

Manage Remote Users page

Tasks

Use the Manage Users page to perform the following tasks:

Manage Remote Users List

The Manage Remote Users list displays the following information for all remote users:

Name

The name of the remote user.

Description

A brief description of the remote user (if available).

Note

  To update the list with the latest information, click Refresh.

Adding a Remote User

Add a remote user to create OST user credentials for use with OST AIR. When you enable Automatic Image Replication for an LSU, you specify a remote user. The remote user credentials on the source InfiniGuard DDE must match the local user credentials on the target (remote) InfiniGuard DDE.

To add a remote user:

  1. Click Add.

The Add Remote AIR Credential window displays.

Add Remote AIR Credential page

2. Enter information about the remote user:

User name

Enter the name of the remote user.

Note: An AIR user name can contain the following characters: 'a-z', 'A-Z', '0-9', '_', and '.'

New Password

Enter the password for the remote user.

Confirm New Password

Enter the password again to confirm it.

Description

(Optional) Enter a brief description of the remote user.

3.Click Apply.

Editing a Remote User

Edit a remote user to change the user's password or description.

To edit a remote user:

  1. Select the user and click Edit.

The Edit Remote Credentials window displays.

Edit Remote Credentials page

2. Enter information about the remote user:

Nope

Note: If you are editing a remote user, you cannot change the User name.

New Password

Enter the password for the remote user.

Confirm New Password

Enter the password again to confirm it.

Description

(Optional) Enter a brief description of the remote user.

3. Click Apply.

Deleting a Remote User

Delete a remote user if the OST user credentials are no longer needed to authenticate an LSU for Automatic Image Replication.
To delete a remote user, select the user and click Delete.

Note

You can select multiple users to delete at once.

Target IP Mapping

The Target IP Mapping page allows you to map a target data IP address to route all network traffic sent to the data IP address to the specified replication IP address instead. This can be necessary if the target InfiniGuard is configured with different network interfaces (and therefore different IP addresses) for data and replication traffic (see Network).

Generally, OST traffic is routed to the data network segment. However, the OST Automatic Image Replication (AIR) and Concurrent Optimized Duplication features use the replication network segment to transmit data to the target system. (Optimized duplication can optionally use the replication channel.) When a data IP address is mapped to a replication IP address, OST traffic that is sent to one of the IP addresses is routed to the other IP address as necessary.

Additional Information

  • You must add target IP mapping information if you are performing optimized duplication on a segmented network and replication is not configured between the source InfiniGuard and target InfiniGuard.
  • Infinidat does not recommend mapping multiple data IP addresses to a single replication IP address. If you have mapped multiple data IP addresses and the routing is not working, try removing the additional data IP addresses, and map only a single data IP address.
  • To switch from using the replication channel to the OST channel for optimized duplication, replication must be unconfigured.

To access the Target IP Mapping page, on the OST page, click the Target IP Mapping tab.

Target IP Mapping page

Tasks

Use the Target IP Mapping page to perform the following tasks:

Target IP Mapping List

The Target IP Mapping list displays the following information for all mapped IP addresses:

  • Target Data IP - The mapped target data IP address.
  • Target Replication IP - The replication IP address to which the data IP address is mapped.

By default, items in the list are grouped by target replication IP address. To turn off grouping, click the arrow to the right of a column heading and clear the Show in groups check box.

Note

To update the list with the latest information, click Refresh.

Mapping a Target IP Address

Add mapping for a target data IP address to route all network traffic sent to the address to the specified replication IP address instead.

To map a target IP address:

  1. Click Add.

The Add Target Data IP Mapping window displays.

Add Target Data IP Mapping page

2. Enter information about the mapping:

Target Data IP

The target data IP address to map.

Target Replication IP

The replication IP address to map the data IP address to.

3. Click Apply.

Editing a Mapped IP Address

Edit a mapped IP address to route traffic sent to the target data IP address to a different replication IP address.

To edit a mapped IP address:

  1. Select the mapped IP address and click Edit.

The Edit Target Data IP Mapping window displays.

Edit Target Data IP Mapping page

2. In the Target Replication IP box, enter the replication IP address to map the data IP address to.

Note

If you are editing a mapped IP address, you cannot change the target data IP address.

3. Click Apply.

Deleting a Mapped IP Address

Delete a mapped IP address if traffic sent to the target data IP address no longer needs to be routed to a replication IP address

To delete a mapped IP address, select the IP address and click Delete.

Note

You can select multiple mapped IP addresses to delete at once.

InfiniGuard NetBoost 

Use the NetBoost page to enable or disable InfiniGuard NetBoost. Infinidat's InfiniGuard NetBoost software accelerates backups and reduces network bandwidth requirements by distributing deduplication between the backup server and the InfiniGuard DDE.

Configuring InfiniGuard NetBoost

Availability and Requirements

InfiniGuard NetBoost Requirements
To use InfiniGuard NetBoost, all the following requirements must be met:

  • Firewall port 1062 is open for IP address that is used for data transfer.
  • The media server is running and is meeting the following minimum requirements:

Operating System

One of the following operating systems:

      • Red Hat Enterprise Linux 5, 6, 7 (x86 64-bit)
      • SUSE Linux 11, 12, 15 (x86 64-bit)
      • Windows Server 2008 R2, 2012, 2016, 2019 (x86 64-bit)
      • Windows Small Business Server 2008 R2, 2012, 2016, 2019 (x86 64-bit)

CPU

Greater than 2.2 GHz processor with at least 2 cores (4 cores recommended)

Memory

2 GB RAM or greater

  • The OST Plug-in is installed on the media server.
  • NetBoost is enabled on the InfiniGuard. (By default, NetBoost is disabled on the InfiniGuard.)
  • NetBoost is enabled on the media server. By default, NetBoost is enabled on the media server when you install the OST Plug-in.

When all these requirements are met, NetBoost will be used for all OST transport between the media server and the InfiniGuard. Otherwise, normal OST transport will be used. for information about the maximum number of connections when NetBoost is enabled see, Maximum Number of InfiniGuard NetBoost Jobs .

Note

When InfiniGuard NetBoost is in use, you can monitor NetBoost performance information in the InfiniGuard remote management console, on the Status > NetBoost page. 

Enabling or Disabling NetBoost on the InfiniGuard

By default, InfiniGuard NetBoost is disabled on the InfiniGuard. To use NetBoost, you must enable it on the InfiniGuard.

Note

If NetBoost is enabled, all media servers that are using the same InfiniGuard DDE must have the latest OST plug-in installed.

To enable or disable NetBoost on the InfiniGuard:

1. Access the InfiniGuard DDE remote management console.

2. Navigate to the Configuration > OST > NetBoost page.


3. To enable InfiniGuard NetBoost, click the Enable Deduplication with NetBoost check box.
Or, to disable InfiniGuard NetBoost, clear the Enable Deduplication with NetBoost check box.

4. Click Apply.

5. To enable or disable encryption when sending OST data from the media server to the InfiniGuard, select the Change Encryption Type link or go to the Configuration > System > Security > Data Encryption page.
6. Select an option in the Encryption drop-down box. Encryption applies to all OST data traffic.

None

OST data is not encrypted.

Default AES 128

OST data is encrypted using AES 128-bit encryption.

Default AES 256

OST data is encrypted using AES 256-bit encryption.

TLS with AES 256

OST data is encrypted using AES 256-bit encryption with Transport Layer Security (TLS)


Additional Information

  • Using 256-bit encryption provides a stronger level of security but may have an impact on system performance in some situations.
  • If encryption is enabled, all other OST data will use TLS with AES 256 encryption.

7. If you selected any encryption option, you must install the required certificate and key files on the InfiniGuard:

    • Certificate File
    • Private Key File
    • Certificate Authority File
    • Rejection List File

To install a file, click the Browse button to browse the system and locate the file, and then click Open. Click Install to install the selected file on the InfiniGuard.

Caution

Installing certificate files requires a system reboot immediately after the changes are applied. Wait for at least 15 minutes before logging back in.

Additional Information

  • You can install new certificate and key files at any time, as long as there are no active network connections between the OST media server and the InfiniGuard.
  • To remove all certificate and key files, click Restore Factory Defaults.

8. Click Apply.

Enabling or Disabling InfiniGuard NetBoost on the Media Server

By default, InfiniGuard NetBoost is enabled on the media server when you install the Infinidat OST Plug-in. Because use of InfiniGuard NetBoost can be enabled individually on each InfiniGuard, there is typically no need to disable NetBoost on the media server. However, you might want to disable NetBoost on an individual media server if that media server is equipped with a slow CPU or if the type of data being backed up is not easily deduplicated. Note that you may mix NetBoost-enabled and NetBoost-disabled media servers with a single InfiniGuard.

To enable or disable NetBoost on the media server:

1. Open the configuration file for editing:

Linux/Unix

/usr/INFINIDAT/INFINIDATPlugin.conf

Windows

C:\libstspiINFINIDAT.ini

2.In the configuration file, locate the IO_PATH variable.

To enable NetBoost

Set the value of the IO_PATH variable to 4. For example: IO_PATH=4

To disable NetBoost and revert to using traditional OST transport

Set the value of the IO_PATH variable to 1. For example: IO_PATH=1

3. Save and close the configuration file.

Maximum Number of InfiniGuard NetBoost Jobs

When InfiniGuard NetBoost is enabled, a maximum of 768 concurrent NetBoost jobs can be run against each DDE in the InfiniGuard.

If the connection limit is reached, one or more of the following messages (or similar) is logged in the InfiniGuard log in the /var/log/messages directory:

  • VServer "hybrid-dedupe-no-encrypt" limit reached (limit 768).
  • VServer "hybrid-dedupe-no-encrypt" connection limit failed due to VServer "hybrid-group".
  • VServer "hybrid-group" connection limit failed due to VServer "hybrid-remote- group".
  • VServer "hybrid-remote-group" limit reached (limit 768).
  • VServer "hybrid-dedupe-no-encrypt" connection limit failed due to VServer "hybrid-group".
  • VServer "hybrid-group" limit reached (limit 768).

In addition, NetBackup displays a message:

NetBackup - The following progress message displays:

Critical bpdm (pid=12515) image open failed: error 2060020: storage server connection limit exceeded

When the connection limit is reached on the InfiniGuard, The OST plug-in retries the connection for 300 seconds by default. If the connection cannot be established after 300 seconds, the connection times out and an error is returned.

The default connection timeout is 300 seconds.

To change the timeout value, edit the following setting:

DATA_CONNECTION_BUSY_TIMEOUT

Linux  /usr/INFINIDAT/INFINIDATplugin.conf  file

Windows C:\libstspiINFINIDAT.ini file

Configuring the Veritas NetBackup (Media Server)

Documentation

Documentation and reference above provides links to important Infinidat and Veritas documentation.

Registering the Storage Server with NetBackup and Discovering Logical Storage Units

After the Infinidat OST Plug-in is installed and configured on the NetBackup media server, you must register the storage servers with NetBackup by defining them on the media server.

You must complete this process on every media server that will access the storage servers on the InfiniGuard. You can configure multiple media servers to use the same storage servers as long as the OST Plug-in is installed on each media server. To register a storage server, first define it using the nbdevconfig command, and then provide credentials using the tpconfig command.

Additional Information

  • You can perform this process using the Storage Server Configuration Wizard instead of the CLI commands.
  • The storage server argument passed to the nbdevconfig command should be in the form of <name_IP>, where the name is the name of storage server to be registered and IP is the IP address of the InfiniGuard. If the InfiniGuard is configured with multiple network interfaces (see the User’s Guide for your InfiniGuard system), the IP will be the network interface used for data. This is also applicable when registering storage servers on a Windows platform.
  • If the IP address of the InfiniGuard or media server changes at any time after registering the storage servers (for example, due to switch changes), you must delete the existing storage servers and disk pools on the media server, and then register the storage servers again using the procedures below. You must take these actions on all media servers that access the storage servers.

Registering the Storage Server using the NetBackup CLI

Registering the Storage Server on Windows Platforms

The procedures in this section assume NetBackup is installed in the default location on the C: drive. If you installed Netbackup in a different drive or location, modify the commands with the correct path. For complete usage information about these commands, refer to NetBackup Commands for Windows.

We use StorageServerName_IpAddress where:

StorageServerName

The name of the storage server defined on InfiniGuard and IpAddress is the IP address on InfiniGuard

1. Add the storage server to NetBackup

NBU CLI
<install path>NetBackup\bin\admincmd\nbdevconfig -creatests -storage_server<storageserver_ip> -stype INFINIDAT -media_server <media_servername> -st 9

Example:

To a server with the Netbackup installation path

C:\Program Files\Veritas\, to add a storage server by name nbustorageserver at IP address 192.168.1.100 and a media server by name nbumedia.

NBU CLI
C:\Program Files\Veritas\NetBackup\bin\admincmd\nbdevconfig -creatests - storage_server nbustorageserver_nnn.nnn.nnn.nnn -stype INFINIDAT -media_server nbumedia -st 9

Note

  • When specifying the -storage_server variable, you must include both the name and IP address (or the name and hostname) of the storage server separated by an underscore. Storage server names are case sensitive on all platforms including Windows. For example: nbustorageserver_192.168.1.100 (or nbustorageserver_hostname).
  • If the InfiniGuard is configured with multiple network interfaces (see the User’s Guide for your InfiniGuard system), the IP address of the interface enabled for data should be used to register the storage server.
  • A message from the prompt indicates that the storage server was added successfully. Otherwise, an error message is displayed.

2. Specify the storage server credentials.

NBU CLI
C:\Program Files\Veritas\Volmgr\bin\tpconfig -add -storage_server <storageserver_ip> -stype INFINIDAT -sts_user_id <username> -password <password>

Example

Add credentials for storage server nbustorageserver.

C:\Program Files\Veritas\Volmgr\bin\tpconfig -add -storage_server nbustorageserver_192.168.1.100 -stype INFINIDAT -sts_user_id ostuser -password INFINIDAT

Caution

The username and password must be the same as the OST user credentials created on the InfiniGuard remote management console

Registering the Storage Server on Linux platforms

To register the storage server on Linux, NetBackup media server platforms:

1. Add the storage server to NetBackup by executing the following command on the NetBackup media server as root:

NBU CLI
/usr/openv/netbackup/bin/admincmd/nbdevconfig -creatests -storage_server <storageserver_ip> -stype INFINIDAT -media_server <media_servername> -st 9

Example:

Adding a storage server by name nbustorageserver and a media server by name nbumedia.

/usr/openv/netbackup/bin/admincmd/nbdevconfig -creatests -storage_server nbustorageserver_nnn.nnn.nnn.nnn -stype INFINIDAT -media_server nbumedia -st 9

Additional Information

  • When specifying the storage_server variable, you must include both the name and IP address (or the name and hostname) of the storage server separated by an underscore. Storage server names are case sensitive on all platforms including Windows. For example: nbustorageserver_ 192.168.1.100 (or nbustorageserver_hostname).
  • If the InfiniGuard is configured with multiple network interfaces (see the User’s Guide for your InfiniGuard system), the IP address of the interface enabled for data should be used to register the storage server.

  • A message from the prompt indicates that the storage server was added successfully. Otherwise, an error message is displayed.

2. Specify the credentials of the storage server:

NBU CLI
/usr/openv/volmgr/bin/tpconfig -add -storage_server <storageserver_ip> -stype INFINIDAT -sts_user_id <username> -password <password>

Example:
Adding credentials for storage server nbustorageserver.

/usr/openv/volmgr/bin/tpconfig -add -storage_server nbustorageserver 192.168.1.100 -stype INFINIDAT -sts_user_id ostuser -password INFINIDAT

Caution

The username and password must be the same as the OST user credentials created on the InfiniGuard remote management console; see Configuring OST Authentication.

Additional Information

  • When specifying the -storage_server variable, you must include both the name and IP address (or the name and hostname) of the storage server separated by an underscore. Storage server names are case sensitive on all platforms including Windows. For example: nbustorageserver_nnn.nnn.nnn.nnn (or nbustorageserver_hostname).
  • No message displays if the credentials are added successfully. But an error message displays if the credentials are incorrect.

Verifying the LSU Discovery with NetBackup CLI

After you have registered the storage server, verify the discovery of LSUs by performing the following step:
From the command line on the master server, type:

NBU CLI
/usr/openv/netbackup/bin/admincmd/nbdevconfig –previewdv –stype INFINIDAT – storage_servers <storageserver_ip>

Example:

Verify LSU discovery for storage server nbustorageserver.

/usr/openv/netbackup/bin/admincmd/nbdevconfig –previewdv –stype INFINIDAT – storage_servers nbustorageserver_nnn.nnn.nnn.nnn

Note

When specifying the storage_server variable, you must include both the name and IP address (or the name and hostname) of the storage server separated by an underscore. Storage server names are case sensitive on all platforms including Windows. For example: nbustorageserver_nnn.nnn.nnn.nnn or nbustorageserver_hostname.

This will show if the LSU has been discovered by NetBackup and if the password is correct.

Configuring the Storage Server using the configuration wizard

The NetBackup Administration Console provides a Storage Server Configuration Wizard to walk through the storage server configuration process

To register storage servers:

1. Start NetBackup:

In Windows, double-click the NetBackup Administration Console icon.
In Linux run the following command:

/usr/openv/NetBackup/bin/jnbSA &

The NetBackup Administration Console displays.

2. In the Details pane (on the right), click Configure Disk Storage Servers

The Storage Server Configuration Wizard is launched

3. Select OpenStorage in the list, and then click Next.
The Add Storage Server details window displays.

4. Enter the following information about the storage server:

Storage server type

Enter INFINIDAT

Storage server name

Enter the name of the storage server in the format <storageserver_ip>.

Note

When specifying the storage_server variable, you must include both the name and IP address (or the name and hostname) of the storage server separated by an underscore. Storage server names are case sensitive on all platforms including Windows. For example: nbustorageserver_nnn.nnn.nnn.nnn (or nbustorageserver_hostname).


Note


If the DDE is configured with multiple network interfaces (see the User’s Guide for your DDE system), the IP address of the interface enabled for data should be used to register the storage server.

Select media server

Select the media server that will access the storage server. The OST Plug-in must be installed on the media server.

Enter credentials

Enter the username and password for the storage server.

Caution

The username and password must be the same as the OST user credentials created on the DDE remote management console.

Note

If an error occurs when authenticating in Windows, try using the tpconfig command to validate the OST target.

5. Click Next.

The Storage Server Creation Status window displays.

6. Select "Create disk pool using the storage Server that you have just created"

7. Click Next.

Select Disk Pool Properties and Volumes is launched

Select available LSU

Note

If AIR is configured on the DDE for your LSU, the Replication choices will be populated when you select the Volume.

7. Click Next

Provide additional disk pool information is launched

Enter a Disk Pool name.

8. Click Next

Verify the disk pool configuration is launched

Confirm the disk pool configuration.

9. Click Next

Storage Unit Creation screen is launched

Storage Unit Name

Enter the name of the storage unit.

Media Server

Select an option to use any available media server to transport data, or select the specific media server(s) to use.

Maximum concurrent jobs

Enter the maximum number of backup jobs that can run concurrently to the storage unit.

Note

Infinidat recommends setting this value to no more than 128 jobs per InfiniGuard (64 per DDE). Keep in mind that restore jobs and optimized duplication jobs will cause additional system load.

Maximum fragment size

Enter the maximum size of backup archives that can be written to the storage unit.

10. Click Next

11. Click Finish

The Disk Pool is now configured and ready for use. You can view or change current configuration settings in Device Management or Storage Unit Management.

NetBackup OST Operations

Initiating an OST backup

See the NetBackup System Administrator’s Guide or the NetBackup User’s Guide for information on creating a backup policy to backup data to an OST disk pool.

Once the backup policies are configured, optimized duplication begins after the backup completes.

Performing Synthetic Full Backups

A synthetic backup is a backup in which the images from a series of backups, starting with a full backup and followed by incremental backups, are combined into a new backup-typically a full backup.

For a synthetic backup to be successful, all the backups from the series must be intact and internally consistent. Intact means that each backup created still exists and no backup in the series has been expired. Internally consistent means that the individual backup catalogs are all consistent. The catalogs can become inconsistent for a variety of reasons, for example, by running two backups for a client and policy concurrently. (A scenario when this example can occur is if a manual incremental backup is performed while a scheduled incremental backup job is in progress.)

A synthetic backup produces its best results when it gets big offset ranges from the participating images that are combined to construct the synthetic image. However, as the offset ranges becomes smaller the performance drops and at some point the overhead to construct the synthetic images can become greater than the ingest of that data in raw form.

For DDE systems, synthetic backups are most effective under the following conditions:

  • The average file size in the data set is greater than 5 MB.
  • The modification of existing data since the previous full backup is not more than 15%. This includes deletion of existing files or append to those files, but does not include addition of new files.
  • More frequent synthetic backups (like twice a week instead of once a week) can be done to keep the change rate under 15% if necessary.

During a synthetic backup, the backup application first queries and analyzes the backups for the given policy and client and then attempts to use their catalog data to combine the content into a new logical backup. If a backup is missing, or if file metadata is inconsistent, the synthetic backup will fail with an error 671.

Primary causes of error 671 include the following:

  • Expiration of a backup in the full/incremental series.
  • Inconsistent incremental metadata due to concurrent backups in the series.
  • Inconsistent incremental metadata due to utilization of Windows Archive Bit and cumulative incremental backups.
  • Inconsistent incremental metadata due to, prior to NetBackup 7.1, use of dynamic selections and multistreaming.

OST Data Replication (Optimized Duplication)

The InfiniGuard has the capability to copy data on one system to another system (that is, the capability to perform replication). NetBackup uses this capability to initiate an optimized duplication of backup images between these appliances. The duplication operation of NetBackup triggers the duplication function in the OST disk appliance if both the source and destination volumes for the copy are OST LSUs.

OST optimized duplication reduces the workload on the NetBackup media server because the replication is performed by the InfiniGuard. Duplication is done in the background, and it is faster because it uses InfiniGuard’s data deduplication capabilities to reduce the copy bandwidth. Duplication is still initiated, managed, and controlled by the NetBackup media server while the actual data movement process is off-loaded to gain the maximum benefits from the InfiniGuard's replication capabilities.

The InfiniGuard can replicate (duplicate) OST data to another InfiniGuard using the following methods

Optimized Duplication

With optimized duplication, backup images on a storage server can be replicated to another storage server on a InfiniGuard DDE that resides in the same NetBackup domain. The duplication occurs when it is initiated in NetBackup. With optimized duplication can specify up to two replication targets

Concurrent Optimized Duplication

For both optimized duplication and Automatic Image Replication, you can optionally enable Concurrent Optimized Duplication. If enabled, as data is written to the storage server, it is simultaneously replicated to the target InfiniGuard DDE. When optimized duplication or Automatic Image Replication subsequently occurs, the operation is more efficient because a portion of the required data has already been replicated to the target storage server.

Automatic Image Replication (AIR)

If you are using Veritas NetBackup 7.6 or higher, you can configure an LSU for Automatic Image Replication (see Configuring InfiniGuard DDEs for OST). If enabled, data on an LSU is automatically replicated to a remote LSU that resides on a InfiniGuard DDE in a different NetBackup domain. The timing of the duplication, as well as the backup images that are duplicated, are determined by the storage lifecycle policies (SLPs) configured in NetBackup. With AIR, you can specify a single replication target.

It is important to remember that, with Automatic Image Replication, the local and remote LSUs reside in different NetBackup domains. This differs from optimized duplication, which occurs between two LSUs residing within the same NetBackup domain.

Note

For information about configuring NetBackup for optimized duplication or Automatic Image Replication (also referred to as duplicating images to a remote master server domain), see the Veritas NetBackup Administrator's Guide.

Configuring Optimized Duplication

To increase the performance, Infinidat recommends configuring the InfiniGuard DDE to use the replication channel when performing optimized duplication.

To initiate an optimized duplication with the Administration Console:

1. In the NetBackup Administration Console, expand the NetBackup Management Catalog.

2. Set up the search criteria for the image you want to duplicate.

3. Click Search Now.

4. Right-click the images you want to duplicate and select Duplicate from the shortcut menu.


Additional Information

You must designate an OST storage unit as the destination for the duplication. Use the Storage Unit field in the Setup Duplication Variables dialog box.

For more information, see the section “Duplicating Backup Images” in the NetBackup System Administrator's Guide.


Configuring Automatic Image Replication - AIR

Setting up Automatic Image Replication (AIR) requires that you first configure the target (remote) DDE and then the source DDE. In addition, you must create storage lifecycle policies (SLPs) in NetBackup that define when the automatic replication occurs and which backup images are duplicated.

To automatically replicate (duplicate) all data on an LSU to a remote LSU that resides on a DDE in a different NetBackup domain:

1. On the target system, add the source system to the list of allowed replication sources.

2. On the target system, create a local OST user.

Caution

On the target system, make sure to create a local user on the Configuration > System > Manage Users page.

3. On the target system, create a storage server and LSU to receive the replicated OST data.


Note

Infinidat recommends selecting the Available Capacity option when creating an LSU for use with Automatic Image Replication.

4. On the source system, configure replication to the target system.

5. On the source system, create a remote OST user with the same user name and password that you used in step 2 above (see Create a Remote User for OST AIR on the next page).

Caution

On the source system, make sure to create a remote user on the Configuration > OST > Manage Remote Users page.

Note

If the target DDE uses different IP addresses for data and replication traffic, you must configure target IP mapping on the source DDE.


6. On the source system, create a storage server and LSU, and enable the LSU for Automatic Image Replication.

For Remote Storage Server and Remote LSU, make sure to specify the storage server and LSU created in step 3 above. Also, for Remote User, make sure to select the remote user created in step 5 above.

7. Register and configure the storage servers in NetBackup. Also, create disk pools in NetBackup and make sure the Replication property on the disk pool is updated.
If the disk pool is the source, the Replication property of the disk pool should be source. If the disk pool is the target on the remote NetBackup media server, then the Replication property should be target.

Note

A disk pool can be a target and also a source to another remote NetBackup media server. Make sure that the Replication property on the disk pool is updated before creating the storage lifecycle policies (SLPs).


8. Configure storage lifecycle policies in NetBackup to control when automatic replication of the LSU occurs (see the Veritas NetBackup Administrator's Guide).

Configure target DDE:

Add allowed replication source.

Create local OST user.

Create storage server and LSU.

Configure the source DDE:

Specify replication target.

Create remote OST user.

Create storage server and LSU with AIR enabled.

Create storage lifecycle policies (SLPs) on the NetBackup server in each domain to control when duplication occurs and images are imported.

Create a Remote User for OST AIR

Add a remote user to create OST user credentials for use with OST AIR. When you enable Automatic Image Replication for an LSU, you specify a remote user. The remote user credentials on the source DDE must match the local user credentials on the target (remote) DDE.

To add a remote user:

1. Log on to the DDE remote management console.

2. Navigate to the Configuration > OST > Manage Remote Users page.


3. Click Add.

4. Enter information about the remote user:

User name

Enter the name of the remote user.

New Password

Enter the password for the remote user.

Confirm New Password

Enter the password again to confirm it.

Description

(Optional) Enter a brief description of the remote user.

5. Click Apply.

OST Plug-in Configurable Options

The following OST Plug-in configurable options are supported:

Linux/Unix

The following Linux and Unix configurable options are supported:

DEBUG_LEVEL

This defines the level of logging to enable. The value of this option defines the level of log messages to output. It is set to one of the following values:

  • EMERGENCY
  • ALERT
  • CRITICAL
  • ERROR
  • WARNING
  • NOTICE
  • INFO
  • DEBUG

By default, DEBUG_LEVEL is set to ERROR.

OPDUP_TIMEOUT

The Optimized duplication option of NetBackup uses the replication feature of the OST server. The DDE replication feature cannot replicate unless the backup image file is deduplicated.

On demand deduplication of the backup image file can take an unknown amount of time. OPDUP_ TIMEOUT is the time in seconds to wait for deduplication of backup image file extent of 256MB or smaller before giving up on the replication attempt. If the file copy extent length is larger than 256MB, then the wait time will be a proportional multiple of OPDUP_TIMEOUT. For example, if the extent length is X*256MB, wait time will be X*OPDUP_TIMEOUT, where X need not be an integer. By default, OPDUP_TIMEOUT is set to 180 seconds.

Note

This option is available only on Linux and Unix platforms. On Windows the timeout is fixed at 180 seconds.

To change the default value of any of these options, edit the /usr/INFINIDAT/INFINIDATPlugin.conf file and set the desired values.

Windows

The following Windows configurable options are supported:

LOG_LEVEL

This is similar to the DEBUG_LEVEL on Linux and Unix. It defines the level of logging to enable. The value of this option defines the level of log messages to output.

  • NONE - Disables logging for the logger.
  • TRACE - Enables tracing to error messages.
  • DEBUG - Enables debug to error messages.
  • INFO - Enables information to error messages.
  • WARN - Enables warning and error messages.
  • ERROR - Enables only error messages.

LOG_LIMIT

This defines the maximum file size (in byte) for the logger. Default size of the log file is 10MB. Increase this value if more logging has to be captured.

Edit %WINDIR%\libstspiINFINIDAT*.ini to change the default values.

Enabling Verbose Logging

OST Plug-in Log

The OST Plug-in logs various messages to %WINDIR%\libstspiINFINIDAT*.log on a Windows media server.

The OST Plug-in logs various messages to log files under: /var/log/ostlog/client directory on a Linux or Unix media server.

Example:
# tail -f /var/log/ostlog/client/ost_client.log
DEBUG - 20080725 16:12:43 15982 pgnapi.c:57 Plugin Prefix INFINIDAT claimed. DEBUG - 20080725 16:12:43 15982 pgnapi.c:58 stspi_claim exited
DEBUG - 20080725 16:12:43 15982 pgnapi.c:754 stspi_get_server_prop_byname_v9 entered
DEBUG - 20080725 16:12:43 15982 comm.c:939 ostSendRequest: message:0x20000005
DEBUG - 20080725 16:12:43 15982 pgnapi.c:798 stspi_get_server_prop_byname_v9 exited
DEBUG - 20080725 16:12:43 15982 pgnapi.c:44 stspi_claim_v9 entered
DEBUG - 20080725 16:12:43 15982 pgnapi.c:57 Plugin Prefix INFINIDAT claimed. DEBUG - 20080725 16:12:43 15982 pgnapi.c:58 stspi_claim exited
DEBUG - 20080725 16:12:43 15982 pgnapi.c:207 stspi_open_server_v9 entered DEBUG - 20080725 16:12:43 15982 comm.c:939 ostSendRequest: message:0x20000002

Other Options

Transmission Control Protocol (TCP)

The TCP Keep Alive settings can be configured to prevent an OST connection termination by a firewall.

TCP_KEEPIDLESet the TCP option TCP_KEEPIDLE for socket connections. This is equivalent to tcp_keepalive_time.System settings276446
TCP_KEEPCNTSet the TCP option TCP_KEEPCNT for socket connections.This is equivalent to tcp_keepalive_probes.System settings1215752191
TCP_ KEEPINTVLSet the TCP option TCP_KEEPINTVL for socket connections. This is equivalent to tcp_keepalive_intvl. System settings.System settings276446

Best Practices for InfiniGuard DDE with OST

OST with NetBackup Granular Recovery

InfiniGuard DDE running OST are certified for Granular Recovery Technology support with NetBackup 7.5 and above. This technology allows for individual data storage recovery, including Microsoft Exchange data.

For additional information see the following Veritas documentation:

OST Load Distribution across NetBackup Media Servers

When multiple hosts are using a single DDE system, you can distribute the load by dividing the hosts into groups. By default, hosts communicate with the DDE over TCP port 3095, but they can be configured to use a different port. To divide hosts into groups, select a group of hosts and configure each to use the same port. For example if there are eight hosts, one group of hosts can use the default port (3095), which requires no modification, and another group can use port 3096, with each host modified as shown in the instructions below. No modifications are required on the DDE.

Two Port Load Distribution:

The load distribution feature (two ports) is available in all current InfiniGuard releases.

Configure the dm_client setting as follows and use the instructions below for the particular type of host (Linux or Windows).

  • The first group will use the default port number 3095
  • The second group will use port number 3096

Eight Port Load Distribution:

The load distribution feature (eight ports) is available in the current InfiniGuard releases.

Configure the dm_client setting as follows and use the instructions below for the particular type of host (Linux/Unix or Windows).

  • The first group will use the default port number 3095
  • The second group will use port number 3096
  • The third group to use port number 3097
  • The fourth group to use port number 3098
  • The fifth group to use port number 3099
  • The sixth group to use port number 3100
  • The seventh group to use port number 3101
  • The eighth group to use port number 3102

Linux Hosts

Add the following entry to the /etc/services file:

dm_client <port_number>/tcp dm_client

Where <port_number> is a port used by one of the host groups (see above).

Example:

dm_client 3096/tcp dm_client

Windows Hosts

Add the following entry to the %WINDIR%\system32\drivers\etc\services file.

There must be a carriage return after the last entry in the services file or it will be ignored by Windows:

dm_client <port_number>/tcp

Where <port_number> is a port used by one of the host groups (see above).

Example:

dm_client 3096/tcp

Deduplication Considerations

InfiniGuard deduplication technology divides a data stream into variable-length data segments using a data-dependent methodology that can find the same block boundaries in different locations and contexts. This block-creation process allows the boundaries to “float” within the data stream so that changes in one part of the data set have little or no impact on the boundaries in other locations of the data set. Through this method, duplicate data segments can be found at different locations inside a file, inside different files, inside files created by different applications, and inside files created at different times. When NetBackup encounters a segment of data that is already stored in the deduplication storage folder, the data is not stored again. So, if you back up the same unchanged file over and over again, it is stored only one time in the deduplication storage folder.

Deduplication works best in the following scenarios:

  • Windows and Linux file system data
  • Where the same file is backed up multiple times
  • Where the percentage of data that changes is small

About Sharing a Deduplication Device between Multiple NetBackup Servers:

If you use the NetBackup SSO Option, you can select which NetBackup servers can share a deduplication disk storage device or an OpenStorage device. When you add a deduplication disk storage device or an OpenStorage device, the NetBackup server that you used to add the device is automatically selected for sharing.

Note

To share a deduplication disk storage device, you must add it as an OpenStorage device on all NetBackup servers that you want to have access the device, except for the NetBackup server that was used to create it.

Backup Streams Considerations

A different storage server should be created and used for each NetBackup domain (master server plus associated Media Servers). This segregates data, so that a NetBackup administrator cannot accidentally modify or remove backup images belonging to another domain.

Multistreaming Considerations

OST works with an NBU capability called “multistreaming.” This causes NBU to generate several backup streams in parallel to back up different subdirectories at the same time. This can cause a single backup stream from a single server to become 10 or more streams. Sometimes a stream contains nothing but a single file. This can produce very short backup files and Infinidat recommends exercising caution when utilizing this option.

The following tables indicate the recommended maximum values for setting the TOTAL number of streams per DDE model. While the DDE is designed and tested for values higher than are what are listed here, lab testing suggests that these values will bring the maximum performance in a generalized environment. Keep in mind that each data protection ecosystem is unique and will determine the final settings.

Maximum Individual Stream Count Guidance

Per InfiniGuard with 2 active DDEs.

ProtocolStreams

OST with NetBoost

1536
OST w/o NetBoost1024
NetBackup Accelerator
220

RMAN with NetBoost

1536
RMAN w/o NetBoost1024
NFS1024
CIFS1024

VTL

1024

Contact Infinidat for multi protocal sizing and performance considerations.

Optimized Duplication Considerations

The DDE uses can use either the replication channel or OST channel when performing optimized duplication. Optimized Duplication performance is significantly enhanced when using the replication channel.

Accelerator Considerations

Use the following best practices to determine if using the Accelerator feature is right for your client back- ups.

  • The first backup of any client will be a traditional full backup. See the NetBackup System Administrator’s Guide for information on creating a full backup.
  • Backups after the first initial full backup will then use the target change rate Accelerator feature. The target change rate is defined as the percentage of ingest data bytes that have been merged with synthetic data bytes on the DDE.
  • The target change rate between backups should be 5% or less, though you may see performance savings above traditional full backups with higher target change rates For more information on recommended target change rates, see the NetBackup System Administrator’s Guide for more information.
  • Change rates can be viewed from the OST Accelerator – Savings report in DDE Advanced Reporting.
  • For backups with consistently high change rates, Optimized Synthetic Backups can be used instead of the Accelerator feature.
  • When using Accelerator to create incremental backups, configure the NetBackup media server to create differential incremental backups. See the NetBackup System Administrator’s Guide for more information.
  • Accelerator use on a DDE system should be configured for fewer concurrent accelerated backup streams from media servers. For example, a DDE can support up to 512 standard concurrent backup streams. With Accelerator enabled backups that number is reduced by a factor of 7. So in that case the number of concurrent backups would be 512/7 or 73 concurrent accelerated backups.
  • High density clients containing many files of smaller size will see slower backup performance than less dense clients.

Additional Best Practice Considerations

Several operational considerations are common to all three access methods (OST, VTL and NAS). See
Common Operational Considerations for NetBackup section at the end of this document for more information on Deduplication, Encryption, Compression, Backup Streams and Replication.

Configuring NetBackup with DDE VTL

Creating a backup image on a virtual tape is no different than creating a backup image on a physical tape. The backup functionality is unchanged.  When the DDE is viewed through Fibre Channel interfaces. it appears as a virtual medium changer with virtual drives and cartridges.

VTL Device Installation and Configuration Considerations

A key element to ensure that SAN connected physical and virtual tape libraries are detected properly is serialization. Serial numbers are used as a unique identifier for each device in a physical or virtual tape library and provides device association to media servers. Serial numbers returned by VTL devices, are separate from the element address that defines the position of elements in the library. The element address is used by the application to manage attributes of the library such as moving a cartridge from a storage slot to a drive or import/export slot.  NetBackup associates the drive element address with its serial number as a unique identifier through multiple data paths and to multiple media servers. As such serialization is a critical element for reliable configuration.

 If the Device Configuration Wizard does not show that a device is “serialized"; resolve the issue before committing changes. Typical issues are that the VTL partition is offline, device drivers are incorrect or not installed or there are issues with the SAN (HBA, SFP. old mappings file, etc.).  When serialization is present, the Device Configuration Wizard will associate drives in their respective VTL partition.

Veritas supports both OEM and OS tape drivers.  Refer to the  Virtual Library and Tape Drive Emulation for Infinidat recommendations.


Note

Infinidat highly recommends installing NetBackup’s latest Device Mappings File for your appropriate Operating System(s) to support properly identifying devices in NetBackup.  Links to the Device Mappings files and other helpful information is included in the Veritas NetBackup ™ Enterprise Server and Server 8.0 - 8.x.x Hardware and Cloud Storage Compatibility List (HCL) https://www.veritas.com/content/support/en_US/doc/NB_80_HCL

Configuring the DDE and NetBackup for VTL operations

Veritas NetBackup seamlessly integrates with InfiniGuard VTL. Once installed and configured, NetBackup can manage the backups through the DDE and can take advantage of the DDE system's capabilities such as data deduplication, and image replication.

Installing and configuring the DDE and NetBackup for VTL operation consists of the following major steps:

Configure the DDE to present as VTL

A virtual tape library (VTL) is a data storage virtualization technology used for backup and recovery. A VTL presents itself as a tape library with tape drives for use with NetBackup. Virtualizing disk storage as tape allows integration of VTLs with existing backup software and existing backup and recovery processes and policies. The benefits of such virtualization include storage consolidation and faster data restores.
In the Remote Management Console, under the Configuration tab, the VTL page allows you to configure a DDE to present its storage capacity as VTL partitions that are compatible with standard backup applications. You can add virtual tape drives and storage slots to VTL partitions, and you can create and work with virtual tape cartridges. Note that Infinidat does not support mixing drive types in the same partition.
Partitioning lets you divide the DDE virtual tape drives and storage elements into separate partitions, usable by separate host computers. The Partitions page contains a list of assigned tape drives, as well as listing all user defined partitions that are currently configured on the system. This page also lets you add, edit, and delete partitions.
The Summary page displays the maximum number of partitions, the total number of tape drives, and the number of assigned tape drives. The Summary page also provides a list of configured partitions on the system. Click the link in the Name column to edit the specific partition.

The "drives" presented by a DDE aren't assigned their own WWPN, but rather appear as LUNs on the DDE Fibre Channel port. While many Operating Systems recognize this, Solaris is not one of those. Solaris uses a combination of st and sg files to control how many LUNs a single WWPN can present to the OS. This requires special handling as the default number of LUNs is 16. So, if a user configures a 20-drive VTL on Solaris it will see the changer and 15 drives. The sg.conf file must be rebuilt in order to allow the OS to "see" those additional LUNs. This Veritas Tech Note contains additional information on this subject: https://www.veritas.com/content/support/en_US/article.100016274.html

The Create Media page allows you to create virtual media for a specific partition. Once created, these virtual cartridges are available for backing up data. You can configure the media type, capacity, starting barcode, and initial location on this page.  For important capacity considerations see: “Tape Cartridge Capacity Considerations”.

If you are planning to replicate partitions to another DDE system, you must ensure that every partition name and barcode number is unique to both systems. You can NOT have duplicate partition names or barcode numbers on the primary DDE or target replication system.


Note

It is possible to oversubscribe space on the DDE system. The sum total of capacity for all media could be more than the physical capacity of the system.

For more information see; “Oversubscription of Space on the DDE”.


Refer to the InfiniGuard User’s Guide for VTL configuration instructions and provide host access before configuring NetBackup.

With VTL mapped to the media servers, confirm the media servers operating systems discovers the devices correctly and proper drivers are loaded. And, confirm the NetBackup mappings file for the OS is current. 

Virtual Library and Tape Drive Emulation:  OS, Drivers and mappings file considerations.

Virtual Library:

VTL emulation/inquiry - Infinidat IBA B4260 DDE (DXi6900)
Windows:  Use Windows  "unknown medium changer" driver
Linux:        Use OS driver
Solaris:     Use OS driver
AIX:           NBU is deprecating OVPASS driver and recommends using a different OS to manage the medium changer. See notes below for AIX medium changer configuration options. 
HP-UX:      Use OS driver

Note: Veritas discontinued Master/Media Server support for AIX and HP-UX starting with NBU v8.1.2

HP LTO drives:

LTO drive emulation:  HP Ultrium x-SCSI
Windows:  Use Windows LTO or HP Windows driver
Linux:        Use OS driver
Solaris:      Use OS driver IBM
AIX:            Use OS drivers  (AIX ost driver)
HP-UX:       Infinidat recommends using IBM LTO drive emulation on HP-UX.  If using HP emulation, use HP-UX stape/estape

Note: Veritas discontinued Master/Media Server support for AIX and HP-UX starting with NBU v8.1.2

IBM LTO drives:

IBM LTO emulation - IBM ULTRIUM-TDx
Windows:  Use OS drivers or IBMTape non-exclusive driver. (Disable multi-path failover and load balancing.)
Linux:        Use OS driver
Solaris:     Use OS driver
IBM AIX:    Infinidat recommends HP LTO drive emulation on AIX.  If using IBM emulation; Atape driver is supported
HP-UX:      Use HP-UX stape/estape driver or IBM atdd driver

Note: Veritas discontinued Master/Media Server support for AIX and HP-UX starting with NBU v8.1.2

NetBackup Mappings files:

Windows systems, refer to:    https://www.veritas.com/docs/100015982
UNIX/Linux systems, refer to:  https://www.veritas.com/docs/100015983


Medium changer configuration options for AIX

There are several ways to configure InfiniGuard medium changer on AIX.  Since NetBackup is depreciating the ovpass driver for the medium changer, the easiest method is to configure the medium changer control through a Linux, Windows or Solaris server.   If that is not an option, then consider configuring AIX with Atape driver v 12.8.9 or newer and configure InfiniGuard VTL emulation/inquiry as Scalar i6000.  In all cases make sure the medium changer and drive LUNs are mapped consecutively and without gaps.

Use the following to configure VIOS AIX with NPIV port:

  1. Install atape.driver version 13.0.34.0 or later
  2. Simulate VPT partition as 'SCALAR i6000' tape library
  3. once partition is mapped use the following proceedure to rescan for medium changer and devices
    1. /usr/openv/netbackup/bin/goodies/netbackup stop
    2. delete the adapter using 'rmdev -Rdl fcsx' (and everything on the adapter), and then rescan again "cfgmgr", the medium changer and proper devices will show (this is only needed for the first time)
    3. /usr/openv/netbackup/bin/goodies/netbackup start
  4. Multiple partitions can be mapped to the same AIX host; each presenting a medium changer.

Note

InfiniGuard does not support multipath configuration.

Configure NetBackup with the VTL

After a VTL has been defined with access mapped to a Master or Media Server; NetBackup can be configured:

  • Make sure the media server OS recognizes the VTL medium changer and drives.  If necessary, install device drivers. 
  • From the Administration Console run the Configure Device Wizard. If SSO is installed, select all servers with access to the VTL.
  • Make sure the Configure Device Wizard has serial numbers for each device and correctly associates the tape drives with the correct medium changer before committing changes.
  • Inventory the robot to scan the VTL elements and add media barcodes to the media pool.
  • Create and run a backup policy.

Refer to NetBackup Administrators guide for details.  see Veritas NetBackup Documentation Center

Caution

It is important to consider that as of NetBackup 7.5; AIX 6.1 and 7.1 operating systems are no longer supported as a robotic library controller. Veritas recommends using an operating system other than AIX as a robotic library controller.  Additionally, NetBackup has changed support for Media Server on some OS platforms so refer to the NetBackup Software Compatibility Guide to confirm supported versions.  NBU  https://www.veritas.com/support/en_US/article.100032808

Configure VTL cartridge/file replication

Refer to the InfiniGuard User Guide: Replication Operations for details on configurating InfiniGuard DDEs for replication.

Best Practices for NetBackup with InfiniGuard DDE  VTL

Device Serialization

NetBackup uses a devices serial number to uniquely identify medium changers and drives. It then associates element addresses within a library to identify locations for drives, media slots and import/export slots. With this detailed map of the library NetBackup can move media into a drive and direct backup data from a media server to the correct drive, tape and barcode.

Serialization is a key element in the address scheme so when configuring a VTL with NetBackup, care should be taken to make sure serial numbers are detected. If the Device Configuration Wizard does not show that a device is “serialized”; resolve the issue before committing changes. Typical issues are, that the VTL partition is offline, Device drivers are incorrect or not installed or there are issues with SAN (HBA, SFP, old mappings file, etc.).  When serialization is present, Device Configuration Wizard will associate drives in their respective VTL partition.

Device Driver and Firmware level

Ensure that the latest drivers and firmware have been installed for the medium changer, tape drives and for the HBA.  The DDE software contains the emulated medium changer and tape drive firmware and as such is managed by the DDE.  On the other hand, physical libraries and drives should be monitored and updated as needed or scheduled with maintenance.  When devices are presented properly the operating systems should have a device inquiry and serial number.  Many operating systems will use native drivers including Windows.  NetBackup supports either the operating systems drivers or drivers provided by the OEM manufacture.  Infinidat recommends using IBM drivers when using IBM LTO emulation. When using the native VTL inquiry, Windows environments will display the device in the Device Manager as an “unknown medium changer”. This is normal and not a problem for NetBackup.

For details on virtual library and drive emulations, operating systems, drivers and mappings file considerations, refer to the Configure the DDE for VTL section:  Virtual Library and Tape Drive Emulation:  OS, Drivers and mappings file considerations.

Number of Concurrent Tape Drives in Use

Each DDE model has a maximum number of virtual tape drives that can be configured. Each model also has a maximum aggregate throughput rate, which will be divided relatively equally between the virtual tape drives in use. This does not prohibit a single tape drive from using all available bandwidth. The Media Server typically determines individual tape drive performance.
It is not a good idea to configure the maximum number of virtual tape drives and perform I/O through all of them concurrently. Better performance can be achieved by using a subset of those virtual tape drives at the same time. Infinidat expects the customer configuration to distribute those virtual tape drives among multiple Media Servers, to simplify initial installation by providing dedicated resources to each Media Server.
It is recommended that backups be staggered so that only a subset of drives is in use at any one time. During a backup, the data transfer rate is primarily controlled by the Media Server because the DDE system does not restrict the ingest data rate. This creates the opportunity for one or more Media Servers to burst data at a higher rate leaving less bandwidth for the remaining virtual tape drives. Conversely, it supports the coexistence of fast data streams with slow streams for maximum use of the available bandwidth.
Keep in mind that increasing the number of concurrently active virtual tape drives does not increase the aggregate DDE bandwidth. It could result in a failed backup job due to a timeout from a bandwidth-starved operation.
The recommended maximum number of concurrently active virtual tape drives for various maximum aggregate bandwidths is listed in the table below.

DDE ModelDDE
Max VTDs (Virtual Tape Drives; max number defined in the system)512
Max number of Concurrently Active VTDs512
Max Aggregate Bandwidth

9,722MB/s (35.0TB/Hr)

Infinidat suggests that you contact NetBackup about possible limitations or other considerations related to the maximum number of concurrently active VTDs

Storage Lifecycle Policies

It is recommended that Storage Unit Groups NOT be used in conjunction with Storage Lifecycle Policies. Both features are completely permissible in their own rights when used properly and in the appropriate applications. However, using both features at the same time can result in problematic situations.

Storage Unit Fragment Size

Based on customer feedback and performance tuning testing, changing the fragment size for the storage unit in NetBackup from the default to 2000 balances backup and restore operations. The fragment size indicates the size for a single fragment before a file mark is inserted. When restoring a file, the operation must search the full fragment. Using the smaller size allows the operation to search a limited area of the backup.

Network Buffering for Windows Servers Overview

Due to complexity of each enterprise backup environment it is almost impossible to recommend an optimal configuration which fits all.  So Infinidat recommends keeping the default settings unless you are comfortable with Veritas suggestions as outlined here and in the Veritas Tech Notes linked below.

Windows NetBackup network buffering only has three components: NET_BUFFER_SZ, the Buffer_Size Registry value and the Communications buffer. For Windows NBU Media servers, Buffer_Size is what is used and the default value varies by NBU version. NET_BUFFER_SZ does not exist by default but is configured by the user and will supersede Buffer_Size, if it does exist. The Communication buffer is for clients and it is set in the NBU GUI.

Note

NetBackup client Buffer_Size KB value should match the Media Server NET_BUFFER_SZ byte value for optimal performance.

There are several Veritas Tech Notes on this subject and Infinidat highly recommends referring to all of them before deciding to make changes to the NetBackup environment. This is a very complex subject and many unintended consequences and unexpected results may occur if all of the following information is not taken into account fully.

They are, but are not limited to:

After making any changes, it is vitally important to verify that the following tests can be completed successfully:

  1. Run a backup
  2. Restore data from the new backup created in step 1.
  3. Restore data from a backup created prior to the changes to SIZE_DATA_BUFFERS and NUMBER_DATA_ BUFFERS.
  4. The number and size of the data buffers used by the NetBackup Media Server can be checked by looking in the bptm log file.
  5. Increasing the size and number of the data buffers will use up more shared memory, which is a limited system resource.
    1. The total amount of shared memory used is: (buffer_size * num_buffers) * drives * MPX

Tape Cartridge Capacity Considerations

Space on a given tape cartridge cannot be reused until after all backup data on that cartridge has expired and scheduled space reclamation has run. The greater the capacity of a cartridge, the longer it will typically take for all data on that cartridge to expire. Expired data continues to take up space on the virtual tape cartridge, as well as in the DDE, until that cartridge is overwritten, relabeled, or erased. This means that lower cartridge capacities are more desirable, so that tapes will be returned the NetBackup scratch pool for reuse and overwritten sooner.

Tape Drive LUN Mapping

It is recommended that mapping the device starting with LUN 0 on each port and not skipping any LUNs. A best practice is to zone the VTL devices and the NetBackup Media Servers together to prevent other servers from taking control of the VTL resources. Additionally, it is recommended to use the HBA driver to bind the devices to a specific address. This helps keep devices in the same order after a reboot. It is also recommended to set the WWNN = WWPN for DDE systems. This allows for binding on the HBA to use either WWNN or WWPN.

Configuring NetBackup with DDE NAS

NAS

A Network Attached Storage (NAS) unit is essentially a self-contained computer connected to an Ethernet network, with the sole purpose of supplying data storage services to other devices on the network. Several DDE models can present themselves as a NAS appliance for backup purposes. Before you can use a DDE system as a NAS appliance you must first configure a NAS share on the DDE.

Note

The DDE is NOT a Network Attached Storage device to be used to store customer data. The DDE only emulates a NAS device for the sole purpose of being a Backup-to-Disk target for backup applications such as NetBackup. Do not use the DDE NAS share as "Drag-and-Drop" file storage.

A DDE system can serve as a NAS backup system where the following protocols are supported:

CIFS Protocol: The CIFS (Common Internet File System) protocol defines a standard for remote file access using many computers at a time. This protocol allows users with different platforms to share files without installing additional software. This protocol is used with Windows networks.

NFS Protocol: The NFS (Network File System) protocol was originally designed by Sun Microsystems and allows all network users to access shared files stored on computers of different types. NFS provides access to shared files through an interface called the Virtual File System (VFS) that runs on top of TCP/IP. Users can manipulate shared files as if they were stored locally on the user's own hard disk. With NFS, computers connected to a network operate as clients while accessing remote files, and as servers when providing remote users access to local shared files. This protocol is used with UNIX/Linux networks.

NAS Device Path Considerations

Network segmentation is the process of splitting a single network into several sub-networks or segments. The advantages of a segmented network are improved performance and security. Performance is improved because there are fewer hosts on the segmented network, which in turn minimizes local traffic. Security is improved because the data traffic is contained on this segment and is not visible to the outside network.

Note

If you are using network segmentation and Automated Deployment Services (ADS), you must
use the data segment IP information for ADS management, NOT the management segment. ADS uses the Server Message Block (SMB) data protocol to manage the NAS shares on your system, which requires that the management traffic use the data segment.

DDE systems allow you to configure your network for separate segment types. The three primary segments are defined by the type of network traffic that can be used on that segment. The three types of network traffic are

  • Replication traffic - This segment is used exclusively for replication data movement.
  • Management traffic - This segment is used exclusively for DDE remote management (Web page access).
  • Data traffic - This segment is used exclusively for NAS data movement.

Each network segment has its own network interface (IP address, network mask, and default gateway). In this way, the segment is separated from other network segment traffic.

Note

Regardless of which type of bonding is used on the DDE (Round Robin or LACP), the ports on the Ethernet switch that the DDE are connected to must be in a matching group type as the bond on the DDE.

Veritas NetBackup seamlessly integrates with InfiniGuard disk backup systems using the NAS (CIFS or NFS) interface. Once installed and configured, NetBackup can manage backups through the DDE and take advantage of the system's capabilities, such as data deduplication and replication.

Installing and configuring the DDE and NetBackup for NAS operation consists of the following major steps, which are discussed below.

Configure the DDE for NAS

The DDE system allows you to configure it to present its storage capacity as NAS shares that are compatible with NetBackup. You can create NAS shares for use with Windows or UNIX/Linux networks. You can also join the DDE to a Windows domain or workgroup and manage users.

In the DDE Remote Management Console (the GUI) the Configuration page allows you to configure many of the features of the DDE, including storage presentation.

Configuring the DDE for NAS lets you choose which network protocol will be used as the transport method for backing up data from client machines to a NetBackup Media Server. CIFS (Windows) and NFS (UNIX/Linux) are available on the NAS > Summary tab. After NAS Shares have been configured on the DDE, NetBackup can be configured to use these shares as storage resources.

Configure the NetBackup NAS Storage Device

On CIFS platforms, from the NetBackup Master Server, you can Create New Storage Unit resources for the NetBackup environment. Although the DDE is presenting its storage capacity as a NAS share, and NetBackup will be creating a network-based storage resource, you still must choose Storage Unit Type
Disk, then Disk Type BasicDisk when configuring NAS storage.

In the "Absolute pathname to directory" field, you must specify a path including the FQDN "Fully Qualified Domain Name" (or IP address) to the DDE share directory you wish to use as a storage unit. Entering the
<DDE FQDN\NAS share name> in this field will enable the NetBackup Media Server to access specific DDE shares. It is possible to use short names for the share directory provided DNS is configured properly.

On UNIX/Linux platforms, you must first mount the NFS share on the host OS of the Media Server you plan to use to backup your data. Use NFS version 3 mount options per your OS' network file system mounting instructions.

From the NetBackup Master Server, you can Create New Storage Unit resources for the NetBackup environment. Although the DDE is presenting its storage capacity as a NAS share, and NetBackup will be creating a network-based storage resource, you still must choose Storage Unit Type Disk, then Disk Type BasicDisk when configuring NAS storage.

In the "Absolute pathname to directory" field, you must specify the local path to a previously mounted share from your DDE (see above UNIX/Linux platform instructions). In this example, entering the </mnt/DDE_share> will allow the NetBackup Media Server to access the DDEs NFS share called "DDE_share" (previously mounted at /mnt/DDE_share) for use with your backups.

Note

NetBackup recommends AGAINST configuring multiple BasicDisk storage units to share the same path as this may lead to unexpected behavior with respect to capacity watermarks on NBU.

DDE NAS Number of Shares Considerations

InfiniGuard DDE support both CIFS (Windows-based) and NFS shares. Each system can support multiple NAS shares, with a maximum of 128 shares. It is recommended that users create only the required number of shares for each Media Server. DDE systems can support concurrent NFS and CIFS shares, and can support Fibre Channel VTLs concurrently with those NFS and CIFS shares.

When using NAS shares on DDE systems, it is recommended to create at least one share for each Media Server to use. Media servers should not share the NAS shares during normal backup operations. Root access to an NFS share is not allowed, and the access rights will be changed to nfsnobody as a security precaution. This does not impact the access to the share from the backup application.

Network Share Access Control Considerations

In Windows Active Directory environments, the share acts as the target for NetBackup. The share is not intended as primary storage or drag-and-drop storage. A best practice is to create a new account and workgroup, as opposed to joining the domain, to limit access and prevent accidental file deletion by another user. It is recommended that you DO NOT reconfigure or delete NAS shares while data is being written.
There is no mechanism to detect the I/O and provide a warning to the user.

In NFS environments, root access to an NFS share is not allowed, and the access rights will be changed to nfsnobody as a security precaution. This does not impact the access to the share from the backup application.

Network Considerations

Some network considerations include:

  • Use a dedicated network for backup data, or use QoS features that guarantee network band width. Another option would be to use virtual networks (VLANs) to segregate backup from production network traffic.
  • Configure network interface cards (NICs) in the server and clients, and set routers to full duplex.
    • Use only CAT5e or CAT6 cables (1Gb/s rated cables).
    • Use only OM3 or OM4 (Aqua) Fibre Optic cables (10Gb/s rated FC).
  • If you are using a DNS server, verify that the DNS server configuration settings are correct and performance capability will be across the ports.
  • It is also a good idea to add the HOSTNAME and IP Address to the host file.
  • Use multiple DDE ports when connecting to the network. The more DDE Ports used, the better
  • Install and configure multiple network ports on the NetBackup Media Servers. Dedicate multiple ports for the transfer of data to the DDE.
  • Install and configure multiple network ports on the Media Servers. Dedicate multiple ports for the transfer of data from NetBackup Client to the Media Server.
  • Setup multiple networks and segregate traffic such that the NetBackup Client to Media Servers traffic does not interfere with the Media Servers to DDE traffic.
  • For redundancy, connect at least two DDE ports to an Ethernet switch.
  • Leverage NetBackup's ability to use multiple Media Servers. This can help ensure the success of data backups even if one Media Server goes down or loses connectivity with the DDE.
  • Leverage DDEs ability to setup multiple networks. The DDE network configuration allows for integration into nearly any networked environment.
  • Set each switch port used by the DDE to auto-negotiate/auto-sensing. The DDE network interface cards are preset to auto/auto and cannot be changed.

NetBackup Storage Settings and Tuning Considerations

When using a DDE as NAS for Disk Based Storage, consider the following when you create a new Storage Unit:

  • Options for NUM_DATA_BUFFERS_DISK and SIZE_DATA_BUFFERS_DISK for optimal performance. To find what works best for your environment, compare the performance of jobs with varied these "DATA_BUFFER" settings.
  • NUM_DATA_BUFFERS_DISK 16
  • SIZE_DATA_BUFFERS_DISK
    • For Windows 2003 SP2 and above use 262144 
    • For Windows 2003 SP1 and below use 65536
    • For UNIX/LINUX use 1048576ooo

Additional Best Practice Considerations

Several operational considerations are common to all three access methods (OST, VTL and NAS). See Common Operational Considerations for NetBackup section at the end of this document for more information on Deduplication, Encryption, Compression, Backup Streams and Replication.

Common Operational Considerations for NetBackup

Deduplication of Data Considerations

Deduplication results can be negatively impacted by compression, encryption, software deduplication, and multiplexing. These functions all change the data stream in a way that obscures patterns in the data content. They will reduce the performance and deduplication from any downstream appliance, including DDE systems. To obtain effective deduplication rates, you should NOT encrypt, deduplicate, compress, or multiplex your backup data before sending it to a DDE appliance.

The use of multiplexing was intended for slow source data, and for the minimum transfer rate required by physical tape drives. Multiplexing backup streams was intended to provide more efficient use of a limited number of physical tape drives. Since the virtual tape drives in DDE systems are not susceptible to performance losses from slow data transfer rates, the number of virtual tape drives can easily be increased in quantity without any time penalty for repositioning. It is not necessary to use multiplexing with the DDE systems. Additionally, multiplexing adds additional header information to the data and reduces the deduplication ratio.

Good Candidates for Data Deduplication

Data deduplication can work well with virtual machines, large databases and unstructured data such as Microsoft Office documents (PowerPoint presentations, Word documents, and Excel spreadsheets), SQL, Oracle and Exchange databases and source code.

Not So Good Candidates for Data Deduplication

Data deduplication does not work well with encrypted data, in-line compressed data, SQL with LiteSpeed (in-line compression), Oracle with multi-channel RMAN (in-line multiplex), Exchange 2010, and compressed or uncompressed music files or movies/videos.

For long-term archiving, it is recommended to vault the data to a physical tape device.

Replication Considerations

For first-time replication setups, when the DDE share is first created, it is highly recommended to manually initiate a Replication while that share is empty. This facilitates the first replication following the first backup to that share/partition.

  • The replication is only available to NAS shares with deduplication enabled.
  • The DDE supports 128-bit AES encryption for replication.
  • Data is only encrypted while in transit between the replication source and replication target.
  • Data is unencrypted upon arrival at the replication target.
  • Encryption may affect replication performance. You should disable encryption if your WAN is already secured.

Oversubscription of Space on the DDE

Deduplication will reduce the amount of space used on the physical system. Users are advised to monitor for Low Space conditions on the DDE and free up virtual media and disk targets before reaching this threshold.

  • The Disk Usage overview on the Home page of the DDE Management GUI displays the following information about disk usage on the system (Note: values are displayed as an amount and as a percentage of the total capacity in the system):
  • Disk Capacity - The total usable disk capacity of the DDE.
  • Available Disk Space - The disk space available for data storage (free space). I/O Write Low Threshold state (Yellow) - Free disk space is equal to or less than 500GB + [10GB * (Total system capacity in TB)]
  • Stop Write state (Red) - Free disk space is equal to or less than 250GB
  • Stop I/O state (Red) - Free disk space is equal to or less than 10GB

Notes

  • For optimal system performance, Infinidat recommends keeping the amount of Available Disk Space (free space) at 20% or more.
  • When disk capacity is low, target replication to the system is paused. In addition, space reclamation is automatically started to free up disk space.

Backup Streams Considerations

A different storage server should be created and used for each NetBackup domain (master server plus associated Media Servers). This segregates data so a NetBackup administrator cannot accidentally modify or remove backup images belonging to another domain.

When multiple hosts are using a single DDE system, you can distribute the load by dividing the hosts into groups. 

Performance tuning recommendations for NetBackup

Evaluating Backup and Restore Performance

A servers capacity to stream data over one or more ports will vary depending on the system model, bus architecture, as well as storage and memory. Heavily utilized systems will not provide optimal transfer rates because CPU resources are in contention. NetBackup users can use the Administration Console to review completed jobs with details on backup/restore sizes, duration of job and overall throughput, per job. The DDE GUI will also show average ingest and restore rates during I/O.

Load Distribution and Capacity Planning

NetBackup allows for servers and clients to share DDE resources and can maximize performance by running concurrent backup or restore operations. Users can configure multiple drives in a VTL, for example, and split the servers work load among them. Similarly with NAS shares, multiple targets can be configured as storage units to service individual jobs submitted by the servers and their clients. NetBackup administrators should perform test backups to determine how long is needed complete the jobs. Adding additional media servers or storage targets can help to maximize the potential I/O on a DDE system.

Troubleshooting, help and support

Our focus is to make it better, faster, easier, while reducing cost and complexity. Our success will be measured by our clients.

Self Help

Before reaching out to Infinidat Storage Support the following should be understood by administrators and considered before calling.

How can I free up disk space on my DDE?

There are multiple ways you can remove data from your DDE:

  • Delete data from your NAS share or VTL partition. 
  • Erase or re-label tapes from your backup application. 
  • Delete the virtual media altogether.
  • If the DDE is a replication target system, delete replicated snapshots.

After you take one or more of the previous actions, and after space reclamation completes, space consumed will be returned to the system.

When should I schedule replication for best performance?

Optimize your performance by scheduling your backups, and replication to run at different times throughout the day.

How can I increase my deduplication ratio?

Optimize your deduplication ratio by disabling software compression, encryption, and multiplexing in the backup application. Space reduction rates are a combination of deduplication and compression and a direct result of the number of redundant backups of data over the life cycle of defined retention. Therefore, client that run more full backups with higher retention values tend to see greater reduction rates than clients that run frequent incremental backups with shorter retention rates.

What should I do when my backups fail?

Backup jobs may fail for some of these reasons:

  1. The DDE ran out of space during the backup window. 
  2. Your backup host lost network connectivity to the DDE.
  3. Your backup application may have crashed. Try re-running the backup
  4. Your client in backup or the data mover managing backup traffic is over-whelmed and unable to process the work at hand.
  5. A backup policy or resource configuration access is misconfigured.

Documentation

The complete InfiniGuard documentation set is available here: https://support.infinidat.com/hc/en-us/categories/115000877369-InfiniGuard

Scope of Support

Support Services shall be provided 24 hours per day, 7 days a week. As part of the Support Services, Infinidat shall provide Installation Services, Updates, Telephone Support, Online Support, Remote Support (if applicable), and Onsite Support (if applicable), solely with respect to a Supported Release of the Product.

Service Levels

Infinidat shall provide Telephone Support, Online Support and Error Correction services in accordance with the chart below, as long as access to the Product is granted to Infinidat.

Response time for acknowledgement by Infinidat

  • Infinidat will provide you with an acknowledgement of the Support Request within the following time periods:
    • Priority A - 1 hour
    • Priority B - 4 hours
    • Priority C - next business day Onsite Support Availability
  • Onsite support will be provided within the following time periods, after Infinidat deems Onsite Support is necessary:
    • Priority A - 4 hour
    • Priority B - next business day
    • Priority C - to be scheduled with you

Contacting Infinidat

See instructions here: https://support.infinidat.com/hc/en-us/articles/360000308858-Best-Practice-for-contacting-INFINIDAT-Support

Was this article helpful?
0 out of 0 found this helpful

0 out of 0 found this helpful

Comments