Difference between revisions of "Selections"

From Tranzman Documentation
Jump to: navigation, search
 
(3 intermediate revisions by the same user not shown)
Line 1: Line 1:
 +
__TOC__
 +
<br>
 +
<br>
 +
<div style="background-color:#fde9e9; padding: 1.5rem; border-radius:8px; max-width:80%; margin: 0 auto; margin-bottom:2rem;">
 +
  <h1 style="border-bottom:none; font-size:2.5em; font-weight:bold; text-align:center;">Selections Overview & Migration Rules</h1>
 +
  <p style="font-size:1.2em; text-align:left;">
 +
    <b>Selections</b> allow you to choose components for migration, providing granularity in selecting configurations, images, and other components.<br>
 +
    <ul style="text-align:left; margin:1em 0 0 2em;">
 +
      <li>Selections are enabled after adding servers to Tranzman and completing Discovery.</li>
 +
      <li>At least one migration pair (origin and destination) is required to enable selections.</li>
 +
      <li>Multiple migration pairs can be created for complex scenarios (e.g., 2-to-1 migrations).</li>
 +
    </ul>
 +
  </p>
 +
  <div style="background-color:#f8e2b3; padding:0.2rem; border-radius:8px; box-shadow:0 2px 4px rgba(0,0,0,0.06); font-size:1em; margin: 0 auto;">
 +
    <p>🛈 <i>Selections should be modified only before the transition is started. Changes after transition will invalidate the existing license.</i></p>
 +
  </div>
 +
</div>
  
−
=== Introduction to Selections ===
+
<div style="max-width:80%; margin: 0 auto;">
 +
  <div style="background-color:#edf7ff; padding:1.5rem; border-radius:8px; box-shadow:0 2px 4px rgba(0,0,0,0.06); margin-bottom:2rem;">
 +
    <h2 style="border-bottom:2px solid #bbdefb; padding-bottom:0.5rem; font-size:1.5em;">Creating Migration Pair</h2>
 +
    <ul>
 +
      <li>Select origin and destination servers from the drop-down list.</li>
 +
      <li>Navigate to <b>Tasks</b> → <b>Selections</b> and click <b>Create a migration pair</b>.</li>
 +
      <li>For 2-to-1 migrations, create two selection pairs (each with an origin and destination).</li>
 +
    </ul>
 +
  </div>
  
−
<b>Selections</b> allows to select components for migration. It provides granularity in selecting configurations/Images and other components for migration.
+
  <div style="background-color:#fef3f7; padding:1.5rem; border-radius:8px; box-shadow:0 2px 4px rgba(0,0,0,0.06); margin-bottom:2rem;">
 +
    <h2 style="border-bottom:2px solid #f8bbd0; padding-bottom:0.5rem; font-size:1.5em;">Defining Rules for Selections</h2>
 +
    [[File:Selections.jpg|700px]]
 +
    <ul>
 +
      <li><b>Image Rules</b>: Select images for migration (all or by properties like Backup Time, Expire Time, Policy, etc.).</li>
 +
      <li><b>Config Object Rules</b>: Granular selection of configuration objects (e.g., Workload, Residency).</li>
 +
      <li><b>Rename Rules</b>: Rename, map, or ignore configurations.</li>
 +
      <li><b>Pre-Duplication & Duplication Rules</b>: Define rules for duplicating image copies pre/post migration.</li>
 +
      <li><b>Merge Configs</b>: Migrate individual config entities and host properties.</li>
 +
      <li><b>Verify</b>: Check for inconsistencies and dependencies in selections.</li>
 +
    </ul>
 +
    <div style="background-color:#f8e2b3; padding:0.2rem; border-radius:8px; box-shadow:0 2px 4px rgba(0,0,0,0.06); font-size:1em; margin: 0 auto;">
 +
      <p>🛈 <i>Resolve all inconsistencies and dependencies for successful configuration migration.</i></p>
 +
    </div>
 +
  </div>
  
−
=== Creating Migration pair ===
+
  <div style="background-color:#eff8f0; padding:1.5rem; border-radius:8px; box-shadow:0 2px 4px rgba(0,0,0,0.06); margin-bottom:2rem;">
−
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. <br>
+
    <h2 style="border-bottom:2px solid #c8e6c9; padding-bottom:0.5rem; font-size:1.5em;">Config Object Rules</h2>
