Quantcast
Channel: Macrium KB » Knowledgebase
Viewing all 166 articles
Browse latest View live

How to use VBScript to check for free space on the backup target drive

$
0
0
This article shows how to use the VBScript functionality in Macrium Reflect to check for available free space before running a backup.


Macrium Reflect includes a VBScript template generator that administrators can use for custom actions/decisions during the backup process. The VBScript source can then be scheduled or run interactively to control the backup process. In this example we'll check the free space on the backup target drive and only execute the backup if there is at least 50GB free.

1. To generate a template right click on your backup definition and select 'Generate a VBScript File'



2. In the dialog that opens, leave all the options at the defaulted values and click 'OK'

3. Click the 'VBScript Files' tab, right click on the newly generated source and select 'Edit'



4. The source file will open in 'Notepad'. Turn off 'Wordwrap' to make editing easier.



5. Change the following line:

Call VBMain()

To:
If GetFreeSpaceGB("\
as\public") > 50 Then
Call VBMain()
End If

Note: Change "\
as\public" to the destination of your backup. This can be any local or network location.

6. At the very end of the source copy and paste the following function text:

Function GetFreeSpaceGB(ByVal drvPath)
Dim objFSo, d
Set objFSo = CreateObject("Scripting.FileSystemObject")
If Not objFSO.FolderExists(drvPath) Then
' return zero if the folder doesn't exist
GetFreeSpaceGB = 0
Exit Function
End If
Set d = objFSo.GetDrive(objFSo.GetDriveName(drvPath))
GetFreeSpaceGB = d.FreeSpace/ (1024 * 1024 * 1024)
End Function
7. Select 'File' then 'Save' in Notepad to save the source file.

When this script is run it will only execute the backup if more than 50GB free space exists in network share "\
as\public".

You can run and schedule VBScript files in the same way as your backup definition XML files. Just right click on the source file entry in Reflect and select 'Run Now' or 'Schedule'.


v5: My CD/DVD Rescue Media will not boot.

$
0
0
This article explains how to diagnose and fix non-booting Rescue media issues.

Notes:

For brevity, CD will refer to either CD or DVD.
Except where stated, it is equally applicable to linux or PE based rescue CDs.


Introduction

The causes of non-booting rescue CD fall into one of two broad categories, either it is an issue with your CD or with your PC.


Verify your CD

