LogoLogo
25.1
25.1
  • Overview
  • Legal Notice
  • Release Notes
    • Previous versions
  • Glossary
  • Abbreviations
  • Getting Started
  • Supported versions
  • Quick Start Guide
  • Installation Guide
    • System Architecture
    • System Requirements
    • Prerequisites
    • Install migration-center
    • Install migration-center on AWS
    • Start migration-center
    • Access Network Shares
    • Upgrade migration-center
    • Backup and Restore
    • Java configuration
    • Uninstall migration-center
  • WebClient User Guide
    • TR Function Reference
  • Third Party Open Source Libraries
  • Administration
  • Oracle Database Creation
  • Database Administrator’s Guide
  • Jobserver Administrator's Guide
  • WebClient Administrator's Guide
  • Oracle Sizing Guide
  • Time zone handling
  • Documentum security enhancements
  • Common Parameters
  • Scanners
    • Amazon Comprehend Enrich Scanner
    • Alfresco Scanner
    • CSV & Excel Scanner
    • Database Scanner
    • Documentum Scanner
    • Documentum NCC Scanner
    • Domino Scanner
    • Exchange Scanner
    • Filesystem Scanner
    • OpenText Scanner
    • Outlook Scanner
    • SharePoint Scanner
    • SharePoint Online Scanner
    • Veeva Scanner
  • Importers
    • Alfresco Importer
    • Alfresco CS Importer
    • AzureBlob Importer
    • Box Importer
    • Cara Importer
    • D2 Importer
    • D2 InPlace Connector
    • Documentum Importer
    • Documentum InPlace Connector
    • Documentum NCC Importer
    • Filesystem Importer
    • Hyland OnBase Importer
    • InfoArchive Importer
    • OpenText Importer
    • OpenText InPlace Connector
    • SharePoint Importer
    • SharePoint Online Importer
    • SharePoint Online Batch Importer
    • TrackWise Importer
    • Veeva Importer
Powered by GitBook
On this page
  • Backup a migration-center database
  • Restore a migration-center database

Was this helpful?

Export as PDF
  1. Installation Guide

Backup and Restore

Was this helpful?

Since in migration-center all the critical data and configuration is saved in the database, only backing up the migration-center database schema is needed.

Backup a migration-center database

Before starting the backup process ensure that there are no scanners, importers, transformation / validation jobs and no scheduled jobs running

To back up a database used by migration-center it is sufficient to back up only the data within the FMEMC schema. The easiest way to do this is with Oracle’s EXP. See screen shot below for the basic steps required to back up a schema. For more information consult the documentation provided by Oracle.

Starting with Oracle 11g release 2, the empty table might not be exported at all. This happens when the database parameter DEFERRED_SEGMENT_CREATION is set to TRUE. Initially this parameter is set to TRUE. To force exporting all tables from the FMEMC schema the following commands should be run connected as user FMEMC: ALTER TABLE SCHEDULER_RUNS ALLOCATE EXTENT; ALTER TABLE SCHEDULERS ALLOCATE EXTENT;

Restore a migration-center database

To restore the backup, follow the steps below:

  2. Use Oracle’s “imp” utility for importing the dump file previously created by the “exp” utility. See screen shot below for the basic steps required to restore a database schema from a dump file. For more information consult the documentation provided by Oracle.

The same character sets in the Oracle Client should be used when exporting and importing the data.

If the database instance where the backup should be restored does not contain the FMEMC user, please create it first as it this describe in the .

Installation Guide