−
Selections allows to define migration pair (an origin and a destination). <br>
+
    <ul>
 +
      <li>Click <b>Config Object Rules</b> under <b>Selections</b> tab.</li>
 +
      <li>Tranzman pre-populates configurations by section.</li>
 +
      <li>Select, deselect, or rename entities as needed.</li>
 +
      <li>Click <b>Commit</b> to save selections.</li>
 +
      <li>Use <b>reset</b> icon to revert to default selections.</li>
 +
    </ul>
 +
    [[File:Selections_config_obj_rule.jpg|700px]]
 +
    <p>
 +
      Download selections using <b>Download filter</b> icon or upload a custom list via <b>Upload filter</b> icon.
 +
    </p>
 +
    [[File:Selections_config_obj_rule_download.jpg|700px]]
 +
  </div>
  
−
Create a migration Pair, by selecting from an added server list drop down for the Origin Environment and one for the Destination. <br>
+
  <div style="background-color:#fffbf4; padding:1.5rem; border-radius:8px; box-shadow:0 2px 4px rgba(0,0,0,0.06); margin-bottom:2rem;">
−
Navigate to <b>Tasks</b> -> <b>Selections</b>. Click on <b>Create a migration pair</b> to create a pair. <br>
+
    <h2 style="border-bottom:2px solid #ffe0b2; padding-bottom:0.5rem; font-size:1.5em;">Image Rules</h2>
−
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. <br>
+
    <ul>
 +
      <li>Granular selection of images for migration.</li>
 +
      <li>Recommended to perform after <b>Config Object Rules</b> to avoid <i>MISSING_XXX_MAPPING</i> errors.</li>
 +
      <li>Cannot be modified after transition starts (requires reverting appliance state).</li>
 +
      <li>Consider already migrated images on destination before making changes.</li>
 +
      <li>Click <b>+</b> to add image rules.</li>
 +
    </ul>
 +
    [[File:Selections_image_rule.jpg|700px]]
 +
    <ul>
 +
      <li>Exclude specific images using <b>Add Exclude Rule</b> icon.</li>
 +
    </ul>
 +
    [[File:Selections_image_rule_exclude_rule.jpg|700px]]
 +
    <ul>
 +
      <li>Download/upload image rules as CSV. First line must define separator (e.g., <i>sep=|</i>).</li>
 +
      <li>Inclusion: <code>&lt;serial num&gt;|+|&lt;criteria&gt;</code>, Exclusion: replace <code>+</code> with <code>-</code>.</li>
 +
    </ul>
 +
    [[File:Selections_image_rule_csv.jpg|700px]]
 +
  </div>
  
−
=== Defining Rules for Selections ===
+
  <div style="background-color:#edf7ff; padding:1.5rem; border-radius:8px; box-shadow:0 2px 4px rgba(0,0,0,0.06); margin-bottom:2rem;">
−
<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.
+
    <h2 style="border-bottom:2px solid #bbdefb; padding-bottom:0.5rem; font-size:1.5em;">Rename Rules</h2>
 +
    <ul>
 +
      <li>Rename objects during migration (must be selected for migration).</li>
 +
      <li>Map objects of same type (object must NOT be selected, new name must exist or be migrated).</li>
 +
      <li>Exclude components using <code>NOT_MIGRATED</code> keyword (affects SLPs and DiskMediaIds).</li>
 +
      <li>Highlight missing config by images not selected, renamed, or mapped (<i>MISSING_XXXX_MAPPING</i>).</li>
 +
    </ul>
 +
    [[File:Selections_rename_rule.jpg|700px]]
 +
    <p>
 +
      <b>Example:</b> Excluding disk/tape backups with multiple copies. Only the copy on the excluded media will not be migrated; others remain on origin.
 +
    </p>
 +
    <table style="width:100%;color:white;background-color:black;font-family:monospace,monospace;border-collapse:seperate;border-radius:5px 5px;border:3px solid #000;box-shadow: 5px 5px 10px grey;">
 +
      <tr><td><font style="color:blue"># </font>bpimagelist -backupid qa-nbu812-o-lnx-g-e2e.devs.com_1692236444</td></tr>
 +
      <tr><td>IMAGE ...</td></tr>
 +
      <tr><td>HISTO ...</td></tr>
 +
      <tr><td>FRAG 1 ... @aaaab ...</td></tr>
 +
      <tr><td><font style="color:red">FRAG 2 ... NBDB06 ...</font></td></tr>
 +
      <tr><td><font style="color:blue"># </font></td></tr>
 +
    </table>
 +
  </div>
  
