1-Touch for Windows

Topics | How To

Overview

Setting up 1-Touch for Windows

Recovering Data in Case of Disaster

License Requirements

Overview

1-Touch for Windows provides the automated rebuilding and restoration of 1-Touch client computers. Automation includes the following options:

1-Touch requires that a 1-Touch server be installed within the CommCell. It also requires that the appropriate Windows File System iDataAgent be installed on the client and that a client boot CD-ROM be created. However, you need not install the iDataAgent individually since this software is bundled with the 1-Touch server software and is automatically installed when you install this server software.

1-Touch clients prepare information for an automated recovery each time the system state is backed up. This information includes the computer name, operating system, IP address(es), and disk partition/format information. In case of disaster, the information can be quickly restored in the format of several automated answer files for silent deployment and restoration of the computer. The 1-Touch server software provides a very simple program that allows you to select the most recent backup data or such data of a specified date to be automatically restored.

You can install multiple 1-Touch servers for a single CommServe; you must have a 1-Touch Server license for each installation. This method would allow, for instance, remote sites to install a 1-Touch server locally to minimize WAN traffic during the Windows installation portion of recovery.

A 1-Touch Recovery is not used to recover a 1-Touch Server. The 1-Touch Server should be backed up using the appropriate File System iDataAgent for data protection and recovery, which is installed with the 1-Touch software.

Dissimilar Disk Restore

1-Touch for Windows also provides a Dissimilar Disk Restore option. This option allows you to recover data to one or more target disks that differ from the source disk(s) in type or size. The option allows you to create partitions on the target disk that differ in size from those on the source disk in order to accommodate the volumes you are recovering.

Do not move the boot partition to a new partition location on the target computer if the 1-Touch recovery computer is a domain controller. Filtering the boot.ini file during the recovery of a domain controller will not work because the process copies and reapplies the boot.ini file from the backup during the automated recovery.

Back To Top

Setting up 1-Touch for Windows

Complete the following tasks to set up 1-Touch for Windows:

Preparing 1-Touch Configuration and Answer Files/Profiles

You can create or modify client preparation answer files or 1-Touch Recovery Profiles from either the 1-Touch Server or the 1-Touch client being recovered. Creation/modification can be done before the 1-Touch Recovery from the 1-Touch Server GUI and after the client has been booted for 1-Touch Recovery from the client boot CD. The associated processes are always run on the 1-Touch Server, and the associated files are always saved to the 1-Touch Server.

1-Touch Recovery Profile

Profile Manager allows the 1-Touch administrator or user to preselect computer recovery options for a specific group of computers. Profile selections include the Windows version to apply, mass storage drivers, NIC drivers and restore options. The profile can be selected for the client recovery rather than individually providing the same answers to each client. 1-Touch Recovery Profiles are saved under System Recovery\Profiles on the 1-Touch Server.

Using Custom Scripts

The Custom Scripts file feature in part allows you to customize the [guirunonce] section of the unattend.txt file to meet Windows deployment requirements for your environment. Custom scripts are incorporated into the recovery by selecting the Custom Scripts option in the 1-Touch Client Preparation Wizard. As customization requirements grow, the features for scripting will be enhanced. For more information, see Custom Scripts.

Back To Top

Recovering Data in Case of Disaster

The following sections explain how to recover data in case of disaster.

Required Capability: See Capabilities and Permitted Actions

Before You Begin

To recover data, use one of the following procedures, as appropriate:

  • By adding 1-Touch ISO images to a PXE server repository, you can configure the PXE server to boot a PXE client from the 1-Touch ISO image and then run the 1-Touch Recovery. See Boot and 1-Touch Recover a Client using the 1-Touch ISO Image on a PXE Server for step-by-step instructions.

  • If you need to manually restore the onetouchinfo.cvf file for troubleshooting purposes, you can restore the file out of place by providing an absolute restore path in the CommCell Console. However, be aware that additional registry files (which you can delete afterwards) will also be restored.

    Use the following procedure to manually restore the onetouchinfo.cvf file:

    1. At the backup set level, right-click and select Restore.

    2. At the backup set level, right-click and select Restore.

    3. Type an absolute restore path (e.g.,  \[System State]\Special Components\One Touch Files).

    4. Deslect Restore to Same Paths and provide a path to which to restore the onetouchinfo.cvf file and the registry.

    5. Click OK.

