StorageCraft ReadMe Files

Announcement: Please check out our new StorageCraft Support Community, which is now online. Please click here to register an account on the new community site, and continue posting to our Forums (now called Discussions) and provide feedback on article content.

NOTICE: Forums are now locked on this site - To post discussions, please continue to the new site and register there.

 


 

Backup
Manage

Cloud
 Replicate
Recover

 

1 ShadowProtect SPX ReadMe

General Information

Go to the SPX Release Notes for information about SPX 6.5.0 and newer.  

This ReadMe includes information about StorageCraft ShadowProtect SPX 6.3.0 and older.  Both documents are supplements to the SPX User Guide

 
What's New

See SPX Release Notes in the SPX User Guide for the latest product information.

 

January 9, 2017 - The Socket Licensing Service was updated to version 1.1.4 on January 9, 2017. See Socket Licensing Service updates for ShadowProtect SPX 6.3.0 (January 2017) for additional Socket Licensing Service information.
 
Windows 10

Windows 10 is now a supported operating system for SPX. For Windows upgrades, StorageCraft recommends deactivating the SPX license prior to upgrading the OS to Windows 10. While a Windows upgrade may work with SPX without a license deactivation, StorageCraft recommends as a best practice to deactivate the software first, then perform the OS upgrade (including Windows 8 to 8.1 or to Windows 10). After the upgrade completes, reactivate SPX.

Caution: SPX currently has an issue with continuing a backup chain from a Windows 10 VM created using VirtualBoot.

Migration Issues from ShadowProtect 5.x

Caution: SPX supports only NTFS and FAT partitions (not "hidden" or "unknown" partitions) for backup in Windows. During an upgrade to SPX, if a ShadowProtect 5.x backup job includes one or more hidden partitions, SPX does not migrate the part of the backup jobs for these hidden partitions.

Note that the vast majority of hidden partitions have static content and do not require incremental backups.  Users may prefer to have a simple periodic full backup of these partitions rather than include them as part of a continuous incremental backup job.

 

1. System Requirements
Linux Operating Systems 

StorageCraft is committed to supporting distributions of Linux with long-term support (It does not support self-compiled or short-term releases.). Refer to the StorageCraft Supported Linux Versions list to determine if your current installed Linux kernel supports SPX, this list is continuously updated.

Kernel Version

An automated approach to determine if SPX supports the installed Linux kernel is to run these commands:

Ubuntu 12.04

1. Set up the repo:

wget https://downloads.storagecraft.com/spx/Ubuntu12.04/storagecraft-repo-latest.deb -O storagecraft-repo-latest.deb
sudo dpkg -i storagecraft-repo-latest.deb

Note: The above command installs a copy of the StorageCraft repository public signing key to the files system. It then automatically adds it to the apt keystore in Ubuntu. To see a copy of this key go to http://downloads.storagecraft.com/spx/Ubuntu12.04/stc/repository.key .

2. Run the command

apt-cache search kmod-stcvsm
Ubuntu 14.04

1. Set up the repo:

wget https://downloads.storagecraft.com/spx/Ubuntu14.04/storagecraft-repo-latest.deb -O storagecraft-repo-latest.deb
sudo dpkg -i storagecraft-repo-latest.deb

Note: The above command installs a copy of the StorageCraft repository public signing key to the files system. It then automatically adds it to the apt keystore in Ubuntu. To see a copy of this key go to http://downloads.storagecraft.com/spx/Ubuntu12.04/stc/repository.key .

2. Run the command

apt-cache search kmod-stcvsm

CentOS/RHEL 6

1. Set up the repo:

wget https://downloads.storagecraft.com/spx/CentOS6/storagecraft-repo-latest.rpm -O storagecraft-repo-latest.rpm
sudo yum install storagecraft-repo-latest.rpm -y

2. Run the command:

yum list kmod-stcvsm*

CentOS/RHEL 7

1. Set up the repo:

wget https://downloads.storagecraft.com/spx/CentOS7/storagecraft-repo-latest.rpm -O storagecraft-repo-latest.rpm
sudo yum install storagecraft-repo-latest.rpm -y

2. Run the command:

yum list kmod-stcvsm*

File Systems

SPX supports these Linux file systems on storage devices:

Hypervisor Support

Supported socket licensed Hypervisors

Supported virtual key licensed Hypervisors

ShadowProtect also correctly detects its licensing on these hypervisors.

Recovering Linux Backup Files

The 64-bit Recovery Environment CrossPlatform (RE-X) supports SPX-generated Linux backup files.

 

Windows Operating Systems

SPX supports the majority of contemporary Windows and Windows Server operating systems, from Windows XP Home or XP Professional w/SP3 and up to and including Windows 10. Minimum is Windows XP SP3.

SPX provides both a 32- and a 64-bit Windows installer. SPX requires the correct bit-level installer for the OS. If the OS is 32-bit, use the 32-bit SPX installer. If the OS is 64-bit, use the 64-bit installer.

SPX does not support:

File Systems
Ports

SPX uses these ports:

Login Credentials

You must use Windows credentials to log into the SPX console. The user  account must be a member of the Local Admin group. SPX requires the user to have a password. If your user doesn't have a password you must create one prior to logging in.

Hypervisor Support
Recovery Environment

The 64-bit Recovery Environment CrossPlatform supports restorations of both Windows and Linux boot volumes. Use the REBuilder app to create the 64-bit Windows Recovery Environment if the restore requires additional driver support. (StorageCraft recommends using the 32-bit Recovery Environment only when required by the destination hardware.)

 

2. Features/Enhancements
 
Socket Licensing Service 1.1.4 updates for ShadowProtect SPX 6.3.0 (January 2017)
ShadowProtect SPX 6.3.0 (August 2016)
ShadowProtect SPX 6.2.0 (May 2016)
ShadowProtect SPX 6.1.0 (March 2016)
ShadowProtect SPX 6.0.16 (November 2015)
ShadowProtect SPX 6.0.14 (November 2015)
ShadowProtect SPX 6.0.12 (September 2015) (Update for Linux endpoints only)
ShadowProtect SPX 6.0.8 (July 2015)
ShadowProtect SPX (March 2015)
3. Known Issues 
ShadowProtect SPX 6.3.0 (August 2016)
ShadowProtect SPX 6.0.16 (November 2015)
ShadowProtect SPX 6.0.14 (November 2015)
ShadowProtect SPX (July 2015)
ShadowProtect SPX (March 2015) (Linux-only)
4. VirtualBox Support

General

When run for the first time, VirtualBoot installs the appropriate plugin for the installed version of VirtualBox. If it sees a newer version of VirtualBox than the one officially supported it will still attempt to install the appropriate plugin. For instance, if it sees VirtualBox 4.3.30, but the latest version SPX supports is 4.3.28, it will install the plugin for 4.3.28. In most instances, this works without issue. However, this may become an issue when SPX must update the plugin between minor releases of VirtualBox. If the VM shows a black screen with a message like "A Disk Read Error Has Occurred," this may be the problem.

VirtualBoot attempts to upgrade the plugin when it determines that VirtualBox was upgraded and there is a new version of the plugin corresponding to the new version of VirtualBox.

Special Considerations For Linux

Warning:
It is possible to configure the VirtualBox Repo on a Linux machine. (This makes it easy to download updates to VirtualBox.) However,  this option will tend to download the latest version of VirtualBox for that particular branch defined in the Repo (e.g. 4.3.x or 4.2.x). This presents two potentially serious problems:

For these reasons StorageCraft recommends downloading directly specific versions of VirtualBox that StorageCraft confirms are supported by SPX. The SPX user guide contains a table of supported VirtualBox versions

