IBM Tivoli Storage FlashCopy Manager 4.1.x for UNIX

Transcription

1 IBM Tivoli Storage FlashCopy Manager 4.1.x for UNIX Objective of this document This document provides comprehensive information about the environment required to support FlashCopy Manager solutions, including: How to prepare for implementation: Complete this checklist before installing the software to avoid issues. Identify stakeholders required for successful implementation. Identify supported release levels of ancillary software. Get the most current tips and hints for installation. Note: This document refers to the following storage systems: IBM System Storage DS8000, IBM System Storage SAN Volume Controller (SVC), IBM Storwize V7000, IBM Flex System v7000, IBM FlashSystem, IBM XIV Storage System, IBM Spectrum Accelerate, IBM N Series, and NetApp, and also for filesystem snapshots with the IBM General Parallel File System TM (GPFS TM ) in the context of DB2 purescale environments. Note: In AIX and Linux environments, some checks are covered by the IBM FlashCopy Manager Checker v For such checks, you find a grey check mark () in the corresponding check column, and a reference to the corresponding property name as it appears in the output of the prerequisite checker is listed, denoted by a double arrow (). On AIX and Linux environments, all checks that are not marked with a grey check mark () must be performed manually. Run the IBM FlashCopy Manager Checker on AIX and Linux in order to perform checks automatically. If the result of the prerequisite checker is pass the checks with a grey check mark were performed automatically and successfully. Otherwise, they must be performed manually. On Solaris and HP-UX environments, all checks must be performed manually. Copyright IBM Corp. 2001,

2 Table of Contents IBM Tivoli Storage FlashCopy Manager 4.1.x for UNIX 1 1. Hardware Requirements General Hardware Requirements Hardware Requirements for DS Hardware Requirements for SVC / Storwize Hardware Requirements for XIV Hardware Requirements for N Series/NetApp Software Requirements Software Requirements Operating System 11 AIX 11 Linux 13 Solaris 14 HP-UX Software Requirements - Storage Subsystems 16 XIV Other Software Requirements Requirements for DB Software requirements Environmental requirements Volume group layout requirements DB2 purescale: GPFS File system layout requirements NFS File system layout requirements Requirements for SAP on Oracle Software requirements Environmental requirements Volume group layout requirements NFS File system requirements Requirements for Oracle (non-sap) Software requirements Environmental requirements Volume group layout requirements Disk Group layout requirements (Oracle ASM) NFS File system layout requirements Requirements for Custom Applications Software requirements Environmental requirements Volume group layout requirements NFS File system layout requirements GPFS File system layout requirements Requirements for FlashCopy Cloning Environmental requirements (DB2) Environmental requirements (Oracle SAP and non-sap) Volume group layout requirements for SAP on Oracle Volume group layout requirements for Oracle (non-sap) Disk Group layout requirements for Oracle ASM DB2 purescale Pre- and Post-Processing Scripts Requirements Environmental Requirements AIX LVM Mirroring Requirements 41 Copyright IBM Corp. 2001,

3 1. Hardware Requirements 1.1 General Hardware Requirements For the use of FlashCopy Manager (hereafter FCM) backup, offloaded tape backup and cloning operations, different sets of systems are required: For FlashCopy disk-only backup / restore: one or more UNIX or Linux production system(s) (hereafter ) each must have a data path to the storage system (DS/SVC/XIV/ IBM N Series/NetApp) via FC or iscsi for SAN or LAN for NAS type storage For FlashCopy backup / restore with offloading to tape: one or more UNIX or Linux production systems () one or more UNIX or Linux auxiliary system(s) for forced mount and offload (hereafter BS) the OS release level on and BS must be the same all of these /BS must have a data path to the same storage system (via FC or iscsi for SAN, or LAN for NAS type storage) For FlashCopy cloning: one or more production system(s) () one or more auxiliary system(s) for cloning (hereafter CS) BS and CS can be running on a single machine or on separate, dedicated machines. the OS release level on and CS must be the same all of these /CS must have a data path to the same storage system (via FC or iscsi for SAN, or LAN for NAS type storage) Copyright IBM Corp. 2001,

4 Note 1: Offloaded backup and cloning operations can run on the same auxiliary system or on separate, dedicated auxiliary systems. Note 2: In an HA environment that uses AIX PowerHA or HACMP, the FCM auxiliary system cannot act as the standby/takeover server for the production server. For HP-UX, Linux, and Solaris, HA cluster environments are not supported. For filesystem snapshots of a DB2 purescale database: one or more UNIX servers of the same operating system (AIX, xlinux) For filesystem snapshots of a DB2 purescale database with offloading to tape: one or more UNIX servers of the same operating system (AIX, xlinux) one or more servers are for, one or more servers act as auxiliary server (BS) Note: For DB2 purescale environments, the term "server" refers to a GPFS cluster as part of a DB2 purescale instance which consists of one or more servers. In DB2 purescale environments GPFS file system snapshots are taken. These are independent of the underlying storage subsystem For the following tasks, a LAN connection is required between and the storage management server (like TSM): tape restore operations backups and restores of the log files For tape backup operations on the BS/CS a LAN connection to the storage management server is required as well unless and BS/CS are installed on the same system. For FlashCopy disk-only backup / restore: LAN connection between and the storage system Note: Under some conditions an auxiliary system (BS) is mandatory even for disk-only backups. For more information, see the Installation and User's Guide. In chapter 2, the section Preparing backup and cloning servers provides details. If a BS is mandatory it requires: LAN connection between and BS LAN connection between BS and the storage system *see Note 2 For FlashCopy backup / restore with offloading to tape: LAN connection between and the storage system LAN connection between BS and the storage system *see Note 2 below LAN connection between and BS LAN connection between the BS and the storage management server for offloaded (tape) backups Copyright IBM Corp. 2001,