Back To Top

Standard Procedure

To recover a system using 1-Touch:

Install Restore Updates on the Client

  1. Before you start the recovery, download the necessary restore updates to the 1-Touch Server's cache. See Run CopyToCache for step-by-step instructions. Note the following:
  2. Continue with the following procedures. When you run the 1-Touch Client Preparation wizard (see Prepare the 1-Touch Configuration and Answer Files/Profiles on the 1-Touch Server), the command to deploy the updates after the software installation will be included in the fullida.bat file. The associated script in this file will deploy the updates silently.
  3. Verify that the updates get applied after the Windows File System iDataAgent is installed.

Manage the Windows Distribution Shares

  1. From the 1-Touch dialog box, click Windows Distribution Manager. Then click Next.
  2. In the Manage Windows Distribution Shares dialog box, to administer your Windows Distribution shares, do one or more of the following as appropriate:
  3. Repeat the preceding step for each Windows Distribution type that you need to manage.
  4. Click Done.
  5. In the Hotfixes/Service Packs dialog box, to administer your Hotfixes and service packs, remove from the list Hotfixes/service packs by clicking Remove and administering as appropriate. Removing a Hotfix or service pack from the 1-Touch list of available Hotfixes does not remove the Hotfix from the Windows Distribution to which it has been applied. Once a service pack or Hotfix is applied/slipstreamed to a Windows Distribution, it cannot be removed. To apply Hotfixes/service packs to Windows Distributions, browse and/or select the appropriate Hotfixes/service packs from the first list, click the Windows Distributions to which you want to apply these items in the second list, and then click Apply.

Integrate Service Packs for non-X86 Windows Distribution Packages

Whenever you attempt to integrate a service pack into a Windows Distribution folder for a processor type (e.g., X64, IA64, etc.) that does not match the version of the 1-Touch Server where the distribution folders reside, the message "update.exe is valid, but is for a machine type other than the current machine" is displayed. The Windows Distribution will have to be copied to a computer with the matching processor type, slipstreamed with the Service Pack, and then imported using the 1-Touch Windows Distribution Wizard. See Integrate Service Packs for non-X86 Windows Distribution Packages for step-by-step instructions.

Integrate Specific Hotfix for Windows 2000

1-Touch will restore the Updates (or Hotfixes) that were applied to the client at the time of the backup. There may be cases where interim security or restore Hotfixes are required.

For Windows 2000, if Hotfix KB828741 is in the backup, it must be applied to the target; otherwise, the system state restore will fail. Slipstream this fix into the Windows 2000 Distribution folder. KB828741 is also known as Microsoft Security Bulletin MS04-012, "Cumulative Update for Microsoft RPC/DCOM (828741)" at http://www.microsoft.com/technet/security/bulletin/ms04-012.mspx.

The 1-Touch option to integrate, or slipstream, Security Updates and Service Packs into Windows distribution shares supports Update.exe 5.4.15.0 or any later version. KB828741 is a lower version (5.4.1.0) and requires manual integration. Information about "How to integrate software updates into your Windows installation source files" can be found at http://support.microsoft.com/default.aspx?kbid=828930.

When integrating Updates in your distribution share(s), be sure to integrate the Service Pack first. Then integrate the Updates. If post-Service Pack Updates are integrated before the Service Pack, you will not be able to include the Service Pack in the Windows Distribution share.

A Hotfix or Service Pack that is slipstreamed into a Windows integrated install cannot be removed.

Manage the Windows Device Drivers

Windows Driver Manager is used to import all third-party or vendor-supplied Windows mass storage and network interface drivers (NICS). When preparing drivers for 1-Touch recovery, keep in mind any non-native Windows mass storage and network interface drivers that the client may need and import them to the 1-Touch driver inventory.

