Migrate Content from Service

[#1]

This option allows you to migrate the contents of 12.3 and above version services.

To migrate Content from Service

1. Go to  (CONFIGURE) > Policies.
2. In the policies panel, click Content.
3. In the left panel, click Services. The list of services are displayed.
4. Select the services from which you want to migrate the content.

Note: By default, you can select up to 5 services for migration. This also includes the services which are under migration. However, you can modify this number from Admin -> Source Server -> Explore -> Central/Content -> Migration.

5. Click Migrate Content.

The Migrate Content from Service pop-up window is displayed.

6. On the Migrate Content from Service pop-up window, choose action and click Migrate.
   • If you select Create/Update Policy and Group for Each Service, policy and group will be created or updated for each service selected for migration. Once the migration process is complete, the policy and group will be listed under the respective listing pages. The policy and group which is created or updated for the service will be in 'Unpublished' state and it can be published only after it is reviewed. In the Policy Listing page, the Publish button for such a policy will be disabled until the policy is reviewed. The policy can be published only after reviewing it either from Policy Details page or Edit Policy Page. When the policy or group gets updated with the new content, the order of the new content will be given priority.
   • If you select Skip Creating/Updating a Policy and Group, only the content will be migrated. All the migrated content will be available in Content Library.

   Note:
   - If the service is assigned to a group which is not attached to any policy, then the Create/Update Policy and Group for Each Service is disabled.
   - When migrating content from two Decoders that have two different types of Custom or Live Base Parser associated with same Custom or Live Base Parser, both the Custom Parsers are added to Content Library. The association inside the Policy will be with the most recently migrated Custom Parser.
   - Within a migrated Policy, a Custom Parser will have only one Custom or Live Base Parser associated with it.
   - Migrated content version will be in the Policy, if as part of migration, the Policy is auto created. If you remove this content, you cannot add the old version of the content back.

   Note: If a service migration fails to update a policy:
   - You can edit the existing policy and add only the required content.
   - Remove the service that is part of a group and remigrate the content. This will only create a policy if the content number is less than 8000.

7. The migration initiation message is displayed on the screen. The Status column displays the following values based on the status of migration:

   • Queued

   • Initializing

   • Analyzing Content

   • Migrating Content

   • Migrated

   • Failed

   Note:
   - The service can also be remigrated if it is already migrated and assigned to groups and policies.
   - During parallel migration, if the selected services are updating common policies or using policies that are already being updated, you will receive a warning message on the screen. In such a scenario, it is recommended to update the policies through migration one service at a time to ensure that the last migrated service influences the policy in terms of order and version.

8. To view the migrated content details, do the following:
   • Click the View Content hyperlink present under the Action column. The hyperlink is available only after the migration process is complete.

   The View Migrated Content pop-up window is displayed with the different tabs such as Feed, Application Rule, Network Rule, Log Device and LUA Parser.

   

   Note:
   - Network Rules tab is not applicable for Log Decoders.
   - Log Device tab is not applicable for Decoders.

   IMPORTANT: During the process of migration, if a Decoder that is being migrated contains multiple application rules and/or network rules with the exact same rule name and rule condition, only one of those rules will be retained in the service. The remaining rules will be considered duplicates and removed. Therefore, post migration, none of the migrated services will have multiple rules with the same rule name and the same rule value.

   • Click  to search the migrated content based on various parameters.

   Note:
   - For Application Rule and Network Rule, the search is based on Rule Name and Rule Value.
   - For Feeds, Log Device and LUA Parser, the search is based on the Name.

   • Click each tab to view the content details. The Application Rule and Network Rule tabs will have details such as Rule Name, Rule Value, Medium, Order and Status. The Log Device, Feeds and LUA Parser tabs will have details such as Name, Medium and Status.

9. To view the error log details in case of failed migration, do the following:

   • Click the View Error Log hyperlink present under the Action column. The hyperlink is available only if the migration process has failed due to some reason.

   The Error Log pop-up window is displayed with the details of error.

   The following screen is displayed if no content is migrated to Content Library.

   

   Note: You should manually migrate the content in case of failed automated migration.

   The following screen is displayed if some content is migrated is Content Library.

   

   • To copy the error logs, click .
   • To retry migration, click Retry Migration.
   • In case of partial migration, to view the content that have been migrated successfully, do the following:
     • Click View Migrated Content. The View Migrated Content pop-up window is displayed with the details of migrated content.

     

     • To create policy and group for the service which is partially migrated, click Create Policy and Group.

     The Confirm Policy and Group Creation pop-up window is displayed.

     

     Best Practice Recommendation: Before creating policy and group for partially migrated service, it is recommended to retry migration.

     • To confirm creation of policy and group, click Confirm. The policy and group will be listed under the Policy Listing and Group Listing pages.
     • To go back to the Service List page, click Cancel.
     • If you do not want to create policy and group for partially migrated service, click Close in View Migrated Content pop-up window.
10. To cancel the migration, click Cancel in the Migrate Content from Service pop-up window.

Note: Migrated Live contents will be categorized as Custom contents, if:
- You have modified the Live content manually before migrating it.
- The migrated Live content is an older version of the content.

                                                  Previous Page                                            Next Page