5 For FlashCopy cloning: LAN connection between and the storage system LAN connection between CS and the storage system *see Note 2 below LAN connection between and CS Note 1: The has a LAN connection to the CIM Agent for DS, SVC cluster, IBM Storwize V7000, XIV or IBM N Series or NetApp. Note 2: (XIV) The BS/CS also has a LAN connection to the XIV management port to allow FlashCopy Manager to issue XCLI commands. (SVC or IBM Storwize V7000 with dynamic host assignment) The BS/CS also have a LAN connection to the SVC cluster or IBM Storwize V7000. Note 3: For simplified installation and configuration of FlashCopy Manager a LAN connection between production and backup/cloning servers is recommended. Note 4: In DB2 purescale environments, maximum performance for tape backup operations can be achieved by either using a high-speed interconnect between production and backup cluster or by using a SAN connection between backup cluster and the GPFS disks itself. For details on GPFS remote mount functionality see GPFS Advanced Administration Guide, Chapter 1 LUNs of the production database must not be distributed over multiple disk storage subsystems / SVC storage clusters. In some environments multiple storage systems must be configured: AIX LVM mirroring environments: Each mirror set of the production database must be located completely on a single storage cluster of the storage system (DS / SVC / XIV / IBM N series / NetApp) Oracle ASM support: All failure groups representing a consistent database image must be located on a single disk storage subsystem DS / SVC storage cluster / XIV / IBM N series / NetApp For DS just one LUN per disk storage subsystem is supported (Linux) For DS only one target set is allowed to be used (Linux) For SVC the setting PREASSIGNED_VOLUMES is not supported for the profile parameter BACKUP_HOST_NAME in the device class section of the profile fcm.same_storage_device, fcm.warn_same_storage The LUNs of the storage system for the production application must be attached/accessible to the and must be visible to FCM. They are used as the source volumes for the FlashCopy / snapshot process. Note: For performance reasons, keep the number of LUNs allocated to one application low. Copyright IBM Corp. 2001,

6 For performing FCM FlashCopy operations, so called target volumes / target LUNs must be created / available. For the different scenarios, consider the following: For FlashCopy disk-only backup / restore: The target volumes must exist but must not be mapped to any host on the storage system. For FlashCopy backup / restore with offloading to tape: The target volumes must be accessible to the BS For FlashCopy cloning: The target volumes must be accessible to the CS. Note: Accessible in this context means the correct zoning/lun masking (SAN) / network configuration (NAS) is configured to ensure the target volumes can be mapped to BS/CS. (DS/SVC/V7000) Note: This applies to DS storage system and also to SVC and IBM Storwize V7000 if preassigned volumes are used. It is recommended to use dynamic target volume mapping instead. (XIV/N Series/NetApp) Note: For XIV, IBM N Series or NetApp the target LUNs are created automatically during snapshot process and are assigned to the BS/CS. See documentation of profile parameter BACKUP_HOST_NAME in the Installation and User's Guide for more details. The sizes of the target volumes must be the same as the source volumes (DS) DS requires source and target volume pairs be located on the same storage system. (SVC/V7000) For SVC and IBM Storwize V7000 those can be located in different storage devices of one and the same SVC cluster FCM operations in VMware Virtual Machines Tivoli Storage FlashCopy Manager can back up, restore, and perform clone operations on VMware virtual machines that run Linux guest operating systems. All source LUNs that participate in backup or clone operations must be attached to the virtual machine by using one of the following attachment methods: VMware physical mode raw device mapping (prdm) iscsi Network File System (NFS) Tivoli Storage FlashCopy Manager can perform a FlashCopy restore operation from a snapshot to an existing prdm disk but does not create a virtual machine or prdm definition as part of the restore process. If the backup or clone system is a virtual machine then all target LUNs that Copyright IBM Corp. 2001,

7 participate in backup or clone operations must be attached to the virtual machine by using one of the following attachment methods: iscsi Network file system (NFS) FCM operations in Linux KVM Virtual Machines Tivoli Storage FlashCopy Manager can back up, restore, and perform clone operations on Linux KVM virtual machines that run Linux guest operating systems. All source LUNs that participate in backup or clone operations must be attached to the virtual machine by using one of the following attachment methods: Block device mapping (BDM) iscsi Network File System (NFS) PCI Passthrough For the Tivoli Storage FlashCopy Manager KVM setup using Block Device Mapping (BDM), the LUNs must be mapped to the KVM guest as multipath devices. The LUNs must be visible inside the KVM guest as multipath devices From within the KVM guest, run the multipath command. The output from running this command looks similar to the following example: kvm-guest:~ # multipath -ll mpathat ( de ) dm-7 IBM,2145 size=2.0g features='1 queue_if_no_path' hwhandler='0' wp=rw `-+- policy='service-time 0' prio=50 status=active `- 3:0:0:3 sdf 8:80 active ready running The LUN identifier is a unique number like this de , and must not be overwritten by the KVM stack. The product storage identifier like this IBM,2145 must be visible inside the KVM guest. If the backup or clone system is a virtual machine then all target LUNs that participate in backup or clone operations must be attached to the virtual machine by using one of the following attachment methods: iscsi Network file system (NFS) Copyright IBM Corp. 2001,

