Enterprise Data Preparation Administrator Guide > Backing Up and Restoring Enterprise Data Preparation > Back Up Enterprise Data Preparation
  

Back Up Enterprise Data Preparation

Back up the application service metatdata, repositories, and storage locations associated with Enterprise Data Preparation.
You do not need to complete the back up procedures in sequence. However, you should disable the Enterprise Data Preparation Service and the associated application services before performing a back up procedure.

Step 1. Disable the Application Services

Disable the Enterprise Data Preparation Service and all associated application services.
You use Informatica Administrator (the Administrator tool) to disable the application services. You can also use the Administrator tool to identify the application services used by the Enterprise Data Preparation Service.
Disable the application services in the following order:
    1. In the Administrator tool, select the Services and Nodes view.
    2. In the Domain Navigator, select the Enterprise Data Preparation Service.
    3. Click the Disable the Service button, and then disable the application service.
    4. In the Properties view, click each application service associated with the Enterprise Data Preparation Service, and then disable the service.

Step 2. Back Up the Model Repository Content

Back up the content of the Model repository associated with the Enterprise Data Preparation Service. The Model repository stores project definitions and transient publication mappings associated with projects created by analysts in Enterprise Data Preparation.
Use the Administrator tool to identify the Model Repository Service associated with the Enterprise Data Preparation Service. You also use the Administrator tool to back up the Model repository. When you back up a Model repository, the Model Repository Service writes the repository contents to a backup file in the service backup directory. The service backup directory is a subdirectory of the node backup directory.
    1. In the Administrator tool, select the Services and Nodes view.
    2. In the Domain Navigator, select the Enterprise Data Preparation Service.
    3. In the Properties view, expand Model Repository Service Options.
    4. Select the Model Repository Service.
    5. On the Manage tab Actions menu, select Repository Contents > Back Up.
    The Back Up Repository Contents dialog box appears.
    6. Enter the options required to back up the Model Repository Service.
    The following table describes the options required to back up the Model Repository Service:
    Option
    Description
    Username
    User name of any user in the domain.
    Password
    Password of the domain user.
    SecurityDomain
    Domain to which the domain user belongs. Default is native.
    Output File Name
    Name of the backup file.
    Description
    Description of the contents of the backup file.
    7. Click Overwrite to overwrite a file with the same name.
    8. Click OK.
    The Model Repository Service writes the backup file to the service backup directory.

Step 3. Document the Configuration Properties for the Scanner Resources

Document the configuration details for each Hive scanner resource and each HDFS scanner resource configured in the Enterprise Data Catalog used by the Enterprise Data Preparation Service.
Use the Administrator tool to identify the Catalog Service associated with the Enterprise Data Preparation Service. Use the Catalog Administrator to find the configuration properties for each scanner resource.
    1. In the Administrator tool, select the Services and Nodes view.
    2. In the Domain Navigator, select the Enterprise Data Preparation Service.
    3. In the Properties view, expand Catalog Service Options.
    4. Select the Catalog Service.
    5. Click the Catalog Administrator URL.
    The URL has the following format:
    <Catalog Service host name>:<Catalog Service port>/ldmadmin
    6. In Catalog Administrator, click Open.
    The Library view opens.
    7. Select a scanner resource.
    8. Document the properties shown on each tab in Catalog Administrator.

Step 4. Back Up the Enterprise Data Preparation Connections