Try as many of the following steps as possible:
    1. Try booting the CD on a 2nd PC.
      If it boots, this indicates a configuration or hardware issue with your PC. Please see Verifying your PC later in this article.
    2. Try a different brand of CD media.
      We have found that CD recordable media is of variable quality. Often, using different media will resolve your issue.
    3. Try creating the rescue media on a 2nd PC.
      If Reflect is installed on the 2nd PC, please try creating rescue media there.
      Alternatively, following the same CD creation steps as before, select Create ISO image file on the last page of the wizard. Transfer this to the 2nd PC and us a third party utility such as ImgBurn to burn the CD.
      In each case, try booting the 1st PC with the new CD.


    Verify your PC.

    To boot rescue media from CD, your BIOS or UEFI firmware must be correctly configured and have hardware suitable for booting. Please try as many of the following steps as possible to diagnose this.

    Note that there is no standard for motherboard firmware configuration, so our instructions are necessarily non-specific. Please consult your motherboard manual for details relevant to your PC.

      1. Try booting a Microsoft Windows install CD.
        If the boot fails, this is indicative the your hardware is incorrectly configured. Please continue through this list for further diagnosis.
      2. Invoke your BIOS/UEFI boot menu.

        Boot menus vary in appearance and are invoked in different ways. You may need to refer to your motherboard manual to find the key combination to access this. Sometimes, this is displayed on the screen and is usually a key such as DEL, F8, F11, F12, F2 etc.
        Please note that on UEFI/BIOS dual systems, you may be given the option to boot UEFI or not for each device. Please boot the type matching your installed OS. There are a few possible outcomes:
        1. You are able to boot your rescue media in this manner, but not without performing this step. In this case, please see the next step in this section.
        2. You are unable to boot your rescue media having seen the hardware in the menu. In this case, you may wish to try the Verify CD steps above. If these do not rectify the issue, your hardware may not support booting Windows PE (you can also try this with the Windows Install CD to verify). In this case, please try an alternative rescue media format such as USB, or attach a different CD/DVD drive to the system.
        3. You are unable to see the hardware in your list. In this case your firmware has not recognised the device and it is not supported for booting.
      3. Change the motherboard boot order.
        Please enter your BIOS or UEFI firmware setup utility and navigate to the "boot order" or "boot menu" equivalent screen. Please ensure CD/DVD booting has a higher priority than your hard disk, which may be labelled ATAPI, SATA, SCSI or various other labels depending on your system. Please press F10, or your equivalent for "save and exit" to reboot the system with the new priority.
        Please note that some UEFI firmware may not have boot priorities for removable media, or booting from removable media may be a configurable option that you must enable.
      4. Create a USB rescue stick.
        Follows the same steps as used when creating a CD, selecting instead "USB media" on the last page. If this works and your have verified your CD, it is indicative that your hardware cannot boot a CD. However, a usb stick, is just as functional as a CD, so we recommend you use this as your rescue device.
        Note: This is only available for PE rescue media.


      What to expect when booting rescue media.

      1. The PE 3.0 environment is based on (a cutdown version of) Windows 7 and so boots in a similar fashion.
      2. The PE 4.0 environment is based on Windows 8 and so boots in a similar fashion.
      3. You may notice a lag during boot on CD/DVD rescue media whilst the WIM is copied into memory. This can take some time, so please be patient. PE 4.0 media on UEFI systems may additionally display no progress bar during initial load, so please be patient if you have a blank screen.

      VSS Error: 0x80042306 - Volume Shadow Copy Error

      $
      0
      0
      Error

      VSS Error: 0x80042306 - Volume Shadow Copy Error

      Description
      This error occurs when a VSS provider blocks the creation of the VSS snapshot. This may be caused by
      • Installing a new 3rd party VSS provider
      • An existing provider becoming corrupted

      Solution
      Re-register the VSS components
      Copy and paste the following lines into a DOS batch (.bat) file and execute:

      cd /d %windir%\system32
      net stop vss
      net stop swprv
      regsvr32 /s ole32.dll
      regsvr32 /s oleaut32.dll
      regsvr32 /s vss_ps.dll
      vssvc /register
      regsvr32 /s /i swprv.dll
      regsvr32 /s /i eventcls.dll
      regsvr32 /s es.dll
      regsvr32 /s stdprov.dll
      regsvr32 /s vssui.dll
      regsvr32 /s msxml.dll
      regsvr32 /s msxml3.dll
      regsvr32 /s msxml4.dll
      vssvc /register
      net start swprv
      net start vss


      Search terms
      tag:backup
      tag:image
      tag:file

      VSS Error: 0x8004231f - Failed to Create Volume Snapshot

      $
      0
      0

      Error

      0x8004231f - Failed to Create Volume Snapshot

      Solution 1 - Remove drive letters allocated unnecessarily to small partitions

      Solution 2 - Increase shadow storage space

      Solution 3 - Remove old VSS snapshots


      Description

      Error code 0x8004231f indicates VSS_E_INSUFFICIENT_STORAGE (Insufficient storage space for the Shadowcopy). Shadow storage space is used for system restore points and by Macrium Reflect. You may have inadvertently allocated a drive letter to the Microsoft System Reserved partition (MSR) or you may have too many restore points on your system.


      Solution 1 - Remove drive letters allocated unnecessarily to small partitions

      The Microsoft System Reserved (MSR) partition is required to boot Windows 7 and later operating systems. Ordinarily, this partition does not have a drive letter assigned to it. If a drive letter is assigned then this can cause problems with Microsoft Volume Shadow copy Service (VSS).

      Note: The same is also true of OEM utility partitions such as DELL utility partitions. It is not required for these partitions to have drive letter associations and allocating a drive letter can cause VSS to fail..

      For more information on correcting this please see this article:

      "How to remove a drive letter from the - MS System Reserved partition"
      http://kb.macrium.com/KnowledgebaseArticle50162.aspx


      Solution 2 - Increase shadow storage space

      To see the amount ofstorage space allocated and used for Volume Shadow Copies run thefollowing command from a command prompt with elevated privileges:

      Vssadmin list shadowstorage

      To allocate more storage (e.g. 50GB) run the following command:

      vssadmin resize shadowstorage /For=C: /On=C: /MaxSize=50GB


      Solution 3 - Remove old VSS snapshots

      During normal Windows operation, restore points will be created during software installation and other day to day operational tasks. These restore points create snapshots that reside in an area of the disk and consume disk space.

      This disk space can be reclaimed by using the vssadmin command in an elevated MS-DOS command prompt. The following KB article will help with launching an elevated command prompt. Once the command prompt is loaded, enter the following command:

      vssadmin delete shadows /all

      This will remove all VSS snapshots on the system, prompting you first for confirmation. Running the command 'vssadmin list shadows' will display a list of snapshots on your system along with associated ID. Deletion by ID must specify a valid snapshot ID, deletion by volume must specify a valid Windows volume (e.g.: C:) and deletion of oldest snapshot simply removes the single, oldest snapshot on the system. An example of deleting by ID follows:

      C:\Users\Dev>vssadmin delete shadows /shadow={42bb9090-723c-4107-8954-92006026defd}

      To not be prompted by any of the commands use the /quiet flag.

      The following Microsoft KB article will provide further information regarding vssadmin list shadows.

      The following Microsoft KB article will provide further information regarding vssadmin delete shadows.


      Search terms
      VSS Error 0x8004231f

      VSS Error: 0x8004230F - Failed to create volume snapshot

      $
      0
      0

      Error

      Backup aborted! - Failed to create volume snapshot error. Result Code: 0x8004230F

      Description

      The windows snapshot component VSS will fail if a disk with a non standard sector size is attached to your system, even if this disk is either being backed up or used to store the image files. This can be an internal disk or one connected by USB or eSata. These disks are fortunately rare, and are typically found only in sizes of 1TB or above.

      Error reporting in V5 Reflect

      The extended VSS error information will be reported as below for version 5. See image, note the result code may be different, but the extended error will always be ...

      ERROR: COM call "m_pVssObject->BackupComplete(&pAsync)" failed.
      - Returned HRESULT = 0x80042301
      - Error text: VSS_E_BAD_STATE



      Error reporting in V4 Reflect

      You will see the following error, note the result code may be different.

      To get the extended VSS information, you need to run the backup from a VBScript file? Right on your XML definition and select 'Generate VBScript'. Accept the defaults and run the VBScript source. To run VBScript, click the VBScript tab, right click on the file and select 'Execute'. Once run, a detailed log file will be created in the same directory as the VBScript source. The log file name will be 'log-<date>-<time>.txt'. Open the log file with notepad or similar and search for the following text as before ...

      ERROR: COM call "m_pVssObject->BackupComplete(&pAsync)" failed.
      - Returned HRESULT = 0x80042301
      - Error text: VSS_E_BAD_STATE



      Identification of disks with a non standard sector size

      Run 'System Information' ('All Programs' > 'Accessories' > 'System Tools' > 'System Information').
      Expand the Components->Storage->Disks node, and scroll down the list of disks, looking for any that have a Bytes/Sector value not equal to 512.


      Solution

      Unfortunately, until Microsoft fix this issue, the only option is to remove this disk from your system. Read this
      Article for general information regarding Microsoft support for non-standard sector sizes.

      Note: Some Western Digital disks can be formatted for "Windows Vista Compatibility" using the supplied software. This enables 512e in the firmware and adds support for VSS.


      Search terms
      tag:backup
      tag:image
      tag:file
      tag:clone

      VSS Error: 0x8004230f - Backup aborted! - Failed To Create Volume Snapshot

      $
      0
      0

      Error

      Backup aborted! - Failed To Create Volume Snapshot. Result Code: 0x8004230f

      You may also see the error VSS_E_UNEXPECTED_PROVIDER_ERROR in the VSS log.


      Description

      This error often occurs if a product called 'ShadowProtect' from 'StorageCraft' or other similar programs such as Acronis are or have been installed on your PC.

      If you receive the following error at the end of your image log then it's likely that Macrium Reflect has a conflict with other imaging software on your PC

      Solution 1

      Check that none of your attached disks have non-standard sector sizes.

      To do this, run 'System Information' ('All Programs' > 'Accessories' > 'System Tools' > 'System Information')

      Expand the Components -> Storage node and select the Disks item.On the right, all your attached disks will be listed. Check that all the disks have a Bytes/Sector value of 512. Due to a limitation of VSS, if a disk is attached with any other value, even if you are not imaging it,then VSS will fail with result code 0x8004230f.

      Please see this article for more information on disk sector size issues: VSS Error: 0x8004230F - Failed to create volume snapshot


      Solution 2

      To fix this problem please take the following steps:
      1. If ShadowProtect is installed on your PC then you must uninstall it if you want to use Macrium Reflect.
        Remove the following registry key:
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\Providers\{24602736-bed9-4619-91b0-243447c6409c}
      2. This key can be left behind after uninstalling ShadowProtect and will cause a VSS error when Reflect creates a shadow copy.
      3. Restart Windows.
      4. For help on editing the registry please see here:
        http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/regedit_overview.mspx?mfr=true
        http://support.microsoft.com/kb/136393

      Solution 3
      If you don't have the registry key above then make sure that you only have the following entry for VSS software providers in registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\Providers



      To add the default VSS provider registry entry.

      1. Copy the following text to Windows notepad:
      Windows Registry Editor Version 5.00

      [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\Providers\{b5946137-7b9f-4925-af80-51abd60b20d5}]
      @="Microsoft Software Shadow Copy provider 1.0"
      "Type"=dword:00000001
      "Version"="1.0.0.7"
      "VersionId"="{00000001-0000-0000-0007-000000000001}"

      [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\Providers\{b5946137-7b9f-4925-af80-51abd60b20d5}\CLSID]
      @="{65EE1DBA-8FF4-4a58-AC1C-3470EE2F376A}"

      2. Save as 'VSSWriters.reg'

      3. Double click 'VSSWriters.reg' in Windows Explorer to import the entries in your system registry

      Solution 4
      We also provide a program which in most cases will recreate the correct registry setting and re-register all VSS components. Please download oneof the below programs to fix your problem:
      VSSfix 32bit - download
      VSSfix 64bit - download

      Search terms
      tag:backup
      tag:image
      tag:file
      tag:clone

      How to Restore an MBR System image to UEFI/GPT

      $
      0
      0

      This article explains how to restore an image of an MBR system disk to a GPT disk that supports the newer UEFI booting standard.

      Background
      UEFI (the Unified Extensible Firmware Interface) is an interface between a computer's firmware and operating system. It is designed as a replacement for BIOS (Basic Input/Output System). UEFI supports hard disks with either MBR (master boot record) or the newer GPT (GUID Partition Table) system. GPT is a newer standard, that supports disks larger than 2TiB and allows for more than four primary partitions per disk.

      As UEFI and GPT become more widespread, older images of MBR disks will often need to be restored to replacement UEFI / GPT systems.

      This article assumes that, apart from the type of disk, there are no other hardware differences between the system being imaged and the system being restored to. For dissimilar hardware, Redeploy may be needed.


      To prepare a GPT disk to boot in UEFI

      1. Boot into Windows PE.
        Please see here for more information on Windows PE and the Macrium Reflect rescue Environment: Understanding Rescue CDs and the Macrium rescue environment

        Rescue media created with v5.2.6249 or later on Windows 7/8 operating systems will be dual boot. That is, they will boot in both MBR and UEFI mode.
        Please boot your rescue media in UEFI mode. Consult your Motherboard user manual for information on how to do this.
      2. Open a Windows command window, and type:
        diskpart

        Note: To open a command window click the icon on the taskbar.

      3. List the disks:
        list disk
      4. Select the disk number that you want to restore to. For example:
        select disk 0
      5. Clean the selected disk:
        clean
      6. By default, "clean" creates an empty MBR disk. Convert it to GPT:
        convert gpt
      7. Create the EFI partition:
        create partition efi size=200
      8. Format the EFI partition:
        format fs=fat32
      9. Create the MSR partition:
        create partition msr size=128
      10. Exit Diskpart:
        exit



      To restore an image to the GPT disk, ready to boot in UEFI

      1. In Macrium Reflect, click the Backup tab and then click Refresh to read the newly initialized disk.


      2. Click the Restore tab, select the image file, drag and drop the imaged partitions but DO NOT restore the MSR partition from the image file. In the example below only the C partition was restored to the target disk.


      3. Once the restore has completed you'll need to configure the UEFI boot files in the EFI system partition.

        Follow the steps in the section "Fix Boot problems for GPT/UEFI Boot Systems" in the following KB article:
        How to fix Windows boot problems

      Note: You may need to edit the UEFI configuration to tell it to boot into the new GPT hard disk.


      Search terms
      tag:restore
      tag:image
      Convert MBR To GPT
      Convert MBR

      v5: How to schedule an incremental or differential Image

      $
      0
      0

      This article provides information on how to schedule incremental and differential backups

      Macrium Reflect v5.0 uses a single xml backup definition file for all backup types; Full, Differential and Incremental. The decision on which 'type' to create is made at run time and not when creating the backup definition file.  
      The article on How to create a disk image outlines how to create a backup definition file.

      1. Once you have saved your xml file, select the 'Backup' tab and then 'Backup Definition Files' tab.

      2. Right click and select 'Schedule':


      3. You can now choose whether to schedule a Full, Differential or Incremental image in scheduled task wizard:


      4. Once the scheduled task is saved it can be seen in the 'Scheduled Backups' tab along with the backup type:




      Search Terms
      How do I schedule an incremental or differential image
      Unable to schedule a differential
      tag:backup
      tag:image
      tag:file

      v5: How to create a disk image

      $
      0
      0

      Macrium Reflect can create file backups as well as disk images. However, for this tutorial you be able to complete the following tasks:

      • Create a full image of your computer's system drives using the wizard

      • Save your options as a XML definition file for easy re-running

      • Retrieve your saved XML definition

      Before you start this tutorial, you need to have installed Macrium Reflect on the machine you wish to backup.


      Creating a backup of your computer

      1. Start Reflect and take the option ‘Create an Image of the partition(s) required to backup and restore Windows’ located in the top left hand pane of the application window to start the backup wizard. It is highlighted in red below.

      2. The wizard should start as shown below. You will note that all partitions are displayed in the wizard, but only the system partitions have been selected. 
      Note: Further information about Windows 7 partitions can be found here

      3. In the 'Destination' section, select where you would like the resultant image to be written. In this tutorial, 'E drive' has been used. Click 'Next'.  For more on choosing a backup destination see the section on Backup Destinations, below.

      4. A summary screen is shown detailing the settings used for this image. Click 'Finish'

      5. You are now given the opportunity to save the backup options as shown in figure 3 below.


      It is also not mandatory to run the backup at this point. However, for the purpose of this tutorial click 'OK'

      Your system partitions will be backed up to the chosen location as shown below.


      When the image has completed click 'OK' to shut down the message box and then click 'Close' to close the backup window.

      Your system has now been backed up.

       


      Retrieving your saved XML backup configuration

      Macrium Reflect saves backup configurations using XML. Using an XML definition you can schedule a backup, generate a VBScript file for complex scenarios or simply create a desktop shortcut for instant running of your backup by clicking the shortcut icon.

      In order to view your saved XML backup configurations, select the 'Backup Definitions Files' tab as shown below.


      This will show all your saved XML configurations. By right clicking on the XML file, you are given the opportunity to rerun the backup, schedule it, create a desktop shortcut and many other functions.

       


      Backup Destinations

      If you plan to automatically delete your excess backups using Disk Space Management (DSM), such as after Scheduling your backups, care should be taken in choosing the destination folder.  At step 3 above, the use of folders as the Destination in E drive would be the preferred way.

      DSM deletes oldest backup sets in the destination folder to make space available for new backups.  DSM for one (XML) Backup Definition can delete backups sets created by another Backup Definition for backups placed in the same destination folder.  The use of different folders should be part of a retention policy for backups to make sure one backup definition does not delete backups of others if you do not want it to do so.  DSM works at folder level but only on the designated destination folder of the backup.

      For information: A 'backup set' consists of a full backup and any incrementals or differentials with the same Image ID.  The Image ID is the part underlined in the following example backup file name: 69B5FC3F39E0F9F5-00-00.mrimg


      Image all drives

      In the tutorial above, we created a backup of all partitions required to backup and restore Windows. However, you can backup all drives and partitions on the PC by clicking the button as shown below:

      This will automatically select all drives and partitions in the wizard to be imaged. Continue from step 2 above.


      Image one drive or partition

      You can also choose to image just one drive:

      or just one partition by selecting the 'Actions...' button underneath the desired partition as shown below:


      Video Tutorial

       

      A Youtube tutorial showing the steps that have been covered above is available below:

       



      Search terms
      tag:backup
      tag:image

      v5: How to restore a file and folder backup

      $
      0
      0

      This tutorial is only for File and Folder backups and not Image backups. Please note that a restore will either restore files to your original folder or you get your folder structure and selected files restored to a place of your choosing. If you want an individual file restored without the folder structure you may wish to copy and paste it from Windows Explorer, see link at bottom of this web page.

      1. Open Macrium Reflect and select the "Restore" tab (marked in red below) and then the "File and Folder Restore" tab (marked in green)

      2. Your backups (shown in blue at the bottom of the above image) are listed at the bottom of the main pane. If the backups are not being shown, you can select the "Browse for a backup file..." or search for backup files in order to find your backup images. Once located, they will be added to the list of backups in the bottom half of the window. For each image, you may delete, verify, browse or restore the backup. In this case, click the "Restore Backup" link.

      3. The next dialogue gives the opportunity to select the files that are to be restored. You may restore all the files as shown in this tutorial, or select the individual directories and files you wish to restore. Click Next.

      4. You are now given the opportunity to select where you would like the files to be restored to. By default they will be placed in the location from which they were backed up, but it is also possible to restore them to a new location. Click Next.
      5. A summary window is displayed showing the details of the restore. Click Finish
      6. The files will now be restored as required.
        Search terms
        tag:restore
        tag:file

      v5: Understanding Rescue CDs and the Macrium rescue environment

      $
      0
      0

      If your computer refuses to boot or load Windows, or if you are trying to restore an image to a partition that Reflect cannot lock (such as your Windows system drive), then you will have to start your PC using a rescue CD or boot into the Macrium Rescue environment.

      For the professional and server editions, you have the option of restoring to a new system or virtual machine, employing the redeploy feature to reconfigure your windows installation for the new hardware.

      You have a number of options, each with their own advantages. The aim of this article is to help you understand which one is the best choice for you.

      The Linux Rescue Environment
      Linux is a free, open source UNIX based operating system, with wide hardware support.

      Windows PE Rescue Environment

      WindowsPE is a reduced version of windows designed to boot off CD/DVD mediaon the widest range of hardware. Macrium v5 enables either PE3.1 or PE4, based on Windows 7 Service Pack 1 and the windows 8 kernel respectively.

      Note: Historically, PE was prebuilt by Macrium. However, due to a global licensing change, the PE components are now downloaded from Microsoft and the rescue environment is built locally. This is an automated process, running as required by the rescue media wizard.

      You have the choice of PE3.1 or PE4, defaulting to PE3.1 unless you are running windows 8 (server 2012). We suggest you stick with the defaults unless you have good reason not to.


      Hardware support

      Just as for your normal windows installation, the rescue environment needs to include support for your hardware, in particular mass storage (inc. RAID if applicable), USB and network interfaces.

      The Linux environment supports most common hardware interfaces, including support for the most widely used RAID systems and USB3 connected devices. It cannot be customised for unsupported hardware.

      The Windows PE environment supports more hardware out of the box. Additionally, support can be added for devices that don't have default drivers. When a rescue CD is created, your system hardware will be analysed. Drivers for unsupported devices will be located on your system or via any driver disks supplied and added to the Windows PE environment.

      A limitation is that support cannot be added for the booting media. For example, if your CD drive is connected via an unsupported SCSI interface or your boot menu lies on a similarly unsupported RAID array, it will not boot. Booting using a USB stick is a good workaround in this case as all USB 2 interfaces are supported by default.
      Note: You can overcome this issue using solution 2 of this article.

      Media types

      The Linux environment can only be booted off CD & DVD media.

      Windows PE will boot off CD & DVD media and also USB sticks / thumb drives and USB attached external hard disks.
      Furthermore, Windows PE can be added as a boot menu item. The main purpose of this is for convenience and for automated restores to your system disk. It should not be relied upon as a rescue mechanism as you may loose the boot menu in the case of hard disk failure or corruption.

      Size

      The Linux rescue environment is extremely compact (circa 20 MB).

      The windows PE environment is a rather larger at about ~180MB.

      Features

      The Linux CD boots straight into a restore wizard and only offers basic restore functions.

      The Windows PE user interface is identical to that of the main application and offers the same core functions.

      Availability

      The Linux and custom Windows PE systems are available on all installation types. The Linux CD is included in the installer, while the custom PE system requires a download from Microsoft.

      Note that redeploy is not available in a trial install.

      Linux
      WinPE
      Fix boot problems
      x y
      Redeploy x Prof & server editions**
      RAID support
      x y*
      USB3 support
      x y*
      CD booting
      y y
      USB booting
      x y
      Boot menu x y
      Features
      Basic restore only
      Full application
      Download size
      none150-350MB***

      * may required additional drivers for PE3.1
      ** excluding trial installs
      *** Dependent on PE version and architecture. PE4 and 64bit PE types are larger than PE3 and 32bit types.

      Once I have created a rescue CD, will it work on all my computers?
      If you are using the Linux CD, the answer is yes.

      For Windows PE, the answer is more complex. If the hardware for all your computers is supported by the default windows PE driver set, then the answer again is a simple yes. You can confirm this on the Rescue Media Wizard drivers page - if all the drivers listed have the status "Device support in WinPE" or "Compatible device support in WinPE" for each of your machines then you only need one CD.

      If any of your machines require extra drivers, then you have three options.

      1) Create one CD per machine.

      2) Invoke the create Rescue media wizard on each of your machine, ensuring that all the necessary drivers have been located and you progress to the Rescue media burn page. Then copy the contents of c:\boot\macrium\drives on each machine to one machine. Finally, burn a Rescue CD on that machine.

      3) Using the Rescue media wizard create a bootable USB stick, inserting the same device on each machine in turn.

      Options 2 & 3 will only work if all your machines are configured to use the same version of PE with the same architecture (i.e. they are all 32bit or all 64bit).


      If your Rescue CD or USB equivalent does not boot

      Have you changed your BIOS settings to boot from CD/USB before your hard drive?

      Accessing the BIOS varies from PC to PC but you will always see a brief message that tells you how to do this as the PC is starting. Power on your PC from a full shutdown (not hibernate) and watch the screen carefully. Look for a line of text that says something like, 'Hit Del to enter setup' or 'Press F2 for BIOS settings'.Once you've found the correct key (generally, Del, or one of the function keys such as F2, F10, F11 or some other key such as ESC), press it repeatedly until you see a BIOS setup screen.

      There are many articles already on the internet about setting your BIOS to boot from CD/DVD or USB (USB is often called 'removable device' or 'USB-HDD' or 'USB zip disk' or something similar): You can find pictures of BIOS setup screens on a number of websites if you do not have your motherboard manual.

      (Note that some old PCs may not be able to boot from USB but only CD/DVD).

      Once you've changed the BIOS settings correctly, your PC should load Windows PE or Linux quickly. You may though see on the screen something like the following line: Press any key to boot from CD or DVD in which case press any key on the keyboard to boot from CD/DVD otherwise your CD/DVD will not boot.


      There is a YouTube video on how to create a rescue CD in Windows 7 using the WAIK.



      Search terms
      tag:restore
      tag:image
      tag:file

      v5 - How to automatically stop the SQL Server service when backing up

      $
      0
      0
      This article explains how to automatically stop the MS SQL service during VSS snapshot creation at the beginning of a Macrium Reflect disk image. SQL Server is a VSS aware application and these steps are only necessary if you receive VSS errors related to SQL that you are unable to resolve. This technique can also be used to briefly stop other services, such as MySQL that are not VSS aware.

      Create two batch files. One to start and one to stop the SQL service


      To disable the SQL server service for the duration of the snapshot, create batch files in the same folder as the XML defnition file. To determine the XML definition file folder, select the XML definition file when in Macrium Reflect and then click the 'Open Containing Folder' button on the toolbar.




      The names of the batch files need to be formatted in such a way that Macrium Reflect will automatically use them for the XML definition.
      The batch files should be named as below:
      <definition file name>_before_snapshot_wait.bat
      <definition file name>_after_snapshot.bat
      Replace <definition file name> to be the same name as the definition file. For example, if you have a definition file with the name:
      'My SQL Backup.xml'
      then the above two batch files will be named:
      'My SQL Backup_before_snapshot_wait.bat'
      'My SQL Backup_after_snapshot.bat'
      The content of the _before_snapshot batch file should be:
      NET STOP MSSQLSERVER
      The content of the _after_snapshot batch file should be:
      NET START MSSQLSERVER
      The'wait' part of the file name will cause Reflect to wait until the batchfile returns before continuing with the volume snapshot. This is recommended when backing up SQL Server to ensure that the database is in a closed state.

      Now, when the backup definition is executed the SQL Service will be stopped just prior to creating thevolume snapshot then started again a few seconds later when the snapshotis created.

      Search Terms:
      SQL Server
      VSS Error
      'MSDEWriter' is in failed state!
      tag:backup
      tag:image
      tag:file
      tag:clone

      v5: Macrium Reflect Command Line Arguments

      $
      0
      0
      This article explains how to use the Reflect from the command line.

      Getting Help

      You can retrieve a prompt for all the command line arguments by simply typing reflect -h from the command line.

      Running a Backup

      The command line form is as follows:

      reflect.exe [-v | -e [-w] [-full | -inc | -diff] [xml filename] ]

      Explanations for the switches are as follows:

      -hThis help text 
      -e Execute the XML file. If no full / diff / inc qualifier is used, a full backup is performed by default.
      -v Validate the XML file and exit
      -w If Reflect is busy then wait until available otherwise exit immediately
      -full Run a full backup
      -diff Run a differential backup
      -log Run an incremental backup

      Please note that the XML file name is the fully qualified path.

      Examples
      To validate an XML file
      reflect.exe -v "c:\backup.xml"

      To execute an XML file
      reflect.exe -e "c:\backup.xml"

      To execute an XML file with wait if busy
      reflect.exe -e -w "c:\backup.xml"

      To execute an XML file and create an incremental image
      reflect.exe -e -inc "c:\backup.xml"


      Mounting an image

      reflect.exe [Path To Image File] -b [-auto -drives [Drives[s]]  -pass [PASSWORD]]

      Explanations for the switches are as follows:

      -b Browse image 
      -auto Automatically assign drive letters. If not specified then you will be prompted
      -drives A comma separated list of drive letters to use. If not specified then the next available letters are used
      -pass The password for protected image files

      The image file name is the fully qualified path. If "LAST_FILE_CREATED" is specified then the last image created in the current Windows session is mounted.

      Examples

      To mount an image and prompt for a drive letter to use 
      reflect.exe "D:\901DBF91346B9A81-00-00.mrimg" -b

      To mount all partitions in an image using the next available drive letter(s)
      reflect.exe "D:\901DBF91346B9A81-00-00.mrimg" -b -auto

      To mount all partitions for the last image created
      reflect.exe "LAST_FILE_CREATED" -b -auto

      To mount all partitions in an image using drive letters j,k,l
      reflect.exe "D:\901DBF91346B9A81-00-00.mrimg" -b -auto -drives j,k,l

      To mount all partitions in a password protected image using drive letters j,k,l
      reflect.exe "D:\901DBF91346B9A81-00-00.mrimg" -b -auto -drives j,k,l -pass "PWD"


      Unmounting an image

      reflect.exe [Drive Letter] -u

      Explanations for the switches are as follows:

      -u Unmount image 

      If a drive letter isn't specified then all mounted images are unmmounted

      Examples

      To unmount an image from drive letter 'j'
      reflect.exe J -u

      To umnount all mounted drives
      reflect.exe -u

      v5: How to restore a backup image

      $
      0
      0

      This article describes how to restore a backup image

      Restoring a backup image is very simple using Macrium Reflect. If the image contains only data, it is a matter of restoring it back to its original location. For system images that contain boot data, the restoration algorithm will automatically reboot the system, launching Windows PE in its place, restoring the image and then rebooting as normal. In this tutorial, both methods will be covered.

      Three main sections are covered in this document:
      1. Restoring an image using the default settings
      2. Modifying the restored partition properties
      3. Restoring a system partition

      Restore a data image

      This tutorial assumes that a backup image has already been taken of a disk.

      1. On the main screen, select the 'Restore' tab as shown in red below.
      2. Backup images available to be restored are shown in the main pane. Select the image you wish to restore and select the 'Restore Image' link as shown in green above.

      3. The next dialog now gives you the opportunity to restore the image.

      Note: By default, partition(s) will be restored to their original locations. However, it is possible to restore to a different partition by using 'Drag and Drop'. Simply drag the source partition to any available partition on the target disk.

      In this instance, the default settings shall be used. Click Next.

      4. A summary screen is displayed confirming the choices that have been made. Click Finish.

      5. The image will now be restored. At the end of the process, an explorer window will open at the root of the destination so that it you can check that the files have been restored correctly.


      Modifying the Restored Partition Properties

      When restoring an image, by default, Macrium Reflect will attempt to locate the partitions in the image back to their original position on the disk. In the images below, I will attempt to restore a small partition to a new disk that is much larger. When you click to restore an image, you will be presented with the following dialog:


      Here, the Source is showing the location of the partition on the original disk. You now have two options. You can either restore the partition onto the new disk in exactly the same location by clicking the 'Copy selected partitions' link (see below)


      or you can click and drag the source partition onto the destination disk. The partition will be located at the first available free area of the disk. In this case, this is at the beginning of the disk. Please note that if you already have established partitions on the target disk, you need to select each one and click theDelete Existing partition link before you can drag and resize partitions from the source. See below:


      You can now modify the size of the target partition by clicking the link 'Restored Partition Properties'. This gives the following dialog.


      There are a number of things you can do here:
      • You can modify the resultant drive letter by choosing one from the pull-down list.
      • You can modify and select the partition type i.e. Primary, Active, Logical
      • By clicking on the < > arrows above the disk view, you can click-and-drag the size of the partition as you wish
      • You can then fine tune the exact partition size, its free space and alignment by using the controls on the bottom left of the dialog
      • The Maximum Size button configures the partition to take the maximum available unallocated space on the disk, in this case about 1TB (the size of the disk)
      • The Minimum Size button configures the partition to take the minimum size which in this case is roughly the same as the amount of data on the disk i.e. 460MB
      • The Original Size button sets the partition to be exactly the same size as it was prior to backup
      When you click OK, you can then follow the steps in the first part of this document to complete the restore.

      A Youtube video outlines some of the basic issues discussed here:



      Restoring a system image

      In the case of system images i.e. the 'C drive' containing the operating system files, it is not possible to restore files in real time because they are in use by the current session of the operating system. In order to get around this problem, Macrium uses Windows PE, a cut down version of Windows which is booted. Macrium then restores the filesystem before rebooting again and loading the main version of Windows. Although this sounds complex, it really is very simple to perform.

      This tutorial assumes you have a backup image of a system drive and this section of the tutorial should be used for restoring to your original hard drive.

      Note: If you are restoring your system Image or whole hard drive Image (which includes system partitions) to a new Hard drive then don’t follow this tutorial. When restoring system Image to a new hard drive: remove old hard drive and install new hard drive then boot computer with Windows PE rescue media (CD or USB) (or use Linux rescue CD) and use the rescue media to restore. See separate Video/tutorial for details.

      1. In the main application window, select the 'Restore' tab as shown in red as shown below


      2. Select the required image and click the 'Restore Image' link as shown in green above.

      3. As above in step 3, you can choose to restore the image to a different partition. However, for this tutorial use the default settings and click Next

      4. Review the summary and click Finish

      5. At this point, Macrium Reflect recognizes that it is not possible to restore the image to the 'C drive' and therefore displays a dialogue informing you that Windows PE must be used. Click 'Run from Windows PE'

      6. You will now be prompted to restart your PC. Close down any saved work and click 'Restart Now'

      7. The system will reboot, Macrium will add a boot menu option and automatically select the recovery environment.

      8. Windows PE will now boot and automatically run Macrium which will detect which image is to be restored and start restoration automatically as shown above. When the restoration is complete, Macrium will automatically reboot the PC again and the normal copy of Windows will boot as normal.

      You should find that the files in the image have been successfully restored.

      A Youtube video tutorial detailing how to perform a system restore is available below:






      Search terms
      tag:restore
      tag:image

      v5: How to sysprep Windows and deploy using Macrium Reflect

      $
      0
      0

      This article describes how to use the Windows sysprep utility to prepare a machine to be deployed across multiple other machines.

      Configure your PC for deployment

      Windows provides a handy utility called sysprep which allows you to prepare a master PC image that is configured and set up to be deployed across multiple workstations. By running sysprep, Windows prepares the machine so that once installed on a workstation, the System Admin will be prompted for Windows Activation and environment configuration as if the PC had just been installed from scratch.

      In order to prepare a PC to be syspreped, ensure that it contains all the applications and configuration you wish the deployed systems to have installed. Also note that unless you have sufficient licenses for the machines you are deploying to, Reflect should be uninstalled from the PC that will used for the base image. However, if is essential to have made a Windows PE based Macrium Reflect rescue CD on that PC first.

      Sysprep your system

      In order to run sysprep, run through the following steps:
      1. Open an explorer window and navigate to C:\Windows\System32\sysprep
      2. Run sysprep.exe
      3. Ensure that the System Cleanup Action is set to the Out-of-Box Experience, and that Generailze is checked as below.

        Shutdown options are up to you, but selecting Quit ensures that the system will not reboot or shutdown automatically.
      4. Click OK.
      This will now prepare this machine so that it can be deployed to other PCs.

      Image with Reflect and deploy

      Once sysprep has completed, shutdown the PC and boot it with the Macrium Reflect Rescue CD. You can now take an image of the PC using Macrium Reflect and store it either to an external USB device or network location. Once this has been completed, you can now deploy the image to the workstations you require. Please note that if using Reflect to do this, you will require a deployment license for each restore. This extends the existing Reflect license which only permits you to restore back to the original PC or a upgraded PC.

      When the restore has been completed, you can then boot the new PC. Windows will then ask for the new license key and environment settings.

      Event 513 errors in Windows 8.1

      $
      0
      0

      Description

      In Windows 8.1, during the backup process, the following error may be found in the Windows Event log.

      Event 513
      Source: Microsoft-Windows-CAPI2
      AddLegacyDriverFiles: Unable to back up image of binary Microsoft Link-Layer Discovery Protocol.
      System Error: Access is denied.

      This message is caused by the Windows Shadow Copy System Writer. If the permissions of the COM catalog folder are incorrect, this writer may not work properly.


      Solution

      The Shadow Copy System Writer is not used by Reflect, and so this error does not affect the backup process. However, if you want to stop the error message from appearing, follow the following steps.
      1. Navigate to your C:\Windows folder within Windows Explorer.
      2. Right click on the folder Registration. Click on Properties, and go to the Security tab.
      3. Click the Advanced button. If the User Account Control dialog box appears, click Continue.
      4. In the following dialog, make sure that the following permissions are set:
        • The Administrators group has Full Control over This folder and files.
        • The Everyone group has List folder/read data, Read attributes, Read extended attributes, and read permissions for This folder and files.
        • The SYSTEM account has Full Control over This folder and files.
      5. Click OK.

      v5: HP Protect service mount issue

      $
      0
      0

      This article details the issues with HP Protect service when trying to mount a Macrium Reflect image in Windows 7


      Problem

      When mounting an Macrium Reflect image in Windows 7 while using HP Protect service you may receive the following message when trying to access the mounted drive:
      <drive> is not accessible \ incorrect function
      The problem is caused by HP Protect service which causes access to the image file which is mounted by Macrium Reflect's thoroughly tested mounted service to fail.

      Solution

      You need to disable HP Protect service before trying to mount any Macrium Reflect image backup. To complete this task follow the below steps:
      1. Right click My computer and select 'Manage ' expand Services and Application, then select 'Services' then navigate to the service entitled 'FLCDLOCK' Double click the service and select 'Stop' see below:

      2. After disabling HP Protect service mount your backup using Macrium Reflect or by right clicking the file and selecting 'Explore Image'
      3. To enable HP Protect service restart your computer.

      Search terms
      HP Protect service
      HP
      <drive> is not accessible \ incorrect function

      v5: Blue screen with Trend Micro Titanium

      $
      0
      0

      This article details the issues with Trend Micro Titanium when trying to mount a Macrium Reflect image backup on Windows 7


      Problem

      When mounting an Macrium Reflect image and selecting to enable 'access to restricted folders' on Windows 7 while using Trend Micro Titanium you may receive the following BSOD:

      The problem is caused by Trend Micro Titanium which causes the computer to crash during the mount of the image file which is mounted by Macrium Reflect's thoroughly tested mounting service.

      Solution

      You need to disable Trend Micro Titanium (version: 7.0.1151) before trying to mount any Macrium Reflect image and enabling access to restricted folders. To complete this task follow the below steps:
      1. Right click the Titanium icon in the task bar and select 'Protection Against Viruses & Spyware'

      2. This will then bring up a warning about disabling the program

      3. After disabling Titanium mount your backup using Macrium Reflect or by right clicking the file and selecting 'Explore Image'
      4. If you want to re-enabled Titanium please follow the first point.

      Search terms
      Titanium
      Micro Trend
      Blue screen Of Death

      Understanding Image Verification Failures

      $
      0
      0
      Though they do happen, verification errors are extremely rare. We estimate that less than 1 in 1,000 systems have problems that lead to image file corruption. The vast majority of Macrium Reflect users will never encounter a single verification issue.

      This article explains what happens during the image verification process and how to troubleshoot problems with your system.

      What is a verification failure?

      Quite simply, it means that data that was written to the backup or image file is not the same as is read back from the same file.

      Errors of this type are symptomatic of a computer system with a marginal hardware problem. The most likely suspect is your backup media - but memory and motherboard faults can also cause this issue.

      How does Macrium Reflect check the data integrity?

      Macrium Reflect uses the unmodified code from the reference implementation of the RSA Data Security MD5 message-digest algorithm. This guarantees that the same block of data cannot generate a different message digest (hash) value. If data is read back with a different MD5 hash to that that was generated when the data was written, it is guaranteed to be corrupt. This is always outside of the control of Macrium Reflect as the OS will report a write without any error.

      When an image is created each block of data (generally 64K but may be larger depending on the partition size) has an MD5 hash created after it is read from the disk and before it is written to the image file. This hash value is saved in the index of the image file. When the file is read back the hash value is recalculated and compared with the original hash in the index. Any discrepancy between the two values indicates that the image file is corrupt or cannot be read back reliably.

      Why can't Macrium Reflect validate the data as it is written?

      It isn't possible to verify the file as it is written because the buffers and caches in the write process aren't flushed to disk until after the file is closed. The only way to verify data integrity is to close the file at the end of the backup process and then read the file back. It's possible to do this automatically by selecting the 'Auto-Verify' option in Macrium Reflect.

      Note: Auto-verify is only available with the full edition of Macrium Reflect. Please see here for information on turning this feature on: http://www.macrium.com/webhelp/Advanced_Settings.asp?nohead=y#AutoVerify

      Why don't I have any other problems with my system?

      You do, you just haven't noticed it yet. If your PC can't write and read back data reliably then this won't just be a problem with Macrium Reflect, all software on your PC will be vulnerable to same problem. Macrium Reflect is either the first to trigger it or is the only software reporting the problem to you.

      Files are not checked for integrity by Windows, so unless an application does it explicitly, disk errors could have been occurring silently. Macrium Reflect handles very large volumes of data with a consequently high chance of triggering any intermittent hardware errors.

      I don't believe you. How can I be sure it isn't a problem with Macrium Reflect?

      To independently corroborate the problem you can use a third party utility to show the same corruption:

      • Use the DOS copy command with the '/v' switch to copy a large single file (peferably the same size as the image file that's failing) from the source of the image to the same backup device. The '/v' switch will verify the file after copying and will report any errors.
      • If you want to use a GUI based application the try the free utility ExactFile available from http://www.exactfile.com. A pdf article on using ExactFile is available here: http://updates.macrium.com/reflect/utilities/exactfile.pdf

      • Try a different imaging application that provides verification such as Acronis or Norton Ghost.

      Note: The DOS copy command and ExactFile checks aren't conclusive as file checkers read the file sequentially and the error may only occur during random access. Due to the different execution and data paths, success in any of the detail test is not an absolute guarantee that your hardware is fault free.



      Troubleshooting verification problems:

      The key to resolving verification errors is to locate the source of the corruption. This can be very difficult and may involve replacing PC components or upgrading firmware or software drivers.

      1. Isolate the backup drive

      If the backup drive is an external drive then backup to the same drive using a different PC. If your system is generally stable then the issue causing the verification error may have very low probability of occuring. Therefore, to optimise the chance of triggering it, you should try to backup the same or a greater volume of data. If you still receive verification errors then your drive is faulty and you should use a different backup device.

      2. Use different data leads and ports

      If possible try using a different sata or usb leads or connecting the device to a different port. Also, if using USB, try removing any USB hubs between the storage device and the computer.

      3. Try a different backup destination

      Try combinations USB/Fire-wire/eSata/Network. If you only get corruption with one of the connection types then that sub-system has a problem. Updating the firmware or software drivers for the controller might resolve the problem.

      3. Replace or swap out your RAM modules

      If the error can't be traced to a single component then you may have faulty system RAM. If you have more than one RAM module installed then swapping out the memory can isolate the faulty RAM module.
      Note: Memory checkers such as 'memtest86' will often fail to find any problems even though there is a latent issue with the RAM.

      4. Turn off your anti-virus software

      We have had an uncorroborated report that some anti-virus software can corrupt disk writes. If you find that your images pass verification after disabling your AV software then we strongly recommend that you un-install your AV software as it is compromising your system.


      Search terms
      tag:backup
      tag:image
      tag:file

      Technicians license explained

      $
      0
      0




      Standard

      Enterprise





      WorkstationsUnlimitedUnlimited
      ServersUp to 10Unlimited
      Reflect Server Edition LicenseIncludedIncluded
      Upgrade ProtectionIncludedIncluded
      Price Year 1$399$699




      Buy Now - <a name="server">Macrium Reflect Server v5</a>Buy Now - <a name="server">Macrium Reflect Server v5</a>
      Renewal Year 2 onwards$279 pa$579 pa

      What is the Technician's License?

      There are two technician's licenses available:

      • Standard - Maintain up to 10 servers and unlimited workstations

      • Enterprise - Maintain unlimited servers and unlimited workstations

      The Standard Technician's License permits a single technician to image and restore up to 10 different servers and unlimited workstations. The Enterprise Technician's license has no restriction on the number of servers that can be imaged. Providing the Macrium Reflect is not installed on more than one PC at a time.

      The Technician's License includes one copy of our premium software, Macrium Reflect Server Edition, for each technician together with free upgrade protection during the subscription period. This software also comes with Portable Application Support, allowing you to create a single USB stick with rescue environment that can image your target workstations online and offline. This enables maintenance of your servers and workstations without the need to install Macrium Reflect.

      Each Technician's License is renewed on an annual subscription basis, with a reduced subscription applying from Year 2 onwards.

      The improved Macrium Reflect Technician's Edition v5 now includes:

      • Portable Application Support
      • Upgrade Protection
      • Macrium Reflect Server License (Technician's)
      Please note: Technician's Licenses first purchased before November 2011do not include these additions, even if they have been renewed afterthis date. Please contact us for a discounted upgrade to the newTechnician's Edition with the additional functionality.


      Who might use a Technician's License?

      This license arrangement is ideal for IT technicians or service companies who might maintain a large number of PCs and may wish to back them up prior to carrying out work. If they did not have the Technician's License, then every time they backed up a different PC a new copy of Macrium would need to be purchased, because the usual licensing arrangement is machine specific. Using a Technician's license allows the technician to backup or image each PC using a single Macrium Reflect license.

      Typically, a technician would use the Portable Application or its accompanying PE environment to image their target workstations. This means Reflect needs only to be installed on a single PC and the Portable Application Media created.

      Note: The base install of Macrium Reflect may only be installed on a single PC at a time. If you wish to move this install, you will have to uninstall and reinstall the software.


      What is Portable Application Support?

      Portable application support ships exclusively with Macrium Reflect Technician's Licenses. In addition to allowing you to create a bootable USB stick from which you can rescue your systems, you can also optionally add Portable Application support to your media.

      This will allow you to run Macrium Reflect on your licensed PCs directly from the USB stick, without needing to install Reflect on the workstation or server first.

      Reflect can then be launched from the USB stick using the file "portable.exe":

      Which launches the familiar Reflect main screen. To this, we have added two notable additions:

      1. Notification of your expiry date, so that you know when your renewal is due. Note: On this date, your USB stick will stop working.
      2. An additional wizard to add drivers to the bootable environment contained on the USB stick. This allows you to have one rescue environment which works on all the workstations/server you wish to back up and restore.


      License templates

      You can view templates of the Technician's Licenses below:

      Technician's License - Standard

      Technician's License - Enterprise

      Viewing all 166 articles
      Browse latest View live