8 1.2 Hardware Requirements for DS IBM System Storage DS8000 (DS8100, DS8300, DS8700, DS8800 or DS8870) with the Point in Time Copy feature enabled. With DS8000 Release 4.1 (bundle ) and later the embedded CIM agent in the HMC is enabled and configured by default and can be used with FlashCopy Manager. Note: IBM CIM Agent for DS Open API version has a known problem with refresh of an incremental FlashCopy using FCM. Therefore make sure that CIM Agent xx is not used. Please upgrade the DS microcode to a level that provides CIM Agent >= (for example: DS8000 bundle version comes with CIM Agent ) DS8000 LIC level for FlashCopy to work with FlashCopy Manager: FlashCopy Manager supports all DS8000 Releases >= R3.1. For older DS8000 releases, the following minimum microcode levels are required: mcode /DSCLI , mcode x/DSCLI or higher mcode Support is provided for Fibre Channel attached volumes The user defined for FCM operations in DS8000 needs to be assigned to the "Administrator" user group. 1.3 Hardware Requirements for SVC / Storwize (SVC) IBM System Storage SAN Volume Controller versions 6.1, 6.2, 6.3, 6.4, 7.1, 7.2, 7.3 and (Storwize) IBM Storwize V7000 v1 Disk System IBM Storwize V7000 Version 6.4, 7.1, 7.2, 7.3 and 7.4 IBM Storwize v3700 Version 6.4, 7.1, 7.2, 7.3 and 7.4 IBM Storwize v , 7.2, 7.3 and 7.4 IBM Storwize V7000 Unified v1.3 Disk System (block level support only) IBM Storwize V7000 Unified v1.4 Disk System (block level support only) IBM Storwize V7000 Unified v1.5 Disk System (block level support only) IBM Flex System v7000 Version 6.4, 7.1 and 7.2 IBM FlashSystem V840 IBM FlashSystem V9000 Note: FlashCopy Manager communicates with the SVC/Storwize only. There is no communication between FlashCopy Manager and storage systems attached to the SVC Support is provided for Fibre Channel and iscsi attached volumes Support for Metro Mirror and Global Mirror: The target volumes of the Metro/Global Mirror relationships are usually located on a secondary storage system in a remote site. It can be the Disaster Recovery site. For Remote FlashCopy backups, FCM requires that Copyright IBM Corp. 2001,

9 the remote relationships are created, started and added to a unique consistency group. For Metro Mirror, the relationships must be synchronized. For Global Mirror the relationships must already be copied for the first time, otherwise FCM could wait too long and fail running out of time. If you are going to offload the FlashCopy disk backup to TSM, an additional backup host is needed on the secondary site. Prior to the offload backup, FCM will attach the FlashCopy target volumes on the secondary site to this backup host If you are using the FlashCopy backup on the secondary site for restores, you need a takeover host for the restore containing the same instance structure as in the production host on the production site. SVC and Storwize must be configured for https or http communication. By default, SVC/Storwize is configured for HTT communication. For SVC and Storwize, the user defined for FCM operations in SVC/Storwize needs to be assigned to the "Administrator" user group. Note: Starting with SVC 6.1, the CIM agent can be restarted using the Service Assistant for At go to the Restart Service navigation item and select the CIMOM. Copyright IBM Corp. 2001,

10 1.4 Hardware Requirements for XIV IBM XIV Storage System Hardware: IBM XIV 2nd Generation Storage System v b, and later 10.x levels IBM XIV 3rd Generation Storage System 11.x levels IBM XIV Storage System Software: IBM XIV Management Tools 3.x for all IBM XIV Generations IBM XIV Management Tools 4.2.x for all IBM XIV Generations or XIV CLI and later 2.x and 3.x levels for IBM XIV 2nd Generation XIV CLI and later 3.x levels for IBM XIV 3rd Generation XIV CLI 4.2 and later 4.2.x levels for IBM XIV 3rd Generation IBM Spectrum Accelerate : IBM Spectrum Accelerate Version 11.5.x FCM requires the usage of mirror consistency groups for synchronous and asynchronous remote mirroring on XIV. This feature is first implemented with XIV Support is provided for Fibre Channel and iscsi attached volumes Support for Synchronous and Asynchronous Mirroring: The target volumes of the Remote Mirroring relationships are usually located on a secondary storage system in a remote site. It can be the Disaster Recovery site. For Remote Snapshot backups, FCM requires that the remote relationships are created, started and added to a unique consistency group. For Synchronous Mirroring, the relationships must be synchronized. For Asynchronous Mirroring the relationships must already be copied for the first time, otherwise FCM could wait too long and fail running out of time If you are going to offload the FlashCopy disk backup to TSM, an additional backup host is needed on the secondary site. Prior to the offload backup, FCM will attach the remote snapshots on the secondary site to this backup host If you are using the FlashCopy backup on the secondary site for restores, you need a takeover host for the restore containing the same instance structure as in the production host on the production site. The user account that will be used by FlashCopy Manager to log onto the storage system must have Storage Administrator privileges 1.5 Hardware Requirements for N Series/NetApp Supported ONTAP versions are 7.3 or later 7.3.x levels and 8.1 or later 8.1.x levels Volumes must be attached to the production server via SAN, iscsi or NAS The user account that will be used by FlashCopy Manager to log onto the storage system must have the permissions / capabilities: Copyright IBM Corp. 2001,

11 api-system-*, api-volume*, login-http-admin, api-lun-list*, api-lun-get-serial-number, api-cg-start, api-cg-commit, and snapshot-list-info Copyright IBM Corp. 2001,

12 2. Software Requirements 2.1 Software Requirements Operating System The following software - if not otherwise specified - is required on the and if applicable on the BS/CS: AIX AIX 6.1 (64 bit) AIX 7.1 (64 bit) os.version and os.architecture The following minimum C++ runtime levels are required: (AIX 6.1): xlc.rte and xlc.aix61.rte (or later) filesets (AIX 7.1): xlc.rte and xlc.aix61.rte (or later) filesets os.lib.xlc.aix61.rte and os.lib.xlc.rte Note 1: The operating system levels must be the same on the and BS/CS servers. Note 2: Virtual I/O support for SAN, see File systems: JFS or JFS2, see fcm.filesystemtype IBM General Parallel Filesystem (GPFS) as a minimum level in combination with DB2 purescale (FCM only) IBM General Parallel Filesystem (GPFS) as a minimum level in combination with Custom Applications NFS in combination with IBM N Series or NetApp storage. fcm.filesystemtype (not : combination with IBM N Series or NetApp) Oracle ASM JFS2 inline logs and concurrent I/O are supported. For concurrent I/O make sure that the option 'cio' is in the /etc/filesystems (check with command 'lsfs') and in the LVCB (logical volume control block) of the filesystem. This can be with the command getlvcb: () BS/CS x1:root:/#getlvcb -AT fslv01 AIX LVCB intrapolicy = m copies = 1 interpolicy = m lvid = 0059d79a00004c fb53c1c4d1.9 lvname = fslv01 Copyright IBM Corp. 2001,

