Difference between revisions of "Tranzman Recorder"

From Tranzman Documentation
Jump to: navigation, search
Line 43: Line 43:
 
</tr>
 
</tr>
 
</table>
 
</table>
 +
  
 
=== Using Recorder on Windows ===
 
=== Using Recorder on Windows ===

Revision as of 04:54, 15 March 2023

Tranzman Recorder

The Tranzman Recorder is a FREE tool that helps create a data snapshot of the origin or destination backup environments involved in a migration. It gathers information from backup environments for initial assessment and for migration of environments. It can also be used as a virtual agent for migrations and recoveries.


Using Tranzman Recorder

The tool is available as downloadable either from Tranzman Appliance deployed for Assessment or through an email to Tranzman Support

Using Recorder on *nix

Step:1 Download the recorder binary on the backup servers involved in migration. Ensure the Filesystem on where the recorder is downloaded has a minimum 2GB freespace. All files/folders will be created on the recorder's current directory. Extract the downloaded file by either one of below command

> tar xzf tzm_recorder_linux.64.tgz
# if tar doesn't support 'z' option then following command sequence can be used #
> gunzip tzm_recorder_linux.64.tgz
> tar xf tzm_recorder_linux.64.tar

Step:2 Update the permission to all files extracted in the newly created tzm_recorder folder.

> chmod +xr -R tzm_recorder

Step:3 Execute the tzm_recorder binary extracted under tzm_recorder directory

> cd tzm_recorder; ./tzm_recorder


Using Recorder on Windows

Step:1 Download the windows binary zip file to the backup server and extract the zip file as below. Please ensure to have at least 2GB free space on the extracted filesystem, as the extracted directory will be going to act as base directory for the tranzman recorder

Right click on the zip file to extract.

Extracted zip.png Extracted zip1.png

Step:2 Open CMD prompt and change to the base directory of extracted tzm recorder and execute tzm_recorder.exe file

# C:
# cd \TZM\tzm_recorder_windows.64\tzm_recorder
# tzm_recorder.exe
Note.png The CMD prompt should be Run as Administrator or as an account with Administrator rights.


Using Tranzman recorder to Anonymise data

By default tzm_recorder creates the output as a zip file. In order to anonoymise the data, either extract the output file manually or by using -no_zip option with tzm_recorder as below.

Step:1 (Run with no_zip option)

> tzm_recorder -no_zip

Step:2 (Discover Identifiable Content) Using the tzm_recorder to discover any identifiable content, will help to prepare a list of current identifiable content to convert it to some random strings.

> tzm_recorder -get_identifiable -recording_path TZM_recording_1234567890

Step:3 (Review/Modify anon_map.txt) The generated map file has mapping between original and random data generated as part of anonymise. This file (anon_map.txt) can be updated as per customer needs.

127.0.0.1 140.1.1.6
192.168.50.255 248.250.87.170
192.168.50.45 248.250.87.5
nbu81-o-solX86 xxoxxc-svxx-osxXuxux

Step:4 (Anonymise the identifiable Content) The generated anon file configurations will be anonymised based on its mapping in the file. This can be carried using below command. The resulted output zip file will have all sensitive data updated with some random invalid data

> tzm_recorder -anoymise -recording_path TZM_recording_1234567890

After the data has been anonymised, user can delete the anon_map.txt file or keep it for their own reference (so that any feed back about issues in the environment can be used by them to determine what systems need to be fixed).


Using Tranzman recorder for sizing information

Sizing information on *nix

Executing the tzm_recorder with -sizer option, let the tool perform sizing information checks

> ./tzm_recorder -sizer

Sizing information on Windows

Open a CMD prompt and run the tzm_recorder.exe tool with -sizer option

# tzm_recorder.exe -sizer

Providing Credentials

Some Backup Product requires credentials to be entered to continue further with the tool execution.

TZM

TSM requires the db2 and tsm credentials as below.

INFO | >>SYSTEM<< Credentials are not valid for db2 database account, please enter correct credentials

Please enter the username for db2 account >tsminst1
Please enter the password for tsminst1 >
INFO | >>SYSTEM<< Credentials are not valid for tsm admin account, please enter correct credentials

Please enter the username for tsm account >admin
Please enter the password for admin >

Commvault

Commvault requires commcell credentials.

INFO | >>SYSTEM<< Credentials are not valid for login to commcell, please enter correct credentials

Please enter the username for cvm account >Administrator
Please enter the password for tsminst1 >

Sample Sizing data

NetBackup Spectrum Protect / TSM Data Protector

------------------------------------------------------------- -- Sizing Information -- ------------------------------------------------------------- Environment Name = nbu-example-srv Backup Product = NBU Backup Product Version = 8.2 Platform = MSWin32 Clustering Technology = Standalone Catalog Size = 1.78TB Catalog Backup Duration = 99981 Protected Data Size = 2.86PB Number of Images / Sets = 245078 Number of Fragments / SubSets = 790218 Largest Image / Set = 3.18TB Largest image file count = 29679145 Average daily images = 7280 Number of Media = NONE Number of Active Clients (in policies) = 756 Number of Clients (with backups) = 6752 Number of Servers under Master Control = 12 Number of Policies / Workloads = 364 Server RAM = 64.00GB Server CPU/Core Count = 36 Backup Data Types = [ 35 0 40 7 24 13 ] New Job / Policy Types = [ 25 35 40 7 17 15 4 0 24 19 13 ] Largest media used capacity = 0.00B Server Roles = [ master server ] Devices = [ AdvancedDisk BasicDisk PureDisk DataDomain ] Encryption = YES Dedupe = YES