−
<b>Config Object Rules</b> - Allows to perform selections of configuration objects. It helps to perform granular selections on different configuration Objects like <i>Workload</i>,<i>Residency</i> etc.
+
  <div style="background-color:#fef3f7; padding:1.5rem; border-radius:8px; box-shadow:0 2px 4px rgba(0,0,0,0.06); margin-bottom:2rem;">
 +
    <h2 style="border-bottom:2px solid #f8bbd0; padding-bottom:0.5rem; font-size:1.5em;">Duplication Rules</h2>
 +
    <ul>
 +
      <li>Define rules for duplication on Origin (pre-migration) or Destination (post-migration).</li>
 +
      <li>Rules are based on images from the Origin.</li>
 +
      <li>Cannot be modified after transition starts (requires reverting appliance state).</li>
 +
      <li>If no rules are defined at start, action is paused; if added after, resume manually.</li>
 +
    </ul>
 +
    [[File:Selections_duplication_rule.jpg|700px]]
 +
  </div>
  
−
<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.
+
  <div style="background-color:#eff8f0; padding:1.5rem; border-radius:8px; box-shadow:0 2px 4px rgba(0,0,0,0.06); margin-bottom:2rem;">
 +
    <h2 style="border-bottom:2px solid #c8e6c9; padding-bottom:0.5rem; font-size:1.5em;">Merge Configs</h2>
 +
    <ul>
 +
      <li>Lists all config settings between Origin and Destination.</li>
 +
      <li>Use arrow to select origin setting and update destination.</li>
 +
      <li>Use <i>revert</i> to undo changes.</li>
 +
      <li>Custom values can be typed directly.</li>
 +
      <li>Click <b>Commit</b> before navigating away or closing dialog.</li>
 +
      <li>Handled during <b>CreateConfig</b> action; must be done before transition starts.</li>
 +
    </ul>
 +
    [[File:Selections_merge_config.jpg|700px]]
 +
  </div>
  
−
<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.
+
  <div style="background-color:#fffbf4; padding:1.5rem; border-radius:8px; box-shadow:0 2px 4px rgba(0,0,0,0.06); margin-bottom:2rem;">
 +
    <h2 style="border-bottom:2px solid #ffe0b2; padding-bottom:0.5rem; font-size:1.5em;">Verify</h2>
 +
    <ul>
 +
      <li>Verify selected configuration objects, images, and rename rules.</li>
 +
      <li>Validate server, SLP, and disk pool mappings.</li>
 +
      <li>Check for valid config names in renames.</li>
 +
      <li>Identify duplicate configuration objects needing rename or mapping.</li>
 +
    </ul>
 +
    [[File:Selections_verify.jpg|700px]]
 +
  </div>
  
−
<b>Merge Configs</b> - Allows to migrate individual entities of configuration files and host properties which are otherwise not migrated automatically.
+
  <div style="background-color:#edf7ff; padding:1.5rem; border-radius:8px; box-shadow:0 2px 4px rgba(0,0,0,0.06); margin-bottom:2rem;">
 +
    <h2 style="border-bottom:2px solid #bbdefb; padding-bottom:0.5rem; font-size:1.5em;">Other Options in Selections</h2>
 +
    <ul>
 +
      <li><b>Import empty media</b>: Add empty (scratch) media to destination. Use only for same vendor transitions.</li>
 +
      <li><b>Demote Origin Master</b>: Demote origin master as media server on destination (yes/no/partial). For domain split, only one pair can be 'Yes'.</li>
 +
      <li><b>Switchover date</b>: Select anticipated switchover date. Tranzman verifies feasibility and ignores images expiring before switchover.</li>
 +
    </ul>
 +
    [[File:Selections_others.jpg|700px]]
 +
    <div style="background-color:#f8e2b3; padding:0.2rem; border-radius:8px; box-shadow:0 2px 4px rgba(0,0,0,0.06); font-size:1em; margin: 0 auto;">
 +
      <p>🛈 <i>Modifying switchover date impacts data transfer and may result in expired images migrated to destination.</i></p>
 +
    </div>
 +
  </div>
 +
</div>
  
