Tranzman Documentation - User contributions [en]

Create Bootable TZM USB using Rufus

2022-08-18T10:36:01Z

Simon: /* Creating bootable TZM media from ISO image */

== Creating bootable TZM media from ISO image ==

This is the installation video shows a glimpse of creating a own bootable media for TZM installation.

[[image:iso_bootable.gif | border]]

{| class="wikitable" style="margin:auto;width:100%;color:blue;text-align:center;borderstyle=ridge;"
|-
| Go to [[ Install TZM Server |TZM Installation steps ]]
|| Return to [[ Installation |Installation ]]
|}

Create Bootable TZM USB using Rufus

2022-08-18T10:31:58Z

Simon: /* Creating bootable TZM media from ISO image */

== Creating bootable TZM media from ISO image ==

This is the installation video shows a glimpse of creating a own bootable media for TZM installation.

[[File:iso_bootable.gif | border|1100x800px]]

{| class="wikitable" style="margin:auto;width:100%;color:blue;text-align:center;borderstyle=ridge;"
|-
| Go to [[ Install TZM Server |TZM Installation steps ]]
|| Return to [[ Installation |Installation ]]
|}

Create Bootable TZM USB using Rufus

2022-08-18T10:27:33Z

Simon: /* Creating bootable TZM media from ISO image */

== Creating bootable TZM media from ISO image ==

This is the installation video shows a glimpse of creating a own bootable media for TZM installation.
{| class="wikitable" style="margin:auto;width:100%"
|-
| [[File:iso_bootable.gif]]
|}

{| class="wikitable" style="margin:auto;width:100%;color:blue;text-align:center;borderstyle=ridge;"
|-
| Go to [[ Install TZM Server |TZM Installation steps ]]
|| Return to [[ Installation |Installation ]]
|}

MediaWiki:Sidebar

2022-08-16T15:28:05Z

Simon:

Anti-Virus Considerations

2022-02-03T23:44:56Z

Simon:

Antivirus software, and some or software based firewall programs, may interfere with Tranzman Agents or even the Backup Software. This can result in performance issues, or unpredictable behaviour.

The requirements for Tranzman are similar to those provided by the Backup Vendors, and in order to ensure that the migration runs as smoothly and efficiently as possible we recommend that any recommendations given by the backup vendors are taken into account, along with the recommendations made below.

===Tranzman Requirements for virus scanner exclusions===

It would be recommended that for the Duration of the migration the virus scanner is either disabled, or the following processes and directories are excluded.

'''Processes'''

Excluded the following agent processes on the Backup servers from on-access scanning
<InstallPath>/srl/tzmclnt/tzmclnt.exe
<InstallPath>/srl/tzmclnt/tzmclntshdw.exe
<InstallPath>/srl/tzmclnt/tzmsub.exe
<InstallPath>/srl/tzmclnt/tzmaction.exe
<InstallPath>/srl/tzmclnt/tzmcurl.exe
<InstallPath>/srl/tzmclnt/nssm.exe

'''Directories'''

Exclude the following folders, and all sub folders, from on-access and full scans
<installPath>/srl/tzmclnt

===NetBackup Specific Requirements===

During the process Tranzman temporarily renames some files, copies in alternatives and then after processing moves the back, this is done with the following NetBackup commands and paths should also be excluded for the duration of the migration

<NBU INSTALL PATH>\NetBackupDB\win64\dbunload.exe
<NBU INSTALL PATH>\NetBackupDB\win64
<NBU INSTALL PATH>\NetBackup\bin\nbdb_unload.exe

Furthermore, NetBackup recommends addition of exclusions in your anti-virus product for the following commonly blocked items.

'''Processes(Windows notation)'''