------------------------------------------------------------- -- Sizing Information -- ------------------------------------------------------------- Environment Name = TSM71-O-LNX Backup Product = TSM Backup Product Version = 7.1.6.0 Platform = linux Clustering Technology = Standalone Catalog Size = 1.16GB Catalog Backup Duration = NONE Protected Data Size = 35.50GB Number of Images / Sets = 30944 Number of Fragments / SubSets = 1708 Number of backup objects = 80177 Largest Image / Set = 7.13GB Average backup objects per Image = 2.59 Largest image object count = 24273 Average daily images = 0.00 Number of Media = 92 Number of Active Clients (in policies) = 36 Number of Clients (with backups) = 36 Number of Servers under Master Control = UNKNOWN Number of Policies / Workloads = 55 Server RAM = 3.70GB Server CPU/Core Count = 1 Backup Data Types = [ "AIX" "DB2/LINUXX8664" "DB2/NT64" "DP Oracle Win64" "Linux x86-64" "OpenVMS" "Postgres" "SunOS" "TDP Dom LINUX64" "TDP Domino WIN64" "TDP MSExchg" "TDP MSSQL Win64" "TDP R3 Linux" "TDP VMware" "WinNT" ] New Job / Policy Types = UNKNOWN Largest media used capacity = 3.00GB Server Roles = UNKNOWN Devices = [ LTO FILE DISK NAS ] Encryption = NO Dedupe = NO

------------------------------------------------------------- -- Sizing Information -- ------------------------------------------------------------- Environment Name = hpe-example-srv Backup Product = HPE Backup Product Version = 10.30 Platform = linux Clustering Technology = Standalone Server Roles = UNKNOWN Catalog Size = 1.52GB Catalog Backup Duration = UNKNOWN Protected Data Size = 2.17PB Number of Images / Sets = 42003 Number of Fragments / SubSets = 42003 Largest Image / Set = 3.96TB Largest image file count = 44640212 Average daily images = NONE Number of Media = 7329 Largest media used capacity = 33.44TB Number of Active Clients (in policies) = 137 Number of Clients (with backups) = 329 Number of Servers under Master Control = NONE Number of Policies / Workloads = 164 Server RAM = 36GB Server CPU/Core Count = 8 Backup Data Types = [ IDB ORACLE8 WINFS FILESYSTEM E2010 ] New Job / Policy Types = NONE Devices = [ ObjectStore LTO-Ultrium ] Encryption = NO Dedupe = TES


Commvault Backup Exec Networker

------------------------------------------------------------- -- Sizing Information -- ------------------------------------------------------------- Environment Name = commvault-o-win Backup Product = CVM Backup Product Version = 11.80.130.0 Platform = MSWin32 Clustering Technology = Standalone Catalog Size = 432.57MB Catalog Backup Duration = 21568 Protected Data Size = 88.67GB Number of Images / Sets = 83 Number of Fragments / SubSets = 221 Number of backup objects = NONE Largest Image / Set = 19.61GB Average backup objects per Image = 0.00 Largest image object count = 223636 Average daily images = 0.00 Number of Media = 258 Number of Active Clients (in policies) = 53 Number of Clients (with backups) = UNKNOWN Number of Servers under Master Control = UNKNOWN Number of Policies / Workloads = 141 Server RAM = 6.00GB Server CPU/Core Count = 2 Backup Data Types = [ AIX File System Exchange Database Exchange Mailbox (Classic) Linux File System Solaris File System SQL Server Windows File System ] New Job / Policy Types = NONE Largest media used capacity = 399.99GB Server Roles = UNKNOWN Devices = UNKNOWN Encryption = UNKNOWN Dedupe = UNKNOWN

------------------------------------------------------------- -- Sizing Information -- ------------------------------------------------------------- Environment Name = bue14-o1-win Backup Product = BUE Backup Product Version = 14.1 Platform = MSWin32 Clustering Technology = Standalone Catalog Size = 48.94MB Catalog Backup Duration = NONE Protected Data Size = 0.00B Number of Images / Sets = 370 Number of Fragments / SubSets = 562 Number of backup objects = NONE Largest Image / Set = 21.99GB Average backup objects per Image = Not Found Largest image object count = 85050 Average daily images = Not Found Number of Media = 421 Number of Active Clients (in policies) = 29 Number of Clients (with backups) = UNKNOWN Number of Servers under Master Control = NONE Number of Policies / Workloads = 88 Server RAM = 8.00GB Server CPU/Core Count = 4 Backup Data Types = [ 84 39 70 71 14 59 49 73 37 43 ] New Job / Policy Types = NONE Largest media used capacity = Not Found Server Roles = UNKNOWN Devices = UNKNOWN Encryption = UNKNOWN Dedupe = UNKNOWN

------------------------------------------------------------- -- Sizing Information -- ------------------------------------------------------------- Environment Name = winemcnetworker Backup Product = NSR Backup Product Version = 9.1.0.2 Platform = MSWin32 Clustering Technology = Standalone Catalog Size = 6.49MB Catalog Backup Duration = 6401226 Protected Data Size = 4.26GB Number of Images / Sets = 703 Number of Fragments / SubSets = 703 Number of backup objects = 162410 Largest Image / Set = 192.17MB Average backup objects per Image = 231.02 Largest image object count = 4652 Average daily images = 10.65 Number of Media = 51 Number of Active Clients (in policies) = 7 Number of Clients (with backups) = 12 Number of Servers under Master Control = 2 Number of Policies / Workloads = 8 Server RAM = 5.00GB Server CPU/Core Count = 4 Backup Data Types = [ Filesystem Sybase ] New Job / Policy Types = [ Filesystem Sybase ] Largest media used capacity = 3.55GB Server Roles = [ Networker Server Storage Node Networker Management Console ] Devices = [ LTO Ultrium-3 adv_file Data Domain ] Encryption = NO Dedupe = NO



Back to Recorder Overview.