Selections

Selections Overview & Migration Rules

Selections allow you to choose components for migration, providing granularity in selecting configurations, images, and other components.

• Selections are enabled after adding servers to Tranzman and completing Discovery.
• At least one migration pair (origin and destination) is required to enable selections.
• Multiple migration pairs can be created for complex scenarios (e.g., 2-to-1 migrations).

🛈 Selections should be modified only before the transition is started. Changes after transition will invalidate the existing license.

Creating Migration Pair

• Select origin and destination servers from the drop-down list.
• Navigate to Tasks → Selections and click Create a migration pair.
• For 2-to-1 migrations, create two selection pairs (each with an origin and destination).

Defining Rules for Selections

• Image Rules: Select images for migration (all or by properties like Backup Time, Expire Time, Policy, etc.).
• Config Object Rules: Granular selection of configuration objects (e.g., Workload, Residency).
• Rename Rules: Rename, map, or ignore configurations.
• Pre-Duplication & Duplication Rules: Define rules for duplicating image copies pre/post migration.
• Merge Configs: Migrate individual config entities and host properties.
• Verify: Check for inconsistencies and dependencies in selections.

🛈 Resolve all inconsistencies and dependencies for successful configuration migration.

Config Object Rules

• Click Config Object Rules under Selections tab.
• Tranzman pre-populates configurations by section.
• Select, deselect, or rename entities as needed.
• Click Commit to save selections.
• Use reset icon to revert to default selections.

Download selections using Download filter icon or upload a custom list via Upload filter icon.

Image Rules

• Granular selection of images for migration.
• Recommended to perform after Config Object Rules to avoid MISSING_XXX_MAPPING errors.
• Cannot be modified after transition starts (requires reverting appliance state).
• Consider already migrated images on destination before making changes.
• Click + to add image rules.

• Exclude specific images using Add Exclude Rule icon.

• Download/upload image rules as CSV. First line must define separator (e.g., sep=|).
• Inclusion: <serial num>|+|<criteria>, Exclusion: replace + with -.

Rename Rules

• Rename objects during migration (must be selected for migration).
• Map objects of same type (object must NOT be selected, new name must exist or be migrated).
• Exclude components using NOT_MIGRATED keyword (affects SLPs and DiskMediaIds).
• Highlight missing config by images not selected, renamed, or mapped (MISSING_XXXX_MAPPING).

Example: Excluding disk/tape backups with multiple copies. Only the copy on the excluded media will not be migrated; others remain on origin.

# bpimagelist -backupid qa-nbu812-o-lnx-g-e2e.devs.com_1692236444

IMAGE ...

HISTO ...

FRAG 1 ... @aaaab ...

FRAG 2 ... NBDB06 ...

#

Duplication Rules

• Define rules for duplication on Origin (pre-migration) or Destination (post-migration).
• Rules are based on images from the Origin.
• Cannot be modified after transition starts (requires reverting appliance state).
• If no rules are defined at start, action is paused; if added after, resume manually.

Merge Configs

• Lists all config settings between Origin and Destination.
• Use arrow to select origin setting and update destination.
• Use revert to undo changes.
• Custom values can be typed directly.
• Click Commit before navigating away or closing dialog.
• Handled during CreateConfig action; must be done before transition starts.

Verify

• Verify selected configuration objects, images, and rename rules.
• Validate server, SLP, and disk pool mappings.
• Check for valid config names in renames.
• Identify duplicate configuration objects needing rename or mapping.

Other Options in Selections

• Import empty media: Add empty (scratch) media to destination. Use only for same vendor transitions.
• Demote Origin Master: Demote origin master as media server on destination (yes/no/partial). For domain split, only one pair can be 'Yes'.
• Switchover date: Select anticipated switchover date. Tranzman verifies feasibility and ignores images expiring before switchover.

🛈 Modifying switchover date impacts data transfer and may result in expired images migrated to destination.

    Previous

   Next