−
<b>Verify</b> - Helps to verify the selections made on Config Object, Image and Rename Rules for any inconsistency. <br> It also verifies dependencies between different selected config objects. Both inconsistency and dependencies should be resolved for successful completion of <b>Configuration migration</b>
+
<div style="display:flex; justify-content:space-between; margin-top:2rem; padding:1rem; background-color:#ffffff; max-width:90%; margin: 2rem auto 0;">
−
 
+
  <div style="text-align:left;">
−
 
+
    [[File:prev_icon.jpg|30px|link=Discovery]] [[Discovery|Previous]]
−
<table style="width:50%;border-collapse:seperate;border-radius:5px 5px;box-shadow: 5px 5px 10px #750000;">
+
  </div>
−
<tr><td>[[File:Note.png|30px]]</td><td> Selections should be modified only before the transition is started.
+
  <div style="text-align:right;">
−
Changes to selections after transition will invalidate the existing license. </td></tr>
+
    [[Pre-Assessment|Next]] [[File:next_icon.jpg|30px|link=Pre-Assessment]]
−
</table>
+
  </div>
−
 
+
</div>
−
 
 
−
====Adding <b>Config Object Rules</b>====
 
−
 
 
−
* Under <b>Selections</b> tab, click on <b>Config Object Rules</b>.
 
−
* Tranzman will pre-populate the configurations segregated 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 any time, a config entity can be reset to default selections (<i>deselected</i>) by click on the <b>reset</b> icon
 
−
 
 
−
[[File:Selections_config_obj_rule.jpg|700px]]
 
−
 
 
−
 
 
−
The selections can be downloaded using <b>Download filter</b> icon and a custom list can be uploaded through <b>Upload filter</b> icon.
 
−
 
 
−
[[File:Selections_config_obj_rule_download.jpg|700px]]
 
−
 
 
−
 
 
−
====Adding <b>Image Rules</b>====
 
−
* 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 <b>Image Rules</b> after the <b>Config Object Rules</b> to avoid <i>MISSING_XXX_MAPPING</i> on rename rules being created.
 
−
* Unlike <b>Config Object Rules</b>, <b>Image Rules</b> 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. <br>
 
−
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 <i>Migrate All</i> images or individual selections (granular level). Click on <b>+</b> icon to add the <b>Image Rules</b>. <br>
 
−
[[File:Selections_image_rule.jpg|700px]]
 
−
 
 
−
Image rules also has a exclude list to deselect specific images based on the matching condition using the <b>Add Exclude Rule</b> icon. <br>
 
−
[[File:Selections_image_rule_exclude_rule.jpg|700px]]
 
−
 
 
−
Image rules can also be downloaded, and a custom rule can be uploaded. However, the csv file for images must follow below syntax.<br>
 
−
The first line of the file should have the seperator defined. (e.g: <i> sep=| </i>)<br>
 
−
Inclusion list should be in <serial num><sep>+<sep><criteria> and exclusion must replace the <i>+</i> with <i>-</i> symbol like below.<br>
 
−
[[File:Selections_image_rule_csv.jpg|700px]]
 
−
 
 
−
 
 
−
====Adding <b>Rename Rules</b>====
 
−
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)
 
−
[[File:Selections_rename_rule.jpg|700px]]
 
−
 
 
−
When excluding disk backups or Tape backup images, it is possible a single image might have multiple copies in disk and tape. <br>
 
−
For example, the above rename rule of <b>nbu_media_id</b> for <i>NBDB06</i> mediaID is updated as <i>NOT_MIGRATED</i> <br>
 
−
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. <br>
 
−
The below backupid has multiple copies, and the <font style="color:red">highlighted</font> copy will not be migrated to Destination master. (It will still exist on Origin)
 
−
 
 
−
<table style="width:50%;color:white;background-color:black;font-family:monospace,monospace;border-collapse:seperate;border-radius:5px 5px;border:3px solid #000;box-shadow: 5px 5px 10px grey;">
 
−
<tr><td><font style="color:blue">[root@qa-nbu812-o-lnx-g-e2e ~]# </font>bpimagelist -backupid qa-nbu812-o-lnx-g-e2e.devs.com_1692236444</td></tr>
 
