DSXchange: DataStage and IBM Websphere Data Integration Forum
View next topic
View previous topic
Add To Favorites
Author Message
rumu
Participant



Joined: 06 Jun 2005
Posts: 267

Points: 2694

Post Posted: Mon Oct 08, 2018 8:34 am Reply with quote    Back to top    

DataStage® Release: 11x
Job Type: Parallel
OS: Unix
Hi,

My client has asked the back up steps for Service tier and Engine tier. We are using V11.5. Could you please help with the steps or link to the relevant documentation?

_________________
Rumu
IT Consultant
ray.wurlod

Premium Poster
Participant

Group memberships:
Premium Members, Inner Circle, Australia Usergroup, Server to Parallel Transition Group

Joined: 23 Oct 2002
Posts: 54431
Location: Sydney, Australia
Points: 295208

Post Posted: Mon Oct 08, 2018 4:03 pm Reply with quote    Back to top    

https://www.ibm.com/support/knowledgecenter/SSZJPZ_11.5.0/com.ibm.swg.im.iis.found.admin.burest.doc/topics/t_admin_backup_restore_super.html

You really should learn to use the Search capabilities of IBM Knowledge Center.

_________________
RXP Services Ltd
Melbourne | Canberra | Sydney | Hong Kong | Hobart | Brisbane
currently hiring: Canberra, Sydney and Melbourne (especially seeking good business analysts)
Rate this response:  
Not yet rated
rumu
Participant



Joined: 06 Jun 2005
Posts: 267

Points: 2694

Post Posted: Thu Oct 11, 2018 8:02 am Reply with quote    Back to top    

The link does not provide detail steps on back up procedure. Few questions raised by our clients:

1)Back up to be taken on the same server were engine and service tiers are installed?

2)Is isrecovery tool available in V11.5 for back up and recovery?

_________________
Rumu
IT Consultant
Rate this response:  
Not yet rated
ray.wurlod

Premium Poster
Participant

Group memberships:
Premium Members, Inner Circle, Australia Usergroup, Server to Parallel Transition Group

Joined: 23 Oct 2002
Posts: 54431
Location: Sydney, Australia
Points: 295208

Post Posted: Fri Oct 12, 2018 12:57 am Reply with quote    Back to top    

The link is to a portal on backup and recovery. Links on that page will provide highly detailed information.

_________________
RXP Services Ltd
Melbourne | Canberra | Sydney | Hong Kong | Hobart | Brisbane
currently hiring: Canberra, Sydney and Melbourne (especially seeking good business analysts)
Rate this response:  
Not yet rated
rumu
Participant



Joined: 06 Jun 2005
Posts: 267

Points: 2694

Post Posted: Fri Oct 12, 2018 5:56 am Reply with quote    Back to top    

I referred the link and prepared the attached document. Client wants more detailed information.

Pasting here the content of the document.
Could you kindly have a look if possible. I will be thankful.


IBM Infosphere Information Server Back Up and Recovery Document
________________________________________


Table of Contents
1.PURPOSE OF DOCUMENT 3
2.INTRODUCTION 3
3. BACKING UP IBM INFOSPHERE INFORMATION SERVER COMPONENTS 4
3.1 PREREQUISITES: 4
3.2 PROCEDURE: 4
3.3 SYSTEM ELEMENTS AND DATABASES THAT REQUIRE BACK UP. 6
4. RESTORING IBM INFOSPHERE INFORMATION SERVER COMPONENTS 11
4.1 PREREQUISITES: 11
4.2 PROCEDURE: 11



1.Purpose of Document

The purpose of this document is to provide a guideline to handle backup and recovery of IBM InfoSphere Information Server components- services tier, engine tier, and metadata repository tier. These three core layers consist of various elements that require back up.

This document is not a core project artefact and is intended to be used as a reference in addition to regular support and IBM Knowledge Center documentation.

The procedures documented here cover backing up and restoring the three main tiers of IBM InfoSphere Information Server


2.Introduction

In the event of hardware failure or other system issue, to prevent the loss of data and to prepare for disaster recovery, it is very important to take back up and restore the components and system elements that are associated with IBM InfoSphere Information Server. Specifically, it is required to take back up of the services tier, engine tier, and repository tier of IBM InfoSphere Information Server.

