Follow


InfiniGuard Configuration and Best Practices Guide for Data Protector

This guide seeks to help Infinidat customers who own InfiniGuard systems and who also use Data Protector 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 Data Protector with Infinidat InfiniGuard systems. This guide includes advice and best practices for using Infinidat InfiniGuard systems with Data Protector.

How to Use This Guide

This document assumes that the reader has basic expertise with Data Protector, as well as basic networking and SAN experience. It also assumes that the reader has an Infinidat InfiniGuard installed in a working Data Protector environment.
This document provides key recommendations and useful information for quickly setting up an InfiniGuard system with Data Protector. It expands on these recommendations and discusses the features and performance tuning considerations relevant to various storage access methods.

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. 

Data Protector 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 Data Protector. The InfiniGuard Data Deduplication Engines (DDE's) can appear as a Virtual Tape Library (VTL) storage device over Fibre Channel (FC) or as a Disk based target. These access methods are discussed in the following order.

  • DDE NAS - NFS and/or CIFS
  • DDE VTL

Documentation and References

The following is a list of documents, references, and links where you can find additional information regarding specific activities and products. Access to some documents may require a login or valid serial number; so, have those details available when following hyperlinks to the documents.

Online Documentation for Infinidat InfiniGuard

InfiniGuard User Guide and Best Practice Guides

Online Documentation for Micro Focus Data Protector

Data Protector Installation and Administration Documentation

Summary of Tuning Parameters for Data Protector

For backup administrators who are well versed on Data Protector and InfiniGuard DDEs, 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 Option

Setting

Compression

Do not utilize Data Protector’s Compression feature.

Encryption

Do not utilize Data Protector’s Encryption feature.

Deduplication

Do not utilize Data Protector’s Deduplication feature.

VTL Options

Settings

VTL sign-on string

Use the native Infinidat IBA B4260 DDE (DXi6900) or Scalar i6000 emulation which is also supported with Data Protector.

Drive sign-on string

Emulate as per the Data Protector HCL:

  • HP LTO4/5 or IBM LTO4/5 recommended

Direct Library Access option

Enable if multiple computers in a cell need to control the virtual tape library and devices, provided they are configured in Data Protector Cell Manager with multiple working paths to these devices.

SCSI Reserve/Release option

Enable

Use Lock Name option

Default

Miscellaneous Options

Recommendations

Server Resources

Set up no more than 1-2 drives per 3.xGHz CPU core. The server should have 2GB RAM, plus 1GB per drive.

Server Name

Use only standard ANSI characters for the computer name of the computer on which you want to install Data Protector. You may receive errors if you install Data Protector on a computer with a name that uses non-standard characters.  

Global options

See the Data Protector Global Options Considerations section later in this document for additional information

Windows OS Options

Recommendations

Services

Service Management Usage:

omnisv (-start | -stop | -status | -start_mon | - version | -help)

Network

On heavy utilized Windows system consider increasing TCP/IP timeout on Data

Protector media server. Reference Microsoft Knowledge Base http://support.microsoft.com/kb/q191143/ 

 

TcpMaxDataRetransmissions

Adjusting the following TCP/IP setting by adding a subkey in the registry should reduce the number of timeouts by allowing more time for the connection to complete. This setting is not present in the registry by default. 

Start Registry Editor (Regedt32.exe) and go to the following subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

On the Edit menu, click Add Value, and then add the following information: 

Value Name: TcpMaxDataRetransmissions
Value Type: REG_DWORD - Number 
Valid Range: 0 - 0xFFFFFFFF 
Default Value: 5 Decimal 
New Value: 10 Decimal 

Click OK, and then quit Registry Editor.
Reboot after registry change has been made.

 

Apply the following Microsoft hot fixes to improve performance:

UNIX OS Options

Recommendations

HP-UX

The schgr and stape (eschgr and estape) drivers have to be loaded in the HP-UX kernel, before adding discovering and adding the devices in Data Protector.

 

See the HP-UX NFS Client Settings later in this document for additional information

Configuring Data Protector with the InfiniGuard

Configuring Data Protector with DDE NAS

A NAS (Network Attached Storage) 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. The InfiniGuard DDEs can present themselves as NAS appliances for backup purposes; but first you must configure a NAS share on the DDE.

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. The Infinidat Network-Attached Storage (NAS) appliance is intended to act as a target for backup applications. This includes Network-Attached Storage or shares. Data Protector can use a NAS share as a Backup-to-Disk Target.

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 Series 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

If you are using the Round Robin (Mode 0) option, and you have either a Dell or Cisco switch, the ports that connect to the DDE must be bonded.


Data Protector seamlessly integrates with an InfiniGuard disk backup system using the NAS (CIFS or NFS) interface. Once installed and configured, Data Protector 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 Data Protector for NAS operation consists of the following major steps, which are discussed below:

Configure the DDE for NAS
Configure the Data Protector NAS Storage Device
Test Backup to DDE NAS storage target device

Configure the DDE for NAS

The DDE system allows you to configure it to present its storage capacity as NAS (Network Attached
Storage) shares that are compatible with Data Protector. You can create NAS shares for use with Windows or 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 the Data Protector media server. CIFS (Windows) and NFS (UNIX/Linux) are available on the NAS > Summary tab. After NAS Shares have been configured on the DDE, Data Protector can be configured to use these shares as storage resources.

For InfiniGuard DDE configuration detail, see InfiniGuard 3.0 Users Guide.

DDE NAS Summary page

image2019-7-11_16-5-59.png

Configure the Data Protector NAS Storage Device

  1. Configuring a file library device:
    Create a share on the DDE Target, CIFS for Windows or NFS for UNIX.
  2. Mount the share to the backup server if it is NFS or through File Explorer if it is CIFS.
  3. For CIFS/Windows support configure workgroup or Domain within the DDE GUI. Also add additional users as required.
  4. Under the Data Protector GUI select Devices & Media.
  5. Right-click Devices and select Add Device to open the device definition pane.
  6. Enter details:

Device name: Example: File Library Device 01
Description: optional
Client: Select the client to which the device is connected
Device type: Select File Library

7. Click Next

8. Specify the directory for the file library device you created in step 1 and click Add

Example:
Windows = \\<DDE_IP>\<CIFSshare> or Unix = /nfsshare
Where cifsshare is a DDE CIFS share and /nfsshare is an active mount point for a DDE NFS share.

9. Click Next. In the Results Area, select the media type: File.

10. Click Finish

Note

Scan and Format operations will not function until after the first backup is run which creates media (referred to as slots) on the target share.

Test Backup to DDE NAS storage target device

After you have completed the configuration, you can and should test the configuration by performing backup jobs and monitoring the results. Configuring and running a test backup:

  1. Select Backup from the Data Protector pull down menu
  2. Select the Task tab at the bottom of the left pane
  3. Choose a sample data set to back up from the file system tree
  4. Select the Storage Target
  5. Choose additional options if needed. Do not choose source-side deduplication.
  6. Specify a schedule or skip to next step
  7. Start the interactive backup – backup type: Full Job status is displayed automatically.

Restoring from a backup
By default, backup objects are restored to the same location they were backed up from.

  1. Select Restore from the Data Protector pull down menu
  2. Select the file system object you wish to restore in the left pane.
  3. In the right pane select the files you wish to restore
  4. Select tabs for options including; Destination, Devices, Media, Copies, and Restore Summary.
  5. Select Restore
  6. Review selection and select Finish Job status is displayed automatically.

Best Practices Guide with DDE NAS

Number of Shares Considerations

InfiniGuard DDEs support both CIFS (Windows-based) and NFS shares. Each system can support multiple NAS shares, with a maximum of 128 shares per DDE; or 256 shares per InfiniGuard. 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 Data Protector. 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.

Network Considerations

Some network considerations include:

  • Use a dedicated network for backup data, or use QoS features that guarantee network bandwidth. 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.
  • Cabling:
    • Use only CAT5e or CAT6 cables (1Gb/s rated cables).
    • Use only OM3 or OM4 (Aqua) Fibre Optic cables (10Gb/s rated FC). and SFP+ Optical or TwinAx for 10 GbE
  • If you are using a DNS server, verify that the DNS server configuration settings are correct by using nslookup on the host name, as well as the IP address.
  • It is also a good idea to add the HOST NAME and IP Address to the host file.
  • Use multiple InfiniGuard ports when connecting to the network. The more InfiniGuard ports used, the better the performance capability will be across the ports.
  • Install and configure multiple network ports on the backup server. Dedicate multiple ports for the transfer of data to and from the InfiniGuard.
  • Install and configure multiple network ports on the backup server. Dedicate multiple ports for the transfer of data from backup clients to the backup server.
  • For redundancy, connect at least two DDE ports to an Ethernet switch.
  • 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.

Data Protector Storage Settings and Tuning Considerations

When using a DDE as NAS for a Backup-to-Disk target with Data Protector, consider the following when you create a backup-to-disk folder:

  • Set the maximum size for backup-to-disk files to an appropriate size. If you create small but numerous files, performance may be slow, since the computer must still process each file. However, if you create large files, file system limitations can cause memory allocation problems or network issues. These issues can be a problem if you store files across a network.

NFS/CIFS Recommended Mount Options

Sun Solaris NFS Client Settings  

Change socket buffer size:

Solaris# ndd –set /dev/tcp tcp_xmit_hiwat 4194304
Solaris# ndd –set /dev/tcp tcp_recv_hiwat 4194304
Solaris# ndd –set /dev/tcp tcp_max_buf 4194304
Solaris# ndd –set /dev/tcp tcp_cwnd_max 2097152

1M and 4M are both fine. Also, as per Solaris documentation, some of these can be added in /etc/system file for persistence.

 set tcp:tcp_xmit_hiwat = 4194304
set tcp:tcp_recv_hiwat = 4194304

Set the socket buffers before doing mounts from clients. If they are already mounted, clients need to unmount and remount for the settings to take place. The unmount and remount may be done after the client is fully configured.

Verify the settings by issuing the command:

ndd –get /dev/tcp tcp_recv_hiwat

If your client has multiple NICs bonding can be beneficial.

Create Link aggregation group with LACP:

Solaris# dladm create-aggr –d bge0 –d bge1 1
Solaris# ifconfig aggr1 unplumb
Solaris# dladm modify-aggr –P L4 –l active 1
Solaris# ifconfig aggr1 plumb <ip> netmask <netmask> up

Verify the settings by issuing the commands:

dladm show-aggr
dladm show-aggr –L

Add the following lines to /etc/system to support > 32K rsize/wsize:

set nfs:nfs3_bsize=1048576
set nfs:nfs3_max_transfer_size=1048576
set nfs:nfs3_max_threads=32

This next step requires a reboot prior to mounting.

 Mount with rsize/wsize set to 1M:

mount –o vers=3,tcp,rsize=1048576,wsize=1048576 …

If the settings above are executed correctly, the default rsize, wsize should be 1M without a need for specifying in the mount command.

 Verify the actual rsize and wsize:

nfsstat –m

Linux NFS Client Settings

Change socket buffer settings to 4M default. Append these lines to /etc/sysctl.conf:

net.ipv4.tcp_rmem = 4194304 4194304 4194304
net.ipv4.tcp_wmem = 4194304 4194304 4194304
net.ipv4.tcp_mem = 10485760 10485760 10485760
net.core.netdev_max_backlog = 30000

Run the command sysctl –p for the newly added configuration to take effect.  Verify the configuration by running sysctl net.ipv4.tcp_rmem, it should show 4194304 4194304 4194304.

Set the socket buffers before doing mounts from clients. If they are already mounted, clients need to unmount and remount for the settings to take place. The unmount and remount may be done after the client is fully configured.

If your client has multiple NICs bonding can be beneficial.

Create Link aggregation group with LACP and add bonded round robin policy by adding this line in /etc/modprobe.conf:

options bonding mode=6 miimon=500

During this testing, in lieu of LACP, Layer3+4 xmit_hash policy was also successfully used to reduce TCP retransmissions. In the /etc/modprobe.conf, add the line:

options bonding mode=2 xmit_hash_policy=layer3+4 miimon=500

This step needs a reboot.

Mount with rsize/wsize set to 1M.           

mount –o vers=3,tcp,rsize=1048576,wsize=1048576 …

The older versions of Linux (pre-2.6.16) only support maximum of 32K rsize/wsizes that are not optimal. 2.6.18 and recent versions showed better performance. Verify the mount options by running the command cat /proc/mounts

IBM AIX NFS Client Settings

Change socket buffer settings to 4M default. Append these lines to /etc/sysctl.conf

/usr/sbin/no -o tcp_sendspace=4194304
/usr/sbin/no -o tcp_recvspace=4194304

To make them permanent, add the following lines into the /etc/rc.net file:

/usr/sbin/no -o tcp_sendspace=4194304
/usr/sbin/no -o tcp_recvspace=4194304

If your client has multiple NICs bonding can be beneficial. Configure the Etherchannel by using the smit etherchannel command. Mount with rsize/wsize set to 1M.

mount –o vers=3,tcp,rsize=1048576,wsize=1048576

AIX clients may not scale past 50 streams on some servers.

HP-UX NFS Client Settings

 Change socket buffer settings to 4M default.

# ndd -set /dev/tcp tcp_recv_hiwater_def 4194304
# ndd -set /dev/tcp tcp_xmit_hiwater_def 4194304

 To make the changes permanent add the following lines to the /etc/rc.config.d/nddconf file and issue the command “ndd –c” to activate the changes:

TRANSPORT_NAME[0]=tcp
NDD_NAME[0]=tcp_recv_hiwater_def
NDD_VALUE[0]=4194304
TRANSPORT_NAME[1]=tcp
NDD_NAME[1]=tcp_xmit_hiwater_def
NDD_VALUE[1]=4194304

To verify the settings have changed following the ndd -c command:

bash-4.2# ndd -get /dev/tcp name to get/set ? tcp_recv_hiwater_def
value ?
length ?
4194304
name to get/set ? tcp_xmit_hiwater_def
value ?
length ?
4194304

If your client has multiple NICs bonding can be beneficial.  See HP-UX System Administration documentation.

 In order to support greater than the default maximum of 32K rsize/wsize do the following:

# kctune nfs3_bsize=1048576
# kctune nfs3_max_transfer_size=1048576
# kctune nfs3_max_transfer_size_cots=1048576

Confirm they were added to the Tunable entries section of the file /stand/system: # cat /stand/system

This change will take effect either after a reboot or after the NFS file systems are unmounted and remounted.
Mount with rsize/wsize set to 1M.

mount –o vers=3,tcp,rsize=1048576,wsize=1048576 …

 Verify the actual rsize and wsize.

nfsstat –m

Microsoft Windows CIFS Client Settings

Microsoft provides comprehensive guidelines for configuration and tuning for networks and storage.
Link to documents for specific Windows versions http://support.microsoft.com

Additional Best Practice Considerations

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

Configuring Data Protector 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. The DDE VTL is viewed through Fibre Channel interfaces and appears as a virtual library with virtual drives and cartridges. During backups, the application creates a backup image on the virtual tape cartridges.

VTL Device Path and Robot/Media Changer Device Serialization Considerations

One of the key ways to ensure that SAN-connected physical and virtual tape libraries are detected properly by backup servers is serialization. Serialization provides a unique identifier for each device in a physical or virtual tape library, to automate device association from multiple backup servers. These identifiers, returned by the VTL devices, are separate from the element address that defines the position of devices in the library. The element address is used by the library's robot or medium changer to manage the tape drives.

Serialization allows the servers running the data protection application (the media servers) to coordinate tape drive configuration by aligning the device serial number with the device's element address. This enables Data Protector device discovery to align these two addresses, reducing the potential for improper configuration.

If the Device Configuration Manager does not serialize the devices listed, do not commit the changes, and be sure to check the VTL online state. The DDE VTL partition must be online for this to function properly.

The Infinidat recommended device identification for each DDE system is the native mode (in other words, use the DDE inquiry response string as the identification for each model, respectively). This allows product identification for the service teams at both Micro Focus and Infinidat.

When using the native device mode, Windows environments will display the device in the Device Manager as an unknown media changer. This is normal and not an error and does not create a problem for Data Protector. If the customer environment has requirements for a specific changer device for compatibility, the InfiniGuard DDE product supports emulation of many popular devices to meet those requirements.

Always ensure that the latest drivers and firmware have been installed for the tape drive, robotic library, and HBA.
To verify that the drivers have been loaded for the tape drive, return to Device Manager in Windows and open the properties of the Tape Drive. Verify that the Driver is at the latest level.

Supported Hardware Compatibility List

If a device is presenting itself properly to the operating system, it should be supplying the operating system with an inquiry string.
For the device to work properly within Data Protector, the inquiry string that the device provides must match exactly with what is documented on the HCL. Micro Focus certifies Libraries and Tape drives separately. See Micro Focus Data Protector 10.x Device Support Matrix

The following steps outline the configuration process at a high-level. For detailed instructions, refer to the Data Protector Guides.

Configure the DDE for VTL
Configure Data Protector with the DDE VTL
Test Backup to DDE VTL storage target device
Advanced Tape Drive Options (under Tape Drive Settings)

Configure the DDE for VTL

Data Protector seamlessly integrates with a InfiniGuard disk backup system using the VTL interface. Once installed and configured, Data Protector can manage the backups through the DDE and can take advantage of the DDE system's capabilities, such as data deduplication and replication.

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 existing backup software. 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 an InfiniGuard to present its storage capacity as VTL (virtual tape library) 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. You can also map partitions to hosts.

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.

Note

Use DDE Native (e.g. Infinidat IBA B4260 DDE (DXi6900)) or Scalar i6000 emulation for the library and HP or IBM LTO emulation for the tape drives


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.

For InfiniGuard DDE configuration detail, see InfiniGuard 3.0 Users Guide.

Partition Summary page

image2019-7-12_13-26-47.png

Note

Ensure that your Data Protector system is properly configured for the correct number of tape drives emulated in the DDE system partition. Failure to do so may cause Data Protector to malfunction or cease to operate.

Note

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

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.

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. See Over-subscription of Space on the DDE in the Common Operational Considerations section for more information on this subject.

Configure Data Protector with the DDE VTL

To configure the Data Protection Manager Library and tape drives, follow these steps:

Install the Data Protector Cell Manager system to configure and control devices and clients within the cell. By default, cell manager installations include media and disk agents, along with a user interface. UNIX Install Path:

<Data Protector Source>/Bxxxx-xxxxx/LOCAL_INSTALL/omnisetup.sh

Example: <install path>/omnisetup.sh –CM, installs a cell manager with default agents and a user interface.

UNIX Binary Path: /opt/omni/bin/xomni - Launches the Data Protector user interface.

Connect DDE VTL via FC SAN to the Data Protector server.

Note

Data Protector supports Infinidat InfiniGuard Virtual Tape Libraries (VTL) as well as CIFS and NFS File Library devices. If necessary, install the latest SCSITab to ensure support for attached Tape devices, physical or emulated, within the VTL.

HP-UX drivers and discovery. Verify that the latest drivers are installed.

HP-UX pass-thru drivers for Autochangers:
The schgr and stape (eschgr and estape) drivers have to be loaded in the kernel before discovering and adding the devices in Data Protector.

To review the special file, execute the following command: # ioscan –fn

Review the sp (special file) that the library and tapes were created.

Example:
Autoch 30 0/4/1/1.1.3.255.0.0.0 schgr NO_HW DEVICE DXi 6900 /dev/rac/c7t0d0

tape50 0/4/1/1.1.3.255.0.0.1 stape NO_HW DEVICE HP Ultrium 5-SCSI/dev/rmt/c7t0d1BEST /dev/rmt/c7t0d1BESTb /dev/rmt/c7t0d1BESTn /dev/rmt/c7t0d1BESTnb

tape 52 0/4/1/1.1.3.255.0.0.2 stape NO_HW DEVICE HP Ultrium 5-SCSI/dev/rmt/52m /dev/rmt/52mn /dev/rmt/c7t0d2BEST /dev/rmt/c7t0d2BESTn

If these were not created, run the following command to install the special files in the devices directory (/dev):
#insf –emc and mt commands

Use the following mc and mt commands to manipulate the library and tape drives directly:

Examples:

Review a slot in the library
#mc -p /dev/rac/c26t0d1 -r S*

Review the drives in the library
#mc -p /dev/rac/c26t0d1 -r D*

Review the cab or mailbox in the library
#mc -p /dev/rac/c26t0d1 -r I*

Move a tape from Slot 1 to Drive 5
#mc -p /dev/rac/c26t0d1 –s S1 –d D5*

Eject the tape from drive 5
#mt –f /dev/rmt/5m offline*

Move a tape from Drive 5 to slot 20
#mc -p /dev/rac/c26t0d1 –s D5 –d S20*

Additional Support Resources
Devbra utility lists the Changer and Tape drives and their paths.

Example  <Install Path>\Omniback\bin\Devbra.exe –dev

Note

Data Protector 8.X and higher includes a GUI for Windows platform (previous DP versions supported Linux GUI too). To use GUI for DP Cell Manager on Linux you must install DP Client on Windows.

Command line interface is provided for both Windows and UNIX platforms.

Clients connect through port 5556 to access the Java GUI.

  • Map the DDE VTL to the host on the appropriate FC connection for target devices using the DDE configuration GUI
  • Verify the SAN-attached VTL is visible and properly configured within the Data Protector operating system.

Note

It may be necessary on some UNIX platforms to remove stale device entries in the OS prior to discovering devices and configuring them in Data Protector. Data Protector provides an Autoconfigure option for configuring SCSI libraries and tape drives. Alternatively, devices may be added manually through the user interface.

Auto configuration process:

  • Navigate to the Devices & Media window in the Data Protector GUI (Data Protector refers to the pull-down menu options as "contexts")
  • Right-click on Devices in the left pane.
  • Select "Autoconfigure Devices" to open the Wizard.
  • Select the client system that is connected to the VTL from the list and click Finish

Manual configuration process

  • Enter details:

Device name: Example: Scalar I6000
Description: optional
Client: Select the client to which the device is connected
Device Type: SCSI Library
Interface Type: SCSI

  • Click Next
  • Select the appropriate SCSI address from the pull-down options. Click Add.
  • After selecting next, select the appropriate media type, e.g. LTO
  • Click Finish

Add tape drives in a similar manner and associate them with the newly created library from the previous step.

  • Configure Additional Library Options 
    • Under Properties:

General: Multipath Device support
Control: Barcode Reader support
SCSI Reserve/Release support
Repository:   Limit the slots, presented by the library, if desired

  • Adding media to the media pools that will be used with the newly configured device:
    • Format unused or import used media to a media pool before backup

Test Backup to DDE VTL storage target device

After you have completed the configuration, you can and should test the configuration by performing backup jobs and monitoring the results.
Configuring and running a test backup

  1. Select Backup from the Data Protector pull down menu
  2. Select the Task tab at the bottom of the left pane
  3. Choose a sample dataset to back up from the file system tree
  4. Select the Storage Target
  5. Choose additional options if needed. Do not choose source-side deduplication.
  6. Specify a schedule or skip to next step 7. Start the interactive backup – backup type: Full 
  7. Job status is displayed automatically.


Restoring from a backup
By default, backup objects are restored to the same location they were backed up from.

  1. Select Restore from the Data Protector pull down menu
  2. Select the file system object you wish to restore in the left pane
  3. In the right pane select the files you wish to restore
  4. Select tabs for options including: Destination, Devices, Media, Copies, and Restore Summary.
  5. Select Restore
  6. Review selection and select Finish

Job status is displayed automatically.

Advanced Tape Drive Options (under Tape Drive Settings)

Direct Library Access option
The Use Direct Library access option allows for multiple computers in a cell to control the virtual tape library and devices, provided they are configured in Data Protector Cell Manager with multiple working paths to these devices. e.g.: A cell manager and a client are both configured with SAN connections to a VTL. If the cell manager loses its FC connection, there is still a path to it from the client using Direct Library Access.
SCSI Reserve/Release option
Selecting this option prevents access to SCSI devices (Library and Tape drives) while they are being utilized by another process.
Use Lock Name option
Selecting the device lock name option will ensures that Data Protector will not try to use the same device with a different name at the same time. The user can create lock names for the devices or go with default names assigned.

Best Practices Guide with DDE VTL

Device Driver and Firmware level

Ensure that the latest drivers and firmware have been installed for the tape drive, robotic library, and the HBA.  Current DDE code includes the latest tape drive and robotic library emulation code. 

Tape Drive LUN Mapping

It is recommended to start device mapping with LUN 0 on each port and not skipping any LUNs. A best practice is to zone the VTL devices and the Data Protector media servers 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.
Infinidat InfiniGuard VTL devices support reserve and release to accommodate sharing drives. The option allows devices to be shared between Data Protector media servers. The advantage of this is that you will have a pool of drives available to each media server. Other SAN architectures assign drives to each media server and eliminate the shared function. For both conditions, it is a good practice to keep the Data Protector media server separate from the production server, to eliminate downtime from maintenance. This requires the media servers to have a fast network connection to the source data.

Number of Concurrent Tape Drives in Use

Each InfiniGuard provides two active DDEs, each of which can be configured with up to 512 VTDs to provide 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.

Infinidat also recommends that backups be staggered, so that only a subset of drives is in use at 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 also 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. Infinidat suggests that you contact Micro Focus about possible limitations or other considerations related to the maximum number of concurrently active VTDs

InfiniGuard DDE  (2 active DDEs per InfiniGuard)

Per DDE

Per InfiniGuard

Max VTDs (Virtual Tape Drives; max number defined in the system)

512

1024

Max number of Concurrently Active VTDs

512

1024

Max Aggregate Bandwidth

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

19,444MB/sec (70.0TB/hr)

Data Protector Block size and transfer size

As with physical tape, larger tape block sizes and host transfer sizes are of benefit. This is because they reduce the amount of overhead of headers added by the backup application and also by the transport interface. The recommended minimum is 256 KB block size, and up to 1 MB is suggested.

Tape Cartridge Capacity Considerations

Space on a given tape cartridge cannot be reused until after all backup data on that cartridge has expired. 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 on the InfiniGuard, until that cartridge is overwritten, relabeled, or erased. This means that lower cartridge capacities are more desirable, so that tapes will be returned to the default scratch pool for reuse and overwritten sooner.

There is virtually no relationship between the configured capacity of a virtual tape cartridge and the tape drive emulation that has been configured for the partition:

  • Backup/restore operations will span the number of tapes required, ignoring the configured capacity.
  • Vaulting/duplicating operations performed by the backup application will ignore the virtual capacity when writing to another cartridge, whether virtual or physical.
  • InfiniGuard devices limit the maximum capacity permitted by the tape drive emulation; the minimum is 5GB.
  • The capacity utilization is tracked in UNCOMPRESSED GB, and the data is stored in compressed form. That is, 100GB of data that is 2:1 compressible will be reported as occupying 50GB of virtual tape cartridge space.
  • Infinidat’s general guidance is to specify a smaller virtual tape cartridge capacity, such as 100GB to 500GB, for the reasons mentioned above.

Recommended Handling of Expired Media

When a tape is expired or recycled by Data Protector, there is no direct communication of the event to the DDE. The result is that a tape may be displayed as empty or SCRATCH in the Data Protector graphical interface, but will show the same tape on the DDE GUI as containing data. This indicates the data on the expired tape is still using space on the DDE.

To reclaim this space, we recommend using Data Protector's graphical interface to re-label the expired media. This new label is a data block written to the virtual tape cartridge at the beginning of tape, effectively blanking the tape. The DDE VTL will act similarly to a physical tape and the data after the label becomes no longer accessible.

Recycling Expired Media within Data Protector

Under Devices and Media -> Pools -> Default Media Pool, select the media you wish to recycle. Data Protector will then allow for it to be overwritten in future backup operations. The user can also format the media, to free up space on the DDE, immediately

Media Management in Data Protector

The following media operations are supported on the virtual tape drives:

  • Barcode Scan
    • Inventory media by barcode
  • Format Medium
    • Data Protector writes its own header on each tape so it can be recognized later. This can be done manually, as described in this section, or automatically.
  • Scan Medium
    • Scan contents of media, one at a time or multiple in parallel.
  • Copy Medium
    • Copy the contents of one tape to another.
  • Eject & Enter Media from Mailslot
    • Not supported in VTL.
  • Import/Export
    • When a tape is moved from a Storage Slot to an I/E mailslot, depending on the Auto Export setting, the media:
      • Will be removed from the virtual I/E slot if Auto Export is enabled. (Default) The user has the option to recycle or import the tape via the DDE GUI
      • Will remain in the virtual I/E slot if Auto Export is disabled.
  • Verify Medium
    • This process checks that the data format is valid on a tape. It will update the Internal Database, following the Verify, which can take a long time, depending on how much data is on the tape.
  • Cleaning
    • Cleaning functions are not supported in a Virtual Tape Library (VTL).

Common Operational Considerations

Over-subscription of Space on the InfiniGuard

Deduplication will reduce the amount of space used on the physical system by the virtual tapes. Users are advised to monitor for Low Space conditions on the InfiniGuard and free up virtual media before reaching this threshold.  See "Recommended Handling of Expired Media".

The Disk Usage overview on the Home page of the InfiniGuard 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 InfiniGuard.
  • 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.

Note

  • 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.

Deduplication 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 VMware, large databases , PowerPoint presentations, Word documents, Excel spreadsheets, SQL, Oracle , Exchange databases and source code

Not So Good Candidates for Data Deduplication
Data deduplication does not work well with in-line compressed data, SQL with LiteSpeed (in-line compression), Oracle with multi-channel RMAN (in-line multiplex), Exchange 2010, compressed video, compressed audio and compressed JPG images.

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

Replication Considerations

For first-time replication setups, it is important to manually replicate the name space once the target system is configured and is online. 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

Backup Streams Considerations

Data Protector uses Load balancing to distribute the backup job objects over multiple devices. When defining a job, the user specifies the devices that are being for the backup. The backup objects are then divided among the target devices.
The default minimum is 1 and the default maximum is 5.

Data Protector Global Options Considerations

Global options affect the entire Data Protector cell and cover various aspects of Data Protector, such as timeouts and limits. All global options are described in the global options file, which you can edit to customize Data Protector. The global options file is located on the Cell Manager:

  • Windows Server 2008: Data_Protector_program_data\Config\Server\Options\global
  • Other Windows systems: Data_Protector_home\Config\Server\Options\global
  • UNIX systems: /etc/opt/omni/server/options/global

To set global options, edit the global file. Uncomment the line of the desired option by removing the '#' mark, and set the desired value.

Note

Most users should be able to operate Data Protector without changing the global options.
The following list includes the most often used global variables. See the global options file for a complete description.
  • MaxMAperSM: Changes the default limit of concurrent devices per backup session. Maximum device concurrency is 32.
  • DCDirAllocation: Determines the algorithm used for selecting the dcbf directory for a new detail catalog binary file: fill in sequence (default), balance size, or balance number. It is recommended to change the allocation policy from fill in sequence (default) to balance size.
  • DailyMaintenanceTime: Determines the time after which the daily maintenance tasks can begin. Default: 12:00 (Noon). For a list of daily maintenance tasks, see the online Help index:
  • DailyCheckTime: Determines the time after which the daily check can begin. Default: 12:30 P.M. You can also disable the daily check. For a list of daily check tasks, see the online Help index:
  • MediaView: Changes the fields and their order in the Media Management context.
  • MaxBSessions: Changes the default limit of five concurrent backups.
  • InitOnLoosePolicy: Enables Data Protector to automatically initialize blank or unknown media if the loose media policy is used.

Disable backup application verify pass

Most backup applications will default to performing a verify operation after a backup job. While this offers a very good way to ensure that data is backed up successfully it will also heavily impact the performance of the whole backup job. Performing a verify operation will more than double the overall backup time due to the fact that restore performance (required for verify) is slower for inline deduplication-enabled devices. Verifying some backup jobs on a regular basis is recommended. For example, verifying the weekly full backups where additional time is available might be an option.

Troubleshooting

Debugging can be enabled through the Data Protector GUI under: File -> Preferences. The default range level is 0 to 99. Users are advised to consult with Micro Focus for further instructions on debugging.

Report level option

Options include: Warning, Minor, Major, and Critical. Messages are reported at the set level and higher, so a Minor setting reports those events and all above it.

Reviewing Sessions

  1. Select Internal Database from the Data Protector pull down menu.
  2. Expand the Sessions folder in the left pane.
  3. Select the session you wish to review.

Generating Reports

  1. Select Reports from the Data Protector pull down menu.
  2. Right-click on Reports, in the left pane. Select Add Report.
  3. Select from available reports, including Reports on a single session.
  4. Event logs are also available under this menu.

Managing Data Protector Services

Run Data Protector file:

/opt/omni/sbin/omnisv –stop (-start, -status)

Or

<Install Path>\OmniBack\bin\omnisv.exe

Example:

Verify that the Data Protector services are running. /opt/omni/sbin/omnisv –status  Output:

    ProcName  Status  [PID]

rds     : Active  [10751]
crs     : Active  [10755]
mmd     : Active  [10753]
kms     : Active  [10754]
omnitrig: Active
uiproxy : Active  [10757]
Sending of traps disabled

Status: All Data Protector relevant processes/services up and running

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/articles/360000491457-InfiniGuard-3-0-documentation

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/sections/360000024169-How-to-contact-INFINIDAT-Support

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

0 out of 0 found this helpful

Comments