Table of Contents

Search

  1. Preface
  2. Command Line Programs and Utilities
  3. Installing and Configuring Command Line Utilities
  4. Using the Command Line Programs
  5. Environment Variables for Command Line Programs
  6. Using infacmd
  7. infacmd as Command Reference
  8. infacmd aud Command Reference
  9. infacmd autotune Command Reference
  10. Infacmd bg Command Reference
  11. infacmd ccps Command Reference
  12. infacmd cluster Command Reference
  13. infacmd cms Command Reference
  14. infacmd dis Command Reference
  15. Infacmd dis Queries
  16. infacmd dp Command Reference
  17. infacmd idp Command Reference
  18. infacmd edp Command Reference
  19. Infacmd es Command Reference
  20. infacmd ics Command Reference
  21. infacmd ipc Command Reference
  22. infacmd isp Command Reference
  23. infacmd ldm Command Reference
  24. infacmd mas Command Reference
  25. infacmd mi Command Reference
  26. infacmd mrs Command Reference
  27. infacmd ms Command Reference
  28. infacmd oie Command Reference
  29. infacmd ps Command Reference
  30. infacmd pwx Command Reference
  31. infacmd roh Command Reference
  32. infacmd rms Command Reference
  33. infacmd rtm Command Reference
  34. infacmd sch Command Reference
  35. infacmd search Command Reference
  36. infacmd sql Command Reference
  37. infacmd tdm Command Reference
  38. infacmd tools Command Reference
  39. infacmd wfs Command Reference
  40. infacmd ws Command Reference
  41. infacmd xrf Command Reference
  42. infacmd Control Files
  43. infasetup Command Reference
  44. pmcmd Command Reference
  45. pmrep Command Reference
  46. Working with filemanager
  47. Working with pmrep Files

restoreContents

restoreContents

Restores the catalog data.
Before you restore the catalog data, you need set the following environment variables:
  • INFA_TRUSTSTORE. See the following sample command to set the variable:
    export INFA_TRUSTSTORE= <Location of the Informatica truststore file>
    . Default location is
    $INFA_HOME/services/shared/security
    .
  • INFA_KEYSTORE. See the following sample command to set the variable:
    export INFA_KEYSTORE=<Location of the keystore file>
    . Default location is
    $INFA_HOME/services/shared/security
    . This variable is required only if you used custom SSL configuration for the Informatica domain. For default SSL and non-SSL configurations, you must unset the variable.
  • Encrypted INFA_TRUSTSTORE_PASSWORD. Encrypt the password that you set. See the following sample command to set the encrypted password:
    export INFA_TRUSTSTORE_PASSWORD="84Ve/soUbpQ/Aae5uGKXQA=="
    .
  • Encrypted INFA_KEYSTORE_PASSWORD. Encrypt the password that you set. See the following sample command to set the encrypted password:
    export INFA_KEYSTORE_PASSWORD="6cDE/ItyUL/Rtui9nhVRI=="
    . This variable is required only if you used custom SSL configuration for the Informatica domain. For default SSL and non-SSL configurations, you must unset the variable.
See the sample command to encrypt password: $INFA_HOME/server/bin/pmpasswd <password>
For example,
  • export INFA_KEYSTORE_PASSWORD=hQDP8O8tfwxRSwbeANEptl4AIQqJcSj9ZMDkVK+9S+Y=
  • export INFA_TRUSTSTORE_PASSWORD=hx/nRWisSjnQ0zEGV3N7j1FCGFOm5RfisQxKTdf5f8Y=
  • export INFA_TRUSTSTORE=/data/Informatica/LDM1051/services/shared/security/
  • export INFA_KEYSTORE=/data/Informatica/LDM1051/services/shared/security