The engine tier installation contains files and configuration data that are linked to elements stored in the metadata repository. IBM InfoSphere DataStage projects are stored in the engine tier installation directory or elsewhere on the same computer. They are linked to elements stored in the metadata repository. There is also information stored in files in the IBM WebSphere Application Server directory that is linked to elements stored in the metadata repository.
Because of these interdependencies, to guarantee a successful back up, the metadata repository, the IBM InfoSphere DataStage projects, and all of the file system-based elements that change after installation must be backed up, and the backup must occur while all services and IBM WebSphere Application Server are shut down.

SMH Physical Architecture follows the following topology: Services and Repository tiers are hosted on one server and Engine tier is hosted on another server. Back-up and Restore procedures of these layers are described in the following sections.


3. Backing up IBM InfoSphere Information Server components

Components of IBM InfoSphere Information Server require backing up so that data recovery can be achieved in the event of hardware failure or other system issue.

3.1 Prerequisites:

• Before stopping the services, we need to disconnect all active sessions.
• We also need to determine if any jobs are running and if any jobs are scheduled to run then pause those scheduled jobs.

3.2 Procedure:

1. Place IBM Infosphere Information Server in maintenance mode.
Follow the steps mentioned below to place the server in maintenance mode:

When you do routine maintenance of InfoSphere Information Server such as applying a fix pack or backing up the system, you can place the InfoSphere Information Server in maintenance mode. To prevent users from authenticating to IBM InfoSphere Information Server during maintenance, you can place it into maintenance mode by using the SessionAdmin command.

Before you begin
You must have suite administrator authority.
About this task
When IBM InfoSphere Information Server is placed in maintenance mode, users who do not have the suite administrator authority are prevented from logging in to the server. All user sessions on the server are then disconnected to prevent any activity on the system during maintenance. The SessionAdmin is in the following location:

 IS_install_dir/ASBServer/bin/SessionAdmin.sh
IS_install_dir/ASBNode/bin/SessionAdmin.sh

Specify the host name and port number where the product is installed. Also, specify your administrator user name and password that allows you to run this command on the server. Instead of specifying the -user and -password options, you can use the -authfile option.
Procedure
 Close all active products sessions by issuing the following command:
SessionAdmin -url https://server_hostname:server_port -user username -password plaintext_password -kill-user-sessions
 Place the product in maintenance mode by issuing the following command:
SessionAdmin -url https://server_hostname:server_port -user username -password plaintext_password -set-maint-mode ON
 Take the product out of maintenance mode by issuing the following command:
SessionAdmin -url https://server_hostname:server_port -user username -password plaintext_password -set-maint-mode OFF
 Determine the current maintenance mode of the product by using the following command:
SessionAdmin -url https://server_hostname:server_port -user username -password plaintext_password -get-maint-mode

2. Stop the InfoSphere Information Server services and IBM WebSphere Application Server services.
3. Back up the metadata repository database. Refer section 3.3 for more details
4. Optional: Backup InfoSphere DataStage operations database. This is an optional step as operations DB can be recreated while restoring the InfoSphere Information Server components.
5. Back up all system elements.Refer section 3.3 for more details.
6. Back up external files or libraries that are used by InfoSphere DataStage jobs. External files are data sets, sequential files, Run-time log files, data files (sql scripts used in DS jobs), reference files that run InfoSphere Information Server tasks, such as InfoSphere DataStage jobs.
Please follow the following steps to copy datasets from one directory to other location:
To move a DataSet you can use the orchadmin copy command.
A persistent dataset is physically represented on disk by:
A single descriptor file and one or more data files.
The location of the data files is directed by what is defined in the configuration file which is stored in the header of the descriptor file. The orchadmin copy command copies a persistent data set. To move the data set descriptor and data file location, you will need to set the environment variable $APT_CONFIG_FILE to the desired configuration file. The new data set will have the same record schema and contents as the original data set; however, the new data is repartitioned based on the information in your configuration file.

This command is located in $APT_ORCHHOME/bin and takes two arguments. Be sure to source the dsenv before running the command.

The syntax is:
orchadmin copy <old_descriptor_file> <new_descriptor_file>

Argument Description
<old_descriptor_file> is the file name of the descriptor file to copy.
<new_descriptor_file> is the file name of the new descriptor file.

