ImageManager Release Notes (ReadMe)

General Information

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

StorageCraft ImageManager 7.1.0

Last Updated: December 13, 2016

Download ImageManager from the Updates/Downloads page. 

 

Table of Contents

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.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

  • Added the functionality for HSR to create GPT partitions. GPT disks created with HSR contain additional partitions required to support the EFI boot sequence. See HSR for GPT Source Images in the ImageManager User Guide for additional information.
    Important: The new HSR partitions are only present in HSR jobs created in ImageManager 7.0.5 or newer. Jobs created prior to upgrading to ImageManager 7.0.5 do not have the additional partitions.
  • The HSR process for an MBR disk now creates a system partition and the target partition which contains the operating system image. However, this additional system partition is not flagged as bootable and does not change the recovery steps for an MBR HSR.
  • Added functionality so ImageManager no longer displays the error, "Chain contains migration file" during the retention process (if a migration file exists). Instead, files created\consolidated after the VirtualBoot migration file, and files older than those defined in the retention settings will be removed. This functionality was added to support SPX VirtualBoot for vSphere. 
    Note: Files created before the VirtualBoot migration file will not be deleted. This has the potential to leave a large number of files in the chain
  • Added functionality that allows more accurate retention which results in minimum chain length. The retention settings now include a retention value of 1 for all image types.

    Note: If a file is required for consolidation, it will NOT be removed even if the minimum retention is set to 1. This primarily happens with consolidated daily and weekly image files.

 

Fixed Issues

  • Fixed an issue where the Details pane reported the incorrect "Failure Time" when it displayed the consolidation error.
  • Fixed an issue where double-clicking the scroll bar when an activity was highlighted opened the properties window for that activity.
  • Fixed an issue where HSR was displaying error “-5 Access Denied” when attempting to write to vCenter Server. 
 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

  • Added functionality in ImageManager for SSH replication jobs to the StorageCraft Cloud. ImageManager now supports both SSH and SSL replication jobs to the StorageCraft Cloud. 

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
 
  • ImageManager now tries to read the hard drive serial number out of the cloud for customers with machines that can't read the serial number.
  • Added enhancements to ImageManager so that it no longer uses the "sent" table for cloud replication.
  • Enhanced the way ImageManager does its file checking to reduce the number of calls to the cloud by 30%. It now checks to see if the file is a base before checking if the volume has been deleted. This reduces the load on the cloud API.

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."

  • 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.

  • The HSR - Getting error "Can not create partition greater than disk size" (even though the target disk is larger than volume size) when trying to set up the job again to the ESX server.


ImageManager 6.7.2 (March 2015) 

 

Enhancements

  •  ImageManager now has a VMware VIX verbose logging option that allows you to gather more information when ImageManager HSR writes to a VMDK file. The additional logging information is written to the ImageManager HSR log when you enable ImageManager Verbose Logging.
  • Moved all cloud retention settings for StorageCraft Cloud replication jobs from ImageManager to the MSP portal. 
  • New cloud icon for ImageManager Replication Job was added.
  • Added "StorageCraft Legacy Cloud Services" replication type. StorageCraft also changed the Replication Type fields so that "StorageCraft Cloud Services" refers to the new StorageCraft cloud and "StorageCraft Legacy Cloud Services" refers to the old StorageCraft cloud.

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) 2016 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.

 

Terms and Conditions of Use - Privacy Policy - Cookies