dbsrv16.exe - Adaptive Server Anywhere - NetBackup Relational Database Manager
(check service to identify precise binary name as it will change when NBU is updated dbsrvNN.exe)
nbars.exe - NetBackup Agent Request Server
nbaudit.exe - NetBackup Audit Manager
nbatd.exe - NetBackup Authentication
nbazd.exe - NetBackup Authorization
bmrd.exe - NetBackup Bare Metal Restore Master Server
nbcssc.exe - NetBackup CloudStore Service Container
bpcompatd.exe - NetBackup Compatibility Service
spoold.exe - NetBackup Deduplication Engine
spad.exe - NetBackup Deduplication Manager
mtstrmd.exe - NetBackup Deduplication Multi-Threaded Agent
nbdisco.exe - NetBackup Discovery Framework
nbevtmgr.exe - NetBackup Event Manager
nbim.exe - NetBackup Indexing Manager
nbkms.exe - NetBackup Key Management Service
nbemm.exe - NetBackup Enterprise Media Manager Service
nbjm.exe - NetBackup Job Manager Service
nbnos.exe - NetBackup Notification Service (on NetBackup 6.x and earlier)
nbpem.exe - NetBackup Policy Execution Manager Service
nbrb.exe - NetBackup Resource Broker Service
nbrmms.exe - NetBackup Remote Manager and Monitor Service
nbsl.exe - NetBackup Service Layer Service
nbostpxy.exe - NetBackup Proxy Service
nbsvcmon.exe - NetBackup Service Monitor Service
nbstserv.exe - NetBackup Storage Lifecycle Manager
nbvault.exe - NetBackup Vault Manager Service
nbftclnt.exe - NetBackup SAN Client Fibre Transport Service
nbwmc.exe - NetBackup Web Management Console
java.exe - Tomcat
vnetd.exe - NetBackup Legacy Network Service
vmd.exe - NetBackup Volume Manager Service
bpcompatd.exe - NetBackup Compatibility Service
bpinetd.exe - NetBackup Client Service
bpdbm.exe - NetBackup Database Manager Service
ltid.exe - NetBackup Device Manager Service
bprd.exe - NetBackup Request Manager Service
bpjobd.exe - NetBackup Job Daemon
bpbkar32.exe - NetBackup Backup Engine
bpbrm.exe - NetBackup Backup and Restore Manager
bpcd.exe - NetBackup Connection Daemon
bptm.exe - NetBackup Tape Manager
bpdm.exe - NetBackup Disk Manager
tar32.exe - NetBackup Restore Engine
pbx_exchange.exe - Veritas (Veritas) Private Branch Exchange Service
cmd.exe - this is called by NetBackup nbproxy.exe, nbpem.exe and nbjm.exe

'''Directories'''
The following paths and their SUBFOLDERS are also normally excluded from on-access scanning
<NBU INSTALL PATH>\Volmgr\
<NBU INSTALL PATH>\NetBackup\
<NBU INSTALL PATH>\VxPBX\
<NBU INSTALL PATH\NetBackup\db (on some systems this has been created as a link, the real endpoint folders / drives should also be excluded )

Clish

2022-01-10T08:36:03Z

Simon:

{|
|[[Initial Configuration|config]]
|   
|Initial Configuration
|-
|exit
|   
|Exit this CLI session
|-
|help
|   
|Display an overview of the CLI syntax
|-
|[[Media Import|media_import]]
|   
|Import media directly to files or destination product
|-
|[[Generate Reports|reports]]
|   
|Reports
|-
|[[Support Menu|support]]
|   
|Support tools
|-
|[[Validation Menu|validation]]
|   
|Perform Pre and Post transition checks
|}

FAQ

2022-01-07T18:50:53Z

Simon:

Here are common problems/ questions asked about Tranzman and simple solutions to fixing them.

'''Q.The Web GUI keeps saying connection refused when I browse to its page. The appliance is on, because I can still remote connect to it.'''

* This can happen if the services on the appliance encounter an error. From the CLI go to '''support => services => services_restart'''
* Now go to the Web GUI address and this should be working now.

