ajdibble
asked on
Windows Clone Install job to Restore a Donor Image bombs out when using IBM Director
I've used IBM Director\Remote Deployment Manager\Get Donor Image to take a snapshot image of my Windows 2003 server.
I then try and restore this image by creating a job under Windows Clone Install.
Watching the console of the server being restored, I see a progress bar as the clone.pqi image is restored.
After a while, the process bombs out - i.e. the progress bar is replaced by a DOS-based screen headed:
CauseWay DOS Extender v3.49 Copyright 1992-99 Michael Devore.
....
Exception: 0E, Error code: 0004
....
CaseWay error 09 : Unrecoverable exception. Program terminated.
We've tried one workaround that a colleague found on the web, which talked about there being a problem with image sizes larger than 2GB, but it didn't fix the problem.
The problem is consistent - i.e. it's not just one image (so it's unlikely to be due to a corrupt image) but several.
Any ideas?
I then try and restore this image by creating a job under Windows Clone Install.
Watching the console of the server being restored, I see a progress bar as the clone.pqi image is restored.
After a while, the process bombs out - i.e. the progress bar is replaced by a DOS-based screen headed:
CauseWay DOS Extender v3.49 Copyright 1992-99 Michael Devore.
....
Exception: 0E, Error code: 0004
....
CaseWay error 09 : Unrecoverable exception. Program terminated.
We've tried one workaround that a colleague found on the web, which talked about there being a problem with image sizes larger than 2GB, but it didn't fix the problem.
The problem is consistent - i.e. it's not just one image (so it's unlikely to be due to a corrupt image) but several.
Any ideas?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
If you are running RDM 4.30 and you have a multiple-file clone image, your Windows Clone Install task may fail with a Causeway 09 error. It is caused by
DeployCenter not handling its command-line syntax (i.e., the /ARG parameter) correctly. You can circumvent this problem by modifying your DEPLOY.BAT file and rebuilding the DOS environments. Here are the steps:
Make a back-up copy of \Program Files\IBM\RDM\local\env\71
Edit the deploy.bat file.
Change the PQImgCtr statement (originally line 62) as follows (by adding REM to line 62 and inserting a modified command after that line):
...
:NOTLINUX
IF "%HASRAID%" == "TRUE" GOTO RAID
IF "%MACHINETYPE%" == "9228" GOTO NOIDE
IF "%MACHINETYPE%" == "7978" GOTO NOIDE
RDAGENT /L "Starting PQImgCtr for Image Deployment - IDE Optimized"
REM PQImgCtr /IMG=\\.\imgsrv\%SERVER_IP
PQImgCtr /IMG=\\.\imgsrv\%SERVER_IP
GOTO RETURN
...
Run U:\Program Files\IBM\RDM\local\env\MK
For Causeway 09 errors in RDM 4.20.3, do not make the above change. Consult the RDM Troubleshooting white paper (on http://www-1.ibm.com/support/docview.wss?uid=psg1MIGR-53487) for instructions about this error in RDM 4.20.3.