13 label = /oracle/c01/sapdata7 machine id = 9D7AA4C00 number lps = 13 relocatable = y strict = y stripe width = 0 stripe size in exponent = 0 type = jfs2 upperbound = 32 fs = vfs=jfs2:log=/dev/loglv10:mount=true:*options=cio,*rw:account=false time created = Wed Mar 10 13:50: time modified = Tue Aug 16 17:11: AIX Base System Locale ISO Code Set - U.S. English (the command 'locale -a' must show that the locale en_us.iso is available) os.localeinstalled.en_us.iso For N series and NetApp storage systems only: The GCC runtime library libgcc version 4 must be installed. The package can be downloaded from the IBM AIX toolbox at: oad.html storage.netapp If SDD is installed, the correct vpath device configuration must be with lsvpcfg. On the production and backup systems, all pvids containing storage-system volumes must be converted to vpath (hd2vp command, only in case of SDD). SDDPCM with AIX MPIO can be used instead of SDD. BS/CS Note: When AIX LVM mirroring is used, then SDD must not be used. Instead AIX MPIO and SDDPCM must be used. Virtual I/O for HBA is supported through - native VIOS on p5 / p6 / p7 with SVC, Storwize V7000 and DS8000 with target disks mapped statically to the backup host (parameter BACKUP_HOST_NAME set to PREASSIGNED_VOLUMES) - N_Port ID Virtualization (NPIV) on p6 and p7 with all storage systems and with target disks mapped statically to the backup host (parameter BACKUP_HOST_NAME set to PREASSIGNED_VOLUMES) or mapped dynamically to the backup host (parameter BACKUP_HOST_NAME set to <hostname>) 6 NPIV is a Fibre Channel facility allowing multiple N_Port IDs to share a single physical N_Port. This allows multiple Fibre Channel initiators to share a single physical port. Disks used with Oracle ASM need the reserve_policy attribute set to no_reserve. Change it with: chdev -l hdiskn -a reserve_policy=no_reserve Copyright IBM Corp. 2001,

14 Linux Red Hat Enterprise Linux 5 x64 Version 5.1 up to 5.8 Red Hat Enterprise Linux 6.1 up to 6.6 SUSE Enterprise Linux 11 x64 os.version and os.architecture Note: The operating system levels must be the same on the and BS/CS. A volume manager must be installed, configured, and running. Volume Managers supported: LVM2 os.package.lvm2 and os.fileinfo.lvm.conf Oracle ASM BS/CS Note: Refer to the following URL for Known Issues and Limitations Filesystems: ext2,ext3 or ext4 fcm.filesystemtype IBM General Parallel Filesystem (GPFS) as a minimum level in combination with DB2 purescale (FCM only) IBM General Parallel Filesystem (GPFS) as a minimum level in combination with Custom Applications NFS in combination with IBM N Series or NetApp storage. fcm.filesystemtype (not : combination with IBM N Series or NetApp) () Oracle ASM Only entire disks are part of the volume groups / disk groups managed by FCM. Note: Disk partitions within volume groups / disk groups are not supported Multipathing needs to be installed and configured. The according package names are: multipath-tools on SLES systems os.package.multipath-tools device-mapper-multipath on RHEL systems os.package.device-mapper-multipath Native DM-MPIO is installed. os.lsmod.dm_multipath The sg3_utils package needs to be installed. Copyright IBM Corp. 2001,

15 Solaris Solaris 10 SPARC Update 4, or later Note 1: The operating system levels must be the same on the and BS/. Note 2: For a proper operation of FlashCopy Manager in conjunction with DB2 it is crucial to install the following Solaris patch or newer patches accumulating it: Patch Id: BS/CS Volume Manager: Veritas Volume Manager (VxVM) version 5.0 or 5.1 or Oracle ASM Note: Refer to following URL for Known Issues and Limitations File systems: UFS, Veritas File System (VxFS), Oracle ASM FlashCopy Manager needs to run in the global zone Native MpxIO is installed. HP-UX HP-UX 11iv3 (11.31) Update 3 release, or later Note 1: The operating system levels must be the same on the and BS/. Note 2: For a proper operation of FlashCopy Manager it is crucial to install the following HP-UX patch or newer patches accumulating it: BS/CS Patch Id: PHCO_41072 Volume Manager: HP LVM (BaseLVM) version B to B or Oracle ASM File systems:veritas File System (VxFS) 4.1, or later, Oracle ASM Volume Group Versions 1.0, 2.0, 2.1 and 2.2 are supported Native MPIO or VxDMP is installed Supported in combination with HP Integrity servers (Intel Itanium ) The LVM volume group configurations for LUNs must be using the agile (persistent) naming model. Copyright IBM Corp. 2001,

16 Prior installing FlashCopy Manager update the /etc/dld.sl.conf to include the following paths: <INSTANCE_DIR>/jre/jre/lib/IA64N <INSTANCE_DIR>/jre/jre/lib/IA64N/server <INSTANCE_DIR>/jre/jre/lib/IA64N/jli <INSTANCE_DIR>/jre/jre/lib/IA64W <INSTANCE_DIR>/jre/jre/lib/IA64W/server <INSTANCE_DIR>/jre/jre/lib/IA64W/jli Examples of the INSTANCE_DIR: DB2: <Instance owner $HOME directory>/sqllib/acs/ Oracle: <Instance owner $HOME directory>/acs/ See IBM Tivoli Storage FlashCopy Manager Installation and User's Guide for UNIX and Linux to find correct INSTANCE_DIR for specific application. BS/CS Copyright IBM Corp. 2001,