The 1-Touch Client Preparation Wizard prepares the client for silent deployment of Windows; therefore, the drivers selected here would be the same drivers required during an interactive Windows installation. The 1-Touch Boot CD Wizard prepares a boot CD for the client to connect to the 1-Touch Server on the network.

In view of all of this, be sure to consider the following:

  1. From the 1-Touch dialog box, click Windows Driver Manager. Then click Next.
  2. In the Driver Manager dialog box, ensure that all the drivers for all the Windows operating systems are available for the recovery. To this purpose, click an operating system in the OS Family list, click the type of driver in the Driver Type list, and then view the Available Device Drivers field for the available drivers for that operating system.
  3. To include a new driver for the operating system, click Add, populate the Add Device Driver dialog box as appropriate, and then click Add. If you want to remove a driver from the available list for the operating system, click the driver in the Available Device Drivers field and then click Remove.
  4. Repeat the previous two steps for each operating system and driver type.
  5. When you are finished, click Done.

Prepare the 1-Touch Configuration and Answer Files/Profiles on the 1-Touch Server

A successful restore requires CommCell user access, valid system state data to restore, and File System iDataAgent Services to be running on the 1-Touch Server to which the client information files are being restored.

  1. On the 1-Touch server, launch 1-Touch from the Start | Programs menu.
  2. Click Next from the Welcome screen.
  3. From the 1-Touch dialog box, click one of the following options:

    If you click 1-Touch Client Preparation Wizard, skip the next step. If you click 1-Touch Profile Wizard, go to the next step.

  4. Decide whether you want to create a new profile or modify an existing profile.
  5. In the Client Information dialog box, select from the list the 1-Touch Client to prepare configuration files for recovery. Provide the CommCell Console user name and password. Then click Next.

Access 1-Touch Recovery Information

  1. From the Client Configuration dialog box, do one of the following to access the 1-Touch Recovery information file for the recovery.

    Click Next.

  2. If you selected to Restore the configuration information from backup of this client, the "Please wait while processing" progress bar appears while files are restored from the system state portion of the backup selected.
  3. From the 1-Touch Server Share Information dialog box (if displayed), do the following:

    Click Next.

Select Method to Prepare Client Answer Files

  1. In the 1-Touch Profile Information dialog box, do one of the following to prepare your client answer files (which will be restored to the 1-Touch Server\SystemRecovery\ClientFiles\%clientname% share).

Select Shares, Drivers, and Filters

  1. In the Select a Windows Distribution Share dialog box, to populate the WINDIST folder, click the appropriate Windows Distribution share type for the recovery from the Share Name list. If you need to include a new share type for the recovery, click Add, enter the appropriate information in the Add Windows Distribution Share dialog box, and then click Add. Then click Next.
  2. In the Select Windows Mass Storage Driver dialog box, determine if the mass storage driver that was detected at the time of backup is appropriate. If not, click the name of the mass storage driver for the client to be used during the recovery from the Select the mass storage driver list. If required, click Add and the appropriate mass storage driver name to include a new mass storage driver for the recovery. When you are ready, click Next.
  3. In the Select Windows PnP Drivers dialog box, click the name of the plug and play device drivers for the client to be used during the recovery from the PnP Drivers for the Client lists. If required, click Add and the appropriate plug and play device driver name to include a new plug and play device driver for the recovery. When you are ready, click Next.
  4. In the Restore Options dialog box, select as appropriate options to do the following: restore the system state, overwrite data during the restore, administer disk mapping, and add Custom Scripts. Then click Next.
  5. In the Add Excluded Folders for Restore dialog box, include in the space any drives and/or folders to be filtered from the restore.  Use Add and Remove as appropriate. Then click Next. If you are using the 1-Touch Profile Wizard, skip the next two steps.

Administer NIC Settings and Drives

  1. In the Internet Protocol (TCP/IP) Properties dialog box if displayed, accept or modify the network interface card (NIC) settings for the client being recovered. Try to bind to the first network adapter that is displayed. Repeat this step for each additional NIC (if any) by using the list. Then click Next.
    If you are booting the 1-Touch client for recovery, this step will be displayed later in the procedure.
  2. In the Disk Layout dialog box (if displayed), use the scroll bar to view all the drive information found at backup time for the client. Also, if you want to recreate the partitions of and format selected drives with this information, click the drives and Recreate partitions and format the selected drives. To perform a dissimilar disk restore, click Show partition layout during recovery on the target computer (you can start the dissimilar disk restore later). To leave the target drives intact, do not click this option. You can also format only the Windows system drive by clicking this drive and the Format the Windows system drive only option. Click Next.
    • If you select to Recreate partitions and format the selected drives, a warning will appear if OEM partitions were present during the backup. OEM partitions can be recreated but will be empty upon completion.
    • If you do NOT select Recreate partitions and format for selected drives, you must select to format the system disk.

Summary Screen

  1. Review the Summary Screen. Click Back as appropriate to make any changes. Then click Done.
  2. To save a new profile, click Finish. To save a modified 1-Touch profile, click Save Profile As, provide a profile name in the space, and press Enter. To save an existing profile that you did not modify, click Finish. To save the client answers but not a profile, click Done.

Create the 1-Touch Boot CD

To avoid network driver errors during a boot, verify that the network drivers imported to the boot CD are WINPE- or Remote Installation Service (RIS)-compatible if the vendor provides an RIS-compatible driver. Many vendors provide native Windows and RIS drivers with the hardware. If both drivers are provided, the RIS driver is provided for a WINPE or RIS boot process and the native version is provided for the Windows Installation. If only a native Windows driver is provided, you can use this driver for a WINPE or RIS boot process. For more information, see Perform 1-Touch Recovery with Broadcom NetXtreme II Driver Workaround.
  1. From the 1-Touch dialog box, click 1-Touch Boot CD Wizard. Then click Next.
  2. In the Processor Type dialog box, click in the list the processor type of the affected client(s) for the 1-Touch Boot CD. Then click Next.
  3. In the Mass Storage Drivers dialog box, click the mass storage drivers that you want to include in the 1-Touch Boot CD. The 1-Touch Boot CD requires Windows 2003-compatible drivers. To include a new mass storage driver, click Add, populate the Add Device Driver dialog box as appropriate, and then click Add. Once you have selected all the desired drivers, click Next.
  4. In the Network Adapter Drivers dialog box, select the network adapter drivers that you want to include in the 1-Touch Boot CD. To include a new network adapter driver, click OK, populate the Add Device Driver dialog box as appropriate, and then click Add. Once you have selected all the desired drivers, click Next.
  5. In the Boot CD ISO Output File dialog box, click in the Save in list the destination location for the 1-Touch Boot CD ISO image (e.g., D:\1-Touch_32.iso). Output including text similar to the following should be displayed.

    ..........
    Scanning source tree complete (1215 files in 47 directories)
    Computing directory information complete
    Image file is 189636608 bytes
    Writing 1215 files in 47 directories to D:\1-Touch_32.iso
    5% complete

     Upon completion, "The ISO file is created" message should be displayed. Click OK.
     
  6. Once the wizard finishes, burn the ISO image to the 1-Touch Boot CD using any software that is ISO-9660-compliant.

Boot the 1-Touch Client for Recovery

During the Windows installation process of a 1-Touch Recovery, the Windows Administrator password is set as 1Touch. Upon completion of the 1-Touch Recovery, the Administrator's original password will be restored from the backup.
  1. Boot the 1-Touch client using the CD-ROM that you created from the 1-Touch boot image ISO file.
  2. From the Welcome screen, click Next.
  3. As prompted, indicate whether DiskPart recognizes all your hard disk devices based on the displayed list of devices. If so, select Yes, click Next, and go to the next step. If not, enter No and follow the procedure in Enable 1-Touch Boot CD-ROM for Mass Storage Recognition before continuing with this procedure.
  4. In the Server Information dialog box, type the IP address of the 1-Touch Server along with your user name and password. Then click Next.
  5. In the Client Information dialog box, select the name of the computer (i.e., the client name) to restore along with its IP address, subnet mask, and default gateway. Also, do one of the following:
  6. Review the Summary screen. If no changes are required, click Next. The recovery is now completed.

Dissimilar Disk Restore: Initialize the Destination Disks

Use the following procedure to initialize the destination disk(s) to which you will be mapping the volumes you are recovering.

  1. From the Customize the Disks dialog box, right-click the destination disk that you want to initialize. Destination disks are represented in the lower part of the dialog box
  2. From the popup menu, click the disk type that you want to assign to the destination disk.
  3. Wait a moment until some processing completes.
  4. Repeat this procedure for each destination disk that you want to initialize. If you will be restoring mirror, span, stripe, or raid volumes, be sure to initialize at least one additional disk if you have not already done so. Then click Done.
  5. The disks that you initialized will be displayed. If you want to initialize additional destination disks, click Cancel and repeat this procedure for the desired additional disks.
  6. When you are finished, click Done. Your disk(s) should now be initialized. Only the disk(s) that you have initialized will now be displayed in the dialog box.

Dissimilar Disk Restore: Map, Create, and Unmap Volumes

Use the following procedure to map the volumes you are recovering to destination disks, create the volumes on these disks, and unmap the volumes from these disks. Note that you will be able to map volumes only to destination disks that have enough space to accommodate the volumes.

  1. From the Map the Disks dialog box, click the source disk volume that you want to map to the destination disk. Source disk volumes are represented in the upper part of the dialog box.
  2. If you are mapping a mirror, span, stripe, or raid volume, the Customize the Volumes dialog box will be displayed. In such a case, change as appropriate the properties for or items associated with the volume, including the type, format, target disk(s), size, and assigned letter. Then click OK.
  3. Click the destination disk where you want to create the volume that you are mapping. The volume will be displayed in the destination disk, and it will be highlighted in the source disk. If you are mapping a mirror, span, stripe, or raid volume, be sure to click at least one additional destination disk.
  4. The Customize the Volumes dialog box will be displayed if at least one of the following is true: partition style that you want to map on the destination disk is different from that on the source disk; or, size of the volume that you want to map is larger than the amount of space available on the destination disk. In such a case, change the affected items as appropriate, make any other desired changes, and then click OK.
  5. If you want to customize the volume that you are mapping and have not already done so, go to the next step. Otherwise, skip the next two steps.
  6. Right-click the source disk containing the volume that you are mapping.
  7. In the Customize the Volumes dialog box, change as appropriate the properties for the volume as discussed in an earlier step in this procedure.
  8. If you want to unmap a volume from the destination disk, right-click the volume on the disk ("Unmap" should be displayed). Repeat this step for each volume that you want to unmap.
  9. Repeat the previous steps for each volume that you want to create on the destination disk.
  10. Once you are done mapping, creating, and unmapping volumes, click OK. The 1-Touch Recovery will install the Operating System and the File System iDataAgent, and it will then automatically execute a full system rebuild of the client

Reboot the System

Following the rebuild, enter y for the prompt that asks you if you want to reboot. Also, if you re-created disk partitions, reboot the client again as prompted. This is necessary because of changes made to the Globally Unique Identifier (GUID) for each volume.

Top of Section

Procedure on a Cluster

Windows Server 2000 and 2003

To recover a system on a cluster using 1-Touch:

Recover the Primary Cluster Node and Quorum Disk

  1. Run the 1-Touch Client Preparation Wizard (see Prepare the 1-Touch Configuration and Answer Files/Profiles on the 1-Touch Server), and select to format and partition all disks that are owned by this cluster node. Select also the quorum disk.
  2. Turn off all nodes except the primary node to be recovered.
  3. Perform a 1-Touch Recovery on the primary node.
  4. When the "Full iDataAgent Restore job completed. Do you want to reboot?" message appears, enter y (yes).
  5. When the "New Hardware found. Windows has finished installing new devices.... Do you want to restart your computer now?" message appears, enter y (yes).
  6. Restart the computer. Then go to the <install directory>\base folder and enter the following command at a command prompt: authorutil.exe -cluster
  7. If a failure message appears, restart the computer to allow the cluster services to start.
  8. If the cluster disks were repartitioned, a failure message may appear. This is because the disk GUIDs for the quorum have been changed. In such a case, restart the computer to allow the cluster services to start.

Restore Program Files for the Virtual Server

The cluster is now available. The Bull Calypso Communications Service (GxCVD) and Bull Calypso Client Event Manager (GxEvMgrC) cluster resources are restored; however, the program files required to start and run these resources must be restored to the virtual server's disk on which they resided. You must restore the program files for the virtual server to the physical node that owns the virtual disk since the virtual server's services are not yet running. You can either select all the virtual disk data and restore this data using this method, or you can restore only the program files to get the services started and then restore the rest of the data using the virtual server's File System iDataAgent.

  1. Browse and select all the desired data for the virtual server disk(s) and restore this data to a different computer. The destination computer will be the physical node that currently owns the virtual disk(s). Select an in-place restore.
  2. Using the Cluster Administrator, bring the cluster resources online.

Recover Passive Node(s)

  1. Run the 1-Touch Client Preparation Wizard (see Prepare the 1-Touch Configuration and Answer Files/Profiles on the 1-Touch Server), and either select to format only the system disk or to recreate and partition selective disks that are owned by this passive node.
  2. Perform 1-Touch Recovery on the passive node.
  3. When the "Full iDataAgent Restore job completed. Do you want to reboot?" message appears, enter y (yes).
  4. When the "New Hardware found. Windows has finished installing new devices.... Do you want to restart your computer now?" message appears, enter y (yes).
  5. Restart the computer. Then go to the <install directory>\base folder and enter the following command at a command prompt: authorutil.exe -cluster
  6. A failure message may appear if the disk GUIDs were changed during a reparation at any time. Allow several minutes for the cluster to correct itself and the cluster services should start.

 If the cluster disks were repartitioned, a failure message may appear because the disk GUIDs for the quorum have been changed. If the cluster service does not start, or if you see Event ID 1034 in the System Event Log, reference the KB 305793 and KB 280425 Microsoft Knowledge Base articles on http://support.microsoft.com/ to get the cluster service back online.

Windows Server 2008

Perform an Authoritative Restore

An authoritative restore is performed only if the administrator accidentally alters the cluster configuration or deletes a large number of resources and therefore needs to revert to a previous cluster configuration. Before you perform an authoritative restore of the cluster configuration database, ensure that all cluster nodes and services are running.

Authoritative cluster restores are not supported using the 1-Touch recovery procedure. An authoritative restore requires that the cluster services are running. For more information, see Restoring Cluster Databases: Authoritative Restores.

Perform a Non-Authoritative Restore

A non-authoritative restore is performed for the scenarios listed below.

To perform a non-authoritative restore of the cluster configuration database:

When the entire cluster is down, perform a non-authoritative restore of the first node and then start adding nodes to the cluster. This is essentially a non-authoritative restore and the cluster service does not need to be running when this is performed.

  1. Perform a 1-Touch Recovery on the cluster node. The default (non-authoritative restore) option for Cluster DB is always selected for a 1-Touch Recovery and this option cannot be changed.
  2. Enter y (yes) when the following message appears:

    Full iDataAgent Restore job completed. Do you want to reboot?

  3. If the restored node shows 'unavailable' in the failover cluster, evict and add the restored node.

 It is recommended that you do not perform an authoritative restore of the cluster after this procedure without performing a full backup.

Top of Section

License Requirements

This feature requires a Feature License to be available in the CommServe® Server.

Review general license requirements included in License Administration. Also, View All Licenses provides step-by-step instructions on how to view the license information.

Back To Top