Back up the connection objects for the HDFS, Hive, and Hadoop connections used by the Enterprise Data Preparation Service.
Use the infacmd isp ExportDomainObjects command to export the connection object for each connection to an .xml file.
You can create an export control file to filter the objects to export from the domain. An export control file is an .xml file that you use with the infacmd isp ExportDomainObjects command. Specify the name of each connection object you want to export in an <objectList> element within the export control file.
The following example shows an export control file that filters the connection objects for the HDFS, Hive, and Hadoop connections used by the Enterprise Data Preparation Service:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<exportParams xmlns="http://www.informatica.com/tools/exportControl/9">
<objectList type="connection" >
<object name="HDFS_CCO" />
</objectList>
<objectList type="connection" >
<object name="HIVE_CCO" />
</objectList>
<objectList type="connection" >
<object name="HADOOP_CCO" />
</objectList>
</exportParams>
If you use an export control file, use the Administrator tool to find the name of each connection used by the Enterprise Data Preparation Service. If you do not use an export control file, the infacmd isp ExportDomainObjects command exports all native users, native groups, roles, connections, and cluster configurations from the Informatica domain.
For more information about creating export control files and using the infacmd isp ExportDomainObjects command, see the Informatica Command Reference.
    1. In the Administrator tool, select the Services and Nodes view.
    2. In the Domain Navigator, select the Enterprise Data Preparation Service.
    3. In the Properties view, expand Data Lake Options.
    4. Copy the values for the HDFS Connection, Hive Connection and Hadoop Connection properties.
    5. Expand Event Logging Options.
    6. Create an export control file to filter the objects that the infacmd isp ExportDomainObjects command exports.
    Specify the name of each connection object you want to export in an <objectList> element within the file.
    7. Run the following command:
    infacmd isp ExportDomainObjects -dn <domain name> -un <user name> -pd <password>
    -sdn <security domain> -fp <export file> -cp <export control file> -rp <true|false>
    The following table describes the infacmd isp ExportDomainObjects command options and arguments you might specify to export connection objects for the HDFS, Hive, and Hadoop connections:
    Option
    Argument
    Description
    -DomainName
    -dn
    domain_name
    Required. Name of the Informatica domain.
    -UserName
    -un
    user_name
    Required if the domain uses Native or LDAP authentication. User name to connect to the domain.
    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.
    -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.
    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.
    -ExportFile
    -fp
    export_file_name
    Required. Path and file name of the export file.
    If you do not specify the file path, infacmd creates the file in the directory where you run infacmd.
    -ExportControlFile
    -cp
    export_control_file
    Optional. Name and path of the export control file that filters the objects to export.
    -RetainPassword
    -rp
    true|false
    Optional. Set to true to retain encrypted passwords for users and connections in the exported file. When set to false, user and connection passwords are exported as empty strings. Default is false.
    The following example exports the connection objects for the HDFS, Hive, and Hadoop connections defined in the specified export control file:
    infacmd isp ExportDomainObjects -dn InfaDomain -un Administrator -pd password -fp
    "/backup/idl_connections.xml" -cp "/backup/idl_exportControl.xml" -rp true

Step 5. Back Up the Data Preparation Repository

Back up the MySQL database or the Oracle database used as the Data Preparation repository.
Use the Administrator tool to find the database type and schema name values configured for the repository database. Follow the instructions in the MySQL documentation or the Oracle documentation to back up the repository database.
    1. In the Administrator tool, select the Services and Nodes view.
    2. In the Domain Navigator, select the Interactive Data Preparation Service.
    3. In the Properties view, expand Data Preparation Repository Options.
    4. Find the values for the Database Type and Schema Names properties configured for the repository database.
    5. Back up the Data Preparation repository database.
    For more information, see the MySQL documentation or the Oracle documentation.

Step 6. Back Up the Interactive Data Preparation Service Durable Storage

Back up the HDFS location where the Interactive Data Preparation Service stores data.
Use the Administrator tool to find the durable storage configuration properties. You can use the Hadoop DistCp tool to export the storage metadata to a backup location.
    1. In the Administrator tool, select the Services and Nodes view.
    2. In the Domain Navigator, select the Interactive Data Preparation Service.
    3. In the Properties view, expand Data Preparation Storage Options, and then document the durable storage configuration properties.
    4. On the HDFS cluster, run the following command:
    hadoop distcp hdfs://<durable storage location> <local file system location>
    The following table describes the DistCp command arguments:
    Argument
    Description
    Durable Storage Location
    The HDFS storage location to back up. Specify the value of the HDFS Storage Location property displayed in the Administrator tool.
    Backup Location
    The path to the backup directory to which to write the storage metadata.

Step 7. Back Up the Rules Metadata

