Pre-Assessment

From Tranzman Documentation
Revision as of 08:53, 18 August 2023 by Lakshmi (talk | contribs) (Analysing Pre-Assessment report)
Jump to: navigation, search

Introduction to Assessment report

The Tranzman Appliance helps pre-validation and Site survey easy and simple through a series of automated checks in TZM Pre-Assessment. This helps consultants to highlight pre-existing issues in the backup environment and can be pro-actively resolved before the start of migration.

  • The number of checks performed depends on the personality used and the origin and destination environments.
  • Same Vendor Migration has additional checks than other migrations. New checks are added often and always suggest to use latest patch to benefit from the latest checks.
  • When doing SPLITS or MERGERS, make sure to verify all the results in each migration pair. Additional care should be taken while merging objects with the same name in multiple environments.
  • In case no immediate fix is available for any issue reported to Stone Ram Support, then those will be added in new checks to provide notification in advnace as part of Pre-assessment.

Running Pre-Assessment

  • Navigate to Tasks -> Pre-Assessment on TZM web UI and click on b>Start Pre-Assessment</b>.
  • There are multiple checks run and the tests can be rerun multiple times. (to verify failed tests)
  • The Logs icon provides the latest Assessment activity logs.

Pre assessment.jpg

Pre assessment result.jpg


Running Pre-Assessment on NetBackup-to-NetBackup migration

The NetBackup to NetBackup migration supports -

  • 28 Individual Checks to verify for pre-existing issues in the origin or destination.
  • 17 Comparison Checks to identify any issues in migrating the selected components in selections between the Origin and Destination.
  • 17 Advisory Checks to understand any limitations within the environment, this may require manual actions to overcome.
  • 9 Advisory comparison checks to help understand limitations / manual actions that may need addressing.

Analysing Pre-Assessment report

The below table list the various status available in report.

  • Red triangle indicates and issues that needs to be resolved or acknowledged, clicking on it will display more information.
  • Grey check denotes the test ran without issue, and no additional information is given.
  • Grey dash means that the test was not applicable and was skipped.
  • Blue info sign denotes the test had more information but that it's not critical.
  • Green check shows that a test has been acknowledged.

Note: Everything with a Red ! Triangle must be resolved and retested or acknowledged before being able to start the migration.

Pre assessment analyse.jpg

Generating Pre-Assessment report

Click on the below icon to generate the Pre-Assessment report. Pre-Assessment document is generated only during the Selections phase. An evidance file created as part of above report, has all the test data of above Pre-Assessment

Downloading the Pre-Assessment report

The below 3 documents for each Selection pair is generated and available for Downloads

Tranzman_Assessment_XXXXXXXXXX_origin-name_destination-name.odt Tranzman_Engagement_Plan_XXXXXXXXXX_origin-name_destination-name.odt Tranzman_Environments_XXXXXXXXXX_origin-name_destination-name.odt

These .odt files can be viewed/edited using MSWord or LibreOffice.


Editing the Pre-Assessment report

It is recommend to edit the document only to provide any additional info on the issues highlighted. For merges, it makes sense to combine multiple documents into ONE document.


Working on issues in Pre-Assessment report

  • Customer is responsible on resolving any issues identified in the Pre-Assessment report.
  • Issues that are unable to get resolved before Migration start, its corresponding components should be deselected from migration. Tranzman can not migrate invalid or inconsistent components, as it will not be able to re-create it on destination.
  • If there are many issues to be resolved, this may impact proposed dates for the project. This should be taken into account when planning the migration start date. Customers change control procedures may also impact the start date.



Prev icon.jpg Next icon.jpg