Backup and Restore
The backup and restore at DB level will function correctly if the tenant ids do not change. By backing up the DB the MDM state is completely saved and can be restored later.
Cloning database
As for backup and restore, cloning also works as expected by cloning the database tables, as long as the tenant ids do not change. All the environment variables have to be updated accordingly and a MDM instance can be cloned to a new host and a new database by cloning the MDM database tables.
If the tenant ids will change between the source and destination in a cloning process, then some additional scripts need to be applied to replace the tenant in all tables. Please contact the MDM development team in this case.
Tables
The following tables need to be backed up (or cloned) in order to have all the MDM data.
-
__EFMigrationsHistory
-
MDM_DeviceCustomPropertyValues
-
MDM_Devices
-
MDM_DeviceSupplements
-
MDM_DeviceTags
-
MDM_DeviceTypeCustomProperties
-
MDM_DeviceTypes
-
MDM_Errors
-
MDM_ErrorSupplements
-
MDM_ErrorTranslations
-
MDM_Facilities
-
MDM_FacilityCustomPropertyValues
-
MDM_FacilityIdentifiers
-
MDM_FacilitySupplements
-
MDM_FacilityTags
-
MDM_FacilityTranslations
-
MDM_FacilityTypeCustomProperties
-
MDM_FacilityTypes
-
MDM_FacilityTypeSupplements
-
MDM_FacilityTypeTranslations
-
MDM_Materials
-
MDM_MaterialProperties
-
MDM_MaterialTranslations
-
MDM_MaterialType
-
MDM_MaterialTypeTranslations
-
MDM_MeasuringPoints
-
MDM_MeasuringPointSupplements
-
MDM_MeasuringPointTranslations
-
MDM_Relations
-
MDM_SyncConfigurations
-
MDM_SyncJobs
-
MDM_SyncLogs
-
MDM_SyncRegistrations
-
MDM_Tags
-
MDM_TagTags
-
MDM_TagTranslations
-
MDM_TenantState
-
Processes
-
ProcessesDescription
-
ProcessesName
-
ProcessGroups
-
ProcessGroupNames
-
ProcessGroupDescriptions
-
ProcessProcessGroup
-
ProcessFacilities
-
ProcessProcessFacility
-
ProcessTags
-
ProcessProcessTag