In general, using HIR, VirtualBoot can launch a VM of a Windows system if the source is the boot volume backup. (Note that the original system may have had a separate volume called "Boot", often without an assigned drive letter, but that volume isn't needed for VirtualBoot.) Linux however is different. 

Frequently in Linux, the /boot and /root directories needed for a successful boot are on separate volumes. There's sometimes a third directory called /home that is required and also on a separate volume. Assume then that VirtualBoot needs all of these volumes for a successful VirtualBoot.

Currently, Linux images can only be booted on Linux hosts. Among other reasons, this is because VirtualBoot needs to mount the volumes contained in the image during the prep phase, and Windows doesn't know how to do this with the Linux filesystems.

 

5. FOSS Components

Information on FOSS software components used in SPX appears at stcfoss.org.

 

 

Copyright © 2016 StorageCraft Technology Corp. All rights reserved. This Software and Documentation are copyrighted.  Ownership of StorageCraft ShadowProtect Software, StorageCraft ImageManager, and StorageCraft Cloud Services is reserved to StorageCraft Technology Corporation. The StorageCraft logo, the StorageCraft ShadowProtect logo, StorageCraft ImageManager logo, and StorageCraft Cloud Services logo are trademarks of StorageCraft Technology Corporation. StorageCraft, ShadowProtect, ShadowControl, and HeadStart Restore are registered trademarks of StorageCraft Technology Corporation in the United States and elsewhere. ShadowProtect Server Edition, intelligentFTP, and ShadowStream are trademarks of StorageCraft Technology Corporation in the United States and elsewhere. All other brands and product names are or may be trademarks or registered trademarks of their respective owners.


2 ShadowProtect Release Notes

General Information

This file contains additional information about ShadowProtect and supplements the content of the ShadowProtect User Guide. Please read all the sections before you proceed with the installation.

This ShadowProtect ReadMe covers up to v5.2.7.

Windows 10 Support

This version of ShadowProtect is certified to support Windows 10 Windows Server 2012 R2.

Table of Contents

  1. Features/Enhancements
  2. Known Issues
  3. Issues Resolved
  4. System Requirements
  5. Installing and Upgrading ShadowProtect
  6. Activating ShadowProtect
  7. General Usage Notes
  8. CDDL Source Code

 

1. Features/Enhancements

For a complete list of changes, see also Section 3 ("Issues Resolved")

ShadowProtect version 5.2.7  (May 2016)

ShadowProtect version 5.2.3  (December 2014)

ShadowProtect version 5.2.2  (December 2014)

ShadowProtect version 5.2.0  (July 2014)

 VIRTUALBOOT PLUGIN FILES SUPPORTED VIRTUALBOX VERSIONS
 Version numbers here      
 correspond to the various
 versions of VirtualBox's    
 disk *plugin interface* 
 
   
ForVBox3.1.0        3.1.0, 3.1.2, 3.1.4, 3.1.6
ForVBox3.1.8     3.1.8
ForVBox3.2.0 3.2.0, 3.2.2, 3.2.4, 3.2.6
ForVBox3.2.8 3.2.8
ForVBox3.2.10 3.2.10, 3.2.12, 3.2.14, 3.2.16, 3.2.18, 3.2.20, 3.2.22
ForVBox4.0.0 4.0.2, 4.0.4, 4.0.6, 4.0.8, 4.0.10, 4.0.12, 4.0.14, 4.0.16, 4.0.18, 4.0.20, 4.0.22, 4.0.24
(VirtualBox 4.0.0 is not supported)
ForVBox4.1.0        4.1.0
ForVBox4.1.2 4.1.2, 4.1.4, 4.1.6, 4.1.8, 4.1.10, 4.1.12, 4.1.14, 4.1.16, 4.1.18, 4.1.20, 4.1.22
4.1.24, 4.1.26, 4.1.28, 4.1.30, 4.1.32
ForVBox4.2.0  4.2.0, 4.2.2, 4.2.4, 4.2.6, 4.2.8, 4.2.10, 4.2.12, 4.2.14, 4.2.16, 4.2.18, 4.2.20, 4.2.22, 4.2.24
ForVBox4.3.0 4.3.0, 4.3.2, 4.3.4, 4.3.6, 4.3.8, 4.3.10, 4.3.12

 

ShadowProtect version 5.1.5 (January 2014)

ShadowProtect version 5.1.4 (November 2013)

ShadowProtect version 5.0.4 (June 2013)

ShadowProtect version 5.0.3 (May 2013)

ShadowProtect version 5.0.2 (April 2013)

ShadowProtect version 5.0.1 (January 2013)

ShadowProtect version 5.0 (December 2012)

VirtualBoot Plugin Files  |  Supported VirtualBox Version

-----------------------------------------------------------------------------------------------------

ForVBox4.0.0                    |  4.0.2, 4.0.4, 4.0.6, 4.0.8, 4.0.10, 4.0.12,
                                            |  4.0.14, 4.0.16 (VirtualBox 4.0.0 not supported)

ForVBox4.1.0                    |  4.1.0

ForVBox4.1.2                    |  4.1.2, 4.1.4, 4.1.6, 4.1.8, 4.1.10, 4.1.12,
                                            |  4.1.14, 4.1.16, 4.1.18

ForVBox4.2.0                    |  4.2.0, 4.2.2, 4.2.4

ShadowProtect version 4.2.7 (August 2012)

ShadowProtect version 4.2.6 (August 2012)

ShadowProtect version 4.2.5 (April 2012)

ShadowProtect version 4.2.0 (December 2011)

ShadowProtect version 4.1.5 (May 2011)

There are no new features for this maintenance release.  See Section 3 for a description of the fix in this 4.1.5 release.  If you are not experiencing any issues with your current ShadowProtect Desktop/Server/SBS Edition 4.1.0 installation, then there is no need for you to upgrade to this 4.1.5 maintenance release.

ShadowProtect version 4.1.0 (February 2011)

ShadowProtect version 4.0.5 (December 2010)

VirtualBoot Plugin Files  |  Supported VirtualBox Version

---------------------------------------------------------

ForVBox3.1.0                    |  3.1.0, 3.1.2, 3.1.4, 3.1.6

ForVBox3.1.8                    |  3.1.8

ForVBox3.2.0                    |  3.2.0, 3.2.2, 3.2.4, 3.2.6

ForVBox3.2.8                    |  3.2.8

ForVBox3.2.10                  |  3.2.10, 3.2.12

 

ShadowProtect version 4.0.1 (July 2010)

ShadowProtect version 4.0.0 (April 2010)

 

2. Known Issues

 

 

3. Issues Resolved

For a list of additional changes, see also Section 1 "Features/Enhancements".

ShadowProtect version 5.2.7  (May 2016)

ShadowProtect version 5.2.3  (December 2014)

ShadowProtect version 5.2.2  (December 2014)

ShadowProtect version 5.2.0  (July 2014)

ShadowProtect version 5.1.5 (January 2014)

ShadowProtect version 5.1.4 (November 2013)

ShadowProtect version 5.0.4 (June 2013)

ShadowProtect version 5.0.3 (May 2013)

ShadowProtect version 5.0.2 (April 2013)

ShadowProtect version 5.0.1 (January 2013)

ShadowProtect version 5.0 (December 2012)

ShadowProtect version 4.2.7 (August 2012)

ShadowProtect version 4.2.6 (August 2012)

ShadowProtect version 4.2.5 (April 2011)

ShadowProtect version 4.2.0 (December 2011)

ShadowProtect version 4.1.5 (May 2011)

ShadowProtect version 4.1.0 (February 2011)

ShadowProtect version 4.0.5 (December 2010)

ShadowProtect version 4.0.1 (July 2010)

ShadowProtect version 4.0.0 (April 2010)

 

4. System Requirements

Supported Operating Systems

ShadowProtect supports the following Windows 32-bit x86 or 64-bit x64 operating systems (IA64/Itanium is not supported):

NOTE: While ShadowProtect supports all of these Windows versions, a particular ShadowProtect license may limit which versions it will activate on. For example, the ShadowProtect SBS license only activates on Windows SBS, SBS R2, Windows Server 2012 Essentials and Foundation and Windows Server 2012 R2 Essentials and Foundation. The SBS license will not activate Windows Storage Server 2008 R2 Essentials.

Windows 2000 support: While ShadowProtect fully supports backup of Windows 2000 environments, lack of hardware support and suitable device drivers for this legacy environment might make recovery of System volumes difficult. If you use Windows 2000, be certain that you have suitable hardware and device drivers available for use as a recovery target in the event of a disaster. The ImageReady utility also does not support Windows 2000.

* Windows Storage Server 2003: ShadowProtect does not support Windows Storage Server 2003.

* Tablet support: ShadowProtect currently does not support any tablet OS, including Windows 8 (such as the Surface Pro). However, the Windows XP Tablet Edition, which is a desktop OS with stylus capability, is supported.

Supported Hypervisors

ShadowProtect Virtual supports Windows guests in these hypervisors:

* ShadowProtect is currently not supported on VMware Fusion for the Mac.

Supported File Systems/Disk/Volume Types

ShadowProtect supports the following File Systems:

ShadowProtect does not support the exFAT or the ReFS file systems. It also does not support Windows Storage Spaces storage pools.

ShadowProtect does support converting to and mounting VHD and VHDX file formats as well as VMware VMDK.

Supported Storage Media

ShadowProtect supports the following storage media:

 

5. Installing and Upgrading ShadowProtect 5.2.0

In versions of ShadowProtect prior to version 4.2.0, there were separate installer files for each of the five editions of ShadowProtect (Desktop Edition/Server Edition/SBS Edition/VM Edition/MSP Edition). For each of these editions, there were also separate installers for each supported language. This complex situation no longer exists. Starting with ShadowProtect 4.2.0, there are only two installers:

Upgrading

In most circumstances, you can upgrade to ShadowProtect 5.2.0 over an existing v3.5.2 or newer installation. You will need a valid and current maintenance agreement to reactivate the license. After the upgrade, ShadowProtect 5.2.0 displays a 30-day Trial license. Use the existing license number (which has the maintenance agreement) and click Activate to re-activate this existing license.

The exceptions to an upgrade include:

Installing over a ShadowProtect MSP Version

If the existing 4.1.5 installation is an MSP installation, you must use the ShadowProtectSetup_MSP_5.2.0.exe installation file to upgrade to 5.2.0. 

Installing over ShadowProtect 3.5.2 or Newer Versions

If your existing 3.5.2 or newer installation is a Desktop/Server/SBS/Virtual Edition, then to upgrade to 5.2.0 you must use the ShadowProtectSetup_5.2.0.exe installation file. 

You do not need to uninstall ShadowProtect 3.5.2 before installing 5.2.0. The installer will upgrade your system from 4.1.5 to 5.2.0 and preserve your job configurations. ShadowPrectect Setup will attempt to deactivate the existing license prior to the upgrade. Should this deactivation fail, the program displays a message to perform a manual deactivation prior to the uninstall.

Installing over Pre-3.5.2 ShadowProtect Versions

If your system has a version of ShadowProtect older than 3.5.2 already installed, then you will need to de-activate and then fully uninstall it (including the post-uninstall reboot) before you can install and activate ShadowProtect 5.2.0.


 

6. Activating ShadowProtect

You will need to activate ShadowProtect before the trial period ends.  Each time you take a backup, the number of days left in your trial period will be displayed in the history. 

To activate ShadowProtect, click Product Activation on the Help menu.  Type in the Serial Number (product key), Name, and Organization (optional) and click OK for immediate online activation. 

Language, Platform, and Serial Number Must Match

The language of your product serial number/key must match the language you chose in the 5.2.0 install wizard at the time you install ShadowProtect. Otherwise the ShadowProtect agent will fail to activate.  For silent installs, the 5.2.0 silent install answer file provides a way to specify the language of the install.

When activating ShadowProtect standard install, your product key type (Desktop/Server/SBS/VM) must match your platform.  Desktop Edition product keys can only be used to activate ShadowProtect on non-Server platforms. SBS Edition keys can only be used to activate ShadowProtect on SBS or Foundation Servers. Virtual Edition keys can only be used to activate ShadowProtect on virtual machines. Server Edition keys can be used to activate ShadowProtect on any supported server platform (Server, SBS, Foundation, etc). ShadowProtect MSP keys can activate ShadowProtect on any supported platform (all supported workstation and server platforms).

Reactivate after Upgrading to 5.2.0

Upgrading from 3.5.2 or later should preserve your activation if you have a current and valid maintenance agreement. If you upgrade from an activated 3.5.1 or earlier installation of ShadowProtect to 5.2.0, you will need to re-activate your license. 

To do this, after performing the upgrade, go to the ShadowProtect user interface's Help menu. Click Product Activation. Fill in any remaining fields (your product key will usually be automatically entered). Click OK to re-activate. 

Error on Activation

** If you receive an error indicating that the StorageCraft Activation server cannot communicate with your system and you access the internet through a firewall, confirm that the SOAP (Simple Object Access Protocol) is enabled on your firewall. **

Trial Version

If you install the Trial Version of ShadowProtect, you can install all the applications and create backup image files of system and data volumes.  You can also restore data volumes or specific files and folders. You will not be able to restore the system volume as the StorageCraft Recovery Environment is not made available with the Trial Version.

When your trial period ends, your ShadowProtect Trial Version will cease to operate.  You can then purchase ShadowProtect at any time and re-activate your install, making it fully functional, without having to reinstall the software. Any existing backup image files will still be accessible.

Evaluation Version

StorageCraft also offers an Evaluation Version of ShadowProtect. The difference between the Trial Version and the Evaluation Version is that the Evaluation Version also includes the bootable StorageCraft Recovery Environment (as an .ISO file which must be burned to a CD-R).  The ShadowProtect installer is identical for both the Trial and Evaluation versions. Like the Trial Version, you can install all the applications and create backup image files of system and data volumes using the Evaluation Version. However, in addition to data volumes, you can also restore system volumes using the Evaluation Version.

Like the Trial Version, when your trial period ends your ShadowProtect Evaluation Version will also cease to operate.  You can then purchase ShadowProtect at any time and re-activate your install, making it fully functional, without having to reinstall the software.

ShadowProtect Licensing

Please review the End User License Agreement for further clarification.

 

 

7. General Usage Notes
 
Defragmentation

ShadowProtect tracks all sector changes when taking incremental backups. Since disk defrag software changes sectors, the next incremental backup may become larger than expected, especially if the disk is severely fragmented. Disable any disk defrag software if you have scheduled continuous incremental backups. If necessary, perform the defragmentation prior to taking the base full image backup then disable the defrag software. If you have a weekly or monthly backup schedule, perform the defragmentation prior to the next full backup.

Windows OS Upgrades

You will need to deactivate the ShadowProtect license and uninstall the software prior to upgrading an existing

Windows 7 to Windows 8

After the OS upgrade, reinstall ShadowProtect and reactivate the license. While it is possible to restore the previous backup job configurations and other ShadowProtect settings, a Best Practice is to create a new backup job for the upgraded system rather than continue an older, existing chain.

Windows 8 to Windows 8 Pro

This upgrade is the same as when upgrading from Windows 7 to Windows 8. Perform a fresh install of ShadowProtect and create a new backup job for the upgraded system.

Test the StorageCraft Recovery Environment

You should test the StorageCraft Recovery Environment to ensure that it runs properly on your computer.  To do this, use the RE Builder to create the StorageCraft Recovery Environment on a CD or USB key. Boot from the CD or USB key to confirm the Recovery Environment runs.

If the StorageCraft Recovery Environment boots and runs as expected, then you can perform ShadowProtect operations from the Recovery Environment:

If the StorageCraft Recovery Environment does not boot:

If the StorageCraft Recovery Environment does not run as expected, you should investigate the following issues:

Be sure to store the Recovery Environment CD or USB key in a safe place for use in the event that you require a bare metal recovery of your computer. In that event, use the CD or USB key as a boot disk for restoring a backup image to the system volume using the Recovery Environment. 

 

 

8. CDDL Source Code

ShadowProtect's VBoxHDDXSP.dll files were built in part using unmodified CDDL-licensed code.  The CDDL license itself, and all referenced CDDL-licensed source code, are available at the following links:

 

*********************************************************************

Copyright © 2014 StorageCraft Technology Corp. All rights reserved. This Software and Documentation are copyrighted.  Ownership of the ShadowProtect Server Edition Software is reserved to StorageCraft Technology Corporation.  StorageCraft, the StorageCraft logo and the ShadowProtect Server Edition logo are trademarks of StorageCraft Technology Corporation.  StorageCraft, ShadowProtect, ShadowControl, and HeadStart Restore are registered trademarks of StorageCraft Technology Corporation in the United States and elsewhere. ShadowProtect Server Edition, intelligentFTP, and ShadowStream are trademarks of StorageCraft Technology Corporation in the United States and elsewhere. All other brands and product names are or may be trademarks or registered trademarks of their respective owners.

3 File Backup and Recovery Release Notes

General Information

This ReadMe was last updated: July 26th, 2017 and contains the latest supplemental information for StorageCraft File Based Backup product and the StorageCraft File Backup and Recovery with Backup Analyzer User Guide

 

New Version Information

(Server information is listed by Product Release Date. Client information is listed by client version number and release date.)

StorageCraft File Backup and Recovery with Backup Analyzer (Server - July 26, 2017)
Fixed Issues
StorageCraft File Backup and Recovery with Backup Analyzer (Client  3.3.0 - July 7, 2017)
Enhancements
Fixed Issues
  • Corrected an issue where last backup times of files were not cleared after deleting a directory from the backup. 
  • When the storage limit has been exceeded the files in process to upload will wait and retry instead of cancelling and retrying during the next scan
StorageCraft File Backup and Recovery with Backup Analyzer (Server - July 6, 2017)
Enhancements
StorageCraft File Backup and Recovery with Backup Analyzer (Client  3.1.1 - May 30, 2017)
Enhancements
Fixed Issues
  • Corrected an issue where several items in the status viewer were not displaying properly in non-English locales.
  • Fixed an issue that caused uploads to hang in the unlikely event that the service was shutdown during audit file pre-processing.
  • Fixed an issue in the client where files with modified dates in the future at time of backup were incorrectly flagged as backup problems.
StorageCraft File Backup and Recovery with Backup Analyzer (May 11, 2017)
Enhancements
Fixed Issues
  • Fixed an issue related to editing the scan and audit schedules for standard configurations.
  • Fixed an issue where files with modified dates in the future when the backup occurred were incorrectly flagged as backup problems. You need to use client version 3.1.1 or above for this fix to take effect.
  • Adjusted the default Backup Scan Time from 6:00 PM local time to 6:05 PM. This prevents conflicts with other software performing snapshots at the top of the hour.

StorageCraft File Backup and Recovery with Backup Analyzer (April 18, 2017)

Enhancements
Fixed Issues
  • Fixed an issue with transient .delta files not being deleted after manually cancelling a backup. This was preventing additional file backups.
  • Fixed an issue that caused ArchiveService.exe to fault when the configuration file size was exactly on a 4K boundary.
  • Fixed a rare issue that prevented the audit generation from closing a directory tag if the system user could not read directory attributes.
  • Fixed an issue that prevented backing up files with long paths. 
  • Fixed an issue that prevented local restores from working. 
Update addendum (February 22, 2017):

The Windows Explorer integrations for File Backup and Recovery won’t work on Windows 7 or Server 2008 R2 if the operating systems are not up to date. The Update for Universal C Runtime in Windows article describes how to correct the issue if you run into this problem.

 
StorageCraft File Backup and Recovery with Backup Analyzer (February 13, 2017)
Enhancements
Fixed Issues
StorageCraft File Backup and Recovery with Backup Analyzer (November 8, 2016)

Enhancements

Fixed Issues

StorageCraft File Backup and Recovery with Backup Analyzer (November 3, 2016)

Known Issues

Fixed Issues

 
StorageCraft File Backup and Recovery with Backup Analyzer (October 4, 2016) 

Known Issues

4 ImageManager Release Notes

General Information

These Release Notes contain information that supplements the ImageManager User Guide.  Please read all the sections before you install ImageManager.

 

StorageCraft ImageManager 7.5.0

Last Updated: June 1, 2017

Download ImageManager from the Updates/Downloads page. 

 

Table of Contents
Update Information by Product Version
ImageManager v7.5.0
 
ImageManager v7.1.0
 
 
ImageManager v7.0.5
 
 
ImageManager v6.7.7
 
ImageManager v6.7.6
 
ImageManager v6.7.4
 
ImageManager v6.7.2
 
Additional Older ImageManager ReadMe information.
  

System Requirements (applicable for the current version)

Installation Tips (for all versions)

Licensing (applicable for the current version)

 
Update Information by Product Version
ImageManager 7.5.0 (May 2017) 
Enhancements
  • Added replication target for AWS. Use your existing (or create a new) IAM (AWS) user account and set an S3 bucket.
  • The Legacy ShadowStream client has been removed from the ImageManager installer and user interface. ShadowStreams jobs don't show up anywhere in the ImageManager 7.5 user interface. The jobs are still running in the background but don't show up in the user interface. If you need to use the legacy ShadowStream client you need to stay on ImageManager 7.1.
    Warning: Do NOT update to ImageManager 7.5 if you are running (and need to continue running) legacy ShadowStream jobs.  If you update to ImageManager 7.5, all legacy ShadowStream jobs will be disabled and will not appear in the ImageManager 7.5 user interface. You will need to downgrade to ImageManager 7.1.0 to see the legacy jobs. 

    The best practice is to create a new ShadowStream job with ShadowStream version 6.

Fixed Issues
  • HSR on ESXi 6.0 U3 and ESXi 6.5 are now available.
  • Fixed an issue with ShadowStream error list timout exceeded. 
Known Issues
 
 
ImageManager 7.1.0 (December 2016) 
Enhancements
  • Added functionality to perform Advanced Verification on Microsoft Hyper-V. ImageManager must be installed on Microsoft Server 2012 R2 and the Hyper-V role must also be enabled. The StorageCraft VirtualBoot Hyper-V Plugin must also be installed.
  • Updated the VirtualBoot hypervisor plugin for VirtualBox Advanced Verification to support newer versions of Oracle VirtualBox. See Known Issues below and the Supported Hypervisors for Advanced Verification in the ImageManager user guide for additional information.
Fixed Issues
  • Fixed an issue where in some rare cases FTP replication threads were locking up if no response was received from the remote server. This caused the replication threads to get stuck in a waiting state and eventually used up the available replication threads.
  • Fixed an issue where verification error notifications were being sent during verification operations. This was caused by network latency or I/O issues. StorageCraft adjusted the retry for the verification attempt to prevent this problem. Notifications are now sent only if verification errors are encountered in managed folders where replication jobs are configured.
  • Fixed an issue so ImageManager would stop managing system folders (Recycle Bin and System Volume Information) that were auto-managed in previous versions of ImageManager.
Known Issues
  • When attempting to create a virtual machine through the HSR ESX browser on vCenter 6, the following error may be displayed, "The input argument had entities that did not belong to the same datacenter." This is caused by having multiple Datacenter objects in the ESX inventory. Users need to manually create the target virtual machine through the vSphere Web Client or VMware vSphere Client and then select the VM during the ImageManager HSR creation.
  • Advanced Verification on Microsoft Windows Server 2016 has limited support for Oracle VirtualBox. StorageCraft recommends that users install Oracle VirtualBox version 5.0.30, or version 5.1.8 and up on Server 2016. 
  • Advanced Verification on Server 2016 with Hyper-V is not currently supported.

ImageManager 7.0.6 (November 2016) 

Fixed Issues
  • Fixed an issue where restarting the ImageManager service caused an HSR error when attempting to create the next incremental. This issue only affected HSR jobs created in ImageManager 7.0.5. The fastest way to correct this issue is to use ImageManager 7.0.6 to re-create any HSR jobs that were created while using ImageManager 7.0.5.
  • Non-critical database errors are no longer added to the managed folder logs. Database execution errors for the managed folder now show up in the respective managed folder logs
  • Fixed an issue where in rare cases ImageManager retention was deleting weekly collapsed files when retention settings were set to 1 for all image types.
  • Fixed an issue where in some cases ImageManager was not correctly reporting verification errors. Files that had successfully been verified, but failed subsequent re-verification now are correctly reported in the user interface.
 
ImageManager 7.0.5 (October 2016) 
 
Enhancements

 

Fixed Issues
 Known Issues
  • Advanced Verify is not currently supported on Server 2016.
  • In some cases, the Advanced Verification process may leave behind the files created during the virtual boot process.
  • In some cases, an error box “Cannot access a disposed object, Object Name:’xxxx’ ” may pop up when expanding folders or accessing folder properties. Acknowledging this error allows normal operation to continue.

ImageManager 7.0.4 (August 2016) 
 
Enhancements
  • The ImageManager UI will now show an hourglass badge on the parent folder if any child folders have running tasks.
  • Users can now unmanage a backup store folder, which will also unmanage all subfolders along with it. Unmanaging folders will remove all verification data, and all Replication and HeadStart jobs for those folders. Unmanaging and re-managing the same folder is a time consuming operation because ImageManager must re-verify all image files and you must re-create all Replication and HeadStart Jobs. This should only be use as a last resort for troubleshooting.
  • Users can now right-click on a managed folder and Run Processing from the drop-down menu.
  • Image.exe is now included as part of the ImageManager installation.  This file and its dependency can be located in the ImageManager install folder.
  • The Password Reset Utility now requires two files:ImageManager.ResetPassword.exe and ImageManager.ResetPassword.exe.config. These files can be downloaded as a .zip folder. Once downloaded, both files must be extracted. Previously only one file was required. Previously downloaded versions of the Password Reset Utility are not compatible with ImageManager 7.0.4 and later. The new Password Reset Utility must be used.
Fixed Issues
  • Fixed an issue where installing a non-American English version of ImageManager onto a Windows machine without .NET 3.5 installed would prompt the user to install it before continuing. This includes both Server 2012 R2 and Windows 10.  Also fixed an issue where an "Infragistics" error would occur on non-American English OS when .NET 3.5 was not installed.
  • Fixed an issue where ImageManager would delete critical files when managing a chain containing old image files.
  • Fixed an issue where the progress bar in the ImageManager UI was not correctly displaying during HSR jobs and the details pane of the HSR jobs was also not correctly updating the progress status.
  • Fixed an issue where the warning badge was not displayed on the parent folder when sub-folders contained a warning badge.
  • Fixed an issue where the UI will no longer automatically scroll to view the latest current action ImageManager is taking.
  • Fixed an issue where the "Override performance..." setting in the child folder would not stay configured and would be "lost" after re-opening the child folder properties window.
  • Fixed an issue where the UI would not auto-refresh when folders no longer met the view filter requirements and would still display the folders.
  • Fixed an issue where the UI no longer reports Consolidating 0% for newly managed folders.
  • Fixed an issue where the UI was not correctly displaying the file name during Verification and Consolidation tasks.
  • Fixed an issue where FTP and HSR jobs will no longer be disabled if IM is licensed with an expired serial key.  ShadowStream jobs will continue to be disabled if the IM license assigned is expired.
  • Fixed an issue to remove outdated Cloud replication information from the UI.
  • Fixed an issue where the image password was overwritten when managed folder properties were modified.
  • Fixed an issue where some ImageManager Event IDs changed in the release of 7.0.2. These Event IDs have been changed back to their original values in 7.0.4
  • Fixed an issue where in some cases the Advanced Verification virtual boot would fail to load the OS with a 0x00000100 error.
 Known Issues
  • In some cases, the Advanced Verification process may leave behind the files created during the virtual boot process.  This can cause an issue where retention will fail to run due to the error “Chain contains migration files”.  This can be resolved by deleting the <ImageName >_VirtualBoot_VM_{GUID} incremental files from the managed folder that were created during the Advanced Verify process.
ImageManager 7.0.2 (April 2016) 
 
Enhancements
  • Full UI rewrite to provide better visibility into managed folders.
  • Added advanced image verification using VirtualBoot to automatically boot specified consolidated image files and provide an email with an attached screenshot to verify the image was booted successfully.
  • Added the ability to configure a managed folder as a Backup Store. Subfolders will be managed automatically and will inherit the settings of the parent Backup Store. Parent settings can be overridden at the subfolder level.
  • Folders can be expanded to display all of their associated activities, jobs, and progress.
  • Folders can be filtered based on predefined characteristics. (All Folders, Failing FoldersSyncing FoldersOffline FoldersFolders with Running TasksFolders with JobsFolders with Replication Jobs, Folders with HeadStart Restore Jobs, Folders without Jobs)
  • iFTP replication, Network Replication, and HeadStart Restore are no longer licensed jobs. These are now considered baseline features. ShadowStream Replication is now the only job type requiring licensing in ImageManager. 
  • Added support for vSphere and ESXi 6.0 Update 1.
Fixed Issues
  • Fixed an issue where Non-American English installs error out in Server 2012 R@ and Windows 10 if .NET 3.5 is not installed. Installing a non-American English version of ImageManager onto a Windows machine running Server 2012 R2 or Windows 10 without .NET 3.5 installed will not prompt the user to install it before continuing.
  • Fixed an issue where replication breaks in ImageManager when a system being backup up with ShadowProtect has its name changed. Changing the computer name for the machine being backed up by ShadowProtect no longer stops the chain from being replicated by ImageManager.
  • Fixed an issue for Non-English versions of the product where clicking on an empty auto-managed folder reports an initial error.
 Known Issues
  • ImageManager 7.0.2 supports VirtualBox versions up to 5.0.16 for Advanced Verification with VirtualBoot. However, ShadowProtect 6.1.0 and earlier only support VirtualBox versions up to 5.0.10. When using ImageManager 7.0.2 and ShadowProtect SPX 6.1.0 or earlier on the same machine,use a version of VirtualBox that is supported for both products.
  • In some situations the Backup Store folder details panel shows all zeros if the Backup Store folder is the first selected folder when IM starts.
  • When installing as a local user without administrator rights, ImageManager does not automatically reboot. The user must manually reboot to resolve the issue. See the warning under Installation Tips for more information.
  • An HSR may display a red hourglass indicating failure even when a file is currently being sent with no problems. This indicates there was an issue in the past, but ImageManager is retrying the file. If successful, the red hourglass will go away. If the retry fails, the job will return to a failed state (red exclamation point).
 
ImageManager 6.7.7 (November 2015) 
 
Enhancements
Fixed Issues
  • Fixed an issue where the base file was being queued to the StorageCraft Cloud even when it had already been sent. The base file is no longer being queued for StorageCraft Cloud replication if the base file was previously sent
  • Fixed an issue where ImageManager retention was not able to query large incremental chains. ImageManager can now remove several thousand incremental files. It is reasonable to expect the synchronization to take a long time if you have many files. 
  • Fixed an issue where in some rare cases ImageManager was unable to replicate critical files in a chain on a new replication job. This now works correctly.
  • Fixed an issue where in some rare cases ImageManager was not recognizing the Image Password property for cloud replication targets. The password properties are now being recognized.
  • Fixed an issue where ImageManager wasn't preserving the non-default install locations when an upgrade was installed. This prevented ImageManager from launching correctly. With this fix, ImageManager now launches successfully. 
  • Fixed an issue that occurred when saving retention settings. Now, if you attempt to set any retention values lower than the intra-daily setting, ImageManager automatically sets them equal to the intra-daily value.
  • Fixed an issue where the retention of consolidated daily files occasionally left orphaned files. Retention should remove the set of files used to create a collapse file.  Consolidated daily files were being removed (one at a time) which was making the remaining files in the file-set unusable. This is now fixed.
  • Fixed a rare error “not connected to sent file" that happened during replication. ImageManager now determines which files must be sent in addition to the disconnected incremental file.
  • Fixed an issue where patent information wasn't being displayed on the "About" page in the product. Patent information is now displayed correctly.
 Known Issues

  • If you upgrade from ImageManager version 6.5.1 to any newer version you need to do a repair install. In some cases when trying to install ImageManager 6.7.6 the service fails to start. It displays error 1067 "Process unexpectedly terminated". You can resolve this problem (in most cases) by doing a repair installation. In some cases, you may need to uninstall ImageManager and then do a fresh installation.
  • ImageManager will not run if the FIPS security mode is enabled. It is possible to configure Windows .Net so that only FIPS compliant encryption algorithms are used for .Net applications. This is also something that you can configure in Group Policies using: 

GPO_name\Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options. 

This setting may prevent ImageManager from running. However, you can avoid this problem with a simple change to the ImageManager configuration file.

To prevent this error, you can make the following change to the ImageManager.exe.config file:
Search for the <runtime> tag which currently has:

<runtime>
<generatePublisherEvidence enabled="false"/>
</runtime>

and after the generatePublisherEvidence entry add the following:

<enforceFIPSPolicy enabled="false"/>

Save the file and then restart the service. Restarting the service causes the setting to take effect.

  • In some situations, it may appear that an ImageManager Replication Job is re-sending files that it has already sent successfully. This happens after restarting the ImageManager service. In this case some replication jobs re-queue the files in the managed folder and attempts to resend them. This is not a bug but it can occur in two situations: (1) When the replication job is deleted and recreated it causes ImageManager to lose history of what has been sent so it resends files that have been deleted on the target. (2) Changing the replication mode to "No ImageManager running remotely."
  • When replicating files via FTP, it is possible to receive the following error: "unable to set file time: Command not understood. (code=500)" This is a known limitation of some FTP Servers, including the IIS FTP server. 


ImageManager 6.7.6 (September 2015) 

 Enhancements
  • The mount driver now includes increased default cache size for use on Windows 64-bit OSs. This should help increase the mount speed on 64-bit OSs. It is also possible to increase the cache size using a registry setting, followed by a reboot.
Registry Settings

HKLM\System\CurrentControlSet\Services\sbmount\Parameters

 

REG_DWORD ChunkCacheMaxSizeInMegabytes
On 64-bit platforms we recommend trying 256.
REG_DWORD ChunkHeaderCacheMaxSizeInMegabytes
On both 32 and 64-bit platforms we recommend you set this to 1
 
Fixed Issues
  • Fixed an issue so that only the most recent chain is processed if there are multiple chains with the same WindowsVolumeGuid. (i.e. ImageManager no longer sends obsolete chains to the cloud).
  • Fixed an issue where chains weren't continued correctly if the user restarted ImageManager after it finished seeding (but before any files were sent directly to the cloud). This release makes sure the chains continue correctly after we have seeded, but haven't uploaded anything directly.
  • Fixed an issue where small network interruptions (5 seconds or less) were sending error messages. A silent retry has been added to cloud replication so that an error message won't be displayed if the interruption is less than 5 seconds.
  • Fixed some issues to improve the functionality of HSR and prevent rare virtual disk corruption. These fixes don't undo any existing HSR virtual disk corruption. If your job stops and an error is displayed it might be because of a problem that may have occurred weeks previously. If this happens you'll need to delete the HSR job and start again.
  • Fixed an issue where on rare occasions there was a long delay between the ShadowStream client and server, over 30 minutes, when attempting to start sending a file. When this happened ImageManager issued a force stop send command after 15 minutes. When the response finally came through from the server indicating it was ready to receive the file the client tried to transfer the file that was aborted and a crash ensued. This is now fixed.
  • Fixed an issue where creating Replication jobs using the REST API would not work for job types requiring ReplicationTargetProperty fields.
  • Fixed an issue where in some rare situations, a Head Start Restore (HSR) job may fail with the following error: "-112 there is not enough space on the disk" This is now fixed.
  • Fixed an issue where ImageManager wasn't syncing files between drives when swapping external target replication drives, ImageManager now correctly syncs files between the drives.
  • Fixed an issue where problems with replicating from ImageManager may result in a broken chain where the user also deleted and recreated the job.
  • Fixed an issue where in some rare situations, it was possible that a verify operation would not complete (because of a network error) and the file was not automatically queued to be re-verified until after restarting the service. This now works correctly. 
  • Fixed an issue where users were unable to connect to their FTP server after upgrading to ImageManager 6.7.4. The issue was caused by a synchronization error and not being able to connect to the destination. This is fixed in ImageManager 6.7.6.
  

ImageManager 6.7.4 (July 2015) 
 
Fixed Issues
  • HSR: Disk Geometry and Alignment: The Virtual Disks (VHD, VHDX, VMDK) generated using ImageManager Head Start Restore (HSR) are now optimized to provide improved read/write performance.

  • Fixed an issue where the daily collapse process was starting but then didn't create a collapse file. Under rare circumstances, ImageManager failed to collapse files within a backup chain. This may have occurred in situations where ImageManager was collapsing files without any problems for a period of time. The issue appeared to have occurred more frequently when the backup chain was on a SMB/CIFS share. This is fixed in this release.

    Note: We have also seen similar issues when Linux-based NAS devices have hosted the SMB/CIFS share and where the NAS has been joined to an Active Directory Domain. The particular cause of this error is the result of permission problems on the shared folder.
  • Fixed an issue where HSR Jobs stop after upgrade: In some rare situations, an upgrade of ImageManager may cause an existing HSR Job to stop if it was writing a VMDK file to a VMWare ESXi host Datastore. You may have seen a pop-up error message that said: "Target not found [datastore1]". You can see evidence of the problem in the ImageManager install log file: 

    RegRemoveValue(Name=VirtualFile,Value=[datastore1] ExSvr1 6-29/C.vmdk,)
    Executing op: RegAddValue(Name=VirtualFile,Value= ExSvr1 6-29/C.vmdk,)

    This happened because the HSR path to the VMDK file was getting changed in the registry and the "[datastore1]" component of the path was removed. Users were able to edit the registry key and add the missing part of the HSR path back in as a short term work-aroundThe underlying problem is fixed in this release.

  • Fixed an issue where the Managed Folder state was incorrectly shown as Green (OK) in the user interface even when verification failed. Under rare situations, the ImageManager user interface was showing a managed folder in a GOOD state (green) in the top of the user interface and was showing a BAD state (red) in the lower part of the user interface. This occurred when a file verification failed. This has been fixed in this release.

  • Fixed an issue where ShadowStream replication was stuck on Ready. In a rare situation, a replication job may have been stuck in a ready state. This would occur in the following scenario: (1) ImageManager was running at both the local/client side and the remote side. (2) The remote ImageManager deleted some -CM files as part of retention. (3) The local ImageManager had not yet removed the original -CM files as part of retention. (4) The local ImageManager service was restarted. After restarting the service the -CM files were queued to send again. This is fixed in this release.

  • Fixed an issue where iFTP was writing files to the root directory after losing connection: Under rare conditions, an iFTP Replication job may have written files to the root folder on the destination FTP server rather than in the sub-folder specified in the replication job. This problem was more likely to occur if the network connection had been lost.

  • Fixed an issue where stopping/restarting the IM service caused the 1053 error (service did not respond to the stop request) to be received. In some rare situations, the ImageManager service would hang or not respond to a restart when it was performing a Consolidation operation. When stopping the IM service, the service stop request failed with error 1053 (the service did not respond to the start or control request in a timely fashion). After the service was restarted, users were unable to connect to the ImageManager console unless the machine was rebooted. The ImageManager logs showed the following message when attempting to connect: "ImageManager.ThreadProc exception: Only one usage of each socket address (protocol/network address/port) is normally permitted." This issue has been fixed in this release. 

    Note: It is also possible to see the 1053 Error temporarily in one other scenario where an attempt is made to Resume a ShadowStream Replication Job that is in a failed state, and then an attempt is made to stop or restart the ImageManger service. If this happens just wait 60 seconds and the service will restart without issues.
  • Fixed an issue where ShadowStream replication was hanging after send failures and would not retry unless the IM service was restarted. In some rare situations, a new ShadowStream Replication Job might hang after send failures. Replication would not continue until the ImageManager service was restarted. This issue has been fixed.

  • Fixed an issue where an HSR to VMDK failed because the destination volume was too small. ESXi HSR jobs where the source volume was resized no longer require a full re-managing of the backup folder. You now only need to delete the HSR job and re-create it to a new disk of the appropriate size.

  • Fixed an issue where ShadowStream replication failed with error "unable to delete .tmp file". In some rare situations, ImageManager may have reported the following error in regard to a ShadowStream Replication Job: “unable to delete .tmp file”. This is fixed in this release.

  • Fixed an issue where the HSR commit file process was failing with error -1326 (bad username or password). In some HSR jobs, replicating to Server 2012 R2 shares failed with authentication errors. This is fixed in this release.

  • Fixed an issue where the bad.log file was not being created when the ReadHeader error was detected outside of normal verification procedures. ImageManager now creates a bad.log file, even when the ReadHeader error is detected outside of normal verification procedures.

  • Fixed an issue where files being sent by ShadowStream show up corrupted on the receiving side. In some rare situations where there was a large number of corrupt packets on a network connection, there was a chance that ShadowStream could write a corrupt file. This is fixed in this release.

  • Fixed an issue where an erroneous error message was logged on failure: "Log open exception". Under some rare circumstances, the following error message was logged in the ImageManager log file(s): "Log open exception". This could have occured where there was a failure with an operation such as replication. The message did not affect the running services and was benign. This release fixes the issue and the error is no longer generateed in the logs.

  • Fixed an issue where changing the backup password in a local HSR job failed. The process could fail when attempting to correct a wrong backup password in an HSR job to a local drive if the backup had two volumes or more. This was not an issue when writing to an ESXi server. This issue is fixed in this release.

  • Fixed an issue where if detailed logging was turned on, there was a chance the password associated with validating an HSR commit file would be included in the log. The password is now obscured in the log file if the user enables detailed logging.

 Known Issues
  • Upgrades from early versions of ImageManager may require Repair install after reboot. If you upgrade from ImageManager version 6.5.1 or earlier you may need to run a Repair install if the service does not start after the reboot.

  • In some rare situations the ImageManager Service may crash when used for ShadowStream Replication. Fixes have been made that will make this much less likely to occur.

  • In some very rare situations the ShadowStream Service may crash. Normally the service can be restarted and replication will continue. If this occurs, you should contact StorageCraft and we will investigate. If you have a memory dump for the crashed service you can provide it to StorageCraft support.

    Upgrades from earlier versions of ImageManager
    If you upgrade from an earlier version of ImageManager (6.5.1 or earlier) you may need to run a Repair install if the service does not start after the reboot.

    ShadowStream Replication fails: SST-Error(10): Connection Lost:
    In some rare situations, an ImageManager ShadowStream Replication Job may fail with the following error message:

    "ShadowStream Send Failure - SST-Error(10): Connection Lost"
    and
    "send error: Connection Lost"

    ShadowStream has been updated to improve the way it handles these kinds of failure conditions. It is worth noting that these kinds of failures can be caused by a firewall that is blocking the UDP traffic used by ShadowStream.

  • HSR to VHDX fails with -87 Parameter is incorrect. If you perform an HSR of a volume that is close to the maximum size of an MBR disk (i.e, 2TB) you would encounter the following error: sbrest 411 Cannot create partition on virtual disk D:\F_VOL_SYS-b001.vhdx (-87 The parameter is incorrect.) and the HSR Job would fail.

    This error occurs because StorageCraft requires a very small amount of space on the volume HSR related meta data. This would result in a volume larger than the 2TB size limit (232 × 512 bytes) being associated with the default MBR partitioning style which is used by HSR when writing virtual disks.

    To prevent this error, you can shrink the Source volume by a few MBs. In a future release, the StorageCraft HSR will detect if the Source volume is close to the 2TB limit (within a few MB) and use the GPT partitioning style within the VHDX file, rather than MBR.

  • "Unknown error occurred": Incorrect Wizard behavior when trying to uninstall. In some rare situations, you may encounter an "Unknown Error" when installing or upgrading ImageManager. This happens in the following situations: 
    1) An install on a server OS that only had .Net 4.0/4.5 installed. One of the components in the installer is not configured to run on these versions of .Net and so an error was generated. The error occurs at the end of the install wizard but is benign. ImageManager still installs just fine. 

    2) During a "Repair" install where the machine is not restarted afterwards. If you then run the installer again, the install wizard will pop up a prompt to install, but the text is missing from the installation path field. After running the installation, the wizard shows "Unknown error occurred" 

    To avoid this error, you must restart your computer after running a Repair install.

  • ImageManager will not run if the FIPS security mode is enabled. It is possible to configure Windows .Net so that only FIPS compliant encryption algorithms are used for .Net applications. This is also something that you can configure in Group Policies using: 

    GPO_name\Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options.

    This setting may prevent ImageManager from running. However, you can avoid this problem with a simple change to the ImageManager configuration file.

    To prevent the error above, you can make the following change to the ImageManager.exe.config file:
    Search for the <runtime> tag which currently has:

    <runtime>
    <generatePublisherEvidence enabled="false"/>
    </runtime>

    and after the generatePublisherEvidence entry add the following:

    <enforceFIPSPolicy enabled="false"/>

    Save the file and then restart the service for the setting to take effect.

  • In some situations, it may appear that an ImageManager Replication Job is re-sending files that it has already sent successfully. This happens after restarting the ImageManager service. In this case some replication jobs requeue the files in the managed folder and attempts to resend them. This is not a bug but it can occur in two situations: (1) When the replication job is deleted and recreated it causes ImageManager to lose history of what has been sent so it resends files that have been deleted on the target. (2) Changing the replication mode to "No ImageManager running remotely."

