Difference between revisions of "Tranzman Recorder"
From Tranzman Documentation
| Line 25: | Line 25: | ||
Ensure at least <b>2GB of free space</b> on the filesystem.<br> | Ensure at least <b>2GB of free space</b> on the filesystem.<br> | ||
Extract using: | Extract using: | ||
| − | <table style="width:100%;color:white;background-color:black;font-family: | + | <table style="width:100%;color:white;background-color:black;font-family:monospace;border-radius:5px;border:3px solid #000;box-shadow:5px 5px 10px grey;"> |
<tr><td><font style="color:blue">> </font>tar xzf tzm_recorder_linux.64.tgz</td></tr> | <tr><td><font style="color:blue">> </font>tar xzf tzm_recorder_linux.64.tgz</td></tr> | ||
</table> | </table> | ||
<p>If tar does not support z:</p> | <p>If tar does not support z:</p> | ||
| − | <table style="width:100%;color:white;background-color:black;font-family: | + | <table style="width:100%;color:white;background-color:black;font-family:monospace;border-radius:5px;border:3px solid #000;box-shadow:5px 5px 10px grey;"> |
<tr><td><font style="color:blue">> </font>gunzip tzm_recorder_linux.64.tgz</td></tr> | <tr><td><font style="color:blue">> </font>gunzip tzm_recorder_linux.64.tgz</td></tr> | ||
<tr><td><font style="color:blue">> </font>tar xf tzm_recorder_linux.64.tgz</td></tr> | <tr><td><font style="color:blue">> </font>tar xf tzm_recorder_linux.64.tgz</td></tr> | ||
| Line 36: | Line 36: | ||
<li> | <li> | ||
<b>Update Permissions</b><br> | <b>Update Permissions</b><br> | ||
| − | <table style="width:100%;color:white;background-color:black;font-family: | + | <table style="width:100%;color:white;background-color:black;font-family:monospace;border-radius:5px;border:3px solid #000;box-shadow:5px 5px 10px grey;"> |
<tr><td><font style="color:blue">> </font>chmod +xr -R tzm_recorder</td></tr> | <tr><td><font style="color:blue">> </font>chmod +xr -R tzm_recorder</td></tr> | ||
</table> | </table> | ||
| Line 42: | Line 42: | ||
<li> | <li> | ||
<b>Execute the Recorder</b><br> | <b>Execute the Recorder</b><br> | ||
| − | + | <table style="width:100%;color:white;background-color:black;font-family:monospace;border-radius:5px;border:3px solid #000;box-shadow:5px 5px 10px grey;"> | |
<tr><td><font style="color:blue">> </font>cd tzm_recorder</td></tr> | <tr><td><font style="color:blue">> </font>cd tzm_recorder</td></tr> | ||
<tr><td><font style="color:blue">> </font>./tzm_recorder</td></tr> | <tr><td><font style="color:blue">> </font>./tzm_recorder</td></tr> | ||
| Line 65: | Line 65: | ||
<b>Execute the Recorder</b><br> | <b>Execute the Recorder</b><br> | ||
Open a CMD prompt, navigate to the extracted directory, and run: | Open a CMD prompt, navigate to the extracted directory, and run: | ||
| − | <table style="width:100%;color:white;background-color:black;font-family: | + | <table style="width:100%;color:white;background-color:black;font-family:monospace;border-radius:5px;border:3px solid #000;box-shadow:5px 5px 10px grey;"> |
<tr><td><font style="color:blue"># </font>tzm_recorder.exe</td></tr> | <tr><td><font style="color:blue"># </font>tzm_recorder.exe</td></tr> | ||
</table> | </table> | ||
| Line 233: | Line 233: | ||
<b>Copy Recorder Binary</b><br> | <b>Copy Recorder Binary</b><br> | ||
Securely Copy the recorder binary from the machine to CloudScale Terraform management server (TMS or tms): | Securely Copy the recorder binary from the machine to CloudScale Terraform management server (TMS or tms): | ||
| − | + | <table style="width:100%;color:white;background-color:black;font-family:monospace;border-radius:5px;border:3px solid #000;box-shadow:5px 5px 10px grey;"> | |
<tr><td><font style="color:blue">> </font>scp tzm_recorder_linux.64.tgz <user>@<cloudscale-tms-ip>:/tmp</td></tr> | <tr><td><font style="color:blue">> </font>scp tzm_recorder_linux.64.tgz <user>@<cloudscale-tms-ip>:/tmp</td></tr> | ||
</table> | </table> | ||
| Line 241: | Line 241: | ||
<b>Access the Environment</b><br> | <b>Access the Environment</b><br> | ||
Log in to the Kubernetes cluster or CloudScale Terraform management server: | Log in to the Kubernetes cluster or CloudScale Terraform management server: | ||
| − | + | <table style="width:100%;color:white;background-color:black;font-family:monospace;border-radius:5px;border:3px solid #000;box-shadow:5px 5px 10px grey;"> | |
<tr><td><font style="color:blue">> </font>ssh <admin>@<cloudscale-tms-ip></td></tr> | <tr><td><font style="color:blue">> </font>ssh <admin>@<cloudscale-tms-ip></td></tr> | ||
</table> | </table> | ||
| Line 250: | Line 250: | ||
List the pods in the target namespace to identify where to deploy the recorder: | List the pods in the target namespace to identify where to deploy the recorder: | ||
The primary server pod will end with “-primary-0” and the namespace will be “netbackup” | The primary server pod will end with “-primary-0” and the namespace will be “netbackup” | ||
| − | + | <table style="width:100%;color:white;background-color:black;font-family:monospace;border-radius:5px;border:3px solid #000;box-shadow:5px 5px 10px grey;"> | |
<tr><td><font style="color:blue">> </font>kubectl get pods -n netbackup</td></tr> | <tr><td><font style="color:blue">> </font>kubectl get pods -n netbackup</td></tr> | ||
</table> | </table> | ||
| Line 258: | Line 258: | ||
<b>Transfer to Pod</b><br> | <b>Transfer to Pod</b><br> | ||
Copy the Recorder from CloudScale to the primary server pod: | Copy the Recorder from CloudScale to the primary server pod: | ||
| − | + | <table style="width:100%;color:white;background-color:black;font-family:monospace;border-radius:5px;border:3px solid #000;box-shadow:5px 5px 10px grey;"> | |
<tr><td><font style="color:blue">> </font>kubectl cp tzm_recorder_linux.64.tgz <namespace>/<pod-name>:/tmp/</td></tr> | <tr><td><font style="color:blue">> </font>kubectl cp tzm_recorder_linux.64.tgz <namespace>/<pod-name>:/tmp/</td></tr> | ||
</table> | </table> | ||
| Line 266: | Line 266: | ||
<b>Extract and Prepare</b><br> | <b>Extract and Prepare</b><br> | ||
Login to the primary server pod and extract the recorder: | Login to the primary server pod and extract the recorder: | ||
| − | + | <table style="width:100%;color:white;background-color:black;font-family:monospace;border-radius:5px;border:3px solid #000;box-shadow:5px 5px 10px grey;"> | |
<tr><td><font style="color:blue">> </font>kubectl exec -it <pod-name> -n <namespace> -- /bin/bash</td></tr> | <tr><td><font style="color:blue">> </font>kubectl exec -it <pod-name> -n <namespace> -- /bin/bash</td></tr> | ||
<tr><td><font style="color:blue">> </font>cd /tmp</td></tr> | <tr><td><font style="color:blue">> </font>cd /tmp</td></tr> | ||
| Line 280: | Line 280: | ||
You’ll be prompted for the following information. Initial user name and password can be found in the azure/deployment TFVARS files used to deploy the CloudScale cluster. | You’ll be prompted for the following information. Initial user name and password can be found in the azure/deployment TFVARS files used to deploy the CloudScale cluster. | ||
| − | + | <table style="width:100%;color:white;background-color:black;font-family:monospace;border-radius:5px;border:3px solid #000;box-shadow:5px 5px 10px grey;"> | |
<tr><td><font style="color:blue">> </font>chmod +x ./tzm_recorder</td></tr> | <tr><td><font style="color:blue">> </font>chmod +x ./tzm_recorder</td></tr> | ||
<tr><td><font style="color:blue">> </font>./tzm_recorder -setup_nbat</td></tr> | <tr><td><font style="color:blue">> </font>./tzm_recorder -setup_nbat</td></tr> | ||
| Line 291: | Line 291: | ||
Now execute the tzm recorder to start the data collection process<br></p> | Now execute the tzm recorder to start the data collection process<br></p> | ||
| − | + | <table style="width:100%;color:white;background-color:black;font-family:monospace;border-radius:5px;border:3px solid #000;box-shadow:5px 5px 10px grey;"> | |
<tr><td><font style="color:blue">> </font>./tzm_recorder</td></tr> | <tr><td><font style="color:blue">> </font>./tzm_recorder</td></tr> | ||
<tr><td><nowiki>INFO | START - Gathering environment information</nowiki></td></tr> | <tr><td><nowiki>INFO | START - Gathering environment information</nowiki></td></tr> | ||
| Line 299: | Line 299: | ||
<p>Once the tzm_recorder completes, log out of the primary pod to get back to the shell on the Terraform management server. <br>Execute the following command to copy the TZM recording file back to the local directory<br></p> | <p>Once the tzm_recorder completes, log out of the primary pod to get back to the shell on the Terraform management server. <br>Execute the following command to copy the TZM recording file back to the local directory<br></p> | ||
| − | + | <table style="width:100%;color:white;background-color:black;font-family:monospace;border-radius:5px;border:3px solid #000;box-shadow:5px 5px 10px grey;"> | |
<tr><td><font style="color:blue">> </font>kubectl cp <namespace>/<pod-name>:/tmp/tzm_recorder/<TZM_RECORDING.ZIP> ./<TZM_RECORDING.ZIP></td></tr> | <tr><td><font style="color:blue">> </font>kubectl cp <namespace>/<pod-name>:/tmp/tzm_recorder/<TZM_RECORDING.ZIP> ./<TZM_RECORDING.ZIP></td></tr> | ||
</table> | </table> | ||
| Line 319: | Line 319: | ||
By default, <b>tzm_recorder</b> generates an output file as a zip. To anonymize data, either extract manually or run with the <b>-no_zip</b> option: | By default, <b>tzm_recorder</b> generates an output file as a zip. To anonymize data, either extract manually or run with the <b>-no_zip</b> option: | ||
</p> | </p> | ||
| − | <table style="width:100%;color:white;background-color:black;font-family: | + | <table style="width:100%;color:white;background-color:black;font-family:monospace;border-radius:5px;border:3px solid #000;box-shadow:5px 5px 10px grey;"> |
<tr><td><font style="color:blue">> </font>tzm_recorder -no_zip</td></tr> | <tr><td><font style="color:blue">> </font>tzm_recorder -no_zip</td></tr> | ||
</table> | </table> | ||
Revision as of 10:48, 2 April 2026
Contents
Tranzman Recorder Overview & Usage
The Tranzman Recorder is a FREE tool designed to 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 migration purposes.
Additionally, it serves as a virtual agent for migrations and recoveries.
Download: Tranzman Recorder or request via email: TZM support
Recorder Usage: UNIX/Linux
-
Download and Extract
Download the recorder binary onto the backup servers involved in the migration.
Ensure at least 2GB of free space on the filesystem.
Extract using:> tar xzf tzm_recorder_linux.64.tgz If tar does not support z:
> gunzip tzm_recorder_linux.64.tgz > tar xf tzm_recorder_linux.64.tgz -
Update Permissions
> chmod +xr -R tzm_recorder -
Execute the Recorder
> cd tzm_recorder > ./tzm_recorder INFO | Tool build date Thu Apr 6 21:45:03 2023 INFO | START - Gathering environment information INFO | Retrieving process list
Recorder Usage: Windows
-
Download and Extract
Download the Windows binary zip file and extract the contents.
Ensure at least 2GB of free space on the extracted filesystem.
Right-click the zip file and select "Extract." -
Execute the Recorder
Open a CMD prompt, navigate to the extracted directory, and run:# tzm_recorder.exe
The CMD prompt should be started as Run as Administrator or with an account that has Administrator rights.
Recorder Usage: NetBackup Appliance
- Copy recorder to NetBackup Appliance
Use scp to copy the recorder tarball to the appliance:> scp recorder.tar.gz admin@<appliance_IP>:/tmp/ Default password is:
P@ssw0rd - Connect via SSH
Log in to the appliance using SSH:> ssh admin@<appliance_IP> Default password is:
P@ssw0rd - Enter Maintenance Mode
From CLISH, navigate to:> Support > Maintenance Enter the Maintenance password when prompted.
- Override IPS Policy
Run the override script:> /opt/Symantec/sdcssagent/IPS/sisipsoverride.sh > /opt/veritas/sdcssagent/IPS/sisipsoverride.sh (in some cases) You will see output such as:
- Symantec Critical Protection Policy Override
- Agent Version: 6.5.0 (build 355)
- Current Policy: NetBackup Appliance Prevention Policy, r33
- Policy Prevention: Enabled
- Policy Override: Allowed
- Override State: Not overridden
Enter the Maintenance password again to proceed.
- Select Override Type
Options:- Override Prevention except for Self Protection
- Override Prevention Completely
Choose option 2 for complete override. (Option 1 may interfere with recorder operations.)
- Set Override Duration
Choose from:- 15 minutes
- 30 minutes
- 1 hour
- 2 hours
- 4 hours
- 8 hours
Select the maximum duration required.
- Optional Comment
Enter a comment or pressEnterto skip. - Elevate to Root
Once override is successful:> maintenance - !> elevate - Execute recorder
cd to /tmp or whichever directory recorder is copied.
Extract the recorder tarball and set execute permissions for the recorder binary:
Execute the recorder:
# cd /tmp # tar -xzf recorder.tar.gz # cd recorder # chmod +x recorder # ./recorder
Recorder Usage: NetBackup Flex Appliance or Flex Scale
- Connect via SSH
SSH into the appliance node using hostadmin as the username:> ssh hostadmin@<node_IP> Default password is:
P@ssw0rd - Elevation in Locked or High-Security Modes
By default Flex/Flex Scale Appliance will be in Compliance or Enterprise lockdown mode. Rungenerate-otpand provide the OTP to Cohesity support to receive security key for root elevation. Set a Support password which will be later used to elevate to root. Log in to the Appliance shell on any node and run:> support unlock Enter the security key provided by Cohesity support to unlock support. Once done run below command to elevate to root
> support elevate Enter the support password set in previous step and Press
Enterkey. Type the maintenance password to get into the root shell.> support unlock - Copy amd Execute recorder
Copy the recorder tarball to /tmp directory using scp:> scp recorder.tar.gz hostadmin@<node_IP>:/tmp/ Extract the recorder tarball and set execute permissions for the recorder binary:
# cd /tmp # tar -xzf recorder.tar.gz # cd recorder # chmod +x recorder # ./recorder
Recorder Usage: NetBackup CloudScale
-
Copy Recorder Binary
Securely Copy the recorder binary from the machine to CloudScale Terraform management server (TMS or tms):> scp tzm_recorder_linux.64.tgz <user>@<cloudscale-tms-ip>:/tmp -
Access the Environment
Log in to the Kubernetes cluster or CloudScale Terraform management server:> ssh <admin>@<cloudscale-tms-ip> -
Identify Target Pod
List the pods in the target namespace to identify where to deploy the recorder: The primary server pod will end with “-primary-0” and the namespace will be “netbackup”> kubectl get pods -n netbackup -
Transfer to Pod
Copy the Recorder from CloudScale to the primary server pod:> kubectl cp tzm_recorder_linux.64.tgz <namespace>/<pod-name>:/tmp/ -
Extract and Prepare
Login to the primary server pod and extract the recorder:> kubectl exec -it <pod-name> -n <namespace> -- /bin/bash > cd /tmp > tar -xzf tzm_recorder_linux.64.tgz > cd tzm_recorder -
Run the Recorder
Set the executable permission and execute the recorder inside the pod. Execute “./tzm_recorder -setup_nbat” to authenticate NBAT for successful authentication with NetBackup. You’ll be prompted for the following information. Initial user name and password can be found in the azure/deployment TFVARS files used to deploy the CloudScale cluster.> chmod +x ./tzm_recorder > ./tzm_recorder -setup_nbat Please enter the type (NIS, NISPLUS, WINDOWS, vx, unixpwd, ldap) > unixpwd #This will always be unixpwd Please enter the broker > PRIMARY_FQDN Please enter the login username > USERNAME Please enter the password for adpadmin > PASSWORD This will create a file /tmp/tzm_recorder/nbat_info.txt
Now execute the tzm recorder to start the data collection process> ./tzm_recorder INFO | START - Gathering environment information INFO | Retrieving process list Once the tzm_recorder completes, log out of the primary pod to get back to the shell on the Terraform management server.
Execute the following command to copy the TZM recording file back to the local directory> kubectl cp <namespace>/<pod-name>:/tmp/tzm_recorder/<TZM_RECORDING.ZIP> ./<TZM_RECORDING.ZIP>
Ensure the pod has sufficient free space (≥2GB) before extraction and execution.
Data Anonymization
By default, tzm_recorder generates an output file as a zip. To anonymize data, either extract manually or run with the -no_zip option:
| > tzm_recorder -no_zip |
Sample Sizing Data
NetBackup
-------------------------------------------------------------
-- 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
|
Spectrum Protect / TSM
-------------------------------------------------------------
-- 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
|
Data Protector
-------------------------------------------------------------
-- 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
-------------------------------------------------------------
-- 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
|
Backup Exec
-------------------------------------------------------------
-- 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
|
Networker
-------------------------------------------------------------
-- 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
|
