Difference between revisions of "Selections"
| Line 1: | Line 1: | ||
| − | == | + | == Introduction to Selections == |
| − | Selections | + | <b>Selections</b> allows to select components for migration. It provides granualarity 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 (a 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 <b>Tasks</b> -> <b>Selections</b>. Click on <b>Create a migration pair</b> to create a pair. | ||
| + | Below example is a 2 to 1 migration, where two Origin servers are migrated to a single destination server. This require two selection pair with an Origin and Destination in each pair. | ||
| − | + | == Defining Rules for Selections == | |
| + | <b>Image Rules</b> - 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 <i>Backup Time</i>, <i>Expire Time</i>,<i>Policy</i> etc. | ||
| − | <b> | + | <b>Config Object Rules</b> - Allows to perform selections of configuration objects. It helps to perform granualr selections on different configuration Objects like <i>Workload</i>,<i>Residency</i> etc. |
| − | <b> | + | <b>Rename Rules</b> - This rule has multiple functionalities such as Renaming a configuration, Mapping a configuration to a different configuration or to ignore a configuration. |
| − | <b> | + | <b>Pre-Duplication Rules</b>, <b>Duplication Rules</b> - Helps to define pre-migration, auto-duplication/file-restore or post-migration duplication rules to duplicate image copies from one storage device to another |
| − | <b> | + | <b>Merge Configs</b> - Allows to migrate individual entities of configuration files and host properties which are otherwise not migrated automatically. |
| − | <b> | + | <b>Verify</b> - 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 <b>Configuration migration</b> |
| + | Note: Selections should be modified only before the transition is started.Changes to selections after transition will invalidate the existing license. | ||
| − | + | == Other options in Selections == | |
| − | |||
| − | + | <b>Import empty media</b> - This option allow to add empty media (scratch media) to the destination | |
| − | + | Avoid selecting this option for a domain SPLIT where multiple environments has media and this option is applicable only for <b>Same Vendor Transition</b> | |
| + | <b>Demote Origin Master</b> - Choose to demote (yes/no/partial) the origin master as media sever on destination. | ||
| + | For a domain split, '<i>Yes</i>' can be selected for one selection pairs, however the other pair must be a '<i>No</i>' or '<i>Partial</i>'. | ||
| + | <i>Partial</i> 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 <b>Same Vendor Transition</b> | ||
| − | + | <b>Switchover date</b> - 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. | |
| + | Note: 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. | ||
| − | + | ===Adding <b>Config Object Rules</b>=== | |
| − | === | + | Under <b>Selections</b> tab, click on <b>Config Object Rules</b>. |
| + | Tranzman will pre-populate the configurations seggreated under different config sections. | ||
| + | Click on each config sections to perform a <i>select</i> or <i>deselect</i> or <i>rename</i> | ||
| + | Click on <b>Commit</b> to save the selections. | ||
| + | At anytime, a config entity can be reset to default selections (<i>deselected</i>) by click on the <b>reset</b> icon | ||
| + | |||
| + | ===Adding <b>Image Rules</b>=== | ||
| − | |||
Follow below steps for selecting everything for a migration.By everything we means all images in catalog and all config objects. | Follow below steps for selecting everything for a migration.By everything we means all images in catalog and all config objects. | ||
| Line 55: | Line 72: | ||
| − | + | ---- | |
| − | [[ | + | {| class="wikitable" style="margin:auto;width:100%;color:blue;text-align:center;borderstyle=ridge;" |
| − | + | |- | |
| − | [[ | + | | [[Image:prev_icon.jpg|30px|link=Discovery]] |
| + | || [[Image:next_icon.jpg|30px|link=Selections]] | ||
| + | |} | ||
Revision as of 09:27, 6 July 2023
Contents
Introduction to Selections
Selections allows to select components for migration. It provides granualarity 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 (a 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 require 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 granualr 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
Note: Selections should be modified only before the transition is started.Changes to selections after transition will invalidate the existing license.
Other options in Selections
Import empty media - This option allow to add empty media (scratch media) to the destination Avoid selecting this option for a domain SPLIT where multiple environments has 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.
Note: 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.
Adding Config Object Rules
Under Selections tab, click on Config Object Rules. Tranzman will pre-populate the configurations seggreated 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 anytime, a config entity can be reset to default selections (deselected) by click on the reset icon
Adding Image Rules
Follow below steps for selecting everything for a migration.By everything we means all images in catalog and all config objects.
Step 1:- Click on the Image Rules and select Migrate everything and hit Apply rules.You will see the notification of Applying Rules , wait for that notification to clear and close the tab.
Step 2:- Toggle the Rules button towards complex for selecting all config objects.
Granular Selections (Migrate Specific Data) :-
Step 1:- Click on the Image Rules and select Images based on different properties.
Step 2:- Click on the Config Object Rules and select Config objects based on different properties.
Note :- Below steps are applied only for Cross Vendor Migrations , for same vendor migration you can break and move to Jump to Pre-Assessment .
Step 3
Click on Pre-Duplication
|
|