ImageManager 6.7.2 (March 2015) 
 
Enhancements
Fixed Issues
  • The ShadowStream Performance Benchmarks and Best Practices white paper has been updated to include more details about firewall configurations that may cause problems with UDP traffic used by the new ShadowStream product.
  • The ImageManager user guide retention settings information has been updated to clarify when files get deleted by the retention mechanism.
  • ImageManager and the new StorageCraft cloud now allow you to replicate a backup chain after resizing the volume.
  • Fixed the hidden .remote file issue where the new ShadowStream replication option failed to send files if the final destination folder was hosted on a Linux NAS device.
  • Fixed an issue that required restarting the ImageManager service if (in rare situations) it crashed when performing an HSR to VMDK. This was more likely to occur when writing to VMware ESXi Datastore.
  • Fixed an issue where in rare situations ImageManager Silent Install was failing.
  • Fixed an issue where in some situations ImageManager was temporarily unable to access an MD5 file which sometimes caused a verification to fail initially. However, a subsequent verify would run automatically when the MD5 file was available then the verify would succeed. These recoverable errors are no longer listed in the user interface as an error or warning. ImageManager reports only non-recoverable verify problems. 
  • Fixed an issue where in some rare conditions an existing Legacy ShadowStream Replication failed with the error message "not connected to remote file" after being upgraded. This is no longer a problem in the 6.7.2 release.
  • This release includes improvements for localized Polish strings in the client user interface which allow you to provide a password for encrypted backup files. The setting is available per agent or per managed folder.
  • Fixed an issue where in some rare situations files failed to replicate to the StorageCraft Cloud because they were temporarily not found. 
  • 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.
  • Fixed an issue where in some rare situations an ImageManager HSR Job appeared to randomly stop restoring, without throwing errors or giving any indication of a problem. This happened regardless of whether the HSR target was a VHD/VHDX or VMDK file. ImageManager now includes improved error handling to make this much less likely to occur. 
  • Fixed an issue where increasing the size of a source volume in an HSR Job caused the HSR Job to fail. The error message was along the lines of: "Too small destination volume:" In the past, the only way to work around this was to create a new chain with a new Full backup file and also create a new HSR Job. In this new release it is no longer necessary to create a new backup chain and new Base image. Instead, you only need to delete the existing HSR Job and then re-create it. This is still not a perfect solution but it does bypass the need to create a new backup chain. This is important for Continuous Incremental backups where a new Base is often not wanted. This fix only applies to HSR jobs that write to a local or network folder. A future update will support HSR jobs directed to a VMWare ESXi/vSphere Datastore. 
  • ImageManager now supports switching Replication Modes (intra-dailies vs daily collapses) when replicating to the new StorageCraft Cloud. This options is not supported if you are replicating to the Legacy StorageCraft Cloud.
  • ImageManager replication to the new StorageCraft Cloud is now enhanced and more robust than replication to the legacy StorageCraft cloud.
  • When an HSR Job is deleted, ImageManager now removes any redundant .hsr files from the ImageManager Log folder.
 Known Issues

  • ESXi Does not have the correct license to support HSR.
  • In some isolated situations ImageManager FTP replication jobs are not written to the targeted destination folder. Instead, the replicated files are written to the root folder of the FTP Server. This is more likely to occur if the network connection is temporarily dropped. StorageCraft plans on fixing this in a future release.
  • ImageManager HSR to VMware vCenter may fail with an "Access Denied" error when it starts processing the HSR Job. This can be caused when VMware vCenter has host machines defined using FQDNs rather than using IP addresses and where the network DNS is not working, or is incorrectly configured. This might occur when a user spins up a new network without their domain controller, and temporarily uses a public DNS option (such as 8.8.8.8). ImageManager tries to get the target VMware host information from vCenter and then tries to write to the matching Datastore. However, the FQDN received from vCenter does not resolve in the local network. ImageManager then fails with an Access Denied error.
  • HSR direct to vCenter: -31 Device error (MSVC90 Missing). This can occur in some rare situations if you don't have the Microsoft Visual C++ 2008 Redistributable Package installed on your machine. In this case, there should be a matching error in the Windows Application Event logs. In the unlikely event this problem still exists, you can manually download and install the latest Microsoft C++ runtime files from the Microsoft website.
  • HSR to VHDX always results in the use of GPT partitioning style for the volume contained within the VHDX. Keep in mind that some earlier versions of Windows will not boot off a GPT volume and other versions do not support data volumes on a GPT disk.
  • New ShadowStream Replication jobs may fail with the error message "Progress is no longer being reported, asking the send to stop" if you enabled UDP Flood Control (or similar) in your firewall. To fix this condition you need to configure your firewall to allow the new ShadowStream UDP traffic to pass through so that the total number of UDP packets sent or received by ShadowStream is not restricted. The ShadowStream Performance Benchmarks and Best Practices white paper provides more information.
  • StorageCraft recommends that you have a local "My Documents" folder on the machine where you are installing ImageManager. If you see "Unknown error encountered" during installation check to see if the My Documents folder exists. This could happen if a machine is configured so the "My Documents" folder is mapped to a network drive. In this case ImageManager may not be able to access the My Documents folder which could cause the failure. This is especially true if a silent install runs on an account where Windows prevents network access.
  • In rare situations, an ImageManager HSR Job may fail with a generic "FFFFFFFF" error. An example error message is shown below:

    12-Feb-2015 14:43:11 send error: HSR init - invalid or missing commit file : FFFFFFFF

    This can occur when you have more than one HSR Job to the ESXi Datastores and each job has the same values for [datastore name][virtual machine name][disk name]. For example, if you have multiple Datastores with the default name of "Datastore1", VM name of "Win2012" and disk name of "C:", the resulting .HSR commit files stored in the ImageManager Log folder will be identical. This will lead to failures of each job to access the same commit file.

  • In some scenarios you may encounter an error pop-up message when you try to log into ImageManager. The error message includes the text: “The property 'AgentConnections' could not be created”. To work around this problem:  1. Login to ImageManager using a different user name, 2. Logout. 3. Log back in with the user name that originally failed. This will be fixed in a future release.
  • StorageCraft best practices recommends that you don’t replicate from ImageManager over a VPN connection.  StorageCraft recommends that you use iFTP or ShadowStream instead.
  • If you install ShadowProtect 5.0.4 or 5.2.3 after ImageManager v6.5 or newer is installed on the same system, the ImageManager Startup menu icons and links may disappear. Run an ImageManager Installation Repair to restore the menu icons and links.
 