17 2.2 Software Requirements - Storage Subsystems XIV Perequisite XIV CLI 2.3.x or 3.x. or 4.2.x XIV CLI 4.1 is not supported XCLI download page: rs=1319&context=stjtag&dc=d400&q1=ssg1*&uid=ssg1s &loc =en_us&cs=utf-8&lang=en Copyright IBM Corp. 2001,

18 2.3 Other Software Requirements Note: For DB2 purescale environments the term server refers to a GPFS cluster as part of a DB2 purescale instance which consists of one or more servers For the installation of FCM, the FCM package according to the application to be protected must be available. For FlashCopy only backup/restore: - BS/CS For FlashCopy backup / restore with offloading into a storage management server: An IBM Tivoli Storage Manager Server (min. V6.3.x) Alternative to TSM - a third party storage management server. FCM makes the data available on the BS. The transfer into the storage management server must be performed by third party components Optional: TSM Storage Agent for LANfree data transfer on (for logs) and BS For FlashCopy cloning: - Copyright IBM Corp. 2001,

19 3. Requirements for DB2 Note: For DB2 purescale environments, the term "server" refers to a GPFS cluster as part of a DB2 purescale instance which consists of one or more servers. 3.1 Software requirements The following software - if not otherwise specified - is required on the and BS/CS. 64-bit DB2 Enterprise Server Edition V9.7; for Solaris, Fix Pack 2 or a later 9.7 Fix Pack is required. 64-bit DB2 Enterprise Server Edition V10.1 Fix Pack 2 and later 10.1.x Fix Packs 64-bit DB2 Enterprise Server Edition V10.5 and later 10.5.x Fix Packs fcm.db_version (Solaris) For a proper operation of FlashCopy Manager in conjunction with DB2 it is crucial to install the following Solaris patch or newer patches accumulating it: BS/CS Patch Id: On the BS a DB2 instance with the same name as on needs to be created with the same configuration as on. (DB2 purescale) DB2 Enterprise Server Edition V10.5 FP4 or a later 10.5 Fix Pack is required. Use the GPFS package included within this DB2 package. Other installed GPFS versions should be uninstalled before the DB2 package is installed. In the backup cluster a DB2 purescale instance with the same name and configuration like in the production cluster needs to be created. Copyright IBM Corp. 2001,

20 For FlashCopy only backup/restore: - BS/CS For FlashCopy backup / restore with offloading into a storage management server: (SAP) an IBM Tivoli Storage Manager for Enterprise Resource Planning V6.3 can be used to backup the database redo logs on the and to backup the database on the BS/CS or the DB2 native TSM agent can be used to backup the database redo logs on the and to backup the database on the BS/CS (non-sap or DB2 purescale) the DB2 native TSM agent must be used to backup the database redo logs on the and to backup the database on the BS/CS For FlashCopy cloning: - Copyright IBM Corp. 2001,

21 3.2 Environmental requirements BS/CS All DB2 database files must reside on source volumes with supported file systems, see 2.1.2, , , (raw devices are not supported) all tablespace containers the local database directory the online log directory fcm.filesystemtype All table spaces must be DMS table spaces except system temporary table spaces or user temporary table spaces which can be SMS table spaces. DB2 automatic storage table spaces are also supported. fcm.tablespace_format The DB2 database must be in log retain mode Make sure that the same unique UID can be used for the DB2 instance owner user on and BS Make sure that the same unique GID can be used for the primary group of the DB2 instance owner on and BS For hardware snapshots, soft links to DB2 tablespace files are supported as long as they are pointing to files residing in volume groups that can be flashed. The normal SAP setup of DB2 tablespaces files is not using links. In combination with DB2 purescale, only soft links pointing to files in the same GPFS file set are supported. In DB2 purescale environments, the backup cluster needs to be authenticated against the production cluster. On the production cluster use mmauth add and mmauth grant to allow for remote mount and write access to all DB2 GPFS database file systems from the backup cluster. On the backup cluster use mmremotecluster add to add the production cluster. Do not use mmremotefs add and mmmount. This will be done by FCM. For details on GPFS remote mount functionality see GPFS Advanced Administration Guide, Chapter 1. In DB2 purescale environments, the backup cluster needs the same cluster topology as the production cluster. The same number of members and also the same member numbers are required. Cluster caching facilities (CF) do not count in this manner. Multiple DB2 members can be created on a single host as logical members, for example through the DB2 setup wizard db2isetup. In case the backup cluster of a DB2 purescale environment consists of two or more machines the backup server identified to FlashCopy Manager must be the system where DB2 purescale member 0 resides. Member numbers and the machines members reside on can be found in db2nodes.cfg. Copyright IBM Corp. 2001,

