Simple steps to backup and restore the Repository and Domain configuration
• For domain backup you can use the infasetup.sh script with BackupDomain parameter.
sh
$INFA_HOME/server/infasetup.sh BackupDomain -da database_hostname:port
-du domain_db_user -dp domain_db_password -dt oracle -ds db_service_name
-bf DomainBackup.xml.mrep -dn Domain_name
• To restore the domain use the infasetup.sh script with RestoreDomain parameter.
sh
$INFA_HOME/server/infasetup.sh RestoreDomain -da database_hostname:port
-du database_db_user -dp domain_db_password -dt oracle -ds
db_service_name -bf DomainBackup.xml.mrep
• You can backup the repository in two ways.
1) Login to admin console.
2) Select Repository service
3) Select Backup contents under Actions menu to take backup by default Adminconsole creates the .rep file in to $INFA_HOME/server/infa_shared/Backup/
4) Restore contents under Actions menu to restore.
From pmrep utility on command line.
• Step1 : Connect to Informatica Repository Database Using pmrep utility.
$ pmrep connect -r REP_NAME -d DOMAIN_NAME -n Administrator -x PASSWORD
Informatica(r) PMREP, version [8.1.1 SP5], build [135.0129], SOLARIS 32-bit
Copyright (c) Informatica Corporation 1994 - 2008
All Rights Reserved.
This Software may be protected by U.S. Patent Numbers 6,208,990;
6,044,374; 6,014,670; 6,032,158; 5,794,246; 6,339,775, 6,850,947;
6,895,471, and other U.S. Patents Pending.
Invoked at Thu Jun 20 07:45:14 2013
Connected to repository REP_NAME in DOMAIN_NAME as user Administrator
connect completed successfully.
• Step 2 : Use the backup command to backup the repository.
By default pmrep utility backup the .rep file in to $INFA_HOME/server/infa_shared/Backup/
in case if you want to replace the existing .rep backup file use the -f option with the backup command. pmrep backup -o REP_NAME.rep -f which will replace the existing backup files in above directory.
$ pmrep backup -o REP_NAME.rep
Informatica(r) PMREP, version [8.1.1 SP5], build [135.0129], SOLARIS 32-bit
Copyright (c) Informatica Corporation 1994 - 2008
All Rights Reserved.
This Software may be protected by U.S. Patent Numbers 6,208,990;
6,044,374; 6,014,670; 6,032,158; 5,794,246; 6,339,775, 6,850,947;
6,895,471, and other U.S. Patents Pending.
Invoked at Thu Jun 20 07:45:37 2013
Back Up Contents operation on repository [REP_NAME] started at 06/20/2013 07:45:38.
Backing up repository contents to file [/application/informatica/infauser/PowerCenter9.1.1/server/infa_shared/Backup/REP_NAME.rep].
Backing up table OPB_SUBJECT
Backing up table OPB_DBD
Backing up table OPB_SCHEMA
Backing up table OPB_TARGINDEX
Backing up table OPB_TARGINDEXFLD
Backing up table OPB_PICDSC
Backing up table OPB_SRC_FLD
Backing up table OPB_SRC
• Step 3 : To restore the .rep file to repository.
pmrep restore -i REP_NAME.rep -u Admin_User -p Admin_Password
Its pretty clear shivakumar.....!! good one
ReplyDeleteShiva,
ReplyDeleteCan you send me the infasetp.sh script please.
Thx
Tienda
Tienda -
ReplyDeletePlease go to the cd $INFA_HOME/server/tomcat/bin you will find the script.
Many Thanks
Shivakumar
Hi,
ReplyDeleteWe've an Informatica project currently running. Server installed in Onsite and Client installed in offshore. Currently operational. Due to space limits we're going to move the Informatica to a new disk. Do we need to install informatica server and client once again in the new space freshly (provide domain, node configurations again)? is it like a fresh installation once again? pls let me know.
Actually the Infa version, database version remains same. All the domain info, repository info, users, roles stays same. we just need to move the entire infa thing to a new space (instead of space upgradation) since we want the infa to be in a new space.
i am not sure if we can tweak in some minor changes to the settings to make this happen or install informatica freshly in client side. the server is in unix.
Can we take backup of entire infa (all services like integration/repository/metadata services, directories, node, domain, repository content) from old space and just do a copy in the new space?
I understand that as far as the repository is concerned we can take backup of the old and place it in new space (but how?). Can you pls guide me on the steps that need to be followed for this purpose (through email)? that would be helpful to me. thanks.
rajesh.rangarao@yahoo.com
Hello Rajesh -
ReplyDelete• No need to install and build new infrastructure in case if your infrastructure is built with robust disk mirroring and cloning techniques.
• There are multiple mechanisms are available for copying the disk volumes to new disk groups and have the mirroring without damaging the Application Platforms built on it. Based on the Operating system which you have (Linux Red hat, Unix Solaris or Windows) and storage technology which your infrastructure is having currently (CDS) or (RIAD) there are cloning mechanism.
1. RAID – Redundant Array Of Independent Disks.
2. CDS – Cross Data Platforms from VERTAS.
• Suppose in case of server migration have your unix and storage team to export the NAS /SAN mounts from existing server and mount it back to the new server.
In above both the cases you will have to confirm with your server and storage teams on this.
Many Thanks
Shivakumar
Just wondering, I've seen older blogs where they say you have to delete the pmrep.cnx. These go back to Informatica 8.6.x. WIth Informatica 9.5.x, do you still need to delete this file?
ReplyDeleteCorrection...the pmrep.cnx file. I guess this used to get generated by connect command and if left, it could cause subsequent problems when backup is attempted again.
ReplyDeleteYes we need to delete pmrep.cnx this binary file holds connectivity information
ReplyDeleteevery time it will get update older one has to be removed for new connectivity
Many Thanks
Shivakumar
what are steps to install informatica in unix please can u share...,
ReplyDeleteVery useful text. Helped me much to migrate Domain from one database schema to another.
ReplyDeleteMany Thanks.
We use your script to backup domain logs. Our repository resides as a service in an Oracle grid.
ReplyDeleteWe use the -ds parameter to tell which service should be used. On the Oracle side we get messages that the call
-ds SRV_ET.world
is translated to
CONNECT_DATA=(SID=SRV_ET.world ...
in Oracle Listener Log, where it should be
CONNECT_DATA=(SERVICE_NAME=SRV_ET.world ...
Stefan
ReplyDeleteRemove the .world and try. Please post the complete error or else generate the log and send it to me.
Many Thanks
Shivakumar
Hi Shiva
ReplyDeleteIf a folder has been deleted by mistake - By restoring through repository backup file, all the folders would loose their latest changes, so would like to know if its possible to recover the folder alone - Please suggest how to recover the folder alone.
Hi Shobhan
DeleteAlways restore the backup to Temporary Repository or Lab environment from their migrate the folder to real Target Repository.
Thanks
Shiva
This did not hit my head. My problem is resolved now. - Thanks a lot Shiva.!!
DeleteHI Shiva
ReplyDeleteWe are not able to start the node, we are getting the below error. Thist started when the DBA team restored the system test DB with production data. They missed to preserve the sten domain and repository schema. I tried to restore the domain from the domain backup there also it throws the same error
Cannot start node due to the error: [[RSVCSHARED_00014] Internal error. The Repository Capability ['Persistence'] failed to initialize for the following reason: '[PERSISTENCEAPI_0307] [DBPERSISTER_1005] Failed to process requested operation. This was caused by result returns more than one elements'. Contact Informatica Global Customer Support.]--Raj
Dear Raj
DeleteStrongly suggest you to pls have a ticket with Informatica Vendor support.
Thanks
Shiva
This comment has been removed by the author.
ReplyDeleteHello,
ReplyDeleteI am aware that we can take domain backup through infasetup.sh script.
Anyone please confirm whether the domain backup can be done through Administrator?
Thanks,
Nambi.
Hi Nambi
DeleteOnly you can take repo backup from administrator console, you can't take the domain backup from admin console.