System Requirements

See System Requirements in the ImageManager User Guide

Note: ImageManager runs on many Windows operating systems but StorageCraft recommends using a Windows Server operating system such as Windows Server 2008 R2 or Windows Server 2012. ImageManager 6 does not work on Windows 2000.

 

Installation Tips
Warning: Run the installation as a Windows administrator to prevent losing settings from previous installations. Right click on the ImageManagerSetup.exe file then select Run as administrator.
  • ImageManager 6.5.0 new installation does not install any ShadowStream components.
  • ImageManager 6.5.0 uninstall removes all ImageManager components but doesn't uninstall the ShadowStream server or client if the ShadowStream Server is installed on the same machine.
  • ImageManager 6.5.0 uninstall removes all ImageManager components and the ShadowStream client if the ShadowStream server is not installed on the same machine.
  • ImageManager 6.5.0 upgrade doesn't remove ShadowStream client or server. However, the ShadowStream client will automatically be downgraded to version 5.x.
  • ImageManager 6.5.0 repair install replaces any missing files but won't install or remove any ShadowStream components.
  • StorageCraft recommends rebooting the computer after installing ImageManager to ensure that all drivers load properly.
  • ImageManager 6.0.1 supports upgrades from previously installed versions 4.0.1 and higher without uninstalling the existing version first. If you are installing 5.0.5 on systems with a version 4.0.0 or older, you will need to manually uninstall the older version prior to installing 6.0.1.
  • ImageManager 5.0.5 supports upgrades from previously installed versions 4.0.1 and higher without uninstalling the existing version first. If you are installing 5.0.5 on systems with a version 4.0.0 or older, you will need to manually uninstall the older version prior to installing 5.0.5.
  • When upgrading to 5.0.5, your existing jobs and settings will be preserved no matter which version of ImageManager you upgrade. To ensure all settings correctly migrate, close the ImageManager console prior to upgrading to ImageManager 5.0.5.
  • If you have active maintenance on your existing install, you can use your existing product key to activate 5.0.5 premium features after upgrading. If you do not have active maintenance with your product, then you will need to contact your reseller and purchase a 5.0.5 product key.
  • The upgrade to 5.0.5 will only work on the machine where a previous ImageManager install was first licensed. This applies only to the first 5.0.5 activation.
  • ImageManager 4.x does not allow license deactivation. Because of this, you must install 5.0.5 on the same system where you first installed and activated ImageManager 4.x. You can then install and activate 5.0.5 on a second system before uninstalling ImageManager on the first system.
  • ImageManagerSetup.exe only installs the ShadowStream Admin Console. To install the ShadowStream Server, you will need to run ShadowStreamSetup.exe. This will allow you to choose to install the server component or to do a full install.

 

Licensing

Previous versions of ImageManager required licensing for

o    Network Replication

o    iFTP Replication

o    ShadowStream Replication

o    HeadStart Restore

Beginning with version 7.0.2, Network Replication, iFTP Replication, and HeadStart Restore are included as free, unlicensed features. ShadowStream still requires a license. For more information, see the Activate ShadowStream page of the ImageManager User Guide.

 

 

 

 

Copyright (c) 2017 StorageCraft Technology Corp. All rights reserved.This Software and Documentation are copyrighted.  Ownership of the StorageCraft ImageManager Software is reserved to StorageCraft Technology Corporation.  StorageCraft, the StorageCraft logo and the StorageCraft ImageManager logo are trademarks of StorageCraft Technology Corporation.  StorageCraft ImageManager is a trademark of StorageCraft Technology Corporation in the United States and elsewhere. All other brands and product names are or may be trademarks or registered trademarks of their respective owners.

 

4.1 ReadMe for ImageManager versions 6.0.1 through 6.6.0

Table of Contents
ImageManager v6.6.0
Enhancements
Fixed issues
Known Issues
 
ImageManager v6.5.4
Enhancements
Fixed issues
Known Issues
 
ImageManager v6.5.3
Enhancements
Fixed issues
Known Issues
 
ImageManager v6.5.1
Enhancements
Fixed issues
Known Issues
 
ImageManager v6.5.0
Enhancements
Fixed issues
Known Issues
 
ImageManager 6.0.1 (April 2013) and Older
Enhancements
Fixed Issues
Known Issues
 
 
ImageManager 6.6.0 (December 2014) 
 
Enhancements
  •  Verbose logging switches added: ImageManager has a registry setting to enable verbose logging. You can set this level between 1-4 or 6. The values 1 through 4 simply increase the amount of detail written to the logs. Level 6 includes more logging information from the new ShadowStream.
  • ImageManager now includes additional error messages that notify the user when an HSR Job encounters a problem updating the related VM file (VMDK, VHD, VHDX). 
     
    Stop the errors by:
    • Stopping the HSR Job
    • Collecting the related log files
    • Submitting the log files to StorageCraft support

     
    Support will review the log files. If the VM file has encountered a critical update issue you will need to recreate the HSR Job. 

    Note: Additional code was added in this release to help mitigate the chance of this error occurring.
  • ImageManager now supports both legacy ShadowStream and the new ShadowStream options. 
  • ImageManager now includes improved localized string support for Polish and other languages.
  • ImageManager now shows a warning pop-up message if you try to access or test an HSR ESXi location running ESXi 4.1 Update 3, or earlier. These older versions of ESXi are not supported. 
  • ImageManager now uses the following terms in the logs to differentiate between legacy ShadowStream and new ShadowStream log entries: 
    • SST  - Original ShadowStream
    • SST2 - New ShadowStream
