Monday, November 25, 2013

Home /Migration /Quest Migration Manager / QMM Transmission Agent (NTA) and Robocopy

QMM Transmission Agent (NTA) and Robocopy

1 comment

Quest Migration Manager (QMM) has its own logic to transfer (migrate) from data a source mailbox to a target mailbox  MSA –> NTA –> MTA.  Latest version of QMM for Exchange supports multiple agents on Quest Agent Host.  You  can have up to 10 MSAs and 10 MTAs but Transmission Agent (NTA) is still limited to 1 per Agent Host.  This is still a huge limitation when transferring  large amount of data.  Quest’s NTA still performs a single threaded, sequential operation.  Even if you have enough “available” bandwidth, these types of applications cannot be able to use all available bandwidth. 

In QMM for Exchange, NTA is responsible for referring the exacted PRV files from Source to Target agent servers.  If NTA is the bottleneck, you can use any other mechanism to copy PRV  files from Transmission OUT folder to Transmission IN Folder.  Keep in mind that you need to copy all extracted files at the same time (or in the correct order).   I have decided replace NTA with a Robocopy option for the initial data copy.  With Robocopy, you can specify the thread up to 128. 

Using the following method, I have reduced the file copy time from weeks to hours!

  1. Stop Transmission Agent (NTA)
  2. Stop Mail Target Agent (MTA)
  3. Start Mail Source Agent (MSA) and generate all PRV files from source mailboxes.
  4. After the initial creation of all PRV files (you can verify this by reviewing the MSA log file), Stop MSA
  5. Perform a Robocopy operation to copy all files from OUT folder to IN folder.  Here is an example:

Robocopy “\\SourceAgentHost01\C$\Windows\SysWOW64\Aelita Exchange Migration Wizard\Mail Transmission Agent\OUT\TargetAgetnHost01\2” “\\TargetAgentnHost01\c$\Windows\SysWOW64\Aelita Exchange Migration Wizard\Mail Transmission Agent\IN\SourceAgentHost01\2” /MT:128

In the above example, MSA and NTA was running on SourceAgentHost01 and MTA was on TargetAgentnHost01

  1. Start MTA agent and complete mail data import process. 
  2. After the initial data copy, you can start the MSA, NTA and MTA agents. The delta change or update will go thought the normal Quest process (MSA –> NTA –> MTA). 

Microsoft Robocopy - http://technet.microsoft.com/en-us/library/cc733145.aspx

Filed under
Share X LinkedIn Facebook Email
SS

Santhosh Sivarajan

Microsoft MVP · Identity & Cybersecurity Architect

Santhosh has 30+ years of hands-on enterprise experience in Identity and Access Management, Microsoft Entra ID, Active Directory, Microsoft 365 and Zero Trust architecture. He is the author of two books on Windows Server and security, and leads consulting, assessments and training at SAG Business Group.

SAG Business Group LinkedIn Publications Work with Santhosh

1 comments:

Is this still the case with the latest versions of QMMEx?

Thanks.

Post a Comment

Popular Posts
Workstation Trust Relationship Issue Issue: You receive the following error message, when you try to login to the domain.  The security database on the server does not have ... ADMT Service Account - Permission and Configuration The ADMT service account needs to have proper permission in source and target domains.  You don’t need to use 2 separate accounts.  You can ... My First Peek into Microsoft Exchange 2010 By Santhosh Sivarajan Before I really dive into Exchange 2010, I thought I would install and play with it first. I took some screen shots and notes during the ins... ObjectSID and Active Directory What is an objectSID in Active Directory? When a new object is created in Active Directory, Domain Controller assigns a unique value used ... AD Group Report - List Group Members in Active Directory–PowerShell Script Updated Script - http://portal.sivarajan.com/2011/10/search-ad-collect-local-admin-group.html Script #1 This script... Add Users to a Group–PowerShell Script Purpose – Add users to a group from an input file – PowerShell V2 Script.  Input file – Input file (Users.csv) contains samAccountName in... User Account Migration and Merging – Part I (ADMT) Part I - User Account Migration and Merging Using ADMT Part II - User Account Migration and Merging Using QMM pre-creating user account ... User Account Migration and Merging – Part II (Quest Migration Manager) Part I - User Account Migration and Merging Using ADMT Part II - User Account Migration and Merging Using QMM Pre-creating user account in... Delete Stale or Inactive Computer Accounts from Active Directory Here is an easy way to identify and delete inactive or stale computers in an Active Directory environment.  Using the dsquery command you c... Converting PowerShell (PS1) to EXE / Standalone Application As we know, there many applications available to convert a PowerShell file to a standalone executable file.  Based on my experience, PowerSh...