Prepare for installation

From ITOM Practitioner Info
Jump to: navigation, search

The Data Protector installer checks for the following prerequisites:

  • Application server certificate corruption.
  • Hostname or domain change after installation.
  • Hostname beginning with a numeric character.
  • Soft link validation (Linux and HPUX).
  • Have sufficient free disk space.
  • Checks for INET, IDB and AS ports.
  • Have the user group hpdp and the dedicated user account hpdp in this user group configured (or equivalent user).

The following has to be checked manually:

  • Reverse lookup of hostname.
  • Default users umask is set to 022.
  • Long filenames are supported. To check if your filesystem supports long filenames, execute the getconf NAME_MAX <DirectoryPath> command.
  • Basic command line calculator (bc) installed.
  • The hpdp or an equivalent user must have access to any directory from the following paths that already exist in the system:
    • /opt/omni/*
    • /etc/opt/omni/*
    • /var/opt/omni/*
  • A name in the hostname or domain must not be a single character. For example, hostname.a.company.com. See RFC 952 for hostname specifications.

The following sections provide information on prerequisites for the installation of Data Protector components:

Contents

Windows Cell Manager in non-cluster mode

  • Prior versions of Data Protector 10.00 GUI are not compatible with Data Protector 10.00 Cell Manager.

  • All configuration and session information files in a Data Protector cell are stored on the Cell Manager. It is difficult to transfer this information to another system. Therefore, ensure that the Cell Manager is a reliable system in a stable, controlled environment.
  • Reverse DNS lookup for host name resolution is required for all Data Protector components in the Data Protector cell.
  • The user account used for the installation must:

    • Have to be a member of the local Administrators Group on the selected target system.

    • Have "SeNetworkLogonRight" or "Access this computer from the network" user rights.

  • User account privileges can be set using the Local Group Policy Editor (gpedit.msc) by navigating to the Local Computer Policy\Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment folder or consult your network administrator of your organization.
  • The Data Protector Inet service by default runs under the Windows local user account SYSTEM. However, if for various reasons the Inet service runs under a Windows domain user account, you must additionally grant it the following Windows operating system Security Policy privileges:

    • Impersonate a client after authentication

      To do this, perform the following:
      1. Go to Start > Programs > Administrative Tools or Start > Control Panel > Administrative Tools.
      2. Open Local Security Policy > Local Policies > User Rights Assignment > Impersonate a client after authentication.
      3. Select the user account in the Local Security Setting tab and click OK.

      4. Close the Local Policies and Administrative Tools windows.
    • Replace a process level token


      To do this, perform the following:


      1. Go to Start > Programs > Administrative Tools or Start > Control Panel > Administrative Tools.
      2. Open Local Security Policy > Local Policies > User Rights Assignment > Replace a process level token.
      3. Select the user account in the Local Security Setting tab and click OK.

      4. Close the Local Policies and Administrative Tools windows.

    For more information, see the Data Protector Help index: “Inet user impersonation”.

  • The system that will become the Cell Manager must:

    • Have a supported Windows operating system installed. For a list of supported operating systems for the Cell Manager, see https://softwaresupport.softwaregrp.com.

    • Have sufficient free disk space for the Data ProtectorCell Manager software. The Cell Manager requires 16 GB of total RAM and 4 CPU cores.

      For recovery of the Internal Database, twice as much total RAM is required.

      For each parallel backup session, 40 MB of RAM are required. For example, if you want to run 60 parallel backup sessions, 3 GB of RAM are needed.

    • Have sufficient free disk space for the Data Protector Internal Database (IDB). 1.5 GB of free disk space + approximately 100 bytes for each backed up file (for use by the IDB).

      If you have insufficient free storage space on the selected disk volume, you can mount another volume to a directory on it, but you should do so before the installation.

    • Have2 × size_of_the_biggest_package_to_be_installed + 10 MB of disk space on the system drive.

    • Have firewall configured to additionally accept "Remote Service Administration" (NP) connections (port 445).

    • Have the Microsoft implementation of the TCP/IP protocol installed and running. The protocol must be able to resolve hostnames. The computer name and the hostname must be the same.

    • Have a static IP address assigned. If the system is configured as a DHCP client, its IP address changes; therefore, it is required to either assign a permanent DNS entry for the system (and reconfigure it), or to configure a DHCP server to reserve a static IP address for the system (IP address is bound to the system's MAC address).

    • Have the following ports free:

      • 5565 - port required for new installation in Data Protector.

      • 5555 - port required during upgrade of Data Protector installation.

      • 7112 - the Internal Database Service port

      • 7113 - the Internal Database Connection Pooler (IDB CP) port

      • 7116 - the Application Server (HTTPS AS) port

      • 9999 - the Application Server management port

      You can change the above listed service ports during installation.

    • To run large number of sessions on a Windows Cell Manager, you must change the desktop heap limit. The size of each desktop heap allocation is controlled by the following registry value:

      HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\SubSystems\Windows

      The default data for this registry value will look something like the following:

      %SystemRoot%\system32\csrss.exe ObjectDirectory=\Windows SharedSection=1024,20480,768 Windows=On SubSystemType=Windows ServerDll=basesrv,1 ServerDll=winsrv:UserServerDllInitialization,3 ServerDll=sxssrv,4 ProfileControl=Off MaxRequestThreads=16

      The numeric values following "SharedSection=" control how desktop heap is allocated. These SharedSection values are specified in kilobytes.

      • 1024 - shared heap size common to all desktops

      • 20480 - size of the desktop heap for each desktop that is associated with an interactive window station

      • 768 - size of the desktop heap for each desktop that is associated with a non-interactive window station

      You must change the SharedSection value that is associated with a non-interactive window station to 20480. A reboot is required for this change to take effect.

    • If you expect DC binary files to grow larger than 2 GB (their size is limited only by the file system settings), it is recommended that you use the NTFS file system for their storage.

  • To install Data Protector on Windows through Microsoft Terminal Services Client, ensure that the system you want to install Data Protector on has Remote Administration selected for the Terminal Server Mode:

    1. In the Windows Control Panel, click Administrative Tools and then Terminal Services Configuration.

    2. In the Terminal Services Configuration dialog box, click Server Settings. Ensure that the Terminal Services server is running in the Remote Administration mode.

UNIX Cell Manager in non-cluster mode

  • Reverse DNS lookup for host name resolution is required for all Data Protector components in the Data Protector cell.

  • The default users unmask must be set to 022 otherwise some of the Data Protector services might fail to start.

  • The user account used for the installation must have administrative (root) privileges on the selected target system.

  • The system that will become the Cell Manager must:

    • Have a supported UNIX operating system installed. For a list of supported operating systems for the Cell Manager, see the latest support matrices.

    • Have sufficient free disk space for the Data ProtectorCell Manager software. The Cell Manager must meet the following minimum requirements:

      • The Soft File Limit per Process on the Cell Manager should be at least 1024.
      • HP-UX systems: 16 GB of total RAM and 4 CPU cores.
      • Linux systems: 16 GB of total RAM and 4 CPU cores.

      For each parallel backup session, 40 MB of RAM and 5-8 MB per data segment size are required. For example, if you want to run 60 parallel backup sessions, 3 GB of RAM plus 512 MB for data segments are needed.

      You can overcome free disk space shortage by installing Data Protector to linked directories. Before creating the links, see Prepare for installation.

    • Have sufficient free disk space for the Data Protector Internal Database (IDB). For recovery of the Internal Database, twice as much total RAM is required. Have 1.5 GB of free disk space + approximately 100 bytes for each backed up file (for use by the IDB) in the /var directory, where the IDB is stored. Note that the current IDB design allows the database binary files to be relocated if growth in database size makes it necessary.

      If you have insufficient free storage space on the disk volume, you can use linked directories, but you should create the links before the installation and ensure that the destination directories exist.

    • Have the TCP/IP protocol installed and running. The protocol must be able to resolve hostnames.

    • Recognize the Cell Manager system if using a NIS server.

      To add the Data Protector information to your NIS server

      1. Log in as root on the NIS server.

      2. If you are managing the /etc/services file via NIS, append the following line to the /etc/services file:

        omni 5565/tcp # Data Protector for Data Protector inet server

        Replace 5565 with an alternative if this port it is not available.

        If you are managing the /etc/inetd.conf file via NIS, append the following line to the /etc/inetd.conf file:

        #Data Protector

        omni stream tcp nowait root /opt/omni/lbin/inet -log /var/opt/omni/log/inet.log

      3. Run the following command so that the NIS server reads the file and updates the configuration.

        cd /var/yp; make

      Note In the NIS environment, the nsswitch.conf file defines the order in which different configuration files will be used. For example, you can define whether the /etc/inetd.conffile will be used on the local machine or from the NIS server. You can also insert a sentence in the file, stating that the nsswitch.conf file controls where the names are kept. See the man pages for detailed information.

      If you have already installed Data Protector, you must prepare the NIS server, and then restart the inet service by killing the process concerned, using the command kill -HUP pid on every NIS client that is also a Data Protector client.

    • Have the following ports free:

      • 5565 - port required for new installation in Data Protector.

      • 5555 - port required during upgrade of Data Protector installation.
      • 7112 - the Internal Database Service port

      • 7113 - the Internal Database Connection Pooler (IDB CP) port

      • 7116 - the Application Server (HTTPS AS) port

      • 9999 - the Application Server management port

    • Support long filenames. To check if your filesystem supports long filenames, execute the getconf NAME_MAX DirectoryPath command.

    • Have the Basic command line calculator (bc) installed.

    • Have the user group hpdp and the dedicated user account hpdp in this user group configured to be used by Data Protector.

    • Have the existing home folder configured for the hpdp user otherwise some of the Data Protector services could fail to start.

    • The hpdp user must have access to any directory from the following paths that already exist in the system:

      • /opt/omni/*

      • /etc/opt/omni/*

      • /var/opt/omni/*

    • It is recommended that you use large file support (LFS) on the file systems which store the Data Protector Internal Database and the DC binary files that are expected to grow larger than 2 GB.

Linux systems:

  • Have the 32-bit GNU C Library (glibc) installed on 64-bit Linux systems (x86_64).
  • Have net-tools installed (some net-tools utilities are needed during installation).

Setting kernel parameters

HP-UX systems:

  • Set the kernel parameter shmmax (maximum size of a shared memory segment) to at least 2.5 GB. To check the configuration, execute:

    kcusage shmmax

  • recommends to set the kernel parameter maxdsiz (max data segment size) or maxdsiz_64 to at least 134217728 bytes (128 MB), and the kernel parameter semmnu (number of semaphore undo structures) to at least 4000. The semmnu parameter must allow maximum number of parallel backup or restore or copy sessions (1000) and the same number of database query sessions (1000). You need not change the value of semmnu parameter, if you do not plan to execute large number of parallel sessions.

    After committing these changes, restart the system.

Linux systems:

  • Set the kernel parameter shmmax (maximum size of a shared memory segment) to at least 2.5 GB. To check the configuration, execute:

    cat /proc/sys/kernel/shmmax

    For recovery of the Internal Database, the kernel parameter should be set to twice the above value.

Cell Manager in cluster mode

Serviceguard cluster

Before you install a Data ProtectorCell Manager on Serviceguard, check the following:

  • Decide which systems are going to be the Primary Cell Manager and the Secondary Cell Manager(s). All of them must have Serviceguard installed and must be configured as cluster members. The recommendation is to set at least one Secondary node dedicated to each of Data Protector Cell Manager packages.
  • Data ProtectorCell Manager, with recommended patches, and all other Data Protector software components for the integrations you want to have in the cluster, must be installed on the Primary node and each of the Secondary nodes.
  • If your Cell Manager is to be cluster-aware, note that the virtual server IP address should be used for licenses.
  • The user group hpdp and the dedicated user account hpdp must have the same IDs on both nodes.
  • In this cluster environment, a Data Protector Cell Manager should have its own package. Before installing the Data Protector Cell Manager in Serviceguard, you need to obtain the following information from your network administrator:
    • Virtual server name (the hostname specified in the cluster package)
    • Package IP or virtual IP-address
  • Ensure that the cluster nodes and the package IP (virtual IP) are on the same subnet.
  • If you have DNS in your environment, ensure that all the nodes in the cluster and the package IP are registered with the DNS server.
  • In a multiple-cell environment (MoM), all Cell Managers must have the same Data Protector version installed.

In addition, the following prerequisites must be met for configuring the Cell Managerpackage:

  • The Data Protector Cell Manager should be installed and configured on both cluster nodes.
  • Before configuring the Data Protector cluster package, you should have a cluster configuration file created and edited.

The legacy package configuration always includes 2 files, the package configuration file and the package control script. The legacy package configuration file is created as an ASCII file, then stored in the binary Serviceguard configuration using the cmapplyconf command. The modular package configuration file contains all the package filesystem, mount point and service definitions in a single file, which is stored in the binary Serviceguard configuration using the cmapplyconf command.

Note The Data Protector daemons are not running anymore on either cluster node.


Symantec Veritas Cluster

Before you install a Data ProtectorCell Manager on Symantec Veritas cluster, the following prerequisites must be fulfilled:

  • Identify Primary and Secondary Cell Manager system(s). All of them must have the Symantec Veritas Cluster Server installed and must be configured as cluster members.

  • Data ProtectorCell Manager with recommended patches, and all other Data Protector software components for the integrations you want to have in the cluster, must be installed on the Primary node and each of the Secondary nodes.

  • The user group hpdp and the dedicated user account hpdp must have the same IDs on both nodes.

  • In this cluster environment, a Data ProtectorCell Manager must have its own cluster service group, which must be created and prepared before cluster-aware Cell Manager configuration. Before installing the Data ProtectorCell Manager in VCS, you need to obtain the virtual server name and its corresponding IP. This server name or IP is later used as the Data ProtectorCell Manager virtual server name or Data Protector service group IP.

  • Ensure that the cluster nodes and the Data Protector service group IP (virtual IP) are on the same subnet.

    Note Ensure that the Data Protector service group IP and Veritas Cluster IP are different.

  • If you have DNS in your environment, ensure that all the nodes in the cluster and the Data Protector service group IP are registered with the DNS server.

  • When the installation has been completed, you must configure the installed Primary Cell Manager and the Secondary Cell Manager(s), and the Cell Manager package.

  • To prepare Cluster Service Group for Data ProtectorCell Manager, you must create a cluster (Data Protector) service group with the following resources:
    • IP cluster resource - Refers to the virtual IP used for IP resource configuration.

    • Mount cluster resource - Refers to the mount resource with corresponding dependent resources for controlling shared volume created on a shared disk and accessible from all nodes, where Data Protector could be running. This shared volume is used for Data Protector configuration and data files shared among nodes.

Microsoft cluster server

Before you install the cluster-aware Data ProtectorCell Manager, the following prerequisites must be fulfilled:

  • Clustering functionality must be installed properly on all cluster nodes. For example, you must be able to move groups from one to another node as many times as needed, without problems with shared disks.

  • Make sure resources with the following names do not exist on the cluster:

    OBVS_MCRS, OBVS_HPDP_AS, OBVS_HPDP_IDB, OBVS_HPDP_IDB_CP and OmniBack_Share.

    Data Protector uses these names for the Data Protector virtual server. If such resources exist, delete or rename them.

    This can be done as follows:

    1. Click Start > Programs >Administrative Tools > Cluster Administrator.

    2. Check the resource list and delete or rename these resources, if necessary.

  • At least one group in the cluster should have a file cluster resource defined. Data Protector will install some of its data files in this file cluster resource under a specific folder.

    Windows Server 2008, Windows Server 2012: Data files are installed on the File Server resource under the shared folder selected by the user at installation.

    Other Windows systems: Data files are installed on the File Share resource under the folder specified when the file cluster resource was created.

    For instructions on how to define a file cluster resource, see the cluster-specific documentation. Note that the file share name of the file cluster resource cannot be OmniBack.

  • If the virtual server does not exist in the same group as the file cluster resource, create a new virtual server using a free registered IP address and associate a network name with it.

  • The file cluster resource where Data Protector is to be installed must have the IP Address, Network Name, and Physical Disk set among the file cluster resource dependencies. This ensures that the Data Protector cluster group can run on any node independently of any other group.

  • Ensure that only the cluster administrator has access to shared folder of the file cluster resource, and they should have full access to it.

  • Data Protector is installed on the same location (drive and path name) on all cluster nodes. Ensure that these locations are free.

  • If you start the cluster-aware Cell Manager installation from a network share, you must have access to this share from all cluster nodes.

  • Ensure no other Microsoft Installer-based installations are running on any cluster node.

  • Each system (node) of the cluster should be running and functioning properly.

  • Setup must be started under the cluster service account on the system (node) where the file cluster resource is active, so that shared folder of the file cluster resource can be accessed directly. The resource owner (the system where the resource is active) can be determined using Cluster Administrator.

  • To properly install and configure cluster-aware Data ProtectorCell Manager, a domain account with the following user rights must be provided during installation:

    • Administrator rights on the Cell Manager system

    • Cluster Administrator rights within the cluster

    • Password Never Expires

    • Logon as a service

    • User Cannot Change Password

    • All logon hours are allowed

    Important An account with administrator rights on all the cluster systems (nodes) is required for Microsoft Cluster Server installation. You should use this account to install Data Protector as well. Failing to do so results in Data Protector services running in the ordinary instead of the cluster-aware mode.

  • The Windows domain user account that is used for the Inet service must additionally be given the following Windows operating system Security Policy privileges on all cluster nodes:

    • Impersonate a client after authentication

    • Replace a process level token

    See the Data Protector Help index: “Inet user impersonation”.

In addition to the above prerequisites, you must prepare Microsoft cluster server running on Windows Server 2008, Windows Server 2012, and Windows Server 2016 for Data Protector installation. Failing to do so may result in failed sessions for backing up the local CONFIGURATION object, which must be backed up during preparation for disaster recovery, and potentially even in a data loss. For information for which combinations of Data Protector cell roles and Windows operating system releases cluster awareness is supported, see the latest support matrices. Ensure that you are logged on to the system with a domain user account. The domain user account must be a member of the local Administrators group.

Preparation procedure

  1. On both cluster nodes, start Windows Firewall and enable exceptions for the program File and Printer Sharing.

  2. On the active cluster node, start Failover Cluster Management, and verify that the witness disk in quorum resource is online. If the resource is offline, bring it online.

    Perform the steps that follow on the active cluster node only.

  3. If you are preparing a cluster without a Majority Node Set (MNS) configured, start Windows Explorer and change ownership of the folder WitnessDiskLetter:\Cluster to the local Administrators group. While changing the ownership in the Advanced Security Settings for Cluster window, ensure that the option Replace owner on subcontainers and objects is selected. In the Windows Security dialog box, confirm the suggested action by clicking Yes, and confirm the notification that follows by clicking Yes.

  4. If you are preparing a cluster without an MNS configured, in Windows Explorer, change permissions of the folder WitnessDiskLetter:\Cluster to allow full control for the SYSTEM and local Administrators groups.

  5. If you are preparing a cluster which will take the role of the Data Protector Cell Manager, in Failover Cluster Management, add a Cluster Access Point resource. Select Add a resource and click 1- Client Access Point to start the New Resource wizard:

    1. On the Client Access Point pane, enter the network name of the virtual server in the Name text box.

    2. Enter the IP address of the virtual server in the Address text box.


  6. If you are preparing a cluster which will take the role of the Data Protector Cell Manager, in Failover Cluster Management, add a shared folder to the cluster. Start the Provision a Shared Folder wizard by clicking Add a shared folder:

    1. On the Shared Folder Location pane, enter a directory path in the Location text box. Ensure that the chosen directory has sufficient free space to store data created during the Data Protector installation. Click Next.

    2. On the NTFS Permissions, Share Protocols, and SMB Settings panes, leave the default option values unchanged. Click Next to move to the next pane.

    3. On the SMB Permissions pane, select the option Administrators have Full Control; all other users and groups have only Read Access and Write Access. Click Next.

    4. On the DFS Namespace Publishing, leave the default option values. Click Next.

    5. On the Review Settings and Create Share pane, click Create.


Windows Installation Server in non-cluster mode

  • Have one of the supported Windows operating systems installed. For details on supported operating systems for the Installation Server, see the latest support matrices.
  • Have enough disk space for the complete Data Protector software depot. The following are the minimum requirements:
    • 512 MB of total RAM
    • 2 GB of free disk space
  • Reverse DNS lookup for host name resolution is required for all Data Protector components in the Data Protector cell.
  • TCP/UDP 445. For new Data Protector client push installation (without any Data Protector components on the client), accessible installation server share is required. Alternatively, if the Installation Server depot share cannot be accessed, initial Data Protector client installation must be done locally.
  • 5565 - the port required for new installation in Data Protector.
  • 5555 - port required during upgrade of Data Protector installation.
  • Have the Microsoft implementation of the TCP/IP protocol up and running. The protocol must be able to resolve hostnames. The computer name and the hostname must be the same.
  • Due to the security restrictions imposed by the Windows operating system, one of the following conditions must be true:
    • Both the Installation Server and the client are not in the same domain.
    • Both the Installation Server and the client are in the same domain.
  • If you do not install the Installation Server for Windows on your network, you will have to install every Windows client locally from the install package (zip).
  • You cannot remotely install a Data Protector client on the Windows system after an Installation Server has been installed on this system. To install an Installation Server and client component(s) on the same system, you must perform a local client installation. During the installation procedure, select all desired client components and the Installation Server component.

UNIX Installation Server in non-cluster mode

The system that will become your Installation Server must meet the following requirements:

  • Have the HP-UX or Linux operating system installed. For details on supported operating systems for the Installation Server, see the Data Protector Product Announcements, Software Notes, and References.

  • Have the inetd or xinetd daemon up and running.

  • Reverse DNS lookup for host name resolution is required for all Data Protector components in the Data Protector cell.

  • Have the port number 5555/5565 (default) free.

  • Have the TCP/IP protocol installed and running. The protocol must be able to resolve hostnames.

  • Have enough disk space for the complete Data Protector software depot. The following are the minimum requirements:

    • 1 GB of total RAM
    • 5 GB of available disk space, at the time of install or upgrade
  • You need either root access or an account with root privileges.

  • The Cell Manager in the Data Protector cell must be of the 10.03 version.

  • To install Data Protector to linked directories, for instance:

    • /opt/omni/ -> /prefix/opt/omni/

    • /etc/opt/omni/ -> /prefix/etc/opt/omni/

    • /var/opt/omni/ -> /prefix/var/opt/omni/

    Create the links before the installation and ensure that the destination directories exist.

  • To install software from a device across the network, first mount the source directory on your computer.

Windows clients

To install a Windows client, you must have the Administrator rights. The Windows system that will become your future Data Protector client system must meet the following requirements:

  • Have sufficient disk space for the Data Protector client software. For details, see the Data Protector Product Announcements, Software Notes, and References.
  • Have port number 5555/5565 (default) free.
  • Reverse DNS lookup for host name resolution is required for all Data Protector components in the Data Protector cell.
  • Have the Microsoft implementation of the TCP/IP protocol installed and running. The protocol must be able to resolve hostnames. The computer name and the hostname must be the same.
  • Ensure that network access user rights are set under the Windows local security policy for the account performing the installation.
  • Prior to installing Data Protector, check if Microsoft Installer (MSI) 2.0 is installed on the system. If an earlier version is installed, it is recommended to upgrade it to the version 2.0 before starting the Data Protector installation. If you do not upgrade MSI beforehand, the Data Protector Setup Wizard automatically upgrades it to the required version. In this case, Data Protector informs you appropriately about the MSI upgrade.

    If MSI is upgraded, it is highly recommended to restart the system.

HP-UX clients

  • At this point, you should have the Cell Manager and Installation Server for UNIX installed on your network.

  • You will need either root access or an account with root capabilities.

  • Reverse DNS lookup for host name resolution is required for all Data Protector components in the Data Protector cell.

  • For HP-UX 11.11, the IPv6NCF11i bundle or TOUR/IPv6 support is required to enable the Internet Protocol version 6 (IPv6).


    RAM and disk space requirements for the Data Protector client components on UNIX systems

    The following table presents the minimum RAM and disk space requirements for different Data Protector client components on UNIX systems:

    RAM and disk space requirements

    Client system component

    RAM (MB) 
    The figures indicate requirements for the components only. The figure does not include space allocation for the operating system, paging file, or other applications.

    Free disk space (MB) 
    The figures indicate requirements for the components only. The figure does not include space allocation for the operating system, paging file, or other applications.

    Disk Agent

    64 for each (recommended 128)

    20 for each

    Media Agent

    Integration components

    English Documentation (Guides, Help)

    N/A

    100

    Solaris clients

    • When installing a Media Agent, make sure that the following entry is in the file /etc/system:

      set semsys:seminfo semmni=100

    • At this point, you should have the Cell Manager and Installation Server for UNIX already installed on your network.

    • To install a Solaris client, you will need either root access or an account with root capabilities.

    • Reverse DNS lookup for host name resolution is required for all Data Protector components in the Data Protector cell.

    Linux clients

    • The 32-bit GNU C Library (glibc) package must be installed on 64-bit Linux systems (x86_64).

    • At this point, you should have the Cell Manager and Installation Server for UNIX already installed on your network.

    • The rpm utility must be installed and set up. Other packaging systems, for example, deb, are not supported.

    • To install Data Protector components on a remote system, the following prerequisites must be met on the remote system:

      • The inetd or xinetd service must be running or set up so that Data Protector is able to start it.

      • The client should have passwordless authentication or ssh configured.

    • Ensure that the kernel supports SCSI devices (modules SCSI support, SCSI tape support, SCSI generic support). The parameter Probe all LUNa on each SCSI device is optional.

      For more details on SCSI support in the Linux kernel, see the documentation of your Linux distribution or the Linux kernel documentation.

    • Reverse DNS lookup for host name resolution is required for all Data Protector components in the Data Protector cell.

    Note Data Protector uses the default port number 5555/5565. Therefore, this particular port number should not be used by another program. Some Linux operating system distributions use this number for other purposes.

    If the port number 5555/5565 is already in use, you should make it available for Data Protector or you can change the default port number to an unused port number.

    IBM AIX clients

    • For system requirements, disk space requirements, supported platforms, and Data Protector components, see the Data Protector Product Announcements, Software Notes, and References.

    • At this point, you should have the Cell Manager and Installation Server for UNIX already installed on your network.

    • Reverse DNS lookup for host name resolution is required for all Data Protector components in the Data Protector cell.

    • Before installing the Disk Agent component, check that the port mapper is up and running on the selected system. In the /etc/rc.tcpip file, there must be the line that starts the port mapper:

      start /usr/sbin/portmap “$src_running”

      The src_running flag is set to 1 if the srcmstr daemon is running. The srcmstr daemon is the System Resource Controller (SRC). The srcmstr daemon spawns and controls subsystems, handles short subsystem status requests, passes requests on to a subsystem, and handles error notifications.

    Mac OS X clients

    • You must have the Cell Manager and Installation Server for UNIX already installed on your network.
    • Reverse DNS lookup for host name resolution is required for all Data Protector components in the Data Protector cell.
    • If you increase the default block size, it is recommended to set the kernel parameter kern.sysv.shmmax (maximum size of a shared memory segment) to 32 MB.

    HP OpenVMS clients

    Before you install a Data Protector client on the OpenVMS platform, check the following:

    • Make sure the TCP/IP transport protocol is installed and running.
    • Set the TIMEZONE features of your system by executing the command SYS$MANAGER:UTC$TIME_SETUP.COM.
    • Log in to the SYSTEM account of the OpenVMS system. Note that you must have appropriate permissions.
    • Make sure that you have access to the Data Protector installation package (zip/tar) containing the HP OpenVMS client installation package.
    • Reverse DNS lookup for host name resolution is required for all Data Protector components in the Data Protector cell.

    Media agent for ADIC/GRAU library

    The following prerequisites for installation must be met before installing a Media Agent on a system:

    • The ADIC/GRAU library must be configured and running. See the documentation that comes with the ADIC/GRAU library.

    • DAS server must be up and running.

      To control the ADIC/GRAU library, the DAS software is required. Every DAS client must have DAS client software installed. Each media- and device-related action initiated by Data Protector first goes from the DAS client to the DAS server. Then, it is passed to the internal part (AMU - AML Management Unit) of the ADIC/GRAU library which controls the robotics and moves or loads media. After a completed action, the DAS server replies to the DAS client. See the documentation that comes with the ADIC/GRAU library.

    • The following information must be obtained before you install a Media Agent:

      • The hostname of the DAS Server (an application that runs on an OS/2 host).

      • The list of available drives with the corresponding DAS name of the drive. The obtained drive names are to be used when configuring the ADIC/GRAU drives in Data Protector.

        If you have defined the DAS clients for your ADIC/GRAU system, you can get this list with one of the following dasadmin commands:

        dasadmin listd2 client

        dasadmin listd client

        where client is the DAS client for which the reserved drives are to be displayed.

        The dasadmin command can be called from the C:\DAS\BIN directory on the OS/2 host, or, if installed on other systems, from the directory where the DAS client software has been installed. On a UNIX client system, this directory is usually the /usr/local/aci/bin system directory.

      • The list of available Insert/Eject Areas, with corresponding format specifications.

        You can get the list of available Insert/Eject Areas in the Graphical Configuration of AMS (AML Management Software) on an OS/2 host:

        1. Start this configuration from the menu Admin > Configuration.

        2. Open the EIF-Configuration window by double-clicking the I/O unit icon, and then click the Logical Ranges field. In the text box, the available Insert/Eject Areas are listed.

          Note One Data Protector library device can handle only one media type. It is important to remember which media type belongs to each one of the specified Insert and Eject Areas, because you will need this data later for configuring Insert/Eject Areas for the Data Protector library.

      • A list of UNIX device files for the drives, if you want to install a Media Agent on a UNIX system.

        Run the ioscan -fn system command on your system to display the required information.

      • A list of SCSI addresses for the drives, if you want to install a Media Agent on a Windows system. For example, scsi4:0:1:0.

    Media agent for StorageTek Library

    The following prerequisites for installation must be met before installing a Media Agent:

    • The StorageTek library must be configured and running. See the documentation that comes with the StorageTek library.

    • Data Protector must be installed and configured.

    • The following information must be obtained before you start installing a Media Agent software:

      • The hostname of the host where ACSLS is running.

      • A list of ACS drive IDs that you want to use with Data Protector. The obtained drive IDs are to be used when configuring the StorageTek drives in Data Protector. To display the list, log in on the host where ACSLS is running and execute the following command:

        rlogin “ACSLS hostname” -l acssa

        You will have to enter the terminal type and wait for the command prompt. At the ACSSA prompt, enter the following command:

        ACSSA&gt; query drive all

        The format specification of an ACS drive must be the following:

        ACS DRIVE: ID:#,#,#,# - (ACS num, LSM num, PANEL, DRIVE)

      • A list of available ACS CAP IDs and the ACS CAP format specification. To display the list, login on the host where ACSLS is running and execute the following command:

        rlogin “ACSLS hostname” -l acssa

        Enter the terminal type and wait for the command prompt. At the ACSSA prompt, enter the following command:

        ACSSA&gt; query cap all

        The format specification of an ACS CAP must be the following:

        ACS CAP: ID:#,#,# - (ACS num, LSM num, CAP num)

      • A list of UNIX device files for the drives, if you want to install a Media Agent on a UNIX system.

        Run the ioscan -fn system command on your system to display the required information.

      • A list of SCSI addresses for the drives, if you want to install a Media Agent on a Windows system. For example, scsi4:0:1:0.

    • Make sure that the drives that will be used for Data Protector are in the online state. If a drive is not in the online state, change the state with the following command on the ACSLS host: vary drive drive_id online

    • Make sure that the CAPs that will be used for Data Protector are in the state online and in manual operating mode.

      If a CAP is not in the online state, change the state using the following command:

      vary cap cap_id online

      If a CAP is not in manual operating mode, change the mode using the following command:

      set cap manual cap_id

    Cluster-aware clients - Microsoft cluster server

    Before you install a cluster-aware Data Protector client, the following prerequisites must be fulfilled:

    • Clustering functionality must be installed properly on all cluster nodes. For example, you must be able to move groups from one to another node as many times as needed, without problems with shared disks.
    • Each system of the cluster should be running and functioning properly.
    • To enable installation of the cluster-aware Data Protector client on a server cluster with Microsoft Cluster Service (MSCS) running on Windows Server 2008 or Windows Server 2012, perform the procedure described in Prepare a Microsoft server cluster running on Windows Server 2008 or Windows Server 2012 for Data Protector installation.

    Integration clients

    • For system requirements, disk space requirements, supported platforms, processors, and Data Protector components, see the Data Protector Product Announcements, Software Notes, and References.

    • You need a license to use the Data Protector integration with a database application (except for the VSS integration).

    • At this point, you should have the Cell Manager and Installation Server (optionally, for remote installation) already installed on your network.

    Before starting the installation procedure, decide which other Data Protector software components you want to install on your client together with an integration component.

    Note that in the cases stated below you need to install the following Data Protector components:

    • The Disk Agent component to be able to back up filesystem data with Data Protector. You can use the Disk Agent for the following purposes:
      • To run a filesystem backup of important data that cannot be backed up using a database application backup.
      • To run a filesystem test backup of a database application server (for example, Oracle Server or Microsoft SQL Server). You need to test a filesystem backup before configuring the Data Protector integration with a database application and resolve communication and other problems related to the application and Data Protector.
      • To run zero downtime backup of filesystems or disk images.
      • To restore from backup media to the application system on LAN in case of SAP R/3 ZDB integrations.
    • The User Interface component to gain access to the Data Protector GUI and the Data Protector CLI on the Data Protector integration client.
    • The General Media Agent component if you have backup devices connected to the Data Protector integration client. On Data Protector clients used to access an NDMP dedicated drive through the NDMP Server, the NDMP Media Agent is required.

    Granular Recovery Extension for Microsoft Exchange Server

    • Install the following to the chosen Microsoft Exchange Server system:
      • The Data ProtectorMS Exchange Server 2010+ Integration component
      • The Data ProtectorUser Interface component
      • All required non-Data Protector components
    • Keep the TCP/IP port 60000 (default) free on the chosen Microsoft Exchange Server system.

    Microsoft Exchange Server software

    Install the following:

    • Microsoft Exchange Server

      Make sure that you have correctly installed and configured the Microsoft Exchange Server environment.

      For supported versions, platforms, devices, and other information, see the latest support matrices.

      For information on installing, configuring, and using Microsoft Exchange Server, see the Microsoft Exchange Server documentation.

    • Microsoft Management Console (MMC) 3.0 or later

    • .NET Framework 3.5.1

    • Internet Information Services (IIS) 6.0 or later

    Data Protector software

    Install the following Data Protector components:

    • The Data ProtectorUser Interface component
    • The Data ProtectorMS Exchange Server 2010+ Integration component on all Microsoft Exchange Server systems

    Make sure that you installed and configured your Data Protector backup solution as described in the Data Protector Installation Section and in the Data Protector Integration Section.

    Other non-Data Protector software and services

    • Install Windows PowerShell 1.0 or later (a Windows Management Framework Core package)
    • Localization for PowerShell other than English is not supported (The Windows OS must use the English Localization).
    • Keep the TCP/IP port 60000 (default) free for the Granular Recovery Web service.
    • Configure a firewall to allow new ports.

    Supported Environments

    The extension can be integrated with Microsoft Exchange Server in different Microsoft Exchange Server environments:

    • a standalone Microsoft Exchange Server system (a standalone environment)
    • multiple Microsoft Exchange Mailbox Server systems (multiple Server systems)
    • Microsoft Exchange Server Database Availability Group environments (DAG environments)

    Depending on your Microsoft Exchange Server environment, install the extension as follows:

    Standalone environment

    All Microsoft Exchange Server services and data are installed on a single Microsoft Exchange Mailbox Server, which is adequate in small scale environments. Install the MS Exchange Granular Recovery Extension component to the Exchange Mailbox Server system.

    Multiple Exchange Server systems environment

    Your environment contains more than one Microsoft Exchange Server database. Install the MS Exchange Granular Recovery Extension component to the Exchange Mailbox Server system of which single items you want to recover.

    DAG environment

    Your environment can contain up to 16 Microsoft Exchange Mailbox Server systems. Install the MS Exchange Granular Recovery Extension component to any Microsoft Exchange Server mailbox role system node. Once the component is installed, the Granular Recovery Extension Graphical User Interface (GUI) displays all mailbox database objects of all the Mailbox Server nodes in the DAG environment. The extension considers the dynamic behavior of the DAG environment automatically.

    CCR environment

    Install the MS Exchange 2010 Granular Recovery Extension component on a mailbox server node.

    LCR environment

    Install the MS Exchange 2010 Granular Recovery Extension component on the server where the active and passive mailbox databases are located.

    For detailed information on Microsoft Exchange Server concepts, see the Microsoft Exchange Server documentation.

    Granular Recovery Extension (GRE) for Microsoft SharePoint Server

    • Microsoft packages:

      Install the following Windows Management Framework Core package:

      • Microsoft PowerShell 2.0 or higher

      • Microsoft SQL Server packages:

        Install the following packages for Microsoft SQL Server 2008:

        • Microsoft SQL Server Native Client

        • Microsoft Core XML Services (MSXML) 6.0

        • Microsoft SQL Server 2008 Management Objects Collection

        Install the following packages for Microsoft SQL Server 2012:

        • Microsoft SQL Server Native Client

        • Microsoft Core XML Services (MSXML) 6.0 or higher

        • Microsoft SQL Server 2012 Management Objects Collection

        Install the following packages for Microsoft SQL Server 2014:

        • Microsoft SQL Server Native Client
        • Microsoft Core XML Services (MSXML) 6.0 or higher
        • Microsoft SQL Server 2014 Management Objects Collection

        Install the following packages for Microsoft SQL Server 2016:

        • Microsoft SQL Server Native Client
        • Microsoft Core XML Services (MSXML) 6.0 or higher
        • Microsoft SQL Server 2016 Management Objects Collection

        These packages must be installed on all the Microsoft SharePoint Server systems that have at least one of the following services enabled:

        • Central Administration

        • Microsoft SharePoint Foundation Web application (Microsoft SharePoint Server 2010/2013)

        Note You must have only one version of Microsoft SQL Server Management Objects Collection installed on each of the SharePoint Server systems. The version number for this Microsoft SQL Server Management Objects Collection must be same as the SQL Server version number that is used with SharePoint farm.

        If there are multiple versions of Microsoft SQL Server Management Objects Collection installed on the system, remove all versions, except for the version that is same as the SQL Server version.

        You can download the packages from the website: http://www.microsoft.com/downloads/en/default.aspx.

        Search for Feature Pack for Microsoft SQL Server 2008 or Feature Pack for Microsoft SQL Server 2012 or Feature Pack for Microsoft SQL Server 2014 or Feature Pack for Microsoft SQL Server 2016.

    • Data Protector components:

      Ensure you installed and configured your Data Protectorbackup solution as described in:

      • Data Protector Installation Section

      • applicable chapters of the Data Protector Integration Section

      • Data Protector Zero Downtime Backup Integration Section

      • Data Protector Integration Section for Microsoft Volume Shadow Copy Service

      In addition, ensure that the Data ProtectorUser Interface component is installed on all Microsoft SharePoint Server systems that have at least one of the following services enabled:

      • Central Administration

      • Microsoft SharePoint Foundation Web application (Microsoft SharePoint Server 2010/2013)

    SAP R/3 clients

    • Ensure that the following Oracle software is installed and configured:
      • Oracle Enterprise Server (RDBMS)
      • Oracle Net8 software
      • SQL*Plus
    • It is assumed that your SAP R/3 Database Server is up and running.

    The Data Protector SAP R/3 integration backup specifications are fully compatible with the previous version of Data Protector. Data Protector will run all backup specifications created by earlier Data Protector versions. You cannot use backup specifications created by the current version of Data Protector on older versions of Data Protector.

    GRE for VMware vSphere Web Client

    • The virtual machines on which you plan to perform recovery operations must have VMware tools 4.x or later installed. You can download the VMware Tools installation package from the webpage http://www.vmware.com/download.
    • Only remote installation of the Data Protector Granular Recovery Extension web client for VMware vSphere is supported.
    • To ensure the proper functionality of the extension, do not install and configure both, a VMware vCenter Server system and a mount proxy system on the same client system.
    • Ensure that the VMware Granular Recovery Extension Agent, the Virtual Environment Integration Agent and the Data ProtectorCell Manager are of the same version. Mixed agent versions are not supported.
    • To use the extension, you need to install and configure the following systems:
      • Data Protector cell and client
      • VMware vCenter Server system
      • Mount proxy system

    The GRE plug-in is accessible through the Advanced GRE Web Plug-in user interface.

    P6000 EVA Disk Array Family integration with Oracle Server

    • The following software must be installed and configured on the application system and on the backup system for the backup set ZDB method:

      • Oracle Enterprise Server (RDBMS)

      • Oracle Net services

      • SQL*Plus

      The Oracle software on the backup system must be installed in the same directory as on the application system. The binaries should be identical to the binaries on the application system. You can achieve this either by copying the files and system environment from the application system to the backup system, or by a clean installation of the Oracle binaries on the backup system with the same installation parameters as on the application system.

    • The Oracle datafiles on the application system must be installed on source volumes that will be replicated using the SMI-S agent you have installed.

      Depending on the location of the Oracle control file, online redo log files, and Oracle SPFILE, the following two options are possible:

      • Oracle control file, online redo log files, and Oracle SPFILE reside on a different volume group (if LVM is used) or source volume than Oracle datafiles.

        By default, instant recovery is enabled for such configuration.

      • Oracle control file, online redo log files, and Oracle SPFILE reside on the same volume group (if LVM is used) or source volume as Oracle datafiles.

        By default, instant recovery is not enabled for such configuration. You can enable instant recovery by setting the ZDB_ORA_INCLUDE_CF_OLF, ZDB_ORA_INCLUDE_SPF, and ZDB_ORA_NO_CHECKCONF_IR omnirc options. For more information, see the Data Protector Zero Downtime Backup Integration Section.

      The Oracle archive redo log files do not have to reside on source volumes.

      If some Oracle data files are installed on symbolic links, then these links have to be created on the backup system too.

    P6000 EVA Disk Array Family integration with SAP R/3

    • The following Oracle software must be installed on the application system.

      • Oracle Enterprise Server (RDBMS)

      • Oracle Net services

      • SQL*Plus

    • If you plan to run SAP compliant ZDB sessions (BRBACKUP started on the backup system and not on the application system), configure the backup system. For details, see the SAP database section for Oracle (split mirror backup, software configuration).

    • The database on the application system can be installed on disk images, logical volumes, or filesystems.

      • The Oracle datafiles must reside on a disk array.

      • For online backup, the control file and online redo logs do not have to reside on a disk array. Online SAP compliant ZDB sessions are an exception, for which the control file must reside on a disk array.

      • For offline backup, the control file and online redo logs must reside on a disk array.

      • Archived redo log files do not have to reside on a disk array.

      If the Oracle control file, online redo logs, and Oracle SPFILE reside on the same LVM volume group or source volume as Oracle datafiles, set the Data ProtectorZDB_ORA_NO_CHECKCONF_IR, ZDB_ORA_INCLUDE_CF_OLF, and ZDB_ORA_INCLUDE_SPFomnirc options. Otherwise, you cannot run ZDB–to–disk and ZDB–to–disk+tape sessions. For details, see the Data Protector Zero Downtime Backup Integration Section.

      Note If some of the Oracle data files are installed on symbolic links, create the links on the backup system too.

      UNIX systems: If the Oracle database is installed on raw partitions (rawdisk or raw logical volumes), ensure that the volume/disk group names on the application system and backup system are identical.

    • On UNIX systems, ensure that the following users exist on the application system:

      • oraORACLE_SID with the primary group dba

      • ORACLE_SID adm in the UNIX group sapsys

    • The SAP R/3 software must be correctly installed on the application system.

      The following is a list of standard directories that must be installed on the application system after installing SAP R/3:

      Note The location of the directories is dependent on the environment (UNIX systems) or registry (Windows system) variables. For more information, see the SAP R/3 documentation.

      • ORACLE_HOME /dbs (UNIX systems) ORACLE_HOME\database (Windows systems) - the Oracle and SAP profiles

      • ORACLE_HOME /bin (UNIX systems) ORACLE_HOME\bin (Windows systems) - the Oracle binaries

      • SAPDATA_HOME /sapbackup (UNIX systems) SAPDATA_HOME\sapbackup (Windows systems) - the SAPBACKUP directory with BRBACKUP log files

      • SAPDATA_HOME /saparch (UNIX systems) SAPDATA_HOME\saparch (Windows systems) - the SAPARCH directory with BRARCHIVE log files

      • SAPDATA_HOME /sapreorg (UNIX systems) SAPDATA_HOME\sapreorg (Windows systems)

      • SAPDATA_HOME /sapcheck (UNIX systems) SAPDATA_HOME\sapcheck (Windows systems)

      • SAPDATA_HOME /saptrace (UNIX systems) SAPDATA_HOME\saptrace (Windows systems)

      • /usr/sap/ORACLE_SID/SYS/exe/run (UNIX systems)

        c:\Oracle\ORACLE_SID\sys\exe\run (Windows systems)

        Note If you plan to do instant recovery, ensure that the sapbackup, saparch, and sapreorg directories reside on different source volumes than the Oracle data files.

      UNIX systems

      On UNIX systems, if the last six directories do not reside at the above specified destinations, create appropriate links to them.

      On UNIX systems, the directory /usr/sap/ORACLE_SID/SYS/exe/run must be owned by the UNIX user oraORACLE_SID. The owner of the SAP R/3 files must be the UNIX user oraORACLE_SID and the UNIX group dba with setuid bit set (chmod 4755 ...). The exception is the file BRRESTORE, which must be owned by the UNIX user ORACLE_SIDadm.

      UNIX example

      If ORACLE_SID is PRO, then the permissions inside the directory /usr/sap/PRO/SYS/exe/run should look like:

      -rwsr-xr-x   1 orapro dba 4598276 Apr 17  2011 brarchive 
      -rwsr-xr-x   1 orapro dba 4750020 Apr 17  2011 brbackup 
      -rwsr-xr-x   1 orapro dba 4286707 Apr 17  2011 brconnect 
      -rwsr-xr-x   1 proadm sapsys 430467 Apr 17  2011
      brrestore 
      -rwsr-xr-x   1 orapro dba 188629 Apr 17  2011 brtools

    P6000 EVA Disk Array Family integration with Microsoft Exchange Server

    The Microsoft Exchange Server database must be installed on the application system source volumes. The following objects must be located on the source volumes:

    • Microsoft Information Store (MIS)
    • optionally, Key Management Service (KMS)
    • optionally, Site Replication Service (SRS)

    To be able to back up transaction logs, disable Circular Logging on the Microsoft Exchange Server.

    P9000 XP Disk Array Family integration with Microsoft SQL Server

    Microsoft SQL Server has to be installed on the application system. User databases must reside on the disk array source volumes, while system databases can be installed anywhere. However, if the system databases are also installed on the disk array, they must be installed on different source volumes than user databases.

    P9000 XP Disk Array Family integration with Oracle Server

    • The following software must be installed and configured on the application system and on the backup system for the backup set ZDB method:

      • Oracle Enterprise Server (RDBMS)

      • Oracle Net services

      • SQL*Plus

      The Oracle software on the backup system must be installed in the same directory as on the application system. The binaries should be identical to the binaries on the application system. You can achieve this either by copying the files and system environment from the application system to the backup system, or by a clean installation of the Oracle binaries on the backup system with the same installation parameters as on the application system.

    • The Oracle data files on the application system must be installed on P9000 XP Disk Array Family LDEVs that are mirrored to the backup system.

      In case of the backup set method, if some Oracle data files are installed on symbolic links, then these links have to be created on the backup system too.

      Depending on the location of the Oracle control file, online redo log files, and Oracle SPFILE, the following two options are possible:

      • Oracle control file, online redo log files, and Oracle SPFILE reside on a different volume group (if LVM is used) or source volume than Oracle datafiles.

        By default, instant recovery is enabled for such configuration.

      • Oracle control file, online redo log files, and Oracle SPFILE reside on the same volume group (if LVM is used) or source volume as Oracle datafiles.

        By default, instant recovery is not enabled for such configuration. You can enable instant recovery by setting the ZDB_ORA_INCLUDE_CF_OLF, ZDB_ORA_INCLUDE_SPF, and ZDB_ORA_NO_CHECKCONF_IR omnirc options. For more information, see the Data Protector Zero Downtime Backup Integration Section.

      The Oracle archive redo log files do not have to reside on source volumes.

    P9000 XP Disk Array Family integration with SAP R/3

    • The following Oracle software must be installed and configured on the application system:

      • Oracle Enterprise Server (RDBMS)

      • Oracle Net services

      • SQL*Plus

    • If you plan to run SAP compliant ZDB sessions (BRBACKUP started on the backup system and not on the application system), configure the backup system. For details, see the SAP database section for Oracle (split mirror backup, software configuration).

    • The database on the application system can be installed on disk images, logical volumes, or filesystems.

      • The Oracle datafiles must reside on a disk array.

      • For online backup, the control file and online redo logs do not have to reside on a disk array. Online SAP compliant ZDB sessions are an exception, for which the control file must reside on a disk array.

      • For offline backup, the control file and online redo logs must reside on a disk array.

      • Archived redo log files do not have to reside on a disk array.

      If the Oracle control file, online redo logs, and Oracle SPFILE reside on the same LVM volume group or source volume as Oracle datafiles, set the Data ProtectorZDB_ORA_NO_CHECKCONF_IR, ZDB_ORA_INCLUDE_CF_OLF, and ZDB_ORA_INCLUDE_SPFomnirc options. Otherwise, you cannot run ZDB–to–disk and ZDB–to–disk+tape sessions. For details, see the Data Protector Zero Downtime Backup Integration Section.

      Note If some of the Oracle data files are installed on symbolic links, create the links on the backup system too.

      UNIX systems: If the Oracle database is installed on raw partitions (rawdisk or raw logical volumes), ensure that the volume/disk group names on the application system and backup system are identical.

    • On UNIX systems, ensure that the following users exist on the application system:

      • oraORACLE_SID with the primary group dba

      • ORACLE_SID adm in the UNIX group sapsys

    • The SAP R/3 software must be correctly installed on the application system.

      The following is a list of standard directories that must be installed on the application system after installing SAP R/3:

      Note The location of the directories is dependent on the environment (UNIX systems) or registry (Windows system) variables. For more information, see the SAP R/3 documentation.

      • ORACLE_HOME /dbs (UNIX systems)

        ORACLE_HOME \database (Windows systems) - the Oracle and SAP R/3 profiles)

      • ORACLE_HOME /bin or (UNIX systems)

        ORACLE_HOME \bin (Windows systems) - the Oracle binaries

      • SAPDATA_HOME /sapbackup (UNIX systems)

        SAPDATA_HOME \sapbackup (Windows systems) - the

        SAPBACKUP directory with BRBACKUP log files

      • SAPDATA_HOME /saparch (UNIX systems)

        SAPDATA_HOME \saparch (Windows systems) - the SAPARCH

        directory with BRARCHIVE log files

      • SAPDATA_HOME /sapreorg (UNIX systems)

        SAPDATA_HOME \sapreorg (Windows systems)

      • SAPDATA_HOME /sapcheck (UNIX systems)

        SAPDATA_HOME \sapcheck (Windows systems)

      • SAPDATA_HOME /saptrace (UNIX systems)

        SAPDATA_HOME \saptrace (Windows systems)

      • /usr/sap/ORACLE_SID/SYS/exe/run (UNIX systems)

        c:\Oracle\ORACLE_SID\sys\exe\run (Windows systems)

        Note If you plan to do instant recovery, ensure that the sapbackup, saparch, and sapreorg directories reside on different source volumes than the Oracle data files.

      UNIX systems

      On UNIX systems, if the last six directories do not reside at the above specified destinations, create appropriate links to them.

      On UNIX systems, the directory /usr/sap/ORACLE_SID/SYS/exe/run must be owned by the UNIX user oraORACLE_SID. The owner of the SAP R/3 files must be the UNIX user oraORACLE_SID and the UNIX group dba with setuid bit set (chmod 4755 ...). The exception is the file BRRESTORE, which must be owned by the UNIX user ORACLE_SIDadm.

      UNIX example

      If ORACLE_SID is PRO, then the permissions inside the directory /usr/sap/PRO/SYS/exe/run should look like:

      -rwsr-xr-x   1 orapro dba 4598276 Apr 17  2011 brarchive 
      -rwsr-xr-x   1 orapro dba 4750020 Apr 17  2011 brbackup 
      -rwsr-xr-x   1 orapro dba 4286707 Apr 17  2011 brconnect 
      -rwsr-xr-x   1 proadm sapsys 430467 Apr 17  2011
      brrestore 
      -rwsr-xr-x   1 orapro dba 188629 Apr 17  2011 brtools

    P9000 XP Disk Array Family integration with Microsoft Exchange Server

    The Microsoft Exchange Server database must be installed on the application system on the P9000 XP Disk Array Family volumes (LDEVs), which are mirrored to the backup system. The mirroring can be BC P9000 XP or CA P9000 XP and the database installed on a filesystem. The following objects must be located on volumes that are mirrored:

    • Microsoft Information Store (MIS)
    • optionally, Key Management Service (KMS)
    • optionally, Site Replication Service (SRS)

    To be able to back up transaction logs, disable Circular Logging on the Microsoft Exchange Server.

    P9000 XP Disk Array Family integration with Microsoft SQL Server

    Microsoft SQL Server has to be installed on the application system. User databases must reside on the disk array source volumes, while system databases can be installed anywhere. However, if the system databases are also installed on the disk array, they must be installed on different source volumes than user databases.

    EMC Symmetrix integration with Oracle

    • The following software must be installed and configured on the application system:

      • Oracle Enterprise Server (RDBMS)

      • Oracle Net services

      • SQL*Plus

    • The Oracle database files used by the application system must be installed on EMC Symmetrix devices which are mirrored to the backup system.

      The database can be installed on disk images, logical volumes or filesystems. The following Oracle files have to be mirrored:

      • Datafiles

      • Control file

      • Online redo log files

      The archive redo log files have to reside on non-mirrored disks.

    EMC Symmetrix integration with SAP R/3

    • The following Oracle software must be installed and configured on the application system:

      • Oracle Enterprise Server (RDBMS)

      • Oracle Net8 software

      • SQL*Plus

    • If you plan to run SAP compliant ZDB sessions (BRBACKUP started on the backup system and not on the application system), configure the backup system. For details, see the SAP database section for Oracle (split mirror backup, software configuration).

    • The database on the application system can be installed on disk images, logical volumes, or filesystems.

      • The Oracle datafiles must reside on a disk array.

      • For online backup, the control file and online redo logs do not have to reside on a disk array. Online SAP compliant ZDB sessions are an exception, for which the control file must reside on a disk array.

      • For offline backup, the control file and online redo logs must reside on a disk array.

      • The archived redo log files do not have to reside on a disk array.

      Note If some of the Oracle data files are installed on symbolic links, create the links on the backup system too.

      UNIX systems: If the Oracle database is installed on raw partitions (rawdisk or raw logical volumes), ensure that the volume/disk group names on the application system and backup system are identical.

    • On UNIX systems, ensure that the following users exist on the application system:

      • oraORACLE_SID with the primary group dba

      • ORACLE_SID adm in the UNIX group sapsys

    • The SAP R/3 software must be correctly installed on the application system.

      The following is a list of standard directories that must be installed on the application system after installing SAP R/3:

      Note The location of the directories depends on the environment variables. For more information, see the SAP R/3 documentation.

      • ORACLE_HOME /dbs - the Oracle and SAP R/3 profiles

      • ORACLE_HOME /bin - the Oracle binaries

      • SAPDATA_HOME /sapbackup - the SAPBACKUP directory with BRBACKUP log files

      • SAPDATA_HOME /saparch - the SAPARCH directory with BRARCHIVE log files

      • SAPDATA_HOME /sapreorg

      • SAPDATA_HOME /sapcheck

      • SAPDATA_HOME /saptrace

      • /usr/sap/ORACLE_SID/SYS/exe/run

        Note If you plan to do instant recovery, ensure that the sapbackup, saparch, and sapreorg directories reside on different source volumes than the Oracle data files.

      If the last six directories do not reside at the above specified destinations, create appropriate links to them.

      The directory /usr/sap/ORACLE_SID/SYS/exe/run must be owned by the UNIX user oraORACLE_SID. The owner of the SAP R/3 files must be the UNIX user oraORACLE_SID and the UNIX group dba with setuid bit set (chmod 4755 ...). The exception is the file BRRESTORE, which must be owned by the UNIX user ORACLE_SIDadm.

      Example

      If ORACLE_SID is PRO, then the permissions inside the directory /usr/sap/PRO/SYS/exe/run should look like:

      -rwsr-xr-x   1 orapro dba 4598276 Apr 17  2011 brarchive
      -rwsr-xr-x   1 orapro dba 4750020 Apr 17  2011 brbackup
      -rwsr-xr-x   1 orapro dba 4286707 Apr 17  2011 brconnect
      -rwsr-xr-x   1 proadm sapsys 430467 Apr 17  2011 brrestore
      -rwsr-xr-x   1 orapro dba 188629 Apr 17  2011 brtools

    EMC Symmetrix integration with Microsoft SQL Server

    Microsoft SQL Server has to be installed on the application system. User databases must reside on the disk array source volumes, while system databases can be installed anywhere. However, if the system databases are also installed on the disk array, they must be installed on different source volumes than user databases.

    Non– Storage Array integration with Oracle Server

    • The following software must be installed and configured on the application system and on the backup system for the backup set ZDB method:

      • Oracle Enterprise Server (RDBMS)

      • Oracle Net services

      • SQL*Plus

      The Oracle software on the backup system must be installed in the same directory as on the application system. The binaries should be identical to the binaries on the application system. You can achieve this either by copying the files and system environment from the application system to the backup system, or by a clean installation of the Oracle binaries on the backup system with the same installation parameters as on the application system.

    • The Oracle datafiles on the application system must be installed on the source volumes that will be replicated using the Storage Provider (through the SMI-S agent) you have installed.

      Depending on the location of the Oracle control file, online redo log files, and Oracle SPFILE, the following two options are possible:

      • Oracle control file, online redo log files, and Oracle SPFILE reside on a different volume group (if LVM is used) or source volume than Oracle datafiles.

      • Oracle control file, online redo log files, and Oracle SPFILE reside on the same volume group (if LVM is used) or source volume as Oracle datafiles.

      The Oracle archive redo log files do not have to reside on source volumes.

      If some Oracle data files are installed on symbolic links, then these links have to be created on the backup system too.

    Non– Storage Array integration with SAP R/3

    • The following Oracle software must be installed on the application system.

      • Oracle Enterprise Server (RDBMS)

      • Oracle Net services

      • SQL*Plus

    • If you plan to run SAP compliant ZDB sessions (BRBACKUP started on the backup system and not on the application system), configure the backup system. For details, see the SAP database section for Oracle (split mirror backup, software configuration).

    • The database on the application system can be installed on disk images, logical volumes, or filesystems.

      • The Oracle datafiles must reside on a storage system.

      • For online backup, the control file and online redo logs do not have to reside on a storage system. Online SAP compliant ZDB sessions are an exception, for which the control file must reside on a storage system.

      • For offline backup, the control file and online redo logs must reside on a storage system.

      • Archived redo log files do not have to reside on a storage system.

      Note If some of the Oracle data files are installed on symbolic links, create the links on the backup system too.

      UNIX systems: If the Oracle database is installed on raw partitions (rawdisk or raw logical volumes), ensure that the volume/disk group names on the application system and backup system are identical.

    • On UNIX systems, ensure that the following users exist on the application system:

      • oraORACLE_SID with the primary group dba

      • ORACLE_SID adm in the UNIX group sapsys

    • The SAP R/3 software must be correctly installed on the application system.

      The following is a list of standard directories that must be installed on the application system after installing SAP R/3:

      Note The location of the directories is dependent on the environment (UNIX systems) or registry (Windows system) variables. For more information, see the SAP R/3 documentation.

      • ORACLE_HOME /dbs (UNIX systems) ORACLE_HOME\database (Windows systems) - the Oracle and SAP profiles

      • ORACLE_HOME /bin (UNIX systems) ORACLE_HOME\bin (Windows systems) - the Oracle binaries

      • SAPDATA_HOME /sapbackup (UNIX systems) SAPDATA_HOME\sapbackup (Windows systems) - the SAPBACKUP directory with BRBACKUP log files

      • SAPDATA_HOME /saparch (UNIX systems) SAPDATA_HOME\saparch (Windows systems) - the SAPARCH directory with BRARCHIVE log files

      • SAPDATA_HOME /sapreorg (UNIX systems) SAPDATA_HOME\sapreorg (Windows systems)

      • SAPDATA_HOME /sapcheck (UNIX systems) SAPDATA_HOME\sapcheck (Windows systems)

      • SAPDATA_HOME /saptrace (UNIX systems) SAPDATA_HOME\saptrace (Windows systems)

      • /usr/sap/ORACLE_SID/SYS/exe/run (UNIX systems)

        c:\Oracle\ORACLE_SID\sys\exe\run (Windows systems)

      UNIX systems

      On UNIX systems, if the last six directories do not reside at the above specified destinations, create appropriate links to them.

      On UNIX systems, the directory /usr/sap/ORACLE_SID/SYS/exe/run must be owned by the UNIX user oraORACLE_SID. The owner of the SAP R/3 files must be the UNIX user oraORACLE_SID and the UNIX group dba with setuid bit set (chmod 4755 ...). The exception is the file BRRESTORE, which must be owned by the UNIX user ORACLE_SIDadm.

      UNIX example

      If ORACLE_SID is PRO, then the permissions inside the directory /usr/sap/PRO/SYS/exe/run should look like:

      -rwsr-xr-x   1 orapro dba 4598276 Apr 17  2011 brarchive 
      -rwsr-xr-x   1 orapro dba 4750020 Apr 17  2011 brbackup 
      -rwsr-xr-x   1 orapro dba 4286707 Apr 17  2011 brconnect 
      -rwsr-xr-x   1 proadm sapsys 430467 Apr 17  2011
      brrestore 
      -rwsr-xr-x   1 orapro dba 188629 Apr 17  2011 brtools

    Non– Storage Array integration with Microsoft SQL Server

    Microsoft SQL Server has to be installed on the application system. User databases must reside on the disk array source volumes, while system databases can be installed anywhere. However, if the system databases are also installed on the disk array, they must be installed on different source volumes than user databases.