22 3.3 Volume group layout requirements Note: For Solaris, the term volume group (VG) corresponds to disk groups. The following prerequisites related to volume groups are applicable to Solaris disk groups in the same way Make sure that the VGs listed in 3.3.2/3/4 do not contain any other file system (FS) than listed below. Only the FS listed below need to be and are allowed to be included in the snapshot backup. the FS of VG1 and VG2 can be put together into one VG the FS of VG3 must be separated from all other listed FS fcm.volume_group_layout Important: For database instances managing multiple databases each of the databases need to be located on its own volume groups according to this layout specification. Volume group layout: Note: In the following rows <SID> means the database name in capital letters and <sid> means the database name in small letters. Also the FS names listed are an example for a SAP database where the DB2 instance owner is db2<sid> and its $HOME directory is /db2/<sid>. The VG names VG1, VG2 and VG3 are samples. The VGs can have any name. VG1 (can be more than 1 VG): /db2/<sid>/sapdata1..n all FS containing data tablespaces /db2/<sid>/sapdatat or /db2/<sid>/saptemp1..n all FS containing temporary tablespaces Location: Supported storage subsystems fcm.volume_group_layout VG2: /db2/<sid>/db2<sid> the FS containing the local database directory (which includes /db2/<sid>/db2<sid>/node0000/sql00001) Location: Supported storage subsystems fcm.volume_group_layout VG3: /db2/<sid>/log_dir the FS containing the online log files. Location: Supported storage subsystems fcm.volume_group_layout Copyright IBM Corp. 2001,

23 3.3.5 For multipartitioned databases (DPF) a dedicated set of VGs must be defined for each partition for a partition-based source- target relation, e.g. VGdata0000: /db2/<sid>/sapdata1..n/node0000 /db2/<sid>/sapdatat/node0000 /db2/<sid>/saptemp1/node0000 /db2/<sid>/db2<sid>/node0000 VGlog0000: /db2/<sid>/log_dir/node VGdata<NNNN>: /db2/<sid>/sapdata1..n/node<nnnn> /db2/<sid>/sapdatat/node<nnnn> /db2/<sid>/saptemp1/node<nnnn> /db2/<sid>/db2<sid>/node<nnnn> VGlog<NNNN>: /db2/<sid>/log_dir/node<nnnn> For DB2 automatic storage make sure that the storage path resides in dedicated file systems on dedicated VGs for each partition. For example: Database AS1 (instance db2as1) is created with storage path /db2/as1/sapdata1. In this case the following filesystems/vgs must exist: VGdata0000: /db2/as1/sapdata1/db2as1/node VGdata<NNNN>: /db2/as1/sapdata1/db2as1/node<nnnn> fcm.no_shared_volumes Other FS like /db2/<sid>/sqllib /db2/<sid> /db2 /opt/ibm/db2/v10.x and other application specific FS are not allowed to be on the same VGs VG1, VG2 and VG3. They are allowed to reside on local storage or on any storage system. fcm.volume_group_layout For performance reasons the number of LUNs should be kept as low as possible. Copyright IBM Corp. 2001,

24 3.4 DB2 purescale: GPFS File system layout requirements Note: For DB2 purescale, the snapshot granularity is an independent fileset. The following prerequisites are related to independent filesets. Note that each GPFS file system has a default independent fileset named root. That means either multiple GPFS file systems and/or independent filesests within one or more file systems can be used for separating data according to the rules listed in the table below Make sure that the filesets listed in 3.4.2/3/4 do not contain any other directories than listed below. Only the directories listed below need to be and are allowed to be included in the snapshot backup. Fileset1 and Fileset2 can be combined into one fileset. Fileset3 must be separated from all other listed filesets. Note: In the following rows <SID> means the database name in capital letters and <sid> means the database name in small letters. Also the directory names listed are an example for a SAP database where the DB2 instance owner is db2<sid> and its $HOME directory is /db2/<sid>. The fileset names Fileset1, Fileset2 and Fileset3 are samples. The filesets can have any name. Fileset1 (can be more than one fileset): /db2/<sid>/sapdata1..n all directories containing data tablespaces /db2/<sid>/sapdatat or /db2/<sid>/saptemp1..n all directories containing temporary tablespaces Location: Any storage supported by GPFS Fileset2: /db2/<sid>/db2<sid> the directory containing the local database directory (which includes /db2/<sid>/db2<sid>/node0000/sql00001) Location: Any storage supported by GPFS Fileset3: /db2/<sid>/log_dir the directory containing the online log files. Location: Any storage supported by GPFS For DB2 automatic storage make sure that the storage path resides in dedicated filesets. Other directories like /db2/<sid>/sqllib /db2/<sid> /db2 /opt/ibm/db2/v10.x and other application specific directories are not allowed to be on the same filesets Fileset1, Fileset2 and Fileset3. GPFS snapshots are located in the GPFS file systems. Due to the copy-on-write technology used, their sizes grow over time as the database is modified. Database administrators must keep monitoring free space in the GPFS file systems in order to avoid a file-system-full condition for the productive database. The number of GPFS snapshots kept in the file systems can be controlled with FlashCopy Manager profile parameter MAX_VERSIONS. Copyright IBM Corp. 2001,

25 3.5 NFS File system layout requirements Note: For NFS support fo IBM N Series or NetApp storage, the snapshot granularity are independent NFS filesystems on dedicated NetApp volumes. FCM does not support the export of sub-directories from the same NetApp volume. The following prerequisites are related to independent NFS filesystems Make sure that the NFS filesystems listed in 3.5.2/3/4 do not contain any other directories than listed below. Only the directories listed below need to be and are allowed to be included in the snapshot backup. fcm.volume_group_layout Volume group layout: Note: In the following rows <SID> means the database name in capital letters and <sid> means the database name in small letters. Also the directory names listed are an example for a SAP database where the DB2 instance owner is db2<sid> and its $HOME directory is /db2/<sid>. The NFS filesystems names NFS-filesystem1, NFS-filesystem2 and NFS-filesystem3 are samples. The NFS filesystem can have any name. NFS-filesystem1 (can be more than one NFS filesystem): /db2/<sid>/sapdata1..n all directories containing data tablespaces /db2/<sid>/sapdatat or /db2/<sid>/saptemp1..n all directories containing temporary tablespaces Location: Supported storage subsystems fcm.volume_group_layout NFS-filesystem2: /db2/<sid>/db2<sid> the directory containing the local database directory (which includes /db2/<sid>/db2<sid>/node0000/sql00001) Location: Supported storage subsystems fcm.volume_group_layout NFS-filesystem3: /db2/<sid>/log_dir the directory containing the online log files. Location: Supported storage subsystems fcm.volume_group_layout Copyright IBM Corp. 2001,

