Moving files when the source and target databases are not physically connected

If migrating to the cloud or a separate data center where two instances of BMC Helix Data Manager are installed, the export package must be copied to the target BMC Helix Data Manager infrastructure. You should scan the migration package before importing.

Scanning the file system is also a useful way to validate the file system connection details.

To scan a file system

1. Select Configuration > Configure File System Connections.
2. Click the Defined File Systems tab, and select a data package.
3. Click the Data Packages tab.

4. Select Action > Scan File System.
   The following data is shown for the selected data package on the Summary sub-tab:

   Field	Description
   Export Date	The date and time that BMC Helix Data Manager created this package.
   Status	The status of the data package. The possible values are: In Progress—BMC Helix Data Manager is creating the package. Complete—The package is fully complete.
   File Format	The type of data package. Options are: Data Dump—A native Oracle export that is intended for import into an Oracle system. Flat—Contains flat files. This format is used when migrating between MS SQL systems, migrating between database types, or when performing JDBC Oracle to Oracle migrations.
   Integrity	Indicates whether all expected files are in the data package folders. BMC Helix Data Manager automatically checks the XML descriptor for a data package against the files in the file system to ensure that no files are missing.
   Incremental	Indicates whether the data package was created by using the Incremental data migration option.
   Records	The number of BMC Helix ITSM records across all forms or tables in the data package.
   Forms or Tables	The number of forms or tables in the data package.
   Migration Pack	The name of the migration pack used to export the data in this data package. This migration pack must exist in the instance of BMC Helix Data Manager used to import the package.
   Source System	The name of the BMC Helix ITSM system from which the data in the data package was exported.
   Source Data Dictionary	The name of the data dictionary that was used to define the forms and fields or tables in the scope of the export that created this package.
   Target System	The name of the BMC Helix ITSM system into which the data package is intended to be imported into. The package can be imported into any BMC Helix ITSM system that shares the same data dictionary as the original target system.
   Target Data Dictionary	The name of the data dictionary that defines the forms and fields or tables in the scope of the import.
   Folder Name	The name of the folder on the file system that holds all the data for the data package.

5. To browse the forms or tables that were exported and view the individual files associated with each form or table, click the Content tab.
   

6. Select a form or table from the tree to show the following details:

   Field	Description
   Source Form or Source Table	The name of the form or table from which data was exported.
   Target Form or Target Table	The name of the form or table into which this data can be imported.
   Records	The number of records exported.
   Mode	The mode used to export this data. Options are: Tree—Exported with respect for the tree structure and automatically filtered by any relationship to the parent form or table. Flat—All records for this form or table were exported. This disregards relationships to parent forms or tables and will only export the form or table once. If the form or table appears in multiple locations in the tree, it is exported only once.
   Export Status	Indicates whether this export was successful.
   Runtime Qual	The qualification used at export time to extract the records. The example above shows that the COM:Company form was filtered to include only non-system companies and with an Enabled Status.

   The Info tab shows the help text for the selected form or table, explaining its purpose.

7. To load the T-table data into a temporary table in any system, click the Stage Data button.

8. To view the list of files associated with the selected form or table, click the Files tab.
   
   The following details are displayed for each file:

   Field	Description
   File Name	The unique name for the file in the data package.
   Type	The type of data held by the file. Possible values are: Data—The main data for the form or table. History—The Status History data for the form or table. Attachment—The main attachment data for the form or table. Attachment Field—The data for a particular attachment field. Group Cache—Data from the Group Cache table related to records in this form or table. User Cache—Data from the User Cache table related to records in this form or table.
   Size	The size of the file in KB, MB, or GB.
   Status	The status of the file. Possible values are: Available—The file is present in the data package folders. Missing—The file is missing. A missing file causes import errors and is typically caused by manual removal of the file from the file system after the initial export. Unknown—The package is in the process of being built and BMC Helix Data Manager has not yet verified the file is present on the file system.

To import a data package

1. Select Configuration >Configure File System Connections.
2. Click the Defined File Systems tab, click the Data Packages tab below, and select a data package.
3. From the Action menu located at the bottom right of the list of data packages, select Import Data Package.
4. If the data package is associated with an existing migration job, click one of the following options:
   • Open Migration Job—Uses the existing migration job.
   • Confirm Import—Creates a new import job.
     
5. If the data package is not associated with an existing migration job (for example, the data package was created using another instance of BMC Helix Data Manager), select the system and the migration pack, and click Confirm Import.
   
   To import data, you must create an import job. You cannot import a data package that was created with another instance of BMC Helix Data Manager unless the same migration pack used to export the data is imported into the local instance of BMC Helix Data Manager. For more information, see Viewing-metadata-files and Importing-template-migration-packs.

To delete a data package

1. Select Configuration > Configure File System Connections.
2. Click the Defined File Systems tab, and select a data package.
3. From the selected file system, click the Data Packages tab, and select the data package. 
4. From the Action menu located at the bottom right of the list of data packages on the Data Package page, select Delete Data Package.
5. Confirm the operation.
   BMC Helix Data Manager Engine will perform the deletion and track it as an activity.