Example:
. ./dsenv
export APT_CONFIG_FILE=/opt/IBM/InformationServer/Server/Configurations/default.apt
orchadmin copy /opt/finance/dataset1.ds /opt/accounting/dataset2.ds



7. Start the InfoSphere Information Server services and WebSphere Application Server services.

3.3 System elements and databases that require back up.

The following steps are taken from IBM Knowledge Center

When you back up IBM InfoSphere Information Server, all file system-based elements that change after installation and all databases must be backed up simultaneously. The backup must occur while all services and IBM WebSphere Application Server are shut down.

Special considerations
Your backup must meet the following criteria:
• User ownership of files and directories is retained
• Group ownership of files and directories is retained
• File names with special characters, such as asterisk (*), ampersand (&), dollar sign ($), and exclamation point (!) are handled
• Hidden files are copied. On Linux or UNIX, these files start with a period (.)
• Zero length files are copied.




File system elements that change after installation


The following tables identify file system elements that change after installation. The paths in these tables use the default installation directory. Your path varies if you installed InfoSphere Information Server in a different location.

File system elements that change after installation (Linux, UNIX)
Element Description Changed by
/opt/IBM/InformationServer
Note If this directory contains /opt/IBM/InformationServer/Repos directory, do not include it in the backup. This directory contains the DB2 database metadata repository files for which you create a backup copy by using DB2 tools. In case of restoring data, it needs to be restored separately from other files in the /opt/IBM/InformationServer directory. The base installation directory for InfoSphere Information Server. Includes all files that are associated with the InfoSphere Information Server installation instance. By default, this directory also stores InfoSphere DataStage and InfoSphere QualityStage projects. All InfoSphere Information Server installation actions, running of analysis jobs, InfoSphere DataStage and InfoSphere QualityStage activities, configuration changes such as application of license files, and various other activities.
IBM WebSphere Application Server Network Deployment
/opt/IBM/WebSphere/AppServer The base installation directory for InfoSphere Information Server which includes all installed services tier components of InfoSphere Information Server. All InfoSphere Information Server installation actions, configuration changes that are made through the IBM WebSphere Application Server or InfoSphere Information Server administrative consoles or external tools that modify configuration values.
Server project directories. By default: /opt/IBM/InformationServer/Server/Projects
Note You can create project directories anywhere on the server's file system. Stores compiled InfoSphere DataStage and InfoSphere QualityStage jobs and routines and metadata that is associated with running InfoSphere DataStage and InfoSphere QualityStage jobs. Whenever a user creates a new InfoSphere DataStage or InfoSphere QualityStage project, a corresponding server directory is created to hold its runtime metadata.

File system elements that do not change or rarely change after installation


File system elements that do not change or rarely change after installation (Linux, UNIX)
Element Description Changed by
On Linux:
• /opt/.ibm/.nif/.nifregistry
• /root/vpd.properties or /user_home/vpd.properties Installation information for IBM WebSphere Application Server. Not changed by use of InfoSphere Information Server. Might be changed if IBM WebSphere Application Server fixes or fix packs are installed separately.
/etc/services Port assignments for the computer. When DB2 or InfoSphere Information Server are installed, the following entries are added:
• DB2_db2inst1 60000/tcp
• DB2_db2inst1_1 60001/tcp
• DB2_db2inst1_2 60002/tcp
• DB2_db2inst1_END 60003/tcp
• dsrpc 31538/tcp # RPCdaemon DSEngine@/u1/IBM/InformationServer/Server/DSEngine
Port assignments might be different in your installation. Not changed after initial installation of InfoSphere Information Server.
/etc/inittab Services to be started on system boot. If you installed DB2 as part of InfoSphere Information Server, this file is modified to add the following entry:
fmc:234:respawn:/u1/IBM/
db2/V10/bin/db2fmcd #DB2
Fault
Monitor Coordinator Not changed after initial installation of InfoSphere Information Server.
Startup and shutdown scripts.
You can determine the scripts to back up and restore by using these commands:
cd /etc
find . -name "SISFServer*" -print
find . -name "SISFAgents*" -print
find . -name "*" -print
| xargs grep -i DSEngine Scripts that are used to start and shut down the services that are associated with InfoSphere Information Server. The SISFAgents script and DSEngine scripts are present only when engine components are installed. The SISFServer script is present only when the services tier is installed. Not changed after initial installation of InfoSphere Information Server.
/opt/IBM/db2/V10 The base installation directory for DB2 when installed as part of InfoSphere Information Server. Not changed by use of InfoSphere Information Server. Installation of DB2 fixes or fix packs modify files in this directory.
/home/dasusr1 The home directory of the DB2 database administrator account. Contains files that are required to run DB2. Not changed by use of InfoSphere Information Server. Installation of DB2 fixes or fix packs might modify files in this directory.
/home/db2inst1 The home directory of the DB2 database instance owner. Contains files that are required to run DB2. Not changed by use of InfoSphere Information Server. Installation of DB2 fixes or fix packs might modify files in this directory.