Fixed Issues
  • ShadowStream replication job logs now specify throttling numbers in bits per second (bps).
  • Fixed an issue where global throttling couldn't be disabled for FTP and ShadowStream jobs.
  • Fixed a licensing issue for the Brazilian Portuguese ImageManager. The Brazilian Portuguese key now works correctly.
  • Fixed an issue where ImageManager wouldn't delete ShadowStream jobs if the destination server was not available. 
  • Fixed ImageManager so that it can now replicate using ShadowStream from a network share.
  • Fixed the issue where in some rare cases, a replication job failed to replicate files immediately when using the new ShadowStream option. This occured if multiple ShadowStream replication jobs were created one after the other and the user selected one of the two replication options: 
    • (1) Replicate only consolidated daily image files
    • (2) Replicate only original unconsolidated intra-daily image files

     
    The error message seen by the user is: 

    • Error sending
      "Sync error: RemoteInfoFile not present after successful send"
  • Fixed the issue where in some situations if an FTP connection was temporarily dropped the newly replicated files were written to the root folder, rather than the correct sub-folder. 
  • Fixed an issue where Concurrent Processing settings were not being immediately applied.
  • Fixed ImageManager so that it no longer generates a verification exception in the Windows Event Manager when managing a large number of folders (300+).
  • Fixed the username and password functionality so that entries are no longer removed  when the Notification Settings are saved and re-opened.
  • Fixed the issue where under rare situations ImageManager might indicate that a Replication job is in a "Ready" status when files are queued for replication, but not actually being replicated. This might happen for any replication type. 
     
    This condition is more likely to be triggered in situations where the target server (or ShadowStream Service) is being restarted. ImageManager should automatically begin replicating within a maximum of 15 minutes. To troubleshoot these conditions, you can enable ImageManager DetailedLogging. 
     
    Some ImageManager logs would also include the following harmless "SyncFiles error" message when replicating files (see example below). This has also been fixed in this release.  

    Example:

    • 07-Oct-2014 12:25:24 SyncFiles error(s):
      Specified cast is not valid.
  • Fixed ImageManager so that it now includes improved support for unicode characters for ShadowStream job usernames, passwords and paths.
  • Fixed ImageManager so that the User Interface no longer hangs if a ShadowStream job is paused and restarted in rapid succession.
  • Fixed the issue where creating a new Replication Job in ImageManager could cause a .remote file to not be written to the correct shared folder on the remote server. This didn't affect Replication at all but generated an error in the logs. This issue is now fixed in this release.
  • Fixed the issue where if a user mounted a backup file as writeable and then chose the "Shrink" option when dismounting the backup file, the resulting file may not have been correctly verified by ImageManager. The file was fine but ImageManager may have incorrectly marked it as bad. The errors generated might include the following error messages: 
    • sbrest 503 Fatal I/O error on (-1392 Invalid data format.)
    • (loader) 504 Final error (-1392 Invalid data format.)

     
    Unfortunately, this could result in ShadowProtect reporting a false verification warning when it next creates a backup for that chain. The warning relates to the backup that the user manually "shrunk". 
     
    In this release ImageManager correctly identifies and verifies a backup "shrunk" by the user. This also prevents ShadowProtect from listing a verification warning for the file.

  • Fixed an issue so that users are now able to enter a value of zero (0) as a peak hour throttling entry.
  • Fixed the issue where on some Windows OS versions, ImageManager attempted to check if there was a valid .Net 3.5 framework installed. If it was missing, the installer normally showed a pop-up window to warn the user. This installer pop-up window is now localized.
  • Fixed ImageManager so it is now possible to delete an FTP Replication job without first pausing the job. Previously this caused the ImageManager user interface to hang.
  • Fixed an issue where In some rare situations the ImageManager user interface didn't report when there was a problem replicating a file.
 Known Issues
  • In some situations it is possible that ImageManager can successfully write the contents of a new incremental backup to the VMDK file but then fail to update the related .HSR file information. This can occur when another process has a lock on the .HSR file. To avoid this, make sure there is no AV product, or similar, that might lock the .HSR files.
    Note: This release includes additional error handling to limit the chance of this error occurring. If this situation occurs ImageManager displays an error in the User Interface.
  • Japanese passwords in HSR jobs aren't being accepted.
  • HSR jobs that create VHD files are unable to select all volumes in the managed folder.
  • HSR jobs to a VMDK disk on an ESXi server are failing with the error: "Missing arguments" in HSR job.
  • Some of the Polish strings are missing in this release.
  • If you create an HSR job and then later increase the size of the Source Volume the HSR Job fails. Increasing the Source Volume used for an HSR Job is not currently supported. If you increase the size of the Source Volume you need to delete the HSR Job, start a new backup chain, and then start a new HSR job with the new backup chain.
  • HSR to VCenter/ESXi returns Access Denied error when processing starts.
  • Replication fails on files that have previously been sent and won't continue until files are removed from destination.
  • An "Unknown error encountered" message is displayed if you attempt to upgrade from ImageManager version 6.5.1 to version 6.5.4 if the "My Documents" folder is missing. 

ImageManager 6.5.4 (July 2014) 
 
Enhancements
  • ImageManager now supports the option to manage encrypted backup files without an SPK file. This means that the password related SPK file is not in the same folder as the backup chain. In order to use this feature and still allow ImageManager to manage these backup chains, the user needs to configure ImageManager to use an Agent-wide and/or Managed Folder-wide password. The password needs to match the password used to encrypt the backup files. The password at the Managed Folder level takes precedence over the Agent-level password. ImageManager will then store the passwords in the normal Windows protected/encrypted data stores. 

    NOTE: In order to create an encrypted backup chain with an SPK file you need to use ShadowProtect 5.2.0 or later.

Fixed Issues
  • Changed the default cloud retention settings to preferred values. The default cloud replication retention settings are now:
    • Consolidate intra-daily recovery points older than: 3 days
    • Consolidate daily recovery points older than: 1 week
    • Delete all recovery points older than: 31 days
  • Changed the Performance option in the ImageManager Agent Settings to indicate that the limitation on Maximum Transfer Speeds is "per job".
  • Added improved localization strings for the Polish language.
  • Fixed an issue where free space wasn't being pruned in unencrypted backup files during consolidation.
  • Fixed an issue where Cloud Replication jobs weren't being shown (the related managed folder was being marked with a red exclamation mark) after upgrading ImageManager. If you see this in a previous installation please contact StorageCraft support for details on how to fix it.
  • Fixed an issue where (in some rare situations) an incorrect "Corruption Error" was being shown in the ImageManager user interface.
  • Fixed an issue where it was possible that verification or replication wouldn't continue because of a failure to extract bitmap data from a backup file. This fix allows verification and replication to continue even if there is a problem extracting the bitmap data. If ImageManager fails to extract the bitmap data, an entry gets written to the ImageManager log file. 

    Note: Bitmap files that can’t be extracted may indicate a problem in the source file system. Run CHKDSK on the source volume (i.e. the volume being backed up) to check for this problem. 

  • Fixed an issue where in some rare situations the Daily Summary Notification email didn't show all the files replicated on that day.
  • Fixed an issue where in some rare cases the ImageManager install wizard was displaying a blank page if you clicked the "Back" button. This doesn't affect the installation.
 Known Issues
  • Microsoft .Net 3.5 SP1 must be installed on the machine prior to installing ImageManager
    • StorageCraft recommends that you install ImageManager on a server OS and that you make sure Microsoft .Net 3.5. SP1 is installed first. This is especially important when a silent install is used because the install may fail otherwise.
    • If you run the ImageManager installer on an OS that does not have .Net 3.5 SP1, then the results will vary based on the OS (details are included below). 
      1. Server OS: Windows Server (version 2008 or later)
        If you run the ImageManager installation on a Windows Server OS (version 2008 or later) that does not have .Net 3.5 SP1, the installer will not detect it and warns you with a pop-up window. You can then cancel the install and manually install .Net 3.5 SP1. For the latest versions of Windows .Net 3.5 SP1 is typically found under the Windows “Turn Windows Features on and off” option.
      2. Server OS: Windows Server 2003
        On Windows Server 2003 with no .Net, Windows attempts to automatically install .Net 3.5 SP1. If .Net 2.0 or .Net 3.5 (non SP1) is installed, ImageManager will install without displaying the warning. However, the ImageManager service will crash when you attempt to connect to it with the ImageManager Client UI.
      3. Desktop OS (Windows 8 and later):
        ImageManager should install correctly and Windows should automatically install .Net 3.5 SP1 if you have an internet connection. If you use a silent install in this scenario a pop-up window is displayed and the installation waits until you respond to the pop-up. 
      4. Desktop OS (Pre-Windows 8): 
        Windows often tries to install the .Net 3.5 SP1 automatically for you. Microsoft opens their own .Net installer wizard which should allow you to install .Net 3.5 SP1 and then complete the installation of ImageManager.
      5. Desktop OS (Windows XP with .Net 3.5): Some very early versions of Windows XP may not have the SP1 version of .Net 3.5. This is extremely rare. If you run the ImageManager installer on these machines the installation may fail and could hang. The solution is to download and manually install .Net 3.5 SP1.

        To avoid these issues it is always best to install .Net 3.5 SP1 before installing ImageManager. 

  • Installation can take a long time if you have Windows System Restore settings enabled for the destination drive. If the System Restore settings are enabled it creates a system restore point which causes the installation to take longer.

 

ImageManager 6.5.3 (June 2014) 
 

Enhancements

  • Added HSR support for VHDX as a new Type. HSR now supports the following types: VHD, VHDX, VMDK, and Volume (this includes support for VHDX and Volume types greater than 2 TB).
  • Added functionality so the retention policy "time" is now the same for managed folders on the local drive and managed folders on network shares. This keeps files more closely in sync in the rare case when a user leverages ImageManager to control retention (on a Continuous Incremental backup) replicated locally to a set of rotated drives.
  • Added functionality so that silent ImageManager installations now require the user to explicitly accept the StorageCraft EULA. The installation will not run if the EULA is not accepted.
  • Added support so you can now right-click on a managed folder to bring up a list of options, including consolidation and retention settings.

