Difference between revisions of "Selections"

Revision as of 09:18, 17 August 2023

Introduction to Selections

Selections allows to select components for migration. It provides granularity in selecting configurations/Images and other components for migration.

Creating Migration pair

Minimum one migration pair is required to enable Selections. Once the servers are added to Tranzman server and Discovery is completed, the Selections will be enabled.
Selections allows to define migration pair (an origin and a destination).

Create a migration Pair, by selecting from an added server list drop down for the Origin Environment and one for the Destination.
Navigate to Tasks -> Selections. Click on Create a migration pair to create a pair.
Below example is a 2 to 1 migration, where two Origin servers are migrated to a single destination server. This requires two selection pair with an Origin and Destination in each pair.

Defining Rules for Selections

Image Rules - Allows to select images for migration. Selection can either to migrate all images in the catalog or select specific images based on different image properties like Backup Time, Expire Time,Policy etc.

Config Object Rules - Allows to perform selections of configuration objects. It helps to perform granular selections on different configuration Objects like Workload,Residency etc.

Rename Rules - This rule has multiple functionalities such as Renaming a configuration, mapping a configuration to a different configuration or to ignore a configuration.

Pre-Duplication Rules, Duplication Rules - Helps to define pre-migration, auto-duplication/file-restore or post-migration duplication rules to duplicate image copies from one storage device to another.

Merge Configs - Allows to migrate individual entities of configuration files and host properties which are otherwise not migrated automatically.

Verify - Helps to verify the selections made on Config Object, Image and Rename Rules for any inconsistency.
It also verifies dependencies between different selected config objects. Both inconsistency and dependencies should be resolved for successful completion of Configuration migration

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

Adding Config Object Rules

• Under Selections tab, click on Config Object Rules.
• Tranzman will pre-populate the configurations segregated under different config sections.
• Click on each config sections to perform a select or deselect or rename
• Click on Commit to save the selections.
• At any time, a config entity can be reset to default selections (deselected) by click on the reset icon

The selections can be downloaded using Download filter icon and a custom list can be uploaded through Upload filter icon.

Adding Image Rules

• Image rules helps to create list of images for migration. It allows for a granular level selection of images for migration.
• It is recommended to perform Image Rules after the Config Object Rules to avoid MISSING_XXX_MAPPING on rename rules being created.
• Unlike Config Object Rules, Image Rules cannot be modified after the start of transition.
• In order to make changes after the start, the appliance state needs to be reverted to selections state.
  

Moreover, consideration on already migrated images on Destination should be taken into account, as it may require manual intervention to remove those data.

Image rules lets to Migrate All images or individual selections (granular level). Click on + icon to add the Image Rules.

Image rules also has a exclude list to deselect specific images based on the matching condition using the Add Exclude Rule icon.

Image rules can also be downloaded, and a custom rule can be uploaded. However, the csv file for images must follow below syntax.
The first line of the file should have the seperator defined. (e.g: sep=| )
Inclusion list should be in <serial num><sep>+<sep><criteria> and exclusion must replace the + with - symbol like below.

Adding Rename Rules

Rename rules has multi-functionality such as -

• To modify and provide a new name for an object when it is migrated (requires that the object is also selected for migration)
• To map between the objects of same type (requires that the object is NOT selected, also the new name object should already exist or is being migrated)
• To exclude some components from migration (using NOT_MIGRATED keyword and it change the way images / image copies are transferred and applies to SLPs and DiskMediaIds ).
• To highlight the missing config by images that was not selected, renamed or mapped (check MISSING_XXXX_MAPPING where XXXX is SLP, DISK or HOST)

When excluding disk backups or Tape backup images, it is possible a single image might have multiple copies in disk and tape.
For example, the above rename rule of nbu_media_id for NBDB06 mediaID is updated as NOT_MIGRATED
If the image has multiple copy, then only the copy residing on the media will not be migrated. If the image has only one copy, then the image will not be migrated.
The below backupid has multiple copies, and the highlighted copy will not be migrated to Destination master. (It will still exist on Origin)

Adding Duplication Rules

• Duplication Rules can be defined to run on the Origin (Pre-Catalog Migration) or on the Destination (Post Catalog Migration). In both case the rule is based on the images that originated from the Origin.
• The rules cannot be modified after the start of transition.
• In order to change Duplication Rules, appliance state must be reverted to the selections state.
• Duplication Rules require LIST of fields and an image of the selection criteria.
• If no rules are defined during the start of Transition, the action will be paused.
• If rules are added after the start of Transition, then the action need to be resumed manually.

Adding Merge Configs

• Lists all the config settings between Origin and Destination.
• Arrow ( ) selects the origin setting and update on Destination.
• The revert ( ) on the right of value, undo the changes
• Any custom values can be directly typed in the Text box.
• The changes require commit before navigating to other tabs or closing the dialog box
• The added changes will be handled during CreateConfig action and so these selections must be done before starting the transition.

Running Verify

• Verify selected Configuration objects, Images and Rename rules.
• Validate whether the servers used by images are selected, or a valid mapping on Rename Rules, if deselected.
• Checks if the SLPs used by images are selected, or a valid mapping on Rename Rules exist.
• Checks if the Disk Pools used by images are selected, or a valid mapping on Rename Rules exist.
• Validate if the mapping data in Renames are valid config names
• Identifies DUPLICATE configuration objects selected which require rename or mapping.

Other options in Selections

Import empty media - This option allows to add empty media (scratch media) to the destination. Avoid selecting this option for a domain SPLIT where multiple environments have media and this option is applicable only for Same Vendor Transition

Demote Origin Master - Choose to demote (yes/no/partial) the origin master as media sever on destination. For a domain split, 'Yes' can be selected for one selection pairs, however the other pair must be a 'No' or 'Partial'. Partial demote results in the Origin visible on Destination as a media server in the database however the Origin is not actually demoted/reconfigured as a media server. Applicable only for Same Vendor Transition

Switchover date - Allows to select an anticipated date for switchover. Tranzman verifies and suggest (on dashboard) if the provided date is possible for switchover or not. This setting also helps Tranzman to ignore images that would expire before the switchover.

Careful consideration should be made while adding the switchover date, as modifying the date will impact the datatransfer or results in expired image migrated on Destination.