Critical files that are unique to each installation
The following tables identify critical files that are unique to each installation.
Critical files that are unique to each installation (Linux, UNIX)
Element Description Changed by
IBM WebSphere Application Server Liberty
/opt/IBM/InformationServer/wlp/usr/servers/iis/lib/iis/15properties/isf-server.keystore
IBM WebSphere Application Server Network Deployment
/opt/IBM/WebSphere/ AppServer/profiles/InfoSphere/ classes/isf-server.keystore
Note A duplicate of isf-server.keystore is used as a deployment source to install isf-server.keystore into the IBM WebSphere Application Server profile. It is in the following location, which is based on your installation of IBM WebSphere Application Server:
IBM WebSphere Application Server Liberty
/opt/IBM/InformationServer/ASBServer/apps/lib/iis/15properties
IBM WebSphere Application Server Network Deployment
/opt/IBM/InformationServer/ASBServer/apps/lib/iis/classes On the service tier, the keystore that contains the InfoSphere Information Server engine private key. If you want to restore a backup in a new installation, you must back up the keystore files. Not changed after initial installation of InfoSphere Information Server.
/opt/IBM/InformationServer
/ASBNode/eclipse/plugins
/com.ibm.iis.client/
isf-node.keystore On the engine tier, the keystore that contains the private key and certificate that is generated when nodes are created. This keystore is updated with the InfoSphere Information Server engine public certificate during registration. If you want to restore a backup in a new installation, you must back up the keystore files. Not changed after initial installation of InfoSphere Information Server.

Databases that must be backed up
Table 5. Databases that must be backed up
Repository or database Description Default database name/schema name
Metadata repository Stores the metadata about external data sources that are governed, managed, and analyzed by InfoSphere Information Server components. Default database name: XMETADefault schema name: User-defined schema user name, typically XMETA




4. Restoring IBM InfoSphere Information Server components
Files, directories, and databases that are associated with IBM InfoSphere Information Server and its components can be restored to recover from an event in which data was lost.

When you restore an installation, all of the same elements that were backed up need to be restored during the same restore session. Restore all elements before you start IBM WebSphere Application Server or InfoSphere Information Server.


4.1 Prerequisites:
• Recovery of IBM InfoSphere Information Server can be done on a system where InfoSphere Information Server was previously installed and that a good backup was previously performed.
• Host name of the computer must be identical to that of the computer on which the backup was taken and that all components are being restored in the exact same location that they originally were in. If a different host name is used, the system is inoperable.
• During restoring an installation, all of the elements that were backed up must be restored before InfoSphere Information Server and IBM WebSphere® Application Server services get started.
4.2 Procedure:
• Disconnect all user sessions. Do not allow users to log in to the system at any point during the restore. Otherwise, it is possible that the restore might fail or users might lose data, which is overwritten when the metadata repository is restored.
• Stop the InfoSphere Information Server services and WebSphere Application Server services.
• Restore the metadata repository.
• Restore the operations database for Infosphere Datastage.
• Restore the system elements that are mentioned in the previous section of backing up IBM Infosphere components (Section 3).


• Restore external files or libraries that are used by IBM InfoSphere DataStage-file details are mentioned in the Back up section (Section 3).
• Restart the InfoSphere Information Server services and WebSphere Application Server services.

_________________
Rumu
IT Consultant
Rate this response:  
Not yet rated
Display posts from previous:       

Add To Favorites
View next topic
View previous topic
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum



Powered by phpBB © 2001, 2002 phpBB Group
Theme & Graphics by Daz :: Portal by Smartor
All times are GMT - 6 Hours