−
<tr><td>IMAGE qa-nbu812-o-lnx-g-e2e.devs.com 0 0 13 qa-nbu812-o-lnx-g-e2e.devs.com_1692236444 lnx_files 0 *NULL* root Full 0 1 1692236444 3 1692409244 0 0 32 1 2 2 0 lnx_files_1692236444_FULL.f *NULL* *NULL* 0 1 0 0 0 *NULL* 0 0 0 0 0 0 0 *NULL* 0 0 0 *NULL* 684 1 0 732 0 0 *NULL* *NULL* 0 0 0 0 *NULL* *NULL* 0 1 0 0<br>
 
−
HISTO 0 0 0 0 0 0 0 0 0 0<br>
 
−
FRAG 1 1 32 0 0 0 0 @aaaab qa-nbu812-o-lnx-g-e2e.devs.com 262144 0 0 -1 4 1;PureDisk;qa-nbu812-m-lnx-g-e2e.devs.com;msdp_nbu812-m-lnx;PureDiskVolume;0 1692409244 0 65537 0 0 0 6 0 1692236447 1 1 *NULL* *NULL* 0 0<br>
 
−
<font style="color:red">FRAG 2 1 32 0 2 20 1 NBDB06 qa-nbu812-m-lnx-g-e2e.devs.com 65536 2 1692259195 1 0 *NULL* 1692409244 0 65537 0 1 0 1 0 1692262390 1 1 *NULL* *NULL* 0 0 </font><br>
 
−
</td></tr>
 
−
<tr><td><font style="color:blue">[root@qa-nbu812-o-lnx-g-e2e ~]# </font></td></tr>
 
−
</table>
 
−
 
−
 
 
−
====Adding <b>Duplication Rules</b>====
 
−
* <b>Duplication Rules</b> 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 <b>Duplication Rules</b>, appliance state must be reverted to the selections state.
 
−
* <b>Duplication Rules</b> 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.
 
−
[[File:Selections_duplication_rule.jpg|700px]]
 
−
 
 
−
 
 
−
====Adding <b>Merge Configs</b>====
 
−
* Lists all the config settings between Origin and Destination.
 
−
* Arrow (  ) selects the origin setting and update on Destination.
 
−
* The  <i>revert</i> (  ) 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 <b>CreateConfig</b> action and so these selections must be done before starting the transition.
 
−
[[File:Selections_merge_config.jpg|700px]]
 
−
 
 
−
 
 
−
====Running <b>Verify</b>====
 
−
* Verify selected Configuration objects, Images and Rename rules.
 
−
* Validate whether the servers used by images are selected, or a valid mapping on <b>Rename Rules</b>, if deselected.
 
−
* Checks if the SLPs used by images are selected, or a valid mapping on <b>Rename Rules</b> exist.
 
−
* Checks if the Disk Pools used by images are selected, or a valid mapping on <b>Rename Rules</b> exist.
 
−
* Validate if the mapping data in Renames are valid config names
 
−
* Identifies DUPLICATE configuration objects selected which require rename or mapping.
 
−
[[File:Selections_verify.jpg|700px]]
 
−
 
 
−
 
 
−
=== Other options in Selections ===
 
−
 
 
−
<b>Import empty media</b> - 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 <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.
 
−
[[File:Selections_others.jpg|700px]]
 
−
 
 
−
 
 
−
<table style="width:50%;border-collapse:seperate;border-radius:5px 5px;box-shadow: 5px 5px 10px #750000;">
 
−
<tr><td>[[File:Note.png|30px]]</td><td> 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. </td></tr>
 
−
</table>
 
−
 
 
−
 
 
−
 
 
−
 
 
−
{| 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=Pre-Assessment]]
 
−
|}
 

Latest revision as of 18:37, 11 September 2025



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

   Selections.jpg
  • 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.
   Selections config obj rule.jpg

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

   Selections config obj rule download.jpg

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.
   Selections image rule.jpg
  • Exclude specific images using Add Exclude Rule icon.
   Selections image rule exclude rule.jpg
  • Download/upload image rules as CSV. First line must define separator (e.g., sep=|).
  • Inclusion: <serial num>|+|<criteria>, Exclusion: replace + with -.
   Selections image rule csv.jpg

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).
   Selections rename rule.jpg

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.
   Selections duplication rule.jpg

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.
   Selections merge config.jpg

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.
   Selections verify.jpg

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.
   Selections others.jpg

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

   Prev icon.jpg Previous

   Next Next icon.jpg
Retrieved from "https://docs.stoneram.com/index.php?title=Selections&oldid=3464"