Windows Server complete recovery.

Bertrand39100

Active Newcomer
Joined
May 5, 2011
Messages
6
Reaction score
0
Points
0
Hello All,

I try to find a way to build a procedure and tools to recover an entire windows server
((W2K3 or W2K8 (Domain Controler or not)) in case of a crash or failure either on the
same hardware or on different hardware (recover inside a vm).


According what I read by using WinPE is the offical way (ibm : xx)


I try two solution one withe WinPE and another with TSM client.


Can anyone help me customizing WinPE image ?


I want to create a WinPE CD with several TSM version clients inside,
I organized the TSM_WINPE_RECOVERY directory like this :






DSM.OPT :
* COMMUNICATION SETTINGS :
TCPSERVERADDR 172.X.X.X
TCPPORT 1500


NODENAME TEST_01_RECOVERY


PASSWORDACCESS PROMPT




* COMPRESSION SETTINGS ; UNCOMMENT IF DESIRED :
* COMPRESSION YES




* PERFORMANCE TUNING OPTIONS :
TXNBYTELIMIT 25600
TCPNODELAY YES
TCPBUFFSIZE 32
TCPWINDOWSIZE 63




* REDIRECT THE ERROR LOG :
ERRORLOGNAME F:\DSMERROR.LOG




* DISABLE AES128 ENCRYPTION LIBRAIRIES FROM LOADING :
ENCRYPTIONTYPE DES56


each TSM version has the same dsm.opt inside their own directory :
TSMXXX\program files\Tivoli\tsm\baclient\dsm.opt
I have a tsm_winpe_x_x_x_x_.cmd for each tsm version :
tsm_winpe_x32_5_5_3_0.cmd :


REM ****************
REM * SCRIPT : TSM *
REM ****************
SET LASTDRIVE=E
SET PATH=%PATH%;\TSM_5.5.30_WIN32\SYSTEM32
SET PATH=%PATH%;\TSM_5.5.30_WIN32\program files\tivoli\tsm\baclient
SET PATH=%PATH%;\TSM_5.5.30_WIN32\program files\tivoli\tsm\baclient\plugins
CD TSM_5.5.30_WIN32\program files\tivoli\tsm\baclient


as described in the ibm document.


I don't manage to add tsm clients inside the VIM image it's failed or doesn't work successfully
to have a complete recovery CD with WinPE


Here below is the script to build WinPE :


@ECHO OFF
SET WINPE=C:\TEST25_WINPE
SET IMGX=%PROGRAMFILES%\WINDOWS AIK\TOOLS\X86
CD /D %PROGRAMFILES%
CD "WINDOWS AIK\TOOLS\PETOOLS"


SET PATH=%PATH%;%~DP0;%~DP0..\%PROCESSOR_ARCHITECTURE%


CALL COPYPE X86 %WINPE%


CD /D "%IMGX%"


ECHO ==========================================================
ECHO MOUNTRW DE %WINPE%\ISO\SOURCES\BOOT.WIM DANS %WINPE%\MOUNT
ECHO ==========================================================
ECHO []


IMAGEX.EXE /MOUNTRW %WINPE%\ISO\SOURCES\BOOT.WIM 1 %WINPE%\MOUNT


ECHO =============
ECHO KEYBOARD : FR
ECHO =============
ECHO "[INTLCFG -INPUTLOCALE:fr-FR -IMAGE:%WINPE%\MOUNT]"


INTLCFG -INPUTLOCALE:fr-FR -IMAGE:%WINPE%\MOUNT


ECHO =====================
ECHO DRIVER NIC : BROADCOM
ECHO =====================
ECHO "[PEIMG.EXE /INF=<path> %WINPE%\MOUNT\Windows]"


PEIMG /INF=C:\TSM_WINPE_RECOVERY\NIC_BC_W2K3_W2K8\RIS\b06nd.inf %WINPE%\MOUNT\Windows


ECHO ============================================================
ECHO COPY "TSM_WINPE_RECOVERY" IN %WINPE%\MOUNT\WINDOWS\SYSTEM32\
ECHO ============================================================
ECHO []


Different tests but none are successfull


MKDIR %WINPE%\Tools\TSM_CLIENTS
XCOPY C:\TSM_WINPE_RECOVERY\*.* %WINPE%\Tools\TSM_CLIENTS /S/E/V


REM XCOPY C:\TSM_WINPE_RECOVERY\*.* %WINPE%\ISO\ /S/E/V
REM XCOPY C:\TSM_WINPE_RECOVERY\*.* %WINPE%\Tools /S/E/V
REM MKDIR %WINPE%\MOUNT\TSM_CLIENTS
REM XCOPY C:\TSM_WINPE_RECOVERY\*.* %WINPE%\MOUNT\TSM_CLIENTS\ /S/E/V
REM XCOPY C:\TSM_WINPE_RECOVERY\*.* %WINPE%\MOUNT\Windows\MyApp\ /S/E/V
XCOPY C:\TSM_WINPE_RECOVERY\*.* %WINPE%\MOUNT\Windows\System32\ /S/E/V




ECHO "[IMAGEX.EXE /UNMOUNT /COMMIT %WINPE%\MOUNT]"


IMAGEX.EXE /UNMOUNT /COMMIT %WINPE%\MOUNT


ECHO "[OSCDIMG -N -B%WINPE%\ETFSBOOT.COM %WINPE%\ISO %WINPE%\WINPE.ISO]"


OSCDIMG -N -B%WINPE%\ETFSBOOT.COM %WINPE%\ISO %WINPE%\WINPE_RECOVERY_CD.ISO






But ouside the winPe image ; tsm client communicate and works fine with server.


dsmc or dsmc -virtualn=source_w2k3 communicate well with the server.




otherwise, I 'm testing anothing way ;


Creating a windows server VM :
Install TSM client
Configure the TSM client as the damaged node.
Over TSM GUI ; restore local drive ;
Cancel requested reboot
Restore SystemState ;
Reboot system


Is the there anyone has a sucessfull way to recover a complete windows system (domain controller or not) ?


Any ideas or hints will be appreciate.


Many Thanks.


Bertrand.
 

Attachments

  • WINPE.JPG
    WINPE.JPG
    226.9 KB · Views: 7
Domino,

MANY Thanks for your answer and informations you provide me.
I found it and I 'm currently testing this document.
Recovering a windows server in a vm by this way.
I have several issues due to hardware difference I think like hdd driver and nic driver.

Have a good day.

Thanks.

Bertrand.
 
Back
Top