Fixed Issues

  • Fixed an issue where in some rare and isolated cases, a HeadStart Restore (HSR) may result in a corrupt VHD file.
    • The backup chain is not affected and does NOT contain any corruption.
    • StorageCraft strongly recommends installing ImageManager 6.5.3 if you plan on doing an HSR to a VHD file because it is not possible to remove the corruption once it has occurred.
    • You also need to delete the original HSR job and create a new one.
    • This change does NOT affect any HSR to VMDK.
    • If you need to restore your backup (before you upgrade ImageManager and re-run your HSR > VHD) you can use your backup for the restore.
  • Adjusted retention rules to allow older (outside of the retention settings) or orphaned ShadowProtect files in local replication folders to be deleted.
  • Fixed an issue where in some rare situations, ImageManager was leaving behind backup-file hidden mounts in a managed folder. This made it difficult for ImageManager (or the user) to delete those files later.
  • Made improvements in handling backup chain passwords.

    Note: When you create an encrypted (password protected) backup chain with ShadowProtect it normally creates a ShadowProtect Key (SPK) file. ImageManager can use the SPK file to mount and consolidate the encrypted backup chain without explicitly knowing your backup password. You can override the SPK backup chain password (if for any reason you don't want to keep the SPK file with the backup chain) by entering the backup chain password in ImageManager. 

    The password can be defined on a global level (in the ImageManager Agent settings), or per Managed Folder. If you define both a global password and a managed folder password, the managed folder password takes precedence. These passwords are protected and encrypted by Windows. In future versions of ShadowProtect the SPK file creation will be optional when a backup chain is created.

  • Fixed an issue where the managed folders and replication targets were erroneously removed during installation. 
  • Fixed a problem that prevented users from editing a password in the HSR job dialog box.
  • Fixed agent Maximum Transfer Speed to prevent larger values from creating a pop-up error.

Known Issues

  • You must manually enable Microsoft .NET 3.5 (it can't be silently enabled) before attempting an ImageManager silent install on Windows 8, Windows 8.1, or Windows Server 2012.
  • Starting with version 6.5.3, ImageManager no longer installs the ShadowStream user interface Admin Client. A separate installation is required.
  • ImageManager does not support the use of apostrophes in managed folder names. ImageManager throws an error when the apostrophe is used.
  • On Japanese systems (when an HSR job is configured to write a VMDK to an ESXI server) there is a chance that the password will be rejected if the user first enters an incorrect password and then subsequently enters the correct password. The work around for this is to delete the HSR job and create it again.

ImageManager 6.5.1 (October 2013) 
 
Important: StorageCraft recommends that you install and use ImageManager version  6.5.1.31908. See Fixed Issues below for additional information.

Enhancements

  • ImageManager now supports HeadStart Restore to an empty NTFS volume or an empty RAW volume. You can use Windows Disk Management to create either of the two.

Fixed Issues

  • ImageManager 6.5.1.31908 StorageCraft recommends using this build for the following reasons:
    • It fixes an issue that prevented optimized consolidation of backups.
    • It fixes an issue that caused an HSR job to not run if a user created the HSR configuration to write to an ESXi server with an incorrect password, then later provided the correct password.
  • ImageManager 6.5.1.31793 fixes a failure to edit an incorrect backup password in an HSR job to a local drive. This affected backups with two or more volumes, but didn't affect writing to an ESXi server.
  • Fixed HSR to VMDK on shared folder failure. In some situations it was possible that a HSR to a VMDK on a network shared folder (UNC path) failed.
  • Fixed HSR to VHD failure after upgrade from SCIM 6.0.1 - Upgrading from 6.01 to 6.5 was causing certain HSR jobs to fail. It now works correctly.
  • Fixed Japanese localization string issues:
    • Retention and Global retention tab strings: "Move all consolidated image files to a subdirectory instead of deleting them" is now localized in Japanese.
    • Fixed a duplicate localization string bug on the Retention setting screen. Now only one of the strings uses the term global.
    • In the Managed Folder configuration option the following string was truncated: "Assign sort priority relative to other managed folders". This is now fixed.
  • Fixed an issue so that the retention policy "time" is the same for managed files on a local drive as on network shares. File counts should match after drives are swapped and processing occurs.
  • Fixed a problem where two ImageManager entries were displayed in the Windows Add/Remove screen after an upgrade. Only one entry is now shown.
  • Fixed an issue to prevent ImageManager and RE builder shortcuts from being removed when ShadowProtect is installed.
  • Fixed an issue so that the ImageManager Daily Report email now correctly shows the number of files restored and the number pending. In some rare cases, where only one file was available for HSR, the number of restored/pending files was given as zero. The numbers are reported correctly now.
  • Fixed an issue for Linux-based NAS devices running FTP where ImageManager was not able to correctly enumerate files in the FTP folders. This caused a replication failure when using iFTP.
  • Fixed an issue where file sizes were being reported as zero during a replication sync comparison.
  • Fixed a remote location problem where files were not deleted as quickly as the user expected. Now retention runs as scheduled. It is no longer calculated  from the "create time" of the Collapsed Daily.
  • Fixed an issue to make sure .bitmap files are removed by the Retention Policy. In some cases the images weren't removed when ImageManager replicated backup files to external drives which were rotated out over a period of time (every day or every week). This is now working correctly.
  • Fixed a problem that was preventing ImageManager from starting up if there were more than 64 managed folders.

Known Issues

  • ImageManager HSR to VMDK on an ESXi server works only with ESXi 4.1 Update 3 or later. StorageCraft  recommends that you update to the latest available version of ESXi 4.1 or update to version 5. You may see the following error "18-Jul-2013 09:31:30 send error: error code FF" if you do an HSR to VMDK on older versions of ESXi.
  • Using double-byte characters in a ShadowProtect backup filename may cause a resulting HSR job to a local disk (in VMDK format) to fail.
  • In rare situations ImageManager may report a backup file property as "Unlocked".  This can occur for a variety of reasons but is benign and can be ignored.

ImageManager 6.5.0 (August 2013) 

Enhancements

  • HeadStart Restore can now restore to physical volumes. Previously HSR could only write to VMDKs or VHDs using an ESXI or other VMWare server program. Now you can use a local physical disk for the HSR process.
  • ImageManager 6.5.0 now has support for the Polish and Czech languages. It also has updated or corrected language strings for other languages including Japanese.
  • ImageManager now allows you to process a specific single folder or multiple folders instead of having to process all managed folders at the same time.
  • ImageManager now has concurrent verify and reverify operations. This means new files will never have to wait for a reverify to complete.
  • ImageManager now has limited support for creating VHDX files. The VHDX drive can appear as a physical drive when mounted if the following conditions are true:
    • You must be using Windows 8 or Windows Server 2012.
    • The volume restored must be smaller than 2 TB.
    • The drive must be visible to ImageManager.

Fixed Issues

  • Fixed installer so it prompts you if Microsoft .NET 3.5 is needed for non-English installations on Windows 8 and Windows 2012.
  • Fixed installer to use Add/Remove Programs when installing .NET 3.5 on Server 2008 R2.
  • Fixed the replication order for split backup files. The files are now replicated in the proper order. This prevents verification failure if ImageManager is being used at the destination.  
  • Fixed ImageManager so it now handles finalization of HSR jobs with missing links in the backup chain.
  • Fixed replication of required collapse files so they are automatically added to the queue where IM is running remotely.
  • Fixed problems with ImageManager and ShadowStream installation. ShadowStream now has separate install and uninstall functionality. See Installation Tips (section 5) for details.
  • Fixed HSR Finalize to display all available finalized points.
  • Fixed missing and incorrect language strings for Japanese and other languages.

Known Issues

  • Changing the IP address of a machine currently running ImageManager causes the ImageManager client to disconnect from the ImageManager service. You can fix this problem by restarting the service. The client should then be able to connect.
  • If ImageManager alerts are turned on, you may receive some StorageCraft Cloud "self-healing" email notifications errors. If you receive multiple notifications for the same error within a short period of time (between 1 hour and 4 hours) you can call StorageCraft support to help resolve the issue.
  • For large drives on Windows Vista and Windows Server 2008 R2 (500 GB and larger), VHD replication targets will gradually use more system memory over time.
  • StorageCraft strongly encourages you to downgrade ShadowStream server to version 5.x (currently posted on the StorageCraft website) especially if your ShadowStream client is version 5.x.
  • The maximum path length for ImageManager is 210 characters. This includes the pathname length plus filename length.  If your path is longer than 210 characters ImageManager may not be able to see or verify the files. Paths exceeding 210 characters may also cause md5 sum errors.
  • If you change a volume size after starting an HSR job, you need to delete the job and start over. HSR does not have the ability to recognize volume changes after a job is started.

ImageManager 6.0.1 (April 2013) and Older

Enhancements

  • Users can now customize agent-wide throttling during peak hours on both weekdays and weekends. This functionality is available in Agent Settings > Performance.

Fixed Issues

  • Fixed the change password functionality for an existing location. The password can now be changed.
  • Fixed consolidation so it doesn't stop when a large number of folders are managed.
  • Fixed HSR so it can now write a VMDK to a top level (user created) folder in a VMWare ESXi Datastore
  • Fixed finalization for a point-in-time (with consolidated weekly and consolidated monthly .spi) so the HSR no longer hangs.
  • Fixed ImageManager language strings for cloud settings.
  • Fixed port conflict by changing default port to 18180.
  • Fixed finalizing HSR jobs with multiple volumes so it no longer hangs after first volume. Fixed other HSR finaliztion issues.
  • Fixed wcf.svclog creation in the top level folder of the boot volume. This log file is no longer created.
  • Fixed uninstall so it now cleans up unused files when upgrading from ImageManager 5.x to 6.x. 
  • Fixed ImageManager iFTP so it writes to the root when a sub-folder not available.
  • Fixed the password routines to require password re-entry to change any agent setting.
  • Fixed installation process to include the backup mount driver (sbmount.sys).
  • Fixed retention policy so that when a backup job resumes (after being stopped longer than the retention period), the last file replicated is not removed and the job resumes replication as expected.

Known Issues

  • To retain your ImageManager settings during an upgrade on MS Vista or newer you must run the installer as Administrator. Right click on the installation file and select "Run as administrator". If UAC is enabled and you don't run the installer as an administrator there is a chance of losing your settings.
  • Uninstalling ImageManager also uninstalls ShadowStream and ShadowStream settings.
  •  Installation of the MS Windows .net framework (version 3.5) sometimes fails on Windows Server 2003 32-bit, Windows Server 2003 R2 Standard and Windows XP 32-bit. If this occurs install the .net framework manually then install ImageManager.
  • If you are installing the .net framework on Windows Server 2008 R2 you need to use the Additional Features option.
  • Creating a HeadStart Restore on a VHD running Windows Vista or Server 2008 can cause crashes when caching is enabled. If caching is not enabled ImageManager can't write AFD (4kn drive). When caching is enabled memory is progressively used and not released until the system crashes.
  • If ShadowStream is not actively replicating a file, changes in throttling happen immediately, otherwise, the changes only take affect when the file transfer is complete. If you want to make a change during a transfer, you must pause the job, make the change, then restart the job.
 
 
 
 
 
 

4.2 Older ImageManager Versions

This page is an extension of the ImageManager ReadMe which contains older information.

Enhancements

6.0 (December 2012)

  • Added StorageCraft Cloud Services replication type.
  • Added functionality to allow monthly consolidated files to be used to create a rolling consolidation file.  The monthly files can then be removed to save storage space.
  • Added ability to scheduled bandwidth replication throttling for iFTP and ShadowStream jobs.
  • Added functionality to allow incremental file replication before the base file has been transferred.  NOTE: The incremental files are unusable until the base file arrives.

5.0.5 (March 2012)

  • Added concurrent job execution for HeadStart Restore and Replication jobs of the same type (such as all Network Replication jobs or all ShadowStream jobs).
  • Added a check every 15 minutes to trigger a retry for failed replication jobs instead of waiting for another file to trigger a retry.

  5.0.1 (December 2011

  • Updated Japanese localization strings to more accurate translations
  • Updated Password Reset Tool to work with ImageManager 5.x service.
  • Updated strings to reflect new branding.

5.0 (September 2011)

  • Changed licensing model to Job-based licensing.
  • Added ShadowStream replication transport
  • Added full support for vCenter clusters by allowing users to select the destination VM folder instead of always using the root folder. In prior versions of ImageManager this issue was prevented ESX failover for users running an ESX cluster. Selecting a VM folder is necessary when ESX permissions restrict user access to specific folders and resource pools.
  • Added Replication Throttling to intelligentFTP and ShadowStream to cap throughput to a passed-in MBPS value.
  • Added Location objects to eliminate retyping shared/stored credentials
  • Added Active/Passive mode option to FTP Replication targets
  • Added Block Size option to FTP Replication targets to allow fine-tuning of FTP transfers
  • Split Consolidation into separate Consolidation and Retention to allow the user to manage and enable/disable Image Consolidation and Image Retention independently.
  • Added support for Retention warnings. When users virtual boot an image chain, an incremental is created for that boot session. ImageManager does not clean this up so when this condition exists it is reported as a Retention warning.
  • Developed a workaround for issues relating to 2GB image file size limit on certain NAS devices running Samba.
  • Added support for local drive swapping with continuous incremental jobs
  • Added support for additional languages.  Supported languages now include English, German, Spanish, French, Italian, Japanese, Korean, Turkish, Chinese (Simplified and Traditional) and Portuguese (Portugal).
 
Known Issues
There are no unresolved known issues for older versions of ImageManager.

 

 Fixed Issues

 6.0 (December 2012)

  • Fixed files stored on a local share so they are now read correctly.
  • Fixed drive rotation for local drive replication. Now it cleans up all old files when drives are replaced.
  • Fixed a rare bug so processing can continue without having to restart the service.
  • Fixed the ability to change the password for an existing location.
  • Fixed the daily summary for HSR jobs so they now show the correct file counts.
  • Added the functionality so that HeadStart Restore now finalizes properly when a point in time is selected that has more than one possible file to choose.  For example, this happens when there is a collapse daily and a collapse weekly for the same point in time.

5.0.5 (March 2012)

  • Fixed an issue related to licenses being invalidated by changing hardware ID.
  • Fixed a replication bug that occurs when the creation date of an image file is earlier than the file it is dependent on (can happen at daylight savings).
  • Fixed a bug related to changing the replication mode of an existing job.  Now the list of files to be sent changes immediately instead of waiting for the job to be disabled and re-enabled.
  •  Removed the check for matching file size on replication of intra-daily images to site where ImageManager is running.
  • Verified the create time function on each sync to resolve the “files created out of sequence” problem when the create date is incorrect.
  • Fixed an error occurring when replication mode changes while a file is being sent or waiting to be sent.
  • Fixed a bug related to the client becoming temporarily unresponsive when receiving too many notifications from the ImageManager service.
  • Fixed a consolidation error when time zone is changed and the time between incrementals is hourly or less throughout the day.

 5.0.1 (December 2011)

  • Fixed a NullReferenceException thrown when attempting to update job licenses when the network is down.
  • Fixed a console refresh issue which prevented the console from refreshing after sitting open for more than 24 hours.
  • Fixed an error in the Send Test Email dialog which required the “This server requires authentication” to be checked.
  • Fixed ImageManagerSetup.exe to allow upgrades from version 4.0.1 and newer, and prompt for uninstall if an older version is detected.
  • Fixed ImageManagerSetup.exe to require EULA acceptance on upgrade.  

 5.0 (September 2011)

  • Fixed ImageManagerSetup.exe to allow installation to a custom path

5 ShadowControl Release Notes

General Information

This ReadMe includes information on StorageCraft® ShadowControl® updates up to and including v4.0.3. Review the readme file carefully to understand the product changes and updates, and determine if you want, or need, to apply it.

Last Updated: 1 June 2017

System Requirements

Warning: Installing the ShadowControl appliance erases any existing data and partitions on that drive.

ShadowControl requires:

 
ShadowControl 4.0.3
 
Fixed Issues
  • Fixed an issue where ShadowProtect Backup Report showed success (green) on failed backups.
  • Fixed an issue where endpoints were showing up as being unresponsive in the appliance even though they had good communication.
  • Fixed other miscellaneous issues. 

 

 

Important: You should still be using ShadowControl endpoint version 4.0.0 with the ShadowControl appliance version 4.0.3. You can now download the version 3.8 endpoint from the appliance. Click EndPoint Installation Instructions on the ShadowControl login/dashboard page.

Known Issues
  • When adding an AWS replication job to a managed folder in ImageManager 7.5 it is possible that the managed folder will be removed from the UI in ShadowControl. This endpoint change will be fixed in the next major release of ShadowControl.
 
ShadowControl 4.0.2
Enhancements
  • ShadowControl 3.8 endpoints can now be managed by and communicate with the ShadowControl 4.0.2 appliance. See the requirements for making this work in the Known Issues section below.
  • Added support for Ubuntu 16.04.
  • Added a status rule for ImageManager Replication Queue Length Threshold.
Fixed Issues
  • Fixed an issue where the endpoint agent didn't recognize valid subscription switches when subscribing to an org and specifying the credentials (username and password).
  • Fixed an issue where the ImageManager page failed to completely load when using Internet Explorer 11
Known Issues
  • In order to support Windows XP and Server 2003 with ShadowControl 4.0.2 you need to manually download and install the ShadowControl 3.8 endpoint. After installing the 3.8 endpoint you need to manually subscribe the 3.8 endpoint to ShadowControl 4.0.2.

 
ShadowControl 4.0.1
 
ShadowControl 4.0.1 includes hotfixes for the ShadowControl appliance. No changes were made to the endpoints in ShadowControl 4.0.1.
 
Fixed Issues
  • Fixed an issue where modifying the SPX policy caused endpoints under that policy to be deleted. Endpoints are no longer deleted. 
  • Added translation strings that weren’t available on initial ShadowControl 4.0.0 launch.
  • Fixed an issue where Read Only users were able to see/trigger endpoint updates and reboots. 
  • Fixed an issue where push install for some languages wasn't working correctly. Push Install for some languages may take longer.
 
ShadowControl 4.0.0
 
ShadowControl 4.0.0 includes functionality to remotely monitor ImageManager and ShadowProtect (both ShadowProtect 5 and SPX), and manage ShadowProtect SPX installations from the web based console.

 Warning: The ShadowControl 4.0 appliance runs on Ubuntu v16.04. Don’t upgrade your appliance from Ubuntu v12.04. You need to build a new appliance on Ubuntu 16.04 and then import your configuration and data from the old appliance. This new integration also requires ImageManager 7.0.6 or newer. 

Important: StorageCraft ShadowControl 4.0 does not support Windows XP or Windows Server 2003.
Enhancements
  • Added a new Managed Folder List view that lets you easily see all ImageManager endpoints and their associated managed folders. 
  • Added the Folder Details page under the Folder List page that displays detailed information about a selected managed folder. These details include:
    • All currently running jobs (validation, consolidation, replication, HSR)
    • The path where the folder exists
    • Current folder size (disk space used)
    • Current space available (remaining disk space)
  •  Migrated the appliance to Ubuntu 16.04 - The ShadowControl appliance now uses Ubuntu v16.04 Linux. It previously ran on Ubuntu v12.04 Linux. The Ubuntu v12.04 end-of-life is April 2017. Updated tools in Ubuntu 16.04 allow more flexibility and power for future versions of ShadowControl.

     Warning: You need to build a new appliance and import the configuration and data from your current appliance.

    Do not upgrade from 12.04 to 16.04 because there were 8 major releases in between and the upgrade process is too risky. It is better to start clean and import your configuration and data. 

  •  Added new status rules to the ShadowControl console that support enhanced ImageManager monitoring. Users can now configure alerts for the new ImageManager functionality. The new status rules are:
    • Chain Incomplete: This rule alerts you if ImageManager detects that the image chain in a managed folder is incomplete (missing one or more files).
    • DiffGen Incrementals: This rule alerts you if ShadowProtect performs a DiffGen incremental.
 
ShadowControl 3.8.0
 
Known Issues
Fixes
Enhancements
ShadowControl 3.7.0
 
Known Issues
Fixes
Enhancements
ShadowControl 3.6.3 (Appliance-only update)
 
Fixes


ShadowControl 3.6.2 (Appliance-only update)
 
Fixes


ShadowControl 3.6.1 (Appliance-only update)
 
Fixes

 

ShadowControl 3.6.0
 
Known Issues

The following are known issues as of the release of ShadowControl 3.6.0. If possible, StorageCraft will fix these issues for the next ShadowControl release.

Fixes
Enhancements


ShadowControl 3.5.1
 
This is an Appliance-only release. The endpoint remains at v3.5.0. 

Fixes


ShadowControl v3.5.0

Known Issues

Fixes

Enhancements

 
ShadowControl v3.0.2
 
This is an Appliance-only release. The EndPoint remains at v3.0.0. 
 
Known Issues
 
Fixes
Enhancements
ShadowControl v3.0.1
 
This is an Appliance-only release. The EndPoint remains at v3.0.0.
 
Known Issues
 
Fixes
ShadowControl v3.0
 
Known Issues
Enhancements
Enhancements for SPX endpoints
Fixes

Fixed bugs where:

Older Versions
ShadowControl v2.6.0
 
Known Issues

Note: To determine if an endpoint's uplink with the appliance is down, use the ShadowControl console to browse to Endpoint Details > Job Details. If the endpoint successfully returns the most recent job log, then the uplink is working properly.

Enhancements and Fixes
ShadowControl v2.5.1

This is an Appliance-only release. The EndPoint remains at v2.5.0. EndPoints update as part of the appliance update only it both appliance and EndPoints are v2.0.1 or older.
 
Known Issues
 
Enhancements and Fixes
 
ShadowControl v2.5.0
 
Known Issues
  • When updating endpoints as part of the appliance upgrade, StorageCraft recommends selecting a longer time-window for the endpoint upgrade. This will reduce the chance for endpoints to miss the update ticket from the appliance due to appliance or network congestion.
  • In some cases, the endpoint auto-update occurs based on GMT instead of the actual endpoint time. This can introduce a delay of up to several hours in the update process, but endpoints will eventually update properly.
  • When restoring an appliance database, endpoints subscribed or resubscribed after a ShadowControl database export must resubscribe after the database restore. The appliance and endpoint sets, or resets, login credentials upon subscription, so login information might change after a database export. For this reason, StorageCraft recommends regularly updating the exported appliance database to keep it current.
  • EndPoint agents may display errors in the Windows Application Event Log when shutting down the EndPoint agent.
Enhancements and Fixes

This release includes:

Notes for the ShadowControl Virtual Plug-Ins
 

ShadowControl v2.0.1

 
Known Issues
 
Enhancements and Fixes

This release addresses previous known issues. There are no new features.

 

ShadowControl v2.0.0

 Known Issues

Enhancements and Fixes

This is a major release:

CMD v1.3.0

Enhancements in this release:

Known issues in this release:

  • Explanatory text on the ShadowControl setup dialog says that the appliance access code is needed to perform a restore. This is currently not implemented in this release.
  • When exporting the appliance database, do not refresh (using the F5 key) your browser window. Doing so restarts the export process.

CMD v1.2.1

This maintenance release:

CMD v1.2

Enhancements in this release:

Known issues in this release:

  • EndPoint auto-update may not complete immediately. StorageCraft recommends waiting an interval of time for the EndPoint to update prior to performing one of the alternative update strategies below.
  • EndPoint updates consume network bandwidth and multiple updates can exhaust bandwidth before completing the update. An EndPoint then attempts the update repeatedly which can limit network access. To conserve bandwidth, stage EndPoint updates rather than execute them simultaneously.
  • On rare occasions the EndPoint automatic update process fails. If this occurs:
    1. Select the affected EndPoint in CMD's EndPoint list. This should trigger the automatic update process.
    2. If this should fail to update the EndPoint, click Update Now in the EndPoint Details Agent info field. This triggers the automatic update process. 
    3. If neither of these initiate the update, restart the StorageCraft Endpoint Agent service in the affected system's Windows Services tool.  Then use the CMD console to perform Steps 1 or 2.
    4. If these don't initiate the automatic update, perform a manual install of the EndPoint agent on the affected system.
  • Site names must be unique across the appliance. Use a more specific name, such as "Jordan Data Center" rather than "Data Center", to avoid this issue.
  • The CMD appliance currently does not report expiring MSP licenses.
  • A CMD appliance or EndPoint might behave erratically if a monitored backup Destination folder includes many (typically, more than 1000) image files. This occurs because of the time it takes to search the folder for new or updated files. To avoid this, StorageCraft highly recommends configuring retention policies in ShadowProtect, and leveraging ImageManager retention and consolidation, to limit the number of files in a Destination folder as much as possible. StorageCraft is working to remove this limitation in an upcoming release of ShadowControl CMD.

CMD v1.1.3

Enhancements in this release:

Known issues in this release:

  • EndPoints running earlier versions of the CMD client may not upgrade to v1.1.3 until after a restart of CMD's StorageCraft EndPoint Agent service.
  • Unsubscribed EndPoints need the v1.1.3 client downloaded and installed manually in order to subscribe to an appliance.
  • CMD Portals do not support EndPoint subscriptions. Subscribe all EndPoints to a CMD appliance instead.
  • The appliance install requires accepting the default language of English in Ubuntu. Selecting another language prevents CMD from installing correctly. Note that CMD itself uses the browser's default language for its UI.

CMD v1.1.1

This release:

CMD v1.0.2

This release:

 

Copyright © 2015 StorageCraft Technology Corp. All rights reserved. This Software and Documentation are copyrighted.  Ownership of the ShadowProtect Server Edition Software is reserved to StorageCraft Technology Corporation.  StorageCraft, the StorageCraft logo and the ShadowProtect Server Edition logo are trademarks of StorageCraft Technology Corporation.  StorageCraft, ShadowProtect, ShadowControl, and HeadStart Restore are registered trademarks of StorageCraft Technology Corporation in the United States and elsewhere. ShadowProtect Server Edition, intelligentFTP, and ShadowStream are trademarks of StorageCraft Technology Corporation in the United States and elsewhere. Windows and WIndows Server are registered trademarks of Microsoft, Inc. VMware is a registered trademark and VMware vCenter is a trademark of VMware, Inc.  All other brands and product names are or may be trademarks or registered trademarks of their respective owners.

6 ShadowProtect IT Edition Release Notes

General Information

This file contains additional information to supplement the manual. Please read all the sections before you proceed with the product. 

Covers up to ShadowProtect IT Edition v5.2.7

Table of Contents
  1. Features/Enhancements/Fixes
  2. Known Issues
  3. System Requirements
  4. Installing ShadowProtect IT Edition
  5. Activating ShadowProtect IT Edition
  6. Upgrading ShadowProtect IT Edition
  7. General Usage Notes
 
1. Features/Enhancements/Fixes

Version 5.2.7 (May 2015)

  • Added support for Windows 10 ADK.
  • Added support for Windows Server 2016

Version 5.2.4 (January 2015)

  • Fixes an issue where, in rare cases, a user could select an invalid incremental file to close an HSR job. This would result in an unusable volume and require a restart of the HSR job.

Version 5.2.2 (December 2014)

  • Supports launching GRE from the IT Edition ISO when run on a booted "hot" Windows system. This allows using GRE on systems: without a USB connection or a VM running on a Type 1 hypervisor. This option is not supported in the IT Edition 3-day ISO.
  • Fixed an issue where the IT Edition would default to using Czech in the UI when run hot on an unsuppoted language system (such as Norwegian). The IT Edition now defaults to English in those situations.

Version 5.2.0 (July 2014)

  • Supports VHDX files.
  • Supports NETGEAR® ReadyDATA® NAS systems..
  • The ShadowProtect Mount wizard supports mounting VHDX files as Read-Only.
  • The NETGEAR system can detect when a ShadowProtect Agent is offline and will also receive notification from ShadowProtect when backups are complete. This allows the NETGEAR to send email notifications with this information.
  • ShadowProtect now supports a new set of retention policy settings for the NETGEAR target backup destination.
  • The StorageCraft EULA opens on starting the IT edition and IT 3-day ISOs for the first time.

Version 5.1.3 (October 2013)

  • Can operate as either the standard IT Edition or as the IT Edition PRO based on the type of license purchased. The PRO version includes ShadowProtect Granular Recovery for Exchange for use with Microsoft Exchange server backups and restores.

Version 5.1.2 (September 2013)

  • Fixed various localization strings, including in Polish, with the Recovery Environment for Windows (REWIND).
  • Fixed a bug that prevented REWIND from accessing SUBST drives and could also prevent taking hot backups on the same system using SUBST mounts.

Version 5.1.0 (August 2013)

  • Uses single ShadowProtect UI shared with Recovery Environment for Windows v5.0.5.
  • USB key Includes the Recovery Environment CrossPlatform (RE-X) v2.1.1 based on Linux. RE-X supports backup and restore from all supported Windows platforms.
  • Incorporates dual-boot functionality to launch either REWIND or RE-X (after using the REBuilder tool v1.1.0 to create and install REWIND).
  • Includes additional features once the IT Edition license is activated. (These include Hot Backups, Disk Copy, and Multi-volume Restores.)

Version 5.0.5 (July 2013)

  • Updated to provide Recovery Environment v5.0.5 functionality, including support for GPT disks.
  • Fixed issues where, on some isolated systems, hot backups, snapshot removal and verifications may not complete in all situations.
  • Added support for Large Block Devices (LBD).
  • Added support for UEFI systems.

Version 4.1.3.13 (January 2012)

  • Fixed a bug that prevented the IT Edition Start Activate.exe in  the Recovery Environment from operating correctly when you try to do anything 'cold'.
  • Fixed an IOCTL error that prevented IT Edition from running correctly on computers using Symantec Volume Manager

Version 4.1.3 (October 2011)

  • Fixed a bug that prevented IT Edition from running on computers using Symantec Volume Manager.

Version 4.1.2 (May 2011)

  • ShadowProtectPE.exe has been fixed and will now run 'hot' on XPx86.
  • Allow NTLM authentication to some older NAS devices.

Version 4.1.0 (March 2011)

  • The system keyboard layout can now be changed within the booted Recovery Environment.
  • Released for English, Japanese, French, German, and Portugal-Portuguese.
  • Fixed a bug where repeatedly creating and then deleting the same partition might cause multiple volumes to be assigned to that partition.

Version 4.0.2 (October 12, 2010)

  • The Recommended Recovery Environment is now based on a clean baseline WinPE build of Windows Server 2008R2, which has excellent default device support. No additional 3rd party drivers are auto-installed.  Instead, all additional 3rd party storage/network/misc drivers (including drivers for various VMs) are found in the Additional_Drivers directory, and should be loaded manually, as needed, using the TOOLS -> LOAD DRIVERS menu item.  In future builds, any changes to the contents of this Additional_Drivers directory will be noted in a ChangeLog.txt file contained within the Additional_Drivers directory.  The purpose for using the clean baseline WinPE was to eliminate some driver conflicts which were occurring (where an injected 3rd party driver would incorrectly claim ownership of hardware it didn't actually support).
  • The USB Update Wizard now updates all critical USB IT Edition files. However, it no longer updates the .ISO file found on the target USB drive. The .ISO file on the USB drive is not actually used by the USB drive when it is booted.  The .ISO file is placed on the USB drive for convenience, to be used as the source for bootable CD-Rs, or directly for VM CD boot sessions.  If you wish to update the .ISO file on the USB drive, you can copy the updated .ISO file from the Update package to your USB drive (overwriting the older .ISO file).
  • When IT Edition is booted, the LOAD DRIVERS menu option is now enabled even if IT Edition is not yet licensed (in cases where it has not yet found the USB drive, or has not yet connected to a license server).  This will enable users to load the necessary network drivers in order to connect to a license server, in cases where the drivers for their NIC aren't automatically loaded.
  • Fixed an issue which caused IT Edition to fail to retrieve its license, which resulted in the error "license content does not match digital signature."
2. Known Issues

Version 5.2.2 (December 2014)

  • When using GRE from the IT Edition ISO, there are some situations where GRE cannot automatically defragment the EDB. In these situations,  run the ESEUTIL utility manually from the command line.
  • The IT Edition requires at least 1GB of RAM. If the system has less than this amount, the IT Edition may fail to boot. Increase the amount of RAM as required to provide 1GB. If this is not an option, use the 32-bit version of the Recovery Environment.

Version 5.2.0 (July 2014)

  • When running the ShadowProtect RE IT Edition "hot" (the system is already booted into Windows) on a Windows OS with an unsupported language, the UI will default to Czech rather than English.

Version 5.1.3 (October 2013)

  • Current licenses of the standard IT Edition cannot upgrade to activate GRE. On the standard IT Edition key, GRE only operates in Trial mode.

Version 5.1.0 (August 2013)

  • The IT Edition now uses the REBuilder tool to create the Recovery Environment for Windows. This REBuilder tool may display an error message and fail to generate the recovery environment if the user specifies paths to additional drivers which change before the REBuilder tool creates the recovery environment. (This could occur when using the REBuilder to generate another copy of the recovery environment some time after the initial one was generated.) To prevent this error, do not delete or move specified drivers until after the REBuilder completes the recovery environment creation.
  • The IT Edition version of Recovery Environment for Windows, REWIND-IT, does not support double-byte characters. It does, however, support the backslash (\) character using the YEN key on Japanese keyboards.
  • To use a Japanese keyboard in RE-X, follow the steps outlined in the Recovery Environment CrossPlatform User Guide.
  • REWIND uses a standard 32-bit network driver by default. On some systems, this driver may not work with the installed network card. The network dialog progress bar may halt and the interface freeze. In those cases, determine the correct driver for the existing hardware. Include this driver in the Additional Drivers list in REBuilder.
  • REWIND-IT may display an error message when opening the Boot Configuration Utility (BCU). This occurs when two or more GPT exist in the system. The informational message states that the disks have duplicate signatures. Click OK to close the error to continue using the BCU.
  • The REBuilder tool may on rare occasions display an obscure error message when using an external USB CD/DVD burner connected to a USB 3 port. It will then fail to burn the disc. Use another device to perform this operation instead.
  • The IT Edition 3-day ISO generated by REBuilder includes a license check. If the IT Edition license is expired, the software displays a notification. Also, the IT Edition functions in the Recovery Environment are disabled, but the remaining functions continue to operate. However, the software may continue to display the "License expired" notification prior to using these other functions, such as Backup or Restore, even though they work as normal. Simply close the notification dialog and complete the operation.
  • The dual-boot capability requires the assigned volume name used on the IT Edition USB drive as shipped. Do not change this. Doing so prevents the dual boot option.

Version 5.0.5 (July 2013)

  • The Disk Copy wizard may perform erratically if the user selects either Disk or Volume copy, navigates forward and then navigates back in the wizard.
  • Some Disk Copy operations may fail when the destination disk is much larger than the source drive.
  • Using Disk Copy on a Windows Vista or newer boot volume may result in the copy failing to boot. (Windows alters the copy's Disk Signature so it doesn't duplicate the original.) To fix this, install the copied drive into a new system and boot it using RE. Use the BCU to automatically repair the copied drive. Restart the system with the copied drive.
  • Unzipping the IT Edition Upgrade package and writing the update to the IT Edition USB drive may take 10 minutes but it can take as much as 50 minutes to complete.
  • Launching the IT Edition's ShadowProtect console (START_SHADOWPROTECT found on the ISO) on a live Windows system allows for taking "hot" backups. However, if the live system has ShadowProtect installed and the ShadowProtect console is open or the ShadowProtect shield appears in the System Tray, attempting to run the console on the ISO does not open the IT Edition's version of the console. Instead, it launches the local ShadowProtect console on the live system. If a hot backup is needed, use the existing ShadowProtect console.
  • The Legacy (Windows 2003-based) Recovery Environment is only for use on old hardware (primarily NVIDIA chipsets).
  • The Legacy environment has limited driver support so some network cards and disks may not appear in the Legacy ShadowProtect Console (UI).
  • The Legacy environment has no option to load a driver after boot up. If this is a required feature, use the Recommended environment instead.
3. System Requirements
  • Must meet the minimum operating system requirements
  • Memory:  At least 1GB of RAM
    Note: If the system has less than 1GB of RAM, the IT Edition may fail to boot. Increase the amount of RAM as required to provide 1GB. If this is not an option, use the 32-bit version of the Recovery Environment.. 
  • An available USB slot.  If a USB slot is not available, either a CD/DVD drive is required or access to a CD .ISO file from within a VM.
  • 3 1/4" diskette drive if using the Legacy Recovery Environment and need to load additional drivers.

Supported Operating Systems

ShadowProtect supports Windows 32-or 64-bit operating systems

  • Windows 8
  • Windows Server 2012
  • Windows Server 2008 R2
  • Windows Server 2008
  • Windows Small Business Server 2008
  • Windows EBS Server 2008
  • Windows Server 2003
  • Windows Small Business Server 2003
  • Windows 2000 Server/Advanced Server (SP4 or above)
  • Windows Small Business Server 2000
  • Windows 7
  • Windows Vista Home Basic
  • Windows Vista Home Premium
  • Windows Vista Ultimate
  • Windows Vista Enterprise
  • Windows Vista Business
  • Windows XP Media Center
  • Windows XP Professional (SP2 or above)
  • Windows XP Home (SP2 or above)
Supported File Systems/Disk types

ShadowProtect Editions support the following file systems:

  • FAT16
  • FAT16X
  • FAT32
  • FAT32X
  • NTFS
  • GPT Disks
  • Dynamic Disks
Supported Storage Media

ShadowProtect supports the following storage media:

  • Local disk drives
  • Network drives
  • SAN
  • NAS
  • iSCSI
  • SCSI
  • USB
  • Firewire
  • Optical media such as CD/DVD/Blu-Ray

REBuilder Requirements

The REBuilder tool creates the IT Edition Recovery Environment for the USB key. This tool runs on a Windows 7 or newer system with an available USB port.

 
4. Installing ShadowProtect IT Edition

IT Edition is run from the USB key or from a CD/DVD.  There is no install for ShadowProtect IT Edition.  A mount driver might temporarily be installed if you are mounting image files while in the running operating system. 

5. Activating ShadowProtect IT Edition

You need to activate ShadowProtect before the trial period ends or the quarter has expired.  You need to continue to activate the product each quarter.  If the autorun does not automatically start IT Edition, browse to the IT Edition USB key and click on Programs → SHADOWPROTECTPE → SHADOWPROTECTPE.EXE.  You will be prompted to enter the product key you received when you purchased your ShadowProtect IT Edition subscription.  Once you have entered the product key correctly, click Activate.  If your subscription has expired, you will be notified and will no longer be able to use ShadowProtect IT Edition until you renew your license. 

 ShadowProtect IT Edition Licensing

ShadowProtect IT Edition is licensed per technician.  You can use the software on as many servers, desktops and laptops as you wish for the period of your subscription.

6. Upgrading ShadowProtect IT Edition

 WARNING: NEVER DELETE OR OVERWRITE the storageCraft.id FILE ON YOUR IT EDITION USB KEY. This renders the drive useless. Follow these instructions to avoid this error.

Current users of ShadowProtect IT Edition 5.0.5 do not need to upgrade using the REBuilder. Users of IT Edition 4.1.3 or earlier should upgrade to RE-Windows IT Edition 5.2.0 with the updated REBuilder.

Note: This upgrade does not install the Recovery Environment CrossPlatform.

 

7. General Usage Notes

The ShadowProtect IT Edition USB or CD/DVD contains the StorageCraft Recovery Environment - Windows which is used as a boot disk for restoring a backup image to the system volume.  Be sure to store the USB key or CD/DVD in a safe place for use in the event that a bare metal recovery of your computer is required.

You should test the StorageCraft Recovery Environment to ensure that it runs properly on your computer.  To do this, boot the StorageCraft Recovery Environment from the ShadowProtect IT Edition USB key or CD/DVD.  

If the StorageCraft Recovery Environment boots and runs as expected, then you will be prepared to perform ShadowProtect operations from the Recovery Environment in the event the system does not boot or you need to restore a system volume from a backup image file or you wish to create cold state backup images using the Recovery Environment.

If the StorageCraft Recovery Environment does not boot or run as expected, investigate the following issues:

  • The system you are booting the recovery environment from must be configured to boot from the USB or CD/DVD device. 
  • Try both the Recommended and Legacy boot options.  There are different drivers in the Legacy boot mode. 
  • You do not have the necessary network interface card (NIC) drivers to access the network.  Download the appropriate 32-bit drivers from the card's manufacturer website. Contact StorageCraft Technical Support by sending an email to support@storagecraft.com so that these necessary NIC drivers can be included in subsequent builds of ShadowProtect IT Edition.
  • You do not have the necessary storage drivers to access a storage device on the computer. Again, locate these drivers on the manufacturer's website, then contact StorageCraft Technical Support to report these drivers.
  • If you find that the Recovery Environment lacks certain drivers, you can load these storage drivers during boot time. In the Legacy environment, the system prompt's you to press F6 during the boot process to add storage drivers. You will then be prompted to load the driver(s) from a diskette. (Legacy does not support loading drivers from a USB drive or from CD.) The storage drivers must be in the textsetup.oem format for loading into the Legacy Recovery Environment. If you have booted the Recommended (Vista) Recovery Environment, you can dynamically load the required storage drivers by providing the directory where the drivers are located. The driver files for the Recommended Recovery Environment must be Vista or later compatible drivers in the .inf and .sys format.
  • It is a good idea to keep all necessary storage drivers not included with the IT Edition on a diskette (for Legacy) or on a USB drive or CD (for Recommended) that is available in the event you need to boot the ShadowProtect USB or CD/DVD to run the Recovery Environment. 

 

=============================================================
© Copyright 2014 StorageCraft Technology Corporation.  All rights reserved.  This Software and Documentation are copyrighted.  Ownership of the ShadowProtect IT Edition Software is reserved to StorageCraft Technology Corporation.  StorageCraft, the StorageCraft logo and the ShadowProtect IT Edition logos are trademarks of StorageCraft Technology Corporation.  ShadowProtect IT Edition is a trademark of StorageCraft Technology Corporation in the United States and elsewhere. All other brands and product names are or may be trademarks or registered trademarks of their respective owners.

 

7 StorageCraft Cloud Services Release Notes

General Information

Cloud Services is a DRaaS based solution. Partners or resellers automatically receive new updates when logging into their StorageCraft Cloud Services accounts. 

This ReadMe was last updated: August 8, 2017 and contains the latest supplemental information for StorageCraft Cloud Services and the StorageCraft Cloud Services User Guide

Policy Changes

Important: ImageManager 7.0.6 or newer is now required to replicate to StorageCraft Cloud Services. 

 

Note: StorageCraft strongly recommends replicating only the consolidated daily file to the StorageCraft Cloud. There will be a fee for replicating intra-daily files.

Table of Contents

1. Update Information by Product Version

StorageCraft Cloud Services - August 8, 2017

Enhancements
Known Issues 

StorageCraft Cloud Services - May 1, 2017

General (behind the scenes) updates and performance improvements. 

StorageCraft Cloud Services - March 29, 2017

General (behind the scenes) updates and performance improvements. 

StorageCraft Cloud Services - September 20, 2016

Resolved Issues

StorageCraft Cloud Services - August 16, 2016

Enhancements

StorageCraft Cloud Services - June 1, 2016

Enhancements
Resolved Issues
Known Issues 

StorageCraft Cloud Services - April 12, 2016

Enhancements
Resolved Issues
Known Issues 

StorageCraft Cloud Services - November 16, 2015

Enhancements
Resolved Issues

StorageCraft Cloud Services March 24, 2015

Enhancements
Known Issues
Resolved Issues - update to resolved issues June 10, 2015

2. System Requirements
3. Installation Tips
4. Licensing and Service Level Agreements

 

1. Update Information by Product Version
StorageCraft Cloud Services (August 8, 2017)

Enhancements

Known Issues:

 
StorageCraft Cloud Services (May 1, 2017)
StorageCraft Cloud Services (March 29, 2017)
 
StorageCraft Cloud Services (September 20, 2016)

Resolved Issues

 
StorageCraft Cloud Services (August 16, 2016)

Enhancements

 
StorageCraft Cloud Services (June 1, 2016)

Enhancements

Resolved Issues

 
 
StorageCraft Cloud Services (April 11, 2016)

Enhancements

Resolved Issues

Known Issues

  1. Verify that the AD controller address is the same as specified in the DHCP Reservation list.
  2. In Services, Disable the DHCP Server (you do not want two DHCP Servers running at the same time).
  3. From a command prompt enter IPConfig /ALL and verify that the DNS entry is pointing only to itself (i.e. the AD machine)
  4. From a command prompt enter NSLookup on the internal Fully Qualified Domain Name of the AD server. It should look to itself for a response

    After verifying that DNS is functioning appropriately on the AD Controller, and after verifying that the DHCP Reservation is handing out the accurate DNS Server IP info, you can begin recovering your other machines.

 
 
 
StorageCraft Cloud Services (November 16, 2015)

Enhancements

Resolved Issues

  
StorageCraft Cloud Services (March 24, 2015)
Enhancements

Known Issues

Resolved Issues

 
2. System Requirements

Software Requirements

Hardware Requirements

Supported Operating Systems

Windows Server 2012 R2

Windows Server 2012

Windows Small Business Server 2011

Windows Server 2008 R2 Foundation

Windows Server 2008 R2 (32-bit x86 and 64-bit x64)

Windows Server 2008 (32-bit x86 and 64-bit x64)

Windows Small Business Server 2008 (32-bit x86 and 64-bit x64)

Windows EBS Server 2008 (32-bit x86 and 64-bit x64)

Windows Server 2003 (32-bit x86 and 64-bit x64)

Windows Small Business Server 2003 (32-bit x86 and 64-bit x64)

Windows 8.1 (32-bit x86 and 64-bit x64)

Windows 8 (32-bit x86 and 64-bit x64)

Windows 7 (32-bit x86 and 64-bit x64)

Windows Vista Home Basic (32-bit x86 and 64-bit x64)

Windows Vista Home Premium (32-bit x86 and 64-bit x64)

Windows Vista Ultimate (32-bit x86 and 64-bit x64)

Windows Vista Enterprise (32-bit x86 and 64-bit x64)

Windows Vista Business (32-bit x86 and 64-bit x64)

Windows XP Media Center (32-bit x86 and 64-bit x64)

Windows XP Professional (SP2 or above) (32-bit x86 and 64-bit x64)

Windows XP Home (SP2 or above) (32-bit x86 and 64-bit x64)

Important: The new StorageCraft Cloud Services requires ImageManager version 6.7.2. ShadowProtect version 5.2.3 or newer is also required.

 

3. Installation and Setup Tips
4. Licensing and Service Level Agreements

 

Copyright (c) 2017 StorageCraft Technology Corp. All rights reserved.This Software and Documentation are copyrighted.  Ownership of StorageCraft Cloud Services, StorageCraft ImageManager, and StorageCraft ShadowProtect Software is reserved to StorageCraft Technology Corporation.  The StorageCraft logo, StorageCraft Cloud Services logo, StorageCraft ImageManager logo, and the StorageCraft ShadowProtect logo are trademarks of StorageCraft Technology Corporation.  StorageCraft ImageManager, StorageCraft ShadowProtect, StorageCraft Cloud, and StorageCraft Cloud Services are trademarks of StorageCraft Technology Corporation in the United States and elsewhere. All other brands and product names are or may be trademarks or registered trademarks of their respective owners.

 

 

8 StorageCraft GRE Release Notes

General Information

This file contains additional information to supplement the manual.

Granular Recovery for Exchange (GRE)

Last updated: February 7, 2017

 

GRE User Guide

GRE System Requirements

 

Table of Contents

Update Information by Product Version

StorageCraft GRE 8.1.3

Fixed Issues 

StorageCraft GRE 8.1

Enhancements
Fixed Issues
Known Issues 

StorageCraft GRE 8.0

Enhancements
Known Issues 

StorageCraft GRE 8.1.3
Fixed Issues
StorageCraft GRE 8.1
Enhancements
Fixed Issues
Known Issues
StorageCraft GRE 8.0 
Enhancements

Enhanced search functionality

Enhanced settings

Support for drag and drop restoration/migration

ShadowProtect IT Edition Pro

GRE is supported in the following languages:

Known Issues
 

 

Copyright © 2016 StorageCraft Technology Corp. All rights reserved. This Software and Documentation are copyrighted.  Ownership of the ShadowProtect Granular Recovery for Exchange (GRE) Software is reserved to StorageCraft Technology Corporation.  StorageCraft, the StorageCraft logo and ShadowProtect Granular Recovery for Exchange (GRE) logo are trademarks of StorageCraft Technology Corporation.  StorageCraft, ShadowProtect, ShadowControl, and HeadStart Restore are registered trademarks of StorageCraft Technology Corporation in the United States and elsewhere. ShadowProtect Server Edition, intelligentFTP, and ShadowStream are trademarks of StorageCraft Technology Corporation in the United States and elsewhere. All other brands and product names are or may be trademarks or registered trademarks of their respective owners.

9 StorageCraft Recovery Environment Release Notes

General Information

This file contains additional information about the StorageCraft Recovery Environment for Windows (REWIND), Recovery Environment CrossPlatform (RE-X) and the Recovery Environment Builder (REBuilder). The Legacy Recovery Environment is no longer available. This information supplements the content of the Recovery Environment User Guide. Please read all the sections before you proceed with the installation.

This covers up to StorageCraft 32- and 64-bit Recovery Environment for Windows v5.2.7, 64-bit Recovery Environment CrossPlatform v2.2.4 (updated January 5, 2017) and REBuilder v1.1.10 (updated November 22, 2016).

Table of Contents

1. Features/Enhancements
2. Known Issues
3. System Requirements
4. General Usage Notes

1. Features/Enhancements
Recovery Environment for Windows

Recovery Environment for Windows version 5.2.7 (June 2016)

Recovery Environment for Windows version 5.2.5 (July 2015)

Recovery Environment for Windows version 5.2.4 (January 2015)

Recovery Environment for Windows version 5.2.2 (December 2014)

Recovery Environment for Windows version 5.2.0 (July 2014)

Recovery Environment for Windows version 5.0.5 (July 2013)

CrossPlatform

Recovery Environment CrossPlatform version 2.2.4 (January 2017)

  • Improved Localization Strings
  • All BMR drives can be restored from a network location
  • Improved Functionality for HIR's (HIR decode will now appear if SP/SPX not installed)
  • Added ability to print root password "shadowprotect" with command /etc/motd 
  • Added support for Ubuntu 16 restores
  • Added confirm button for "Initialize MBR Disk"
  • Added "Cancel" option to "Format" popup
  • Added LVM Labels for LVM restores
  • Added "Cancel" option for HSR override
  • Added additional Boot repair functionality for Linux restores
  • Corrected issue with "Restore Disk Layout" not handling extended partition correctly
  • Corrected crash if user does not select any "Advanced Recovery Options"
  • Corrected repeatable crash after partitioning during restore
  • Corrected issue with not being able to unmount Images
  • Corrected grub install failure when /etc/mtab is a link to /proc/self/mounts
  • Corrected issue with recovery environment not shrinking image files
  • Corrected an error with not being able to explore .spi files
  • Corrected issue where Image Header Information was blank
  • Corrected an issue that caused a crash if additional files were added to a folder while exploring
  • Corrected an issue with LVM where a partition needed to be created before restoring
  • Corrected an issue where the recovery environment was not booting on EFI enabled machines
  • Corrected issue with partition sizes being incorrect from Image File Header and creating in OS
  • Corrected issue with a crash occurring after wiping disk partitions
  • Clicking "Unmount" in the restore wizard crashes the recovery environment
  • Restoring an image with a long MountPoints entry in the header crashes the recovery environment

Recovery Environment CrossPlatform version 2.2.2 (June 2016)

Recovery Environment CrossPlatform version 2.2.0 (March 2015)

Recovery Environment CrossPlatform version 2.1.1 (August 2013)

Recovery Environment CrossPlatform version 2.1 (July 2013)

REBuilder

RE Builder version 1.1.10 (November 2016)

REBuilder version 1.1.9 (June 2016)

REBuilder version 1.1.7 (July 2015)

REBuilder version 1.1.6 (January 2015)

REBuilder version 1.1.5 (December 2014)

REBuilder version 1.1.4 (July 2014)

REBuilder version 1.1.2 (September 2013)

REBuilder version 1.1 (August 2013)

REBuilder version 1.0 (July 2013)

HIR (Hardware Independent Restore) Decode

If a client is running a restore to dissimilar hardware they will need to use the HIR Configuration to complete the process.  This is a licensed feature of ShadowProtect.  If the HIR Configuration doesn't detect the activation within the image that is being restored the client may be prompted for an "HIR Decode" key.  If the client is using an OEM issued license then they will need to open a support ticket with the license provider for further assistance.

Note: The StorageCraft Recovery Environment for Windows will prompt for an HIR Decode.  The StorageCraft CrossPlatform Recovery Environment does not support that feature and the HIR process will fail.

2. Known Issues

Windows

Recovery Environment for Windows version 5.2.2 (December 2014)

Recovery Environment for Windows version 5.2.0 (July 2014)

Recovery Environment for Windows version 5.0.5 (July 2013)

CrossPlatform

Recovery Environment CrossPlatform version 2.2.0 (March 2015)

Recovery Environment CrossPlatform version 2.1.1 (August 2013)

Recovery Environment CrossPlatform version 2.1 (July 2013)

REBuilder
 
REBuilder version 1.1.7 (July 2015)
REBuilder version 1.1.5 (December 2014)
REBuilder version 1.1.4 (July 2014)
REBuilder version 1.1 (August 2013)

REBuilder version 1.0 (July 2013)

 

3. System Requirements
4. General Usage Notes

Test the StorageCraft Recovery Environment

To do this for Recovery Environment Windows, use REBuilder to create the ISO then::

To do this for Recovery Environment CrossPlatform, download the ISO from the STC website then:

Boot the StorageCraft Recovery Environment using the CD or the USB key. (The system may need to be set to boot from the USB port.)

If the StorageCraft Recovery Environment boots and runs as expected, then you can perform ShadowProtect operations from the Recovery Environment:

If the StorageCraft Recovery Environment does not boot, confirm that:

If these are okay, but StorageCraft Recovery Environment still does not run as expected, you should investigate the following issues:

Be sure to store the Recovery Environment CD or USB key in a safe place for use in the event that you require a bare metal recovery of your computer. In that event, use the Recovery Enviironment CD or USB key to boot the system and restore the required volume(s).

*********************************************************************

Copyright © 2015 StorageCraft Technology Corp. All rights reserved. This Software and Documentation are copyrighted.  Ownership of the ShadowProtect Server Edition Software is reserved to StorageCraft Technology Corporation.  StorageCraft, the StorageCraft logo and the ShadowProtect Server Edition logo are trademarks of StorageCraft Technology Corporation.  StorageCraft, ShadowProtect, ShadowControl, and HeadStart Restore are registered trademarks of StorageCraft Technology Corporation in the United States and elsewhere. ShadowProtect Server Edition, intelligentFTP, and ShadowStream are trademarks of StorageCraft Technology Corporation in the United States and elsewhere. All other brands and product names are or may be trademarks or registered trademarks of their respective owners.

10 ShadowStream Release Notes

This ReadMe contains information to help you understand and use the new StorageCraft ShadowStream product. The readme supplements and leverages information in the user guide.  Take a few minutes to understand the issues before you start the installation.

StorageCraft ShadowStream 6.1.4

Last Updated: June 9, 2017


Table of Contents

1. Update Information by Product Version

ShadowStream v6.1.4

ShadowStream v6.1.2
 
ShadowStream v6.0.12
 
ShadowStream v6.0.8
 
 
ShadowStream v6.0
2. System Requirements (applicable for the current version)

3. Installation Instructions (applicable for the current version)


1. Information by Product Version

ShadowStream 6.1.4 (June 2017)

Fixed Issues

ShadowStream 6.1.2 (July 2016)

Enhancements
Fixed Issues

 


ShadowStream 6.0.12 (December 2015)

Enhancements

Fixed Issues

Known Issues
  • In some situations the uninstall does not close the Admin Console. If you have the ShadowStream 6.x User Admin open when you try to uninstall the product, the user interface may not always close automatically. If this occurs you can manually close the open user interface. This does not affect the uninstall at all.
     
  • This release significantly reduces the chance of a rare ShadowStream crash. However, under extreme conditions there is a chance that the ShadowStream Service may still crash. If this occurs the service will automatically resart.
 

ShadowStream 6.0.8 (July 2015) 
 
Enhancements
Fixed Issues
Known Issues
 

ShadowStream 6.0.4 (March 2015)
 
Enhancements
Fixed Issues

Known Issues

ShadowStream 6.0 (December 2014)
 
Enhancements
Note: When you upgrade to ShadowStream 6.0, it doesn't install over (or update) your existing (legacy) version of ShadowStream. The new ShadowStream is a new (parallel) installation that allows you to run both versions side by side. This makes it easier to migrate your settings from the legacy version to the new version.
Fixed Issues

Known Issues


2. System Requirements


3. Installation Instructions

11 Archive ReadMe - Cloud Backup for Office 365

See Cloud Backup Release Notes for the most recent information about new releases.

 

This page is only for archival purposes. Last Archive ReadMe update: December 1, 2016

 
Purpose of this Archive Page

This document will contain historical ReadMe files for older versions of StorageCraft Cloud Backup.

Note: No archive information is available now because this is the first release of this product.