26 For multipartitioned databases (DPF) a dedicated set of NFS filesystems must be defined for each partition for a partition-based source- target relation, e.g. NFS FS for partition 0: /db2/<sid>/sapdata1..n/node0000 /db2/<sid>/sapdatat/node0000 /db2/<sid>/saptemp1/node0000 /db2/<sid>/db2<sid>/node0000 /db2/<sid>/log_dir/node NFS FS for other partitions: /db2/<sid>/sapdata1..n/node<nnnn> /db2/<sid>/sapdatat/node<nnnn> /db2/<sid>/saptemp1/node<nnnn> /db2/<sid>/db2<sid>/node<nnnn> /db2/<sid>/log_dir/node<nnnn> For DB2 automatic storage make sure that the storage path resides in dedicated file systems on dedicated VGs for each partition. For example: Database AS1 (instance db2as1) is created with storage path /db2/as1/sapdata1. In this case the following NFS filesystems must exist: NFS FS for partition 0: /db2/as1/sapdata1/db2as1/node NFS FS for other partitions: /db2/as1/sapdata1/db2as1/node<nnnn> fcm.no_shared_volumes Other directories like /db2/<sid>/sqllib /db2/<sid> /db2 /opt/ibm/db2/v10.x and other application specific directories are not allowed to be on the same NFS filesystems NFS-filesystem-1, NFS-filesystem-2 and NFS-filesystem-3. They are allowed to reside on local storage or on any storage system. fcm.volume_group_layout Copyright IBM Corp. 2001,

27 4. Requirements for SAP on Oracle 4.1 Software requirements Note: The following software - if not otherwise specified - is required on and BS/CS by FlashCopy Manager Oracle Enterprise Server Edition 11gR1 or 11gR2-64-bit at a level certified by the respective SAP release The following Oracle release at a level certified by the respective SAP release is currently supported: Oracle Enterprise Server Edition 11gR2 64-bit fcm.db_version Note: If off-loading or cloning shall be used, an Oracle DBMS must be installed on BS server. The following BR*Tools releases are currently supported: BR*Tools release 7.10 (patch level 14 or higher) BR*Tools release 7.20 (patch level 6 or higher) BR*Tools release 7.40 Hint: For Oracle 11gR2 release 7.20 or 7.40 of BR*Tools is required. Note: FlashCopy-Manager-only interfaces with the SAP BR*Tools through the backint interface (BC-BRI volume based). For FlashCopy only backup/restore: - For FlashCopy backup / restore with offloading into a storage management server: an IBM Tivoli Storage Manger for Enterprise Resource Planning v6.3 on and BS For FlashCopy cloning: - BS/CS Copyright IBM Corp. 2001,

28 4.2 Environmental requirements All Oracle database files must reside on source volumes in supported file systems, see 2.1.2, , , (raw devices are not supported) all tablespace data files all control files all redo log files (origloga/b, mirrloga/b) fcm.filesystemtype The SAP environment files (.sapenv_<hostname>.csh,.sapenv_<hostname>.sh) of the user ora<sid> must not contain statements like 'tset -I -Q'. If this statement exists in the environment files, the FlashBack Restore does not work. The software reports that a source volume is no longer attached to the production system. Make sure that the same unique UID can be used for user ora<sid> on and BS Make sure that the same unique GID can be used for group dba on and BS BS Copyright IBM Corp. 2001,

29 4.3 Volume group layout requirements As a general rule: Layouts which were supported with previous releases also work with this one Make sure that the VGs listed do not contain any other FS than those listed below. Only the FS listed below need to be and are allowed to be included in the snapshot backup. fcm.volume_group_layout Volume group layout: Note: In the following rows <SID> means the database name in capital letters. The VG names VG1 and VG2 are samples. The VGs can have any name. VG1 (can be more than 1 VG): /oracle/<sid>/sapdata1..n all FS containing tablespaces and the control files Location: Supported storage subsystems fcm.volume_group_layout VG2 (can be more than 1 VG): /oracle/<sid>/origloga the FS containing the online redo logs and optionally a copy of the control file /oracle/<sid>/origlogb the FS containing the online redo logs and optionally a copy of the control file /oracle/<sid>/mirrloga the FS containing the online redo logs and optionally a copy of the control file /oracle/<sid>/mirrlogb the FS containing the online redo logs and optionally a copy of the control file Location: Allowed to reside on local storage or on any storage system as long as only FCM backup but not FCM cloning is desired. The DB control files can be stored in the origloga/origlogb and mirrloga/mirrlogb as well as in sapdata1..n. fcm.volume_group_layout Note: For performance reasons the number of LUNs should be kept as low as possible. Other FS like /oracle/<sid>/oraarch /oracle/<sid>/saparch /oracle/<sid>/sapbackup /oracle/<sid>/sapreorg /oracle/<sid> /oracle and other application specific FS are not allowed to be on the same VGs VG1 and VG2. They are allowed to reside on local storage or on any storage system. fcm.volume_group_layout Copyright IBM Corp. 2001,