'''Q.How do I configure my Windows NBU environment to work with the Tranzman Appliance?'''
* When using Tranzman for Cross-Vendor migrations with a Windows NBU master server as the destination, the NetBackup Client Service (bpcd.exe) needs to be configured to use a "service account" and not "local system" account.
* This is because the Tranzman Appliance storage is presented as a "share" to the NetBackup Master server. See [https://www.veritas.com/support/en_US/article.000014282 Veritas Technote 000014282] for more details.

'''Q.I am trying to download the ISO/OVA file through StoneRam Fileshare, but it's failing after downloading some content.'''
*This can happen due to some bandwidth issues, proxy restrictions or endpoint protection tools that cause the connection to timeout.
*Please follow the [[ StoneRam FileShare | this ]] procedure to download the file in chunks.

'''Q.How do I configure Tranzman Agent on a NetBackup Flex environment or other containerised environment'''
* When using Tranzman for Cross-Vendor or Same-Vendor migrations with a containerised Master running on a Flex Appliance, the following steps should be taken to ensure that the agent installs and doesn't keep stopping.
* install the agent to "/mnt/nbdata/SRL" this ensures that it is in a persistent volume
* change the path for curl to "/bin/curl" as that is where it is on a Flex instance.
* create a cron entry to start the agent, this ensures that even if you log out the agent will keep running, as for some reason, even though the agent is set to run in the background, it is being terminated with the shell session.
{| class="wikitable" style="padding-left: auto; color:#FFFFFF; background-color: black; width: 600px; FONT-FAMILY:monospace,monospace; LINE-HEIGHT:15px; white-space: pre-wrap;
|
crontab -e
21 * * * * cd /mnt/nbdata/opt/SRL/tzmclnt; ./tzmclnt
|}

'''Q.When working with NetBackup appliances that use Symantec Critical Protection, we need to tell Tranzman the maintenance password'''
* When using Tranzman on a NetBackup appliance where Symantec Critical Protection is enabled we need to create a file in the agent folder
/opt/SRL/tzmclnt/nbu_appliance_maintenance_pw
in it we need to put the password you use when you go into "maintenance" in the clish.

Installation

2022-01-07T14:58:53Z

Simon:

Download Tranzman installation ISO image or the OVA Template provided by Stone RAM Ltd.

For help in performing an installation follow below links in the table:-

{| class="wikitable" style="border:5px double maroon" font-family:Arial, Helvetica, sans-serif !important align=center cellpadding=40px width=80%;;"
|+Installation Table
|-
| [[Create Bootable TZM USB using Rufus]]
| Guide for creating your own bootable USB for TZM install on to physical servers
|-
| [[Install VA - Hyper-V]]
| Prepare a Virtual Appliance in Hyper-V
|-
| [[Install TZM Server]]
| Install Tranzman Appliance onto a Physical/Virtual Machine
|-
| [[Install TZM Server Using OVA]]
| Install Tranzman Appliance in a VMWare Environment
|}

[[ Configuration | Jump to Configuration ]]

[[ Planning | Return to Planning and Sizing ]]

FAQ

2022-01-07T14:56:30Z

Simon:

FAQ

2022-01-07T14:53:58Z

Simon:

Here are common problems/ questions asked about Tranzman and simple solutions to fixing them.

'''Q.The Web GUI keeps saying connection refused when I browse to its page. The appliance is on, because I can still remote connect to it.'''

* This can happen if the services on the appliance encounter an error. From the CLI go to '''support => services => services_restart'''
* Now go to the Web GUI address and this should be working now.

'''Q.How do I configure my Windows NBU environment to work with the Tranzman Appliance?'''
* When using Tranzman for Cross-Vendor migrations with a Windows NBU master server as the destination, the NetBackup Client Service (bpcd.exe) needs to be configured to use a "service account" and not "local system" account.
* This is because the Tranzman Appliance storage is presented as a "share" to the NetBackup Master server. See [https://www.veritas.com/support/en_US/article.000014282 Veritas Technote 000014282] for more details.

'''Q.I am trying to download the ISO/OVA file through StoneRam Fileshare, but it's failing after downloading some content.'''
*This can happen due to some bandwidth issues, proxy restrictions or endpoint protection tools that cause the connection to timeout.
*Please follow the [[ StoneRam FileShare | this ]] procedure to download the file in chunks.

'''Q.How do I configure Tranzman Agent on a NetBackup Flex environment or other containerised environment'''
* When using Tranzman for Cross-Vendor or Same-Vendor migrations with a containerised Master running on a Flex Appliance, the following steps should be taken to ensure that the agent installs and doesn't keep stopping.
* install the agent to "/mnt/nbdata/SRL" this ensures that it is in a persistent volume
* change the path for curl to "/bin/curl" as that is where it is on a Flex instance.
* create a cron entry to start the agent, this ensures that even if you log out the agent will keep running, as for some reason, even though the agent is set to run in the background, it is being terminated with the shell session.

crontab -e
21 * * * * cd /mnt/nbdata/opt/SRL/tzmclnt; ./tzmclnt

FAQ

2022-01-07T14:43:41Z

Simon:

FAQ

2022-01-07T14:40:18Z

Simon:

Planning

2022-01-07T14:37:55Z

Simon: /* Overview */

{|style="font-size: 15px;"
|
== Overview ==
|}
To help determine the correct sizing for a Tranzman Appliance Deployment, it is recommended that the [[Recorder|Tranzman Recorder]] is used to help better understand the current environment and its sizing.

A deployment can be done either using an ISO image, or in the case of VMware an OVA template (A virtual appliance should only be used for same-vendor transitions, and where no connectivity to tape media or very large ( > 2TB) disk volumes is required)

The OVA template can be used for environments with up to 2 Million images without any modifications. We recommend an additional 2GB of ram per 500K additional images.

A single Tranzman Appliance can be used to convert many environments, the following considerations need to be taken into account when sizing it.

{|style="font-size: 15px;"
|
===RAM===
|}
{| class="wikitable" style="text-align:center; font-size:14px; font-family:Arial, Helvetica, sans-serif !important;;"
|- style="font-weight:bold; font-size:16px;"
! RAM Size
! Use Case
|-
| Minimum 4G
| style="text-align:left;" | Using appliance only for assessments
|-
| Minimum 8GB
| style="text-align:left;" | Migrating Same Vendor
|- style="text-align:left;"
| Minimum 8GB
| Migrating Cross Vendor
|}
{|style="padding: 5px; width: 85%;"
| style="width: 1%;"|[[File:Note.png|30px]]|| style="padding: 10px; width: 85%;"|'''Note:''' Additional 1GB of RAM is required for every tape drive connected to the Appliance
|
|}

{|style="font-size: 15px;"
|
===CPU===
|}
{| class="wikitable" style="font-size:14px; font-family:Arial, Helvetica, sans-serif !important;;"
|- style="font-weight:bold; font-size:16px;"
! CPU Core
! Use Case
|- style="text-align:center;"
| Minimum 4 core Intel CPU
| style="text-align:left;" | Migrating Same Vendor
|-
| Minimum 8 core Intel CPU
| Migrating Cross Vendor
|}

{|style="padding: 5px; width: 85%;"
| style="width: 1%;"|[[File:Note.png|30px]]|| style="padding: 10px; width: 85%;"|'''Note:''' Additional 1 core for every tape drive connected to the Appliance
* ONLY INTEL processors have been tested and are supported.
|
|}

{|style="font-size: 15px;"
|
===Network===
|}
* 1Gbit minimum connection required (for Same Vendor migration and recovery on Demand).
* 10Gbit connection recommended for Cross Vendor to ensure that tape drive are kept running at a reasonable speed.
* If multiple links are used, aggregation is needed to provide maximum throughput.
* Multiple connections may be required if there are multiple tape drives.

{|style="font-size: 15px;"
|
===Ports===
|}
The appliance needs to communicate over the network. If you have internal firewalls, you must allow the following connections or the appliance cannot function.

{|style="font-size: 16px;"
|
====Backup Servers (Clients of Tranzman)====
|}

=====All servers=====
{| class="wikitable"
|-
|INBOUND || TCP 443 from ANY
|-
|OUTBOUND || to Tranzman Appliance TCP 55560
|}

=====Destination servers=====
* Windows
{| class="wikitable"
|-
|OUTBOUND || to the Tranzman Appliance TCP 139 and 445 and UDP 137 and 138
|}
* Unix/Linux
{| class="wikitable"
|-
|OUTBOUND || to the Tranzman Appliance TCP 111,4045 and 2049 and UDP 111,4045 and 2049
|}

{|style="font-size: 16px;"
|
====Tranzman Appliance (Server)====
|}
{| class="wikitable"
|-
|INBOUND || TCP 443 from ANY
|-
|INBOUND || TCP 22 from ANY
|-
|INBOUND || TCP 80 from ANY
|-
|INBOUND || TCP 55560 from all origin and destination backup servers
|-
|INBOUND || TCP 139 and 445 and UDP 137 and 138 from destination Windows servers
|-
|INBOUND || TCP 111,4045 and 2049 and UDP 111,4045 and 2049 from destination *nix servers
|-
|INBOUND || TCP 139 and 445 and UDP 137 and 138 from Administration PC(s) Windows Only
|-
|OUTBOUND|| TCP 53 and UDP 53 to the DNS servers
|-
|OUTBOUND|| UDP 123 to the NTP servers
|-
|INBOUND || UDP 123 to the NTP servers.
|-
|OUTBOUND || TCP 25, 587 to the Email server
|}

{|style="font-size: 16px;"
|
====Administration PC====
|}
{| class="wikitable"
|-
|OUTBOUND || to Tranzman Appliance TCP 443
|-
|OUTBOUND || to Tranzman Appliance TCP 80
|-
|OUTBOUND || to Tranzman Appliance TCP 22
|-
|OUTBOUND || to the Tranzman Appliance TCP 139 and 445 and UDP 137 and 138
|}

{|style="font-size: 16px;"
|
===Storage===
|}
* Minimum 3GB local disk for OS Installation.
* Local/SAN attached disks needed for temporary staging of converted images, sized according to volume of recoveries to accommodate at any one time. The following is for guidance only, it would be recommended that you use the [[Recorder|Tranzman Recorder]] and Stone Ram Consulting Services to correctly size the volumes.
{|style="font-size: 15px;"
|

{| class="wikitable" style="font-weight:bold;"
|+Table for Guidance
|- style="font-size:16px; font-family:Arial, Helvetica, sans-serif !important;;"
! Assessment Only
! Same Vendor
! Cross Vendor
|- style="font-weight:normal;"
| style="text-align:center; font-size:16px; font-family:Arial, Helvetica, sans-serif !important;;" | Additional disk of Minimum 20GB
| Additional disk(s) of Minimum ((2.5 * Size of combined catalogs) + (2 * Total Memory))
| Additional disk(s) of Minimum ((2.5 * Size of combined catalogs) + (2 * Total Memory) + Largest of either 3 x Largest image size Number of Drives * max size of compressed tape
|}

[[ Installation | Jump to Installation ]]

[[ Tranzman| Return to Overview ]]

Planning

2022-01-07T14:35:37Z

Simon: /* Headline */

{|style="font-size: 15px;"
|
== Overview ==
|}
To help determine the correct sizing for a Tranzman Appliance Deployment, it is recommended that the [[Recorder|Tranzman Recorder]] is used to help better understand the current environment and its sizing.

A deployment can be done either using an ISO image, or in the case of VMware an OVA template (A virtual appliance should only be used for same-vendor transitions, and where no connectivity to tape media or very large ( > 2TB) disk volumes is required)

The OVA template can be used for environments with up to 2 Million images without any modifications. We recommend an additional 2GB of ram per 500K additional images.

A single Tranzman Appliance can be used to convert many environments, the following considerations need to be taken into account when sizing it.

{|style="font-size: 15px;"
|
===RAM===
|}
{| class="wikitable" style="text-align:center; font-size:14px; font-family:Arial, Helvetica, sans-serif !important;;"
|- style="font-weight:bold; font-size:16px;"
! RAM Size
! Use Case
|-
| Minimum 2G
| style="text-align:left;" | Using appliance only for assessments
|-
| Minimum 8GB
| style="text-align:left;" | Migrating Same Vendor
|- style="text-align:left;"
| Minimum 8GB
| Migrating Cross Vendor
|}
{|style="padding: 5px; width: 85%;"
| style="width: 1%;"|[[File:Note.png|30px]]|| style="padding: 10px; width: 85%;"|'''Note:''' Additional 1GB of RAM is required for every tape drive connected to the Appliance
|
|}

{|style="font-size: 15px;"
|
===CPU===
|}
{| class="wikitable" style="font-size:14px; font-family:Arial, Helvetica, sans-serif !important;;"
|- style="font-weight:bold; font-size:16px;"
! CPU Core
! Use Case
|- style="text-align:center;"
| Minimum 4 core Intel CPU
| style="text-align:left;" | Migrating Same Vendor
|-
| Minimum 8 core Intel CPU
| Migrating Cross Vendor
|}

{|style="padding: 5px; width: 85%;"
| style="width: 1%;"|[[File:Note.png|30px]]|| style="padding: 10px; width: 85%;"|'''Note:''' Additional 1 core for every tape drive connected to the Appliance
* ONLY INTEL processors have been tested and are supported.
|
|}

{|style="font-size: 15px;"
|
===Network===
|}
* 1Gbit minimum connection required (for Same Vendor migration and recovery on Demand).
* 10Gbit connection recommended for Cross Vendor to ensure that tape drive are kept running at a reasonable speed.
* If multiple links are used, aggregation is needed to provide maximum throughput.
* Multiple connections may be required if there are multiple tape drives.

{|style="font-size: 15px;"
|
===Ports===
|}
The appliance needs to communicate over the network. If you have internal firewalls, you must allow the following connections or the appliance cannot function.

{|style="font-size: 16px;"
|
====Backup Servers (Clients of Tranzman)====
|}

=====All servers=====
{| class="wikitable"
|-
|INBOUND || TCP 443 from ANY
|-
|OUTBOUND || to Tranzman Appliance TCP 55560
|}

=====Destination servers=====
* Windows
{| class="wikitable"
|-
|OUTBOUND || to the Tranzman Appliance TCP 139 and 445 and UDP 137 and 138
|}
* Unix/Linux
{| class="wikitable"
|-
|OUTBOUND || to the Tranzman Appliance TCP 111,4045 and 2049 and UDP 111,4045 and 2049
|}

{|style="font-size: 16px;"
|
====Tranzman Appliance (Server)====
|}
{| class="wikitable"
|-
|INBOUND || TCP 443 from ANY
|-
|INBOUND || TCP 22 from ANY
|-
|INBOUND || TCP 80 from ANY
|-
|INBOUND || TCP 55560 from all origin and destination backup servers
|-
|INBOUND || TCP 139 and 445 and UDP 137 and 138 from destination Windows servers
|-
|INBOUND || TCP 111,4045 and 2049 and UDP 111,4045 and 2049 from destination *nix servers
|-
|INBOUND || TCP 139 and 445 and UDP 137 and 138 from Administration PC(s) Windows Only
|-
|OUTBOUND|| TCP 53 and UDP 53 to the DNS servers
|-
|OUTBOUND|| UDP 123 to the NTP servers
|-
|INBOUND || UDP 123 to the NTP servers.
|-
|OUTBOUND || TCP 25, 587 to the Email server
|}

{|style="font-size: 16px;"
|
====Administration PC====
|}
{| class="wikitable"
|-
|OUTBOUND || to Tranzman Appliance TCP 443
|-
|OUTBOUND || to Tranzman Appliance TCP 80
|-
|OUTBOUND || to Tranzman Appliance TCP 22
|-
|OUTBOUND || to the Tranzman Appliance TCP 139 and 445 and UDP 137 and 138
|}

{|style="font-size: 16px;"
|
===Storage===
|}
* Minimum 3GB local disk for OS Installation.
* Local/SAN attached disks needed for temporary staging of converted images, sized according to volume of recoveries to accommodate at any one time. The following is for guidance only, it would be recommended that you use the [[Recorder|Tranzman Recorder]] and Stone Ram Consulting Services to correctly size the volumes.
{|style="font-size: 15px;"
|

{| class="wikitable" style="font-weight:bold;"
|+Table for Guidance
|- style="font-size:16px; font-family:Arial, Helvetica, sans-serif !important;;"
! Assessment Only
! Same Vendor
! Cross Vendor
|- style="font-weight:normal;"
| style="text-align:center; font-size:16px; font-family:Arial, Helvetica, sans-serif !important;;" | Additional disk of Minimum 20GB
| Additional disk(s) of Minimum ((2.5 * Size of combined catalogs) + (2 * Total Memory))
| Additional disk(s) of Minimum ((2.5 * Size of combined catalogs) + (2 * Total Memory) + Largest of either 3 x Largest image size Number of Drives * max size of compressed tape
|}

[[ Installation | Jump to Installation ]]

[[ Tranzman| Return to Overview ]]