Note the following points before you run this command:
  • The restoreContents command requires the INFA_KEYSTORE and INFA_KEYSTORE_PASSWORD environment variables to connect to Solr and MongoDB services of Informatica Cluster Service.
  • You should not use the restoreContents command to restore one node backup in multinode setup. The constraint applies to the SEARCH store restore option.
  • Set the INFA_TRUSTSTORE and INFA_TRUSTSTORE_PASSWORD environment variables on both SSL and non-SSL enabled Informatica domain.
  • If Solr is installed on multi-node setup, you need to configure the
    ClusterSharedFilesystemPath
    option in Informatica Cluster Service to restore the Solr.
You cannot use catalog data from the current version to restore data for a previous version. However, if you have applied a cumulative patch release or a service pack, you can use the existing catalog data to restore data for a previous version.
You must verify that the base versions are the same for both the existing and previous versions.
The
infacmd ldm restoreContents
command uses the following syntax:
restoreContents <-DomainName|-dn> domain_name <-UserName|-un> user_name <-Password|-pd> password <-ServiceName|-sn> service_name [<-SecurityDomain|-sdn> security_domain] [<-ResilienceTimeout|-re> timeout_period_in_seconds] <-InputFileName|-if> input_file_name (Complete path of backup ZIP file on local machine. The content of ZIP file will be copied to cluster.) [<-Force|-fr> force(This is to forcefully clean the existing contents of cluster where data is to be restored and restore the backup data from scratch)]
The following table describes infacmd ldm restoreContents options and arguments:
Option
Argument
Description
-DomainName
-dn
domain_name
Required. Name of the Informatica domain. You can set the domain name with the -dn option or the environment variable INFA_DEFAULT_DOMAIN. If you set a domain name with both methods, the -dn option takes precedence.
-UserName
-un
user_name
Required if the domain uses Native or LDAP authentication. User name to connect to the domain. You can set the user name with the -un option or the environment variable INFA_DEFAULT_DOMAIN_USER. If you set a user name with both methods, the -un option takes precedence.
Optional if the domain uses Kerberos authentication. To run the command with single sign-on, do not set the user name. If you set the user name, the command runs without single sign-on.
-Password
-pd
password
Required if you specify the user name. Password for the user name. The password is case sensitive. You can set a password with the -pd option or the environment variable INFA_DEFAULT_DOMAIN_PASSWORD. If you set a password with both methods, the password set with the -pd option takes precedence.
-ServiceName
-sn
service_name
Required. Catalog Service name.
-SecurityDomain
-sdn
security_domain
Required if the domain uses LDAP authentication. Optional if the domain uses native authentication or Kerberos authentication. Name of the security domain to which the domain user belongs. You can set a security domain with the -sdn option or the environment variable INFA_DEFAULT_SECURITY_DOMAIN. If you set a security domain name with both methods, the -sdn option takes precedence. The security domain name is case sensitive.If the domain uses native or LDAP authentication, the default is Native. If the domain uses Kerberos authentication, the default is the LDAP security domain created during installation. The name of the security domain is the same as the user realm specified during installation.
-ResilienceTimeout
-re
timeout_period_in_seconds
Optional. Amount of time in seconds that infacmd attempts to establish or reestablish a connection to the domain. You can set the resilience timeout period with the -re option or the environment variable INFA_CLIENT_RESILIENCE_TIMEOUT. If you set the resilience timeout period with both methods, the -re option takes precedence.
-InputFileName
-if
input_file_name
Required. Complete path of backup .zip file on the Catalog Service host.
-Force
-fr
force
Optional. Use this option to forcefully clean the existing contents of the Informatica cluster where data is to be restored and restore the backup data from scratch.
If the backup does not contain the SEARCH store, you must recycle the Informatica Cluster Service and then re-index the Catalog Service to populate the data for Apache Solr.
Effective in Enterprise Data Catalog version 10.5.1.1, you can see the status of the restore operation in the following log file on the node where you run the command:
<Informatica installation directory>/logs/<Node name>/services/CatalogService/<Catalog Service name>/LDMRestore.log
. The maximum file size for each log file is 100 MB. After the maximum file size is reached, a new file is created. The maximum number of log files that are stored is 20. After this limit is reached, the oldest log file is replaced with the latest log file.

0 COMMENTS

We’d like to hear from you!