30 4.4 NFS File system requirements Note: For NFS support fo IBM N Series or NetApp storage, the snapshot granularity are independent NFS filesystems on dedicated NetApp volumes. FCM does not support the export of sub-directories from the same NetApp volume. The following prerequisites are related to independent NFS filesystems Make sure that the NFS filesystems listed do not contain any other FS than those listed below. Only the FS listed below need to be and are allowed to be included in the snapshot backup. fcm.volume_group_layout Volume group layout: Note: In the following rows <SID> means the database name in capital letters. The NFS filesystems names NFS-filesystem1 and NFS-filesystem2 are samples. The NFS filesystems can have any name. NFS-filesystem1 (can be more than 1 NFS filesystem): /oracle/<sid>/sapdata1..n all FS containing tablespaces and the control files Location: Supported storage subsystems fcm.volume_group_layout NFS-filesystem2 (can be more than 1 NFS filesystem): /oracle/<sid>/origloga the FS containing the online redo logs and optionally a copy of the control file /oracle/<sid>/origlogb the FS containing the online redo logs and optionally a copy of the control file /oracle/<sid>/mirrloga the FS containing the online redo logs and optionally a copy of the control file /oracle/<sid>/mirrlogb the FS containing the online redo logs and optionally a copy of the control file Location: Allowed to reside on local storage or on any storage system as long as only FCM backup but not FCM cloning is desired. The DB control files can be stored in the origloga/origlogb and mirrloga/mirrlogb as well as in sapdata1..n. fcm.volume_group_layout The FS listed here are not allowed to be located on the same NFS filesystems NFS-filesystem1 and NFS-filesystem2: /oracle/<sid>/oraarch /oracle/<sid>/saparch /oracle/<sid>/sapbackup /oracle/<sid>/sapreorg /oracle/<sid> /oraclevgs and other application specific FS. They are allowed to reside on local storage or on any storage system. fcm.volume_group_layout Copyright IBM Corp. 2001,

31 5. Requirements for Oracle (non-sap) 5.1 Software requirements The following software - if not otherwise specified - is required on both the production and backup systems by DataProtection for FlashCopy: The following Oracle releases are currently supported: Oracle Database Standard Edition 11gR1 64-bit Oracle Database Standard Edition 11gR2 64-bit BS/CS Oracle Database Enterprise Server Edition 11gR1 64-bit Oracle Database Enterprise Server Edition 11gR2 64-bit Oracle Real Application Clusters (RAC) option on supported Oracle Database releases fcm.db_version Note 1: Oracle Real Application Clusters (RAC) is only supported in combination with Oracle ASM only. Please also consider Known Issues and Limitations on following URL: Note 2: An Oracle DBMS must be installed on the backup server for offloaded tape backups. An Oracle DBMS does not need to be installed on the BS for disk-only backups. For FlashCopy only backup / restore: - For FlashCopy backup / restore with offloading to tape: Tivoli Storage Manager for Databases - Oracle version v6.3 or later on and BS For FlashCopy cloning: - For ASM on AIX, the following patches are required: Oracle Enterprise Server 11gR1: Patch (included in ) Patch Oracle Enterprise Server 11gR2: Patch (included in ) Patch (included in ) Patch Copyright IBM Corp. 2001,

32 fcm.oracleasmpatches Copyright IBM Corp. 2001,

33 5.2 Environmental requirements All Oracle database files must reside on source volumes in supported file systems, see 2.1.2, , , fcm.filesystemtype or Oracle ASM storage (AIX only) Make sure that the same unique UID can be used for the Oracle instance owner user on and BS. One dedicated instance owner user is required per database instance. Make sure that the same unique GID can be used for the primary group of the Oracle instance owner on and BS RMAN catalog database needs to be configured (even for disk only backups). It should not reside on the (because it would be lost in the case of a disaster) but must be accessible from both and BS. fcm.catalog_db_connection (Linux) On Linux FCM supports only ASM environments setup with Oracle ASMLib since Oracle recommends ASMLib over raw devices for ease-of-use and performance reasons. Raw devices are not supported. ASMLib 2.0 is required by FCM. (Linux) For multipathing to work properly the parameters ORACLEASM_SCANORDER and ORACLEASM_SCANEXCLUDE need to be set in the ASMLib configuration. For example exclude single paths from the scan by setting ORACLEASM_SCANEXCLUDE= sd and force multipath devices by setting ORACLEASM_SCANORDER= dm-*. For details see section Configuring the Scan Order on this page: (Linux) In Oracle ASM environments with ASMLib on Linux, the ASM_DISKSTRING parameter is required to be set to 'ORCL:*' on production and backup system. For further information see: CWLIN293 (AIX, Solaris, HPUX) For Oracle ASM the setting of the ASM_DISKSTRING parameter has to be left to the default for the backup server. For Oracle ASM diskgroups are created on entire disks. (Setups on disk partitions are not supported.) For Oracle Real Application Clusters (RAC) databases, the database instance owner user is required to be member of the group: asmadmin For Oracle Real Application Clusters (RAC) databases, a shared file system across all RAC nodes of the the production database is required. It is used to share the FCM binaries, configuration and repository. Database file names must not contain blanks, tab or new line characters. BS/CS Copyright IBM Corp. 2001,

34 5.3 Volume group layout requirements One or more Oracle control file copies can be placed in the same VG as the data files. If they are, follow the recovery procedure described in the user's guide chapter Restoring Oracle snapshots after a restore operation. Make sure that the VGs listed do not contain any other FS than those listed below. Only the FS listed below need to be and are allowed to be included in the snapshot backup. fcm.volume_group_layout Volume group layout: Note: In the following rows <SID> means the database name in capital letters. The VG names VG1 and VG2 are samples. The VGs can have any name. VG1 (can be more than 1 VG): /oracle/<sid>/data1..n all FS containing tablespaces Location: Supported storage subsystems fcm.volume_group_layout VG2 (can be more than 1 VG): containing the online redo logs and optionally a copy of the control file Location: Allowed to reside on local storage or on any storage system as long as only FCM backup but not FCM cloning is desired. fcm.volume_group_layout For performance reasons the number of LUNs should be kept as low as possible. The FS listed here are not allowed to be located on the VGs (VG1,VG2) where data, log and control files are located and must be explicitly separated: /oracle/<sid>/oraarch /oracle/<sid> /oracle They are allowed to reside on local storage or on any storage system. fcm.volume_group_layout Copyright IBM Corp. 2001,