Selections - Revision history

Lakshmi at 18:37, 11 September 2025

2025-09-11T18:37:05Z

Lakshmi at 17:22, 11 September 2025

2025-09-11T17:22:36Z

Show changes

Lakshmi at 11:59, 17 August 2023

2023-08-17T11:59:50Z

Lakshmi at 11:58, 17 August 2023

2023-08-17T11:58:21Z

Lakshmi at 09:18, 17 August 2023

2023-08-17T09:18:46Z

Lakshmi at 09:10, 17 August 2023

2023-08-17T09:10:20Z

Lakshmi at 09:06, 17 August 2023

2023-08-17T09:06:50Z

Lakshmi at 09:05, 17 August 2023

2023-08-17T09:05:40Z

Lakshmi at 15:50, 16 August 2023

2023-08-16T15:50:47Z

Lakshmi at 15:49, 16 August 2023

2023-08-16T15:49:48Z

@@ Line 92: / Line 92: @@
        <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: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;">
+     <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>
+       <tr><td>IMAGE ...</td></tr>
-        IMAGE ...<br>
+      <tr><td>HISTO ...</td></tr>
-        HISTO ...<br>
+      <tr><td>FRAG 1 ... @aaaab ...</td></tr>
-        FRAG 1 ... @aaaab ...<br>
+      <tr><td><font style="color:red">FRAG 2 ... NBDB06 ...</font></td></tr>
        <tr><td><font style="color:blue"># </font></td></tr>
      </table>

@@ Line 57: / Line 57: @@
 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>
+* 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>
+* 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>
+* 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>
+* 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>
+* 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]]
@@ Line 77: / Line 77: @@
 [[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>
+* 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>
+* 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)
@@ Line 133: / Line 133: @@
 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.
+<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.<br>
 [[File:Selections_others.jpg|700px]]
@@ Line 140: / Line 141: @@
 <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>

← Older revision		Revision as of 11:58, 17 August 2023
Line 13:		Line 13:

	=== Defining Rules for Selections ===		=== Defining Rules for Selections ===
		+	[[File:Selections.jpg\|700px]]
		+
	<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>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.

@@ Line 52: / Line 52: @@
 * 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. Moreover, consideration on already migrated images on Destination should be taken into account, as it may require manual intervention to remove those data.
+* In order to make changes after the start, the appliance state needs to be reverted to selections state. <br>
 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>
@@ Line 75: / Line 76: @@
 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> tape media is updated to <i>NOT_MIGRATED</i> <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 tape media will not be migrated. If the image has only one copy, then the image will not be migrated. <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>
-'''[root@qa-nbu812-o-lnx-g-e2e ~]# bpimagelist -backupid qa-nbu812-o-lnx-g-e2e.devs.com_1692236444
+<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;">
-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
+<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>
-HISTO 0 0 0 0 0 0 0 0 0 0
+<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>
-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
+HISTO 0 0 0 0 0 0 0 0 0 0<br>
-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
+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>
-[root@qa-nbu812-o-lnx-g-e2e ~]#
+<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>
 ====Adding <b>Duplication Rules</b>====

@@ Line 74: / Line 74: @@
 [[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.
+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> tape media is updated to <i>NOT_MIGRATED</i>
+For example, the above rename rule of <b>nbu_media_id</b> for <i>NBDB06</i> tape media is updated to <i>NOT_MIGRATED</i> <br>
-If the image has multiple copy, then only the copy residing on the tape media will not be migrated. If the image has only one copy, then the image will not be migrated.
+If the image has multiple copy, then only the copy residing on the tape media will not be migrated. If the image has only one copy, then the image will not be migrated. <br>
 '''[root@qa-nbu812-o-lnx-g-e2e ~]# bpimagelist -backupid qa-nbu812-o-lnx-g-e2e.devs.com_1692236444

@@ Line 39: / Line 39: @@
 * 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]]
@@ Line 59: / Line 62: @@
 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.
+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]]

@@ Line 2: / Line 2: @@
 === Introduction to Selections ===
-<b>Selections</b> allows to select components for migration. It provides granualarity in selecting configurations/Images and other components for migration.
+<b>Selections</b> allows to select components for migration. It provides granularity in selecting configurations/Images and other components for migration.
 === Creating Migration pair ===
@@ Line 15: / Line 15: @@
 <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>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>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.
-<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>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>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>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>Merge Configs</b> - Allows to migrate individual entities of configuration files and host properties which are otherwise not migrated automatically.
@@ Line 28: / Line 28: @@
 <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> Selections should be modified only before the transition is started.
-Changes to selections after transition will invalidate the existing license.</td></tr>
+Changes to selections after transition will invalidate the existing license. </td></tr>
 </table>
@@ Line 35: / Line 35: @@
 * Under <b>Selections</b> tab, click on <b>Config Object Rules</b>.
-* Tranzman will pre-populate the configurations seggreated under different config sections.
+* 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 anytime, a config entity can be reset to default selections (<i>deselected</i>) by click on the <b>reset</b> icon
+* 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]]
 ====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
+* 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.
@@ Line 53: / Line 56: @@
 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]]
@@ Line 58: / Line 66: @@
 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 exists or is being migrated)
+* 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 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 )
+* 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]]
 ====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 can not be modified after the start of transition.
+* 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.
@@ Line 85: / Line 104: @@
 ====Running <b>Verify</b>====
-* Verify selected Configuration objects, Images and Renam
+* 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 DiskPools 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.
@@ Line 96: / Line 115: @@
 === Other options in Selections ===
-<b>Import empty media</b> - This option allow to add empty media (scratch media) to the destination
+<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 has media and this option is applicable only for <b>Same Vendor Transition</b>
+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.
@@ Line 104: / Line 123: @@
 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.
+<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>
+<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>