Using DataMove with InterSystems IRIS

Migrate InterSystems IRIS namespace data by initializing a DataMove process to transfer globals, routines, and packages to a new database location. The process manages data integrity through validation and journaling while copying data in the background.

Yes, you can move namespace globals and routines without downtime using background copying processes and journaling. This ensures ongoing operations remain uninterrupted while data is transferred and validated in the new database location.

Yes, namespace data migration supports complex scenarios like mirrored systems and ECP environments. It provides specific APIs for mapping initialization, modification, and data transfer to ensure compatibility across these distributed architectures.

Ensure data integrity during an InterSystems IRIS database move by utilizing built-in validation and journaling mechanisms. These features track changes and verify data consistency throughout the background copying process.

Initialize a DataMove process for an InterSystems IRIS namespace by calling the provided APIs to define the move parameters, such as naming the DataMove instance and targeting the specific namespace like 'SALES' for transfer.

Use a dedicated namespace data migration process instead of manual copying to guarantee data consistency through automated validation, journaling, and background transfer APIs, which safely handle complex mirrored and ECP configurations.