White Paper
on
PCT / Recovery Integration
-1-
Table of Contents
1. Introduction…………………………………………………………………………….…….3
1.1. Prerequisites…………………………………………………………………………...3
2. Step to be followed on Source Side……………………………………………………….4
3. Step to be followed on Destination Side…………………………………………………..7
4. Assumptions………………………………………………………………………………….8
5. Issues……………………………………………………………………………..................9
-2-
PCT / Recovery Integration
1
Introduction
Module ‘CR Integration’ involves changes in two components of PC Transplant namely
PCTWiz and PCTInst.
Following is the overview on each side.
PCTWiz
A new package type ‘Recovery Package’ will be introduced to accomplish CR Integration.
When specified, only references to files that need to be picked up will be stored in
packages with some exceptions. This list currently include resource file, AClient related
files and help files. After detection of existence of the Recovery agent on source
computer, PC Transplant in this case PCTWiz will request CR Client to take machine
backup after forming list of files that it need to capture.
PCTInst
When Recovery type of package is executed on Destination machine PC Transplant, in
this case PCTInst will determine the existence of CR Client on the machine. If found, it
will request the last backed up data from CR Server after forming the list files that need to
be requested. This migration process will be done category wise and will be done in
batches. For this purpose, a tool provided by CR will be used. This tool will accept
arguments from PC Transplant in form of command lines. Once a category or batch,
whichever applicable, is processed PC Transplant will analyze the individual file status
returned by CR Tool. Due to nature of the migration, in this case, batch or category, files
will be added to the Rollback file before being requested from CR.
1.1
Prerequisites:Server Side

NS with Recovery Solution installed. This is the machine where backup
of other machine’s data would be kept and later on requested for restore.
Client Side
Source Side/Capture Side


PCTWiz installed.
Recovery Agent installed.
Destination/ Deploy Side

Recovery Agent installed.
-3-
2.
Steps to be followed on Source/Capture Side:Logged in user should be administrator on source machine and should be the user of
same domain as of NS.
1. Steps to install Recovery client agent.
First Method
a. Open the web browser on client machine.
b. Type http://<ServerName>/agent. (<ServerName> is the name of server on which NS
with Recovery Solution is installed)
c. Follow the four easy steps to install Recovery agent. (Please see the inserted gif)
-4-
-5-
Second Method
a. Execute \\<ServerName>\NSCap\Bin\Win32\X86\Recovery Agent
Package\AgentSetup.exe
(<ServerName> is the name of server on which NS with Recovery Solution is installed)
b. This would install the client agent.
In the above two method after the installation of Recovery Client Agent on source
machine the user have to restart the machine and take the initial snapshot manually.
2. Install PCTWiz on source machine.
3. Commandline used for recovery type package creation.
Provide the following command line switch on wizard side to make it Recovery type
package:>PCTWiz.exe –recoverypackage:0/–recoverypackage:1

-RecoveryPackage:0 means a normal package will be created if
Recovery agent is not found or error occurs with Recovery on source side.

-RecoveryPackage:1 means package creation will be aborted if
Recovery agent is not found or error occurs with Recovery on source side.
4. Select Desktop, Network, Application, Some files, folders and files types Settings from
respective Pages and go to ‘’Creating a Personality’ Page and click on ‘OK’ Button.
5. A dialog box of 'Recovery Agent Snapshot Progress' is shown and snapshot of entire
machine is taken (Snapshot: - Backup of entire machine).
6. After the completion of snapshot the dialog box closes and the package gets created.
7. The package that is created will have only references for the data.
-6-
3.
Steps to be followed on Destination/Deploy Side
Logged in user should be administrator on destination machine and should be the user of
same domain as of NS.
1. Install Recovery agent with the following commandline:/Silent /Reinstall /Comp:<Comp-Name> /User:<User Name> /Domain:<domain name>
/Pass:<Password> /Initialsnapshot:0 /Reboot.
(
<Comp-Name> is the name of the computer from which user have took the snapshot.
<User Name> is the name of the user whose credentials where used while installing
recovery client on source machine.
<Domain Name> is the name to which the user belongs.
<Password> is the password of the user.
)
2. The machine will restart automatically and after the restart snapshot will not be taken.
3. Execute the Recovery type of package is executed on Destination machine.
4. PCTInst will determine the existence of CR Client on the machine. If found, it will
request the last backed up data from CR Server after forming the list files that need to be
requested. This migration process will be done.
5. After migration verify all the setting and data.
Note:If network connection becomes disabled while deploying a package than a message box
appears in the taskbar of client machine, which needs to be clicked for execution of
package. The dialog looks similar to
-7-
4.
Assumptions:1. The data that will be requested from CR will be the latest one that is backed up.
2. Both data and setting files will be restored from CR server.
3. If in the time duration between capture and deploy certain file is removed from the
source machine, it is assumed that last backed up version will be available on CR
Server.
4. The warning about deploying the package as soon as possible will be displayed on
source machine.
5. RsaCmd tool will support redirection of files and folder by parsing ini or XML file.
6. Settings and data will be roll backed if connection fails during migration
7. Compression will not be enabled for such packages.
8. Application Installation is not been tested with Recovery type package in PCT
Standalone. This feature may or may not work.
9. Some file types, which require special processing (INI, CONFIG, BATCH).
10. Some files needs to be stored inside package.
11. We would be requesting complete backup of machine just before capturing and not after
migration or rollback.
12. Recovery to a different machine is only supported if the Administrator follows CR’s
process definition for agent rollout to a target machine. Only then will the RsaCmd tool
and migration work from a source to destination machine.
13. Recovery will determine if a file needs to be sent down. They have built in CRC
fingerprinting that will determine file differences prior to requesting it from the server.
14. PCTWiz will not allow these package types to be edited. But PCTEdit and PkgCntnt can
still view the contents of the file, but will not be able to edit them for support reasons.
15. RsaCmd will be included with the CR client install. It will be located in a specific folder
for easy access.
16. Since the migration is supposed to happen as soon as a package is built, we will be able
to determine analysis size depending upon the information available in package.
-8-
5.
Issues:1. When the logged in user on destination machine is Local Administrator then recovery
type package fails to recover major part of the data (Reference TTPRO bug#1298).
2. 'Migration of Cookies' of MS Internet Explorer from Win 9x to Win NTx through
recovery type package is not working (Reference TTPRO bug#1288).
3. While capturing a recovery type package in -q/-qm mode, 'Recovery Agent Snapshot
Progress' should not be shown (Reference TTPRO bug#1302).
4. If simulation is carried out in UI mode with Recovery type Package then actual
migration of data is done whereas simulation works fine in –q/-qm mode
(Reference TTPRO bug#1320). That means in case of quiet mode even if user has
mentioned –simulate switch, that flag would be reset to false for recovery kind of
packages.
-9-