If rules are configured for the Interactive Data Preparation Service, back up the rules metadata stored in the Model repository that contains rule objects and metadata.
The rules metadata is stored in projects in the Model repository. Use the Administrator tool to find the Model Repository Service used by the Interactive Data Preparation Service. Use the infacmd tools ExportObjects command to export the rule objects, the dictionary content, and the NER and Classifier model files from a project in the Model repository.
The infacmd tools ExportObjects command creates an .xml file that contains the rule objects. The command also creates a .zip file containing the dictionary content as .dic extension flat files and the NER and Classifier models as .ner and .classifer files.
Run the infacmd tools ExportObjects command to export rules metadata from each project that contains rules metadata. When you run the command, you specify the name of a project that contains the rule objects. You also specify the name of the Model Repository Service that manages the Model repository that contains the project. The Model Repository Service must be running when you run the command.
You can create an export control file to filter the objects to export from the Model repository. An export control file is an .xml file that you use with the infacmd tools ExportObjects command. Specify the name of each rule object you want to export in an <objectList> element within the export control file.
The following example shows an export control file that filters the rule objects to export from the Model repository:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<exportParams xmlns="http://www.informatica.com/tools/exportControl/9">
<folders>
<folder recursive="false" select="all">
<objectList type="Rule" >
<object name="validate_address" />
</objectList>
<objectList type="Rule" >
<object name="validate_USA_zip_code" />
</objectList>
<objectList type="Rule" >
<object name="validate_Canadian_postal_code" />
</objectList>
</folder>
</folders>
</exportParams>
If you do not use an export control file, the infacmd tools ExportObjects command exports all objects in the specified project.
For more information about creating export control files and using the infacmd tools ExportObjects command, see the Informatica Command Reference.
    1. In the Administrator tool, select the Services and Nodes view.
    2. In the Domain Navigator, select the Enterprise Data Preparation Service.
    3. In the Properties view, expand Interactive Data Preparation Service Properties.
    4. Select the Interactive Data Preparation Service shown.
    5. In the Properties view, expand Model Repository Service Properties to identify the Model Repository Service used by the Interactive Data Preparation Service.
    You must identify each project within the Model repository that contains rules metadata.
    6. If the Model Repository Service is not running, recycle the Model Repository Service.
    For more information, see Step 6. Recycle the Application Services.
    7. Run the following command:
    infacmd tools ExportObjects -dn <domain name> -un <user name> -pd <password>
    -sdn <security domain> -pn <project name> -rs <Model Repository Service name>
    -fp <export file> -ow <true|false> -cp <export control file> -oo <options>
    The following table describes infacmd tools ExportObjects options and arguments you might specify to back up the Content Management Service metadata:
    Option
    Argument
    Description
    -DomainName
    -dn
    domain_name
    Name of the Informatica domain.
    -UserName
    -un
    user_name
    User name to connect to the domain. Optional if the domain uses Kerberos authentication.
    -Password
    -pd
    password
    Password for the user name.
    -SecurityDomain
    -sdn
    security_domain
    Name of the security domain to which the domain user belongs.
    -ProjectName
    -pn
    project_name
    Name of the project in the Model repository from which to export the rules metadata.
    -RepositoryService
    -rs
    service_name
    Model Repository Service name.
    -ExportFilePath
    -fp
    export_file_path
    Path and XML file name of the export file that contains the rules metadata. You can specify an absolute path or a relative path to the file name.
    -OverwriteExportFile
    -ow
    true|false
    Set to true to overwrite an existing export file. Default is false.
    -ControlFilePath
    -cp
    control_file_path
    Path and file name of the export control file that filters the exported objects.
    -OtherOptions
    -oo
    options
    Additional options to export the dictionary content and the NER and Classifier models to a zip file. Enter options using the following format:
    rtm:<option_name>=<value>,<option_name>=<value>
    Option names include:
    • - codePage. Code page of the reference data.
    • - refDataFile. Path and file name of the zip file where you want to export the reference table data.
    The following example exports the rules objects defined in the specified export control file from a project named TEST_PROJECT to the dq_rules_metadata.xml file. The example also exports the dictionary content and the NER and Classifier models from the project named TEST_PROJECT to a dq_rules_artifacts.zip file.
    infacmd tools exportObjects -dn InfaDomain -un Administrator -pd password -sdn native
    -pn TEST_PROJECT -rs MRS_dev2 -fp "/export/dq_rules_metadata.xml" -ow true
    -cp "/dq_rules_export.xml" -oo "rtm:codePage=UTF-8,refDataFile="/output/dq_rules_artifacts.zip""