Migration Scenarios Using Simple Mode and Advanced Mode

this section shows the steps to take when migrating data in different scenarios and when disabling the ivanti service manager development project and using simple mode and advanced mode it skips the conceptual information and only shows the procedure steps see appendix b migrating data from one tenant instance to another using simple mode or advanced mode docid\ stq b6ebnoc64jdl9kbiz for conceptual information and details about these steps these examples migrate data by disabling the ivanti service manager development project and using simple mode and advanced mode migrating data from the production instance of the tenant to the staging or uat instance of the tenant docid\ t9nc3i l41hfwpczkgbuirefreshing the staging or uat instance of the tenant docid\ t9nc3i l41hfwpczkgbuiperforming a quick migration from the staging or uat instance to the production instance docid\ t9nc3i l41hfwpczkgbuimigrating certain types of metadata and validation data from the staging or uat instance to the production instance, or from the staging instance to the uat instance docid\ t9nc3i l41hfwpczkgbuimigrating certain types of metadata, validation data, and master data from the staging or uat instance to the production instance, or from the staging instance to the uat instance docid\ t9nc3i l41hfwpczkgbuimigrating only transactional data from the staging or uat instance to the production instance, or from the staging instance to the uat instance docid\ t9nc3i l41hfwpczkgbuioverwriting all metadata and validation data from the staging or uat instance to the production instance, or from the staging instance to the uat instance docid\ t9nc3i l41hfwpczkgbuimigrating configuration data (settings) from the staging or uat instance to the production instance, or from the staging instance to the uat instance docid\ t9nc3i l41hfwpczkgbuiexample migrating service level data docid\ t9nc3i l41hfwpczkgbui migrating data from the production instance of the tenant to the staging or uat instance of the tenant in this scenario, you are just starting out and have only created an initial production instance of your tenant log in to the operations console and click the tenants tab navigate to the landscape you will perform the migration in and click manage migration click push in the arrow representing the migration path to use (see migration dashboard docid\ nk99nfacluuwabumozwcu in starting the data migration docid\ nk99nfacluuwabumozwcu ) the system displays the copy source tenant instance to target tenant instance (for example, copy production to staging ) dialog box enter the following information for the first data migration to a tenant instance select an option in the target db option field in the target db server field, if the target landscape contains more than one database server, select the server that hosts the ivanti service manager configuration database (optional) check keep existing users enabled in the target tenant to keep all the users, and not just the administrators, active (optional) check scrub email address in users to scrub user emails (optional) check scrub email address in other places to scrub email accounts saved in transactional data (optional) check trim data to keep last 90 days only to only copy transactional data that was created or modified within the last 90 days do not check this option if you are creating the database from the sample ("out of the box") database, because the records are likely to be older than 90 days in the sample database (optional) check shrink database after scrubbing and trimming to truncate unnecessary data when the tenant instance is created from a backup click execute refreshing the staging or uat instance of the tenant in this scenario, you have a database on the staging or uat instance of the tenant and you want to update it with the latest version from the production instance of the tenant log in to the operations console and click the tenants tab navigate to the landscape you will perform the migration in and click manage migration click push in the arrow representing the migration path to use (see migration dashboard docid\ nk99nfacluuwabumozwcu in starting the data migration docid\ nk99nfacluuwabumozwcu ) the copy source tenant instance to target tenant instance (for example, copy production to staging ) dialog box appears enter the following information for the first data migration to a tenant instance select an option in the target db option field in the target db server field, if the target landscape contains more than one database server, select the server that hosts the ivanti service manager configuration database (optional) check keep existing users enabled in the target tenant to keep all the users, and not just the administrators, active (optional) check scrub email address in users to scrub user emails (optional) check scrub email address in other places to scrub email accounts saved in transactional data (optional) check trim data to keep last 90 days only to only copy transactional data that was created or modified within the last 90 days (optional) check shrink database after scrubbing and trimming to truncate unnecessary data when the tenant instance is created from a backup click execute performing a quick migration from the staging or uat instance to the production instance log in to the operations console and click the tenants tab navigate to the landscape you will perform the migration in and click manage migration click push in the arrow representing the migration path to use (see migration dashboard docid\ nk99nfacluuwabumozwcu in starting the data migration docid\ nk99nfacluuwabumozwcu ) the copy source tenant instance to target tenant instance (for example, copy staging to production ) dialog box appears in the copy dialog box, make these selections do not check advanced mode (optional) check skip target tenant backup before operation to not perform a database backup (optional) under copy the following selected data , check service request if you want to migrate service request information, and check escalation schedule if you want to migrate escalation schedule information click execute migrating certain types of metadata and validation data from the staging or uat instance to the production instance, or from the staging instance to the uat instance log in to the operations console and click the tenants tab navigate to the landscape you will perform the migration in and click manage migration click push in the arrow representing the migration path to use (see migration dashboard docid\ nk99nfacluuwabumozwcu in starting the data migration docid\ nk99nfacluuwabumozwcu ) the copy source tenant instance to target tenant instance (for example, copy staging to production ) dialog box appears in the copy dialog box, check advanced mode in the copy dialog box, for the operation field, choose copy configuration (see copy dialog box (migrate metadata and validation data) docid\ stq b6ebnoc64jdl9kbiz in appendix b migrating data from one tenant instance to another using simple mode or advanced mode docid\ stq b6ebnoc64jdl9kbiz ) (optional) check skip target tenant backup before operation to not back up the target tenant instance prior to the data migration (optional) check the items to delete if those objects were deleted on the target tenant instance in the delete metadata items in target tenant instance that do not exist in source tenant instance section if you do not select any checkboxes in this section, all data is merged, and no data on the source tenant instance is deleted (optional) check the items under the replace metadata items in target tenant instance that are newer than those in source tenant instance section to delete items that exist on both the source tenant instance and the target tenant instance when the version on the target tenant instance is newer than the version on the source tenant instance if you do not select any checkboxes in this section, all data on the target tenant instance is overwritten by data from the source tenant instance (optional) check the items under the custom defined validation list data objects section to delete customized validation list items on the target tenant instance that were also deleted on the source tenant instance click execute migrating certain types of metadata, validation data, and master data from the staging or uat instance to the production instance, or from the staging instance to the uat instance log in to the operations console and click the tenants tab navigate to the landscape you will perform the migration in and click manage migration click push in the arrow representing the migration path to use (see migration dashboard docid\ nk99nfacluuwabumozwcu in starting the data migration docid\ nk99nfacluuwabumozwcu ) the system displays the copy source tenant instance to target tenant instance (for example, copy staging to production ) dialog box in the copy dialog box, check advanced mode the system displays more options in the dialog box in the copy dialog box, for the operation field, choose copy configuration & master data (see copy dialog box (migrate metadata, validation data, and master data) top half docid\ stq b6ebnoc64jdl9kbiz in appendix b migrating data from one tenant instance to another using simple mode or advanced mode docid\ stq b6ebnoc64jdl9kbiz ) fill in the top portion of the copy dialog box (the settings for metadata and validation data) as described in migrating certain types of metadata and validation data from the staging or uat instance to the production instance, or from the staging instance to the uat instance docid\ t9nc3i l41hfwpczkgbui (optional) check delete data items in target tenant instance that do not exist in source tenant instance to delete master data on the target tenant instance that was also deleted on the source tenant instance (optional) check any items under the copy the following selected data section to include them when the data is migrated (optional) select one or more items to migrate from the additional data list click execute migrating only transactional data from the staging or uat instance to the production instance, or from the staging instance to the uat instance log in to the operations console and click the tenants tab navigate to the landscape you will perform the migration in and click manage migration click push in the arrow representing the migration path to use (see migration dashboard docid\ nk99nfacluuwabumozwcu in starting the data migration docid\ nk99nfacluuwabumozwcu ) the system displays the copy source tenant instance to target tenant instance (for example, copy staging to production ) dialog box in the copy dialog box, check advanced mode in the copy dialog box, for the operation field, choose copy data only (see copy dialog box (migrate only transactional data) docid\ stq b6ebnoc64jdl9kbiz in appendix b migrating data from one tenant instance to another using simple mode or advanced mode docid\ stq b6ebnoc64jdl9kbiz ) (optional) check skip target tenant backup before operation to not back up the target tenant instance prior to the data migration (optional) check delete data items in target tenant instance that do not exist in source tenant instance under the data only copy options section to delete transactional data on the target tenant instance if that data was also deleted on the source tenant instance (optional) in the transactional data list, select the items to migrate click execute overwriting all metadata and validation data from the staging or uat instance to the production instance, or from the staging instance to the uat instance log in to the operations console and click the tenants tab navigate to the landscape you will perform the migration in and click manage migration click push in the arrow representing the migration path to use (see migration dashboard docid\ nk99nfacluuwabumozwcu in starting the data migration docid\ nk99nfacluuwabumozwcu ) the system displays the copy source tenant instance to target tenant instance (for example, copy staging to production ) dialog box in the copy dialog box, check advanced mode in the copy dialog box, for the operation field, choose copy to replace (see copy dialog box (to overwrite metadata and validation data) docid\ stq b6ebnoc64jdl9kbiz in appendix b migrating data from one tenant instance to another using simple mode or advanced mode docid\ stq b6ebnoc64jdl9kbiz ) enter the following information select an option in the target db option field in the target db server field, if the target landscape contains more than one database server, select the server that hosts the ivanti service manager configuration database (optional) check keep existing users enabled in the target tenant to keep all the users, and not just the administrators, active (optional) check scrub email address in users to scrub user emails (optional) check scrub email address in other places to scrub email accounts saved in transactional data (optional) check trim data to keep last 90 days only to only copy transactional data that was created or modified within the last 90 days (optional) check shrink database after scrubbing and trimming to truncate unnecessary data when the tenant instance is created from a backup (optional) check skip target tenant backup before operation to not back up the target tenant instance prior to the data migration click execute migrating configuration data (settings) from the staging or uat instance to the production instance, or from the staging instance to the uat instance log in to the operations console and click the tenants tab navigate to the landscape you will perform the migration in and click manage migration click push in the arrow representing the migration path to use (see migration dashboard docid\ nk99nfacluuwabumozwcu in starting the data migration docid\ nk99nfacluuwabumozwcu ) the system displays the copy source tenant instance to target tenant instance (for example, copy staging to production ) dialog box in the copy dialog box, check advanced mode in the copy dialog box, for the operation field, choose copy settings (see copy dialog box (migrate settings) docid\ stq b6ebnoc64jdl9kbiz in appendix b migrating data from one tenant instance to another using simple mode or advanced mode docid\ stq b6ebnoc64jdl9kbiz ) (optional) check skip target tenant backup before operation to not back up the target tenant instance prior to the data migration (optional) check delete setting records in target tenant that do not exist in source tenant to delete configuration data (settings) on the target tenant instance if that data was also deleted on the source tenant instance (optional) to update configuration data (settings) that has changed in both the source and the target tenant instances, check update setting records that changed in the setting type list, select the configuration data types (settings) to migrate click execute example migrating service level data this example shows how to migrate service level data such as service level agreements, operational level agreements, underpinning contracts, service level targets, and service level packages all of these are made up of master data and transactional data log in to the operations console and click the tenants tab navigate to the landscape you will perform the migration in and click manage migration click push in the arrow representing the migration path to use (see migration dashboard docid\ nk99nfacluuwabumozwcu in starting the data migration docid\ nk99nfacluuwabumozwcu ) the system displays the copy source tenant instance to target tenant instance (for example, copy staging to uat ) dialog box in the copy dialog box, for the operation field, select copy master data only (optional) check delete data items in target tenant instance that do not exist in source tenant instance to delete master data on the target tenant instance that was also deleted on the source tenant instance under the copy the following selected data section, check service request and escalation schedule from the additional data list, hold down the control key and select all of the following service agreement (serviceagreement) service level agreement (servicelevelagreement sla) service level objective (servicelevelobjective) service level package (servicelevelpackage) service level target (serviceleveltarget) service level target – general (serviceleveltargetgeneral) vendor (vendor) click execute