Create HSR Job

Use the Create HeadStart Restore job icon on the Managed Folder Task Bar to configure a specific restore operation.

VMware Considerations

HeadStart Restore can use VMware targets with these considerations:

  • Close all instances of VMware VSphere client before attempting to contact an ESX server with ImageManager.
  • When creating an ESX job type, the Domain or Share fields don't appear when you select the ESX/ESXi target type for HSR. See ESX Server Permissions for information about the minimum permissions ImageManager needs to use an ESX server target.
  • ImageManager doesn't support the free (limited functionality) version of ESXi.
  • To restore to a VCenter Cluster, set the correct permissions on the datacenter's root VM folder.
Note: ImageManager doesn’t show folders (on the Folder tab) for an ESXi target when creating a minimal virtual machine. This is because the datastores folder is different than the datacenters virtual machine folders. Learn more about the ESXi folder hierarchy in the Folders section of the vSphere Managed Inventory Objects page.

To Create a new HeadStart Restore Job

  1. In the ImageManager console, select the ImageManager agent and then the managed folder you want to use for this HeadStart job. 
  2. From the Folder Management Task Bar, click the Create HeadStart Restore Job icon(Create HeadStart Restore Job). You can also right-click the managed folder, select Create Job and then select HeadStart Restore.)

    Create a HeadStart Restore Job

  3. In the HeadStart Restore job dialog General tab, select or specify the applicable settings:
Name (Optional) Enter a descriptive name for the HSR job.
The type of virtual disk or volume HeadStart Restore should create.

The supported types are:

  • VMware VMDK: Create a Virtual Machine Disk (VMDK) file compatible with VMWare virtual environments.
  • Microsoft VHD: Create a Virtual Hard Disk (VHD) file compatible with Microsoft Hyper-V and Oracle VirtualBox virtual environments.
  • Microsoft VHDX: Create a Virtual Hard Disk (VHDX) file compatible with Microsoft Hyper-V virtual environments.
  • Volume: Create a physical volume on a local physical disk.
Destination Type
The destination type for your HSR. The supported destination types are:

    • Local Drive (locally-attached device) (2TB volume size limit for VMDK. Additional conversion may also be necessary to boot the VM in the ESX/ESXi Server.)
    • Network Drive (2TB volume size limit for VMDK. Additional conversion may also be necessary to boot the VM in the ESX/ESXi Server.)
    • VMware ESX/ESXi Server (Recommended destination type for VMDK targets. Not available for VHD/VHDX or Volume type HSRs.)

The list of pre-defined destination locations based on destination type. You can use your pre-defined locations or create new ones with Add new location. ImageManager asks for:

    • Type The Location type defaults to the most recently used type.
    • Name (Optional) The Location name should make it easy to identify the location.
    • Server The destination server name can be UNC (for VHD targets), or an IP address.

      Note: For VMDK targets, click Test ESX server connection to confirm the connection is active with the destination server.
    • Share The Windows Share on the server to use for this operation. (Only available for VHD targets.)
    • Authentication (Default: Disabled) The credentials ImageManager needs (Domain/Computer/NAS name, Username, and Password) to log into the server or network resource.

The default subdirectory created by ImageManager on the destination where HSR files are stored. The name can be changed if necessary.

Lag Time The delay between the creation and application of incremental backup images. ShadowProtect creates backup image files and HSR applies the backup images to the HSR volume. Lag time gives you a chance to identify problems (system errors, image corruption, virus, etc.) in the images before they are applied.

Lag time can be set:

    • 1-23 hours
    • 1-30 days

Add HeadStart Volumes

ImageManager lets you create one or more new HSR volumes from existing base images in the backup chain.

To create the volumes

  1. Click the HeadStart Restore Volumes tab.
  2. Click Add new HeadStart volumes. 
  3. In the Base Backup Images dialog, select the base image file to use, then click OK.
  4. (By default, ImageManager lists all the .spf files in the managed folder.)
  5. Provide the the password for encrypted backup image files, then click Save to create the new HeadStart job.

To create a raw (unformatted) local physical volume

Warning: Configuring an HSR job to locally-attached physical storage requires a raw (unformatted) drive. When you configure an HSR for a physical volume, the volume must be created first. If the volume has been formatted you need to use Windows Disk Manager, or another similar tool, to delete the volume and then create it again WITHOUT formatting it. 

  1. Go to the Windows "Run" menu or command prompt and run diskmgmnt.msc.
  2. Create a new volume (which automatically creates a raw volume).
  3. Set the volume size as needed. The volume size must be bigger than the volume being backed up.
  4. Select a drive letter.
  5. In the Format Partition window select Do not format this volume.
  6. Finish the volume creation by clicking Next.

You should now be able to configure an HSR job for the new local physical volume.

To create a VMware ESX/ESXi Server HSR job (Conditional)

  1. Locate the target VMDK by clicking on Click to Browse for Volume.
  2. Select the VMDK, then click Select.

ImageManager displays the ESX Inventory dialog box.
This dialog lets you: 

  • Browse an ESX server for an existing VMDK. 
    When creating a target VMDK without using ImageManager (for example with the vSphere client), add 18 MB to the minimum size shown in ImageManager to compensate for worst-case sector alignment in the file system structure.
    Note: Slot '0:7' is no longer listed as an option for creating an HSR to ESXi host. StorageCraft fixed an error that occured when creating a HeadStart Restore job directly to an ESXi host. The error was displayed when trying to attach more than 7 virtual disks using the HSR job to create/configure the virtual machine and virtual disks. This happened when Slot '0:7' (reserved by VMware) was used to attach a disk.
  • Create a new VMDK in an existing VM. 
    To do this, right-click an existing VM, then select Create New Virtual Disk.
  • Create a new VM in an existing Resource Pool. 
    To do this, right-click an existing Resource Pool, then select Create New Virtual Machine
    After it is created, you can add a virtual disk to the new VM.
Note: After the job is configured and saved, the only thing you can change is the image file password. If you need to modify any other settings, or change volume sizes, you need to delete the job and create a new one.

ImageManager enables the HeadStart Restore job and displays it below its associated managed folder in the Managed Folder Pane.

Warning: Do not click Delete on an HSR job once it begins creating a new virtual disk. This may cause ImageManager to freeze. If it is necessary to delete a job, click Pause first. When the job pauses, click Delete.

Terms and Conditions of Use - Privacy Policy - Cookies