Release Note

July 31, 2024

Patch Version 24.7.31.2（July 31, 2024）

This patch Version applies to Version 7.0.3.8919 and 7.0.4.9021.

When this patch is applied, the version will be as follows.

• Agent Version：7.1.0.9188

• Console Version：7.1.0.9188

  When this patch is applied, the default changed block tracking mode is [Tracking Driver Mode].

Added / Updated Features

• ActiveVisor Version 8 is supported.

• Neutrix Cloud Storage is not listed as the default backup destination.

• Wasabi is not listed as the backup destination for File Recovery.

• A recovery point for AWS can be created when using a virtualization adapter.

Fixed Issues

• When a task name includes a double-byte character, the result of an E-mail notification is not correctly displayed.

• When restoring a file by selecting a folder whose name includes a double-byte character, the process size in the task log is indicated as “0.00GB.”

• Multiple incremental backup schedules can be created in Tracking Driver Mode for a volume assigned without a volume letter.

• When an image file size exceeds 16TB, corruption of the image file occurs.

• When the E-mail notification feature is enabled (when the task fails or completes), the HyperStandby task incorrectly sends E-mail notifications of “termination code: 3 (task skip)” with high frequency.

• When a HyperStandby task fails, the E-mail notification does not work correctly.

• When the virtual switch name includes “-“ in vStandby or HyperStandby, the fixed IP is not reflected in the standby VM.

• The data disk is recognized as offline When using HyperRecovery and restoring a HyperBack backup image.

• While running the Replication process as a post-backup process, if the system is restarted, cancel is not recorded in the task log.

• The recovery point is not correctly displayed When [Backup by disk] is enabled, and a certain number of backup files are created.

• When restoring a backup file created by enabling the [Backup by disk] option, the items from the different disks are not correctly restored.

• Volume Recovery does not correctly restore a volume in the RescueBoot boot environment.

• When running a task by executing a command, E-mail notification result is not correctly displayed.

Patch Version 24.4.18.1（April 18, 2024）

This patch Version applies to Version 7.0.3.8919.

When this patch is applied, the version will be as follows.

• Agent Version：7.0.4.9021

• Console Version：7.0.4.9021

  When this patch is applied, the default changed block tracking mode is [Tracking Driver Mode].

Added / Updated Features

• The required drivers can be added to Recovery Media created using RescueBoot, QuickRecovery, or Recovery Media Maker.

• The option to eject the destination tape media after completing the backup is provided.

• The default settings for the following backup options are changed.

  • [Ignore bad sectors] in [Advanced Options] is disabled.

  • [System Volume Information] option is eliminated from [Excluding Files] in [Advanced Options].

• Changed the acceptable setup range for [Limit the maximum load on CPU] in[Preference] - [Default Performance].

• [Next License Authentication] option is now hidden in [License Authentication].

• Changed the method for outputting log records.

  ActiveVisor Version 7.1.1 does not support monitoring of log records of the tasks executed by using this version.

Fixed Issues

• The information of the mounted image is not displayed in Tray Icon.

• The option for detecting disks is disabled in [Preference].

• [The last date/time of successful authentication] is not updated in the License Authentication window.

• A large amount of memory is consumed when backing up a large volume of data to cloud storage.

• Restoring a disk, including system volume, is subject to firmware limitations.

• You can change the compression option settings, among other things, when editing schedule settings from the Schedule link in the Dashboard.

• The cold backup task fails when the used space on the disk of a Windows PE/RE-based boot environment exceeds 3TB.

• HyperStandby virtual conversion process fails.

• Verify or Recovery tasks fail When using a backup image containing a volume for which bitmap information cannot be correctly obtained.

• Retention Policy enabled with File Backup did not function at a specific destination storage.

• A vStandby task for Hyper-V host failed in Error -621, when accessing the Hyper-V host with domain member account.

• When running Virtual Conversion task, accessing Hyper-V host with domain member account failed.

Version 7.0.3.8919 (January 31,2024)

When Upgrading to this version, the default changed block tracking mode is [Tracking Driver Mode].

Added / Updated Features

• While connected to a remote agent in the boot environment, the option to remotely shut down or reboot the connected computer is enabled.

• A remotely connected agent in the boot environment can do the following:
  • Copy disks and volumes
  • Launch the command line interface
  • Configure network settings
• The method for mounting a backup image of a basic disk has been improved. This enhancement has resulted in better performance when copying a large number of items from a backup image that was created using the Data Deduplication Compression option.
  • The backup image of a dynamic disk only supports the traditional mount method.
• Oracle and Google Clouds are now supported.

Fixed Issues

• When attempting to run a volume backup task in tracking driver mode after reinstalling a product following uninstallation and system reboot, the task may fail with an error message (-601).

• During the cancellation of product uninstallation, after rebooting the system, an attempt to run the volume backup task in tracking driver mode fails with the -601 error, which results in rolling back the uninstallation operation.

• During an upgrade, in an environment where a license file is employed for activation purposes, the corresponding license file information does not get transferred.

• When trying to restore more than 31 files/folder from a File Backup image (*.AFB), the recovery task fails in unknown error.

• There was an issue with the Image Manager’s operation as it is unable to access a backup image stored on Amazon S3.

• When using an AES128-encrypted backup image and a password longer than 16 characters, ActiveImage Protector Service may crash when performing the following operations:
  • File Recovery
  • BootCheck
  • HyperRecovery LIVE!
  • P2V Adapter

• The IP settings in the [Network Settings] of the RescueBoot environment are not set

• When attempting to create a recovery media through Recovery Media Maker, the task failed despite the status indicating “Successful”.

• When attempting to move a tape from Actiphy to a different tape pool, Volume Restore Wizard fails to detect the tape.

• When creating a new tape pool and naming it “Actiphy,” the backup process encounters a failure.

• The Destination Isolation Option appears to be ineffective following the completion of the File Backup task.

• When using HyperBack to back up a virtual machine on Hyper-V Server, the RCT process fails.

• When utilizing HyperRecovery for [Restore disk only] to a VMware ESXi host, if the ESXi host has a virtual machine with the same name as the restore source machine, the process won’t succeed.

• When restoring a virtual machine in VMware ESXi using HyperRecovery, the task fails with an error if the virtual machine name is enclosed in brackets.

• When creating a schedule for a remote Linux agent, the advanced settings on the connecting host are provided in the Advanced Settings window.

Patch Version 23.12.8.1 (December 8, 2023)

This patch Version is applicable to Versions 7.0.0.8643 and 7.0.1.8725.

When this patch is applied, the version will be as follows.

• Agent Version : 7.0.2.8821

• Console Version : 7.0.2.8821

  When this patch is applied, the default changed block tracking mode is [Tracking Driver Mode].

Added / Updated Features

• The method of creating backup files is enhanced. The performance of Recovery and Deep Verify processing is enhanced with the backup images created by enabling Data Deduplication Compression option and using this and later versions.

• The option for Recovery Media Maker is now provided enabling to create ISO media without specifying the media size.

• When running RescueBoot selected from Tray Icon, the behavior is reviewed.

• Quick Verify now supports the backup image files created in Actiphy StorageServer by using this or later versions.

• Enhanced the specification of Quick Verify process and reduced the process time.

Fixed Issues

• The process time increased when running Recovery and Deep Verify task by selecting a backup image created by enabling Data Deduplication Compression option and saved in Actiphy StorageServer.

• In some cases, the driver for network interface card used on the system is not added to RescueBoot.

• In the OS configured by using the installation media of English version, the characters in Japanese or other languages are garbled in RescueBoot built with WindowsRE.

• When RescueBoot boots up on a cloud instance where the time zone is changed from UTC, the connection to cloud storage service fails to establish.

• The system failed to boot up on some machine with a recovery media created on an optical disk by using Recovery Media Maker.

• The size of ISO file created by selecting pre-set size by using Recovery Media Maker is too large to write on the optical media of the selected type.

• Image Management operation fails for the backup image file saved in SFTP server which private key is required for authentication to access.

• When using Image Management and browsing a bucket or a folder on Actiphy StorageServer, an unnecessary folder is created.

• When running Virtual Conversion task by selecting a backup image located in a bucket on Actiphy StorageServer which authentication settings are configured, the console crashed.

• The processing size for a File Recovery task is recorded as “0.00GB”.

• When running HyperBack task for a guest machine restored by using HyperRecovery and specifying the virtual machine name or VHD/VMDK name with double-byte characters, the incremental backup process stops to remain at “1.0%”.

• The command prompt does not appear in RescueBoot environment booted from some environments remotely accessed via VNC viewer.

• Backup image file of a volume including 10.7TB or more used space was corrupted.

• When restoring a password-protected backup image file using Image Explorer, the application crashed.

Version 7.0.1.8790（November 22, 2023）

This version is released as ActiveImage Protector IT Pro.

Fixed Issues

• After performing Virtual Conversion by using EXE file and adding the required driver, when trying to perform the same process again without system reboot, unknown error occurred.

Patch Version 23.10.19.2（October 20, 2023）

This patch is applicable to Version 7.0.0.8643.

When this patch is applied, the version will be as follows.

• Agent Version：7.0.1.8725

• Console Version：7.0.1.8725

  When this patch is applied, the default changed block tracking mode is [Tracking Driver Mode].

Added / Updated Features

• After creating a backup image file by using HyperBack, scripts are executable with HyperAgent.

• [Move the tape media back to the slot after completing the backup] option is now provided.

• VMware vSphere ESXi 8.0 U2 is now supported.

• A temporary file is created in File Backup process.

• You can now configure the authentication settings to access a bucket on Actiphy StorageServer.

• When selecting [Move to slot], [Move to pool], [Erase] or [Rescan] in [Tape Manager], the tape media after the processing is moved to an empty slot (if no available slot, move to mail slot).

• Network connection is available in RescueBoot boot environment built on VM instance of Google Cloud Compute Engine.

• The environment restored and booted by using QuickRecovery feature can be connected via VNC.

Fixed Issues

• When selecting Actiphy StorageServer as backup destination and enabling [Split image into xx MB files], the consolidated file is not split.

• The History records for hypervisor is not saved with HyperRecovery.

• When restoring a backup image file of multiple virtual machines created by using HyperBackup, the restore task failed with [Unknown AIP error].

• When running HyperRecovery LIVE! task to restore a backup image file of multiple virtual machines created by using HyperBackup, the virtual machine in restore process may not normally boot up.

• [Limit maximum CPU load] is not working.

• ReZoom IT! does not detect a backup image file that includes a virtual machine with a check point.

• When a tape device is selected as the backup destination and incremental backup file is created by selecting Tracking Driver mode, the size of the created incremental image file is the same as full backup image file.

• After upgrading from Version 6.5.2 to 7.0.0, full (base) backup is not created by running a volume backup task according to the migrated incremental backup schedule.

  The incremental backup task executed after applying this patch creates full (base) backup image file.

• Network connection is not available in boot environment booted by RescueBoot on the instance using the following NIC on AWS.
  • Amazon Elastic Network Adapter
  • Intel 82599 Virtual Function

• When Reconcile task runs and incremental backup file is created, the subsequent incremental backup task fails in Error -603.

• When a backup task fails due to VSS error, conhost.exe continues to remain and desktop heap limitation is caused.

• Backup task for AIP agent installed on Hyper-V host crashes on rare occasions.

Version 7.0.0.8643 (September 7, 2023)

Added / Updated Features

• Tracking Driver is now provided to support change tracking.

• Actiphy StorageServer is now provided.

• Image file format is changed. Image Version is [302].

• QuickRecovery feature is now provided.

• The method of building RescueBoot is enhanced. On the system that does not include Windows RE, the use of Windows ADK enables to build RescueBoot.

• Recovery Media Maker feature is now provided. ** Server 2012 R2 is not supported.

• FCD (First Class Disk) is now supported.
  ** Stand-alone disk is not supported.

• Safe-mode operation is now supported.

• The backup default setting is changed as follows:

  • Standard Compression -> Data Deduplication Compression
  • [Make backup image file P2V ready] option is enabled.

• VMware vSphere 8 is now supported.

• You will be prompted to enter the pre-defined password when deleting a password-protected backup file in Image Manager.

• By default, Neutrix Cloud Storage is now supported to select for the destination storage. The following features do not support the backup files saved in Neutrix Cloud Storage.

  • BootCheck
  • Mount Image
  • Image Target Server
  • HyperStandby
  • HyperRecovery LIVE!
  • Virtualization
  • Virtualization adaptor

• NIFCLOUD’s new service [Object Storage Service] is now supported.

• DropBox short-term access tokens is now supported.

• The method of restoring an incremental backup is enhanced.

• Even in the environment where [Remote Console] was disabled when installing the product, remote console is available to operate RescueBoot boot environment.

• Backup data compression method used in backup process is enhanced.

• Erase feature for tape media is now provided.

• vStandby now supports both virtual host and guest.

Fixed Issues

• Authentication to access Dropbox failed for Replication of Post-backup Process.

• [exception (0xc0000005)] error occurred and backup task terminated with Exit code -701 and failed in error.

• aip.log causes the launched AIP console to hang up.

• Recovery task, running on Windows PE/RE-based boot environment, does not gain the percentage of progress from around 95% and not complete.

• The information of a virtual machine running on hypervisor host is not transmitted to activation server. Activation failed in [Product not in Network ID whitelist] error.

• E-Mail notification to Microsoft 365 failed in error.

• Exit Code -403 error is not listed in Task Log on AIP console.

• File Backup program crashed and did not normally terminate.

• In-Cloud Recovery to MS Azure failed.

• Activation of AIP fails when installed with virtual guest key and when the following conditions are satisfied.
  • Windows is installed on virtual machine by using OEM media.
  • 2 or more NICs are present and the 1st NIC is disabled.

• The process size of File Backup task is not correct.

• Depending on the product key used to install the product on remotely connecting computer, the information of the remotely connected computer is not correctly displayed.

• Double-clicking on a folder on the right-pane in File Backup window, “wait for response” occurs.

• After backup source partition size is changed, incremental backup chain is continued.

• When backing up a large volume disk, backup image file is corrupted.

• After virtualization \ restoring a backup image file of Windows Server 2008 R2 by using HyperRecovery, OS does not boot up.

• When execution of a task failed under one of the following conditions, the task result is not recorded in Task Log in Dashboard on AIP console.

  • A task is executed while RDX is ejected.
  • When enabling Destination Isolation Option and selecting [Eject the destination USB hard disk after completing the backup] option, the subsequently scheduled backup task starts while the removable USB remains to be ejected.

• Installation of AIP failed in the environment where Virus Buster is installed.

• When creating a volume from a snapshot converted from incremental backup by using In-Cloud Standby and attach the volume to the instance, the system failed to boot up.

• File Recovery does not support disk based backup image files.

• Error processing of File Backup is not properly performed.

• When restoring a backup image file connected to multiple disks by running HyperRecovery - [Restore disk only] task, only the system disk is restored.

• When the HyperBack settings are configured and migrated in Hyper-V cluster environment, backup task failed.

Patch Version 22.9.8.1 (September 8, 2022)

This patch is applicable to Versions 6.5.0.7616 and 6.5.1.7720.

When this patch is applied, the version will be as follows.

• Agent Version : 6.5.2.7778

• Console Version : 6.5.2.7778

Added / Updated Features

• The default value [Copy] is set for the backup type of recovery check point created by running HyperBack for the virtual machines configured on Hyper-V host.

Fixed Issues

• When ESXi in vCenter is registered, HyperRecovery task for ESXi failed in error.

• The incremental backup image after changing the host name is not displayed when using restore / mount feature.

• A series of operations failed to run File Recovery task by using a backup image saved in Wasabi.

Patch Version 22.8.22.6 (August 23, 2022)

Fixed Issues

• Downloading the update files detected by selecting [Check Update] failed.

Patch Version 22.7.26.3 (July 26, 2022)

When this patch is applied, the version will be as follows.

• Agent Version : 6.5.1.7720

• Console Version : 6.5.1.7720

Added / Updated Features

• Wasabi is now supported to select as the destination saving the backup files. The following features do not support using the backup files saved in Wasabi.

  • BootCheck
  • Mount Image
  • Image Target Server
  • HyperStandby
  • HyperRecovery LIVE!
  • Virtualization
  • Virtual Adapter

  The following features do not display Wasabi as the destination saving backup files. Before using backup files located in Wasabi, please select Amazon S3, go to [Enter Provider] - [Add New Target] and select Wasabi.

  • In-Cloud Recovery
  • In-Cloud Standby

• When SFTP is selected as the destination for saving backup images, Replication is now supported to execute as Post-backup Process.

• Recovery points can be selected by specifying dates.

Fixed Issues

• Console menu is not correctly displayed.

• RescueBoot does not boot up on the virtual machine using uEFI configured on Citrix hypervisor.

• Credential information for accessing destination storage is not ported to RescueBoot boot environment.

• When copying a disk or a volume and if exFAT volume is included in copy source disk, the copied disk does not include exFAT volume.

• When using Virtual (HyperAgent) edition and when backing up a virtual machine configured on ESXi host by using HyperBack, license error may occur.

• When selecting USB HDD as the destination saving backup files, if Destination Isolation option is enabled by selecting [Make destination Local Hard disk Offline post backup], the second and the subsequently executed backup tasks fail.

• When selecting Destination Isolation option, [Disable destination Network Connection post backup] option may not work.

• When a large amount of incremental backup files exist, recovery points may not be correctly displayed.

• When [Force script execution] option is disabled in Advanced backup setting and execution of a script before / after the snapshot is taken fails in error, [Script to execute after image creation] runs.

• Virtualization using a backup image, when virtualizing multiple disks to Hyper-V host, virtualization of the second or later disks is not correctly performed.

• When using vStandby and selecting vCenter as the conversion target, Add NIC fails and the task cannot be created.

• When Mirror-configured dynamic volumes are corrupted, restoring backups failed (you have to take backups again).

• When a large amount of incremental backups exist between the selected recovery point and the base backup, the processed size is not correctly indicated in the log record of the executed recovery task.

• When editing existing schedule and changing the destination for saving backup images, post backup process does not work.

• Backup tasks created by using Version 2018 or earlier and configured by enabling [Backup by disk] are not properly displayed.

• When displaying a backup task configured by enabling [Backup by disk] on console, the disks are listed in the inverse order of the original.

• Following issues of HyperRecovery

  • When restoring a backup of Windows virtual machine using uEFI boot and configured on VMware vSphere to virtual machine configured on Hyper-V host, the virtual machine is restored as the first generation guest machine.

  • When restoring a backup of Linux virtual machine using uEFI boot and configured on Hyper-V to virtual machine configured on VMware vSphere, the virtual machine uses BIOS boot.

• When selecting SFTP as the destination saving backup files and accessing SFTP server by using Private Key, HyperBack task fails in -459 error.

• Image Manager operation for backups saved in SFTP, when accessing SFTP server by using Private Key, fails in -459 error.

• When selecting the respective files in shared folder as the backup source, if double-byte characters are used for specifying a file name, execution of the backup task fails.

• When restoring MBR disk to enlarged size by enabling [Restore Disk Signature] option, the task fails in Error -999.

• When using Virtual (Guest) key and character strings of BIOS are reflected to a virtual machine on ESXi or Citrix Hypervisor (XenServer), authentication fails.

• When executing HyperBack tasks for backing up multiple virtual machines in parallel, the backup process may fail in -701 error.

• When Weekly scheduled backup task is executed, the subsequently scheduled task is indicated as ‘N/A’ and does not run.

Version 6.5.0.7616 (May 24, 2022)

Added / Updated Features

• The following features are additionally provided.

  • In-Cloud Standby Snapshot feature enabling to take snapshots for Standby VM on cloud (Amazon EC2 and Microsoft Azure)

  • HyperRecovery LIVE! Restore feature enabling to restore a backup image as VM on hypervisor while the system is up and running.

  • File Exclusion for File Backup and Backup Network Shared Folder Excluding Files setting can be configured for File Backup and Backup Network Shared Folder feature is provided.

• Enhanced Tape Manager feature.

• In-Cloud Recovery supports backups accessible from appliance on cloud.

• The following hypervisors are additionally supported as the activation target by using Virtual license Guest key.

  • Citrix Hypervisor

  • Proxmox VE

  • Nutanix Acropolis

• Cancel / roll-back operation is enabled while upgrading between 2022 versions.

  Cluster edition does not support cancel / roll back operation while upgrading.

• Enhanced RescueBoot feature

  • When booting in RescueBoot, VNC Viewer can be used for remote operation.

  • Shortcut icon can be created on desktop for immediately booting up RescueBoot environment.

• The use of ppk file of Version 3 enables to establish the connection with SFTP server.

• Hidden folder is supported to specify as the destination for saving created backup files.

Fixed Issues

• When a specific preferred language and area are selected to configure the system setting, “Extract Drivers failed:1 is not a supported code page.” message is displayed and installation fails.

  When you have this problem but continue retrying installation on the same computer, please run Setup.exe by selecting “Run as administrator”.

• When tape drive is powered on again, the backup task failed in error -640 error.

• When tape media is replaced in tape drive, the backup task failed in error -640 error.

• When restoring the second generation Linux system as a new virtual machine by using HyperRecovery, the virtual machine is created as the first generation.

This version is not available with IT Pro edition.

Patch Version 22.3.14.3 (March 15, 2022)

When this patch is applied, the version will be as follows.

• Agent Version : 6.0.2.7482

• Console Version : 6.0.2.7482

Added / Updated Features

• ActiveVisor Version 7 is now supported.

• When booting RescueBoot, you are prompted to enter the computer name on which RescueBoot was created, and IP address to configure the settings.

Fixed Issues

• Some of Amazon S3 compatible storages are disabled to use.

• Restore operation is unstable in Windows PE/RE-based boot environment.

• When running BootCheck task, access authentication to Hyper-V fails if using domain account’s credential information.

• Virtual conversion fails when using encrypted backup file.

• Restore disk using 4k sector drive image fails.

Patch Version 22.1.25.3 (January 26, 2022)

When this patch is applied, the version will be as follows.

• Agent Version : 6.0.1.7411

• Console Version : 6.0.1.7411

Added / Updated Features

• When registering a hypervisor in Virtual Edition (HyperAgent), the registered hypervisor will be the target hypervisor in HyperBack.

• History of File Backup task execution is recorded in Windows Event Log.

Fixed Issues

BootCheck

• Booting BootCheck from Image Management failed.

• When selecting a virtual machine configured on Hyper-V on remote computer as backup source by using HyperBack and enabling BootCheck on the Hyper-V host as the post-backup process, BootCheck task failed in Error-571 upon completion of incremental backup process.

HyperBack

• When selecting the hypervisor host registered by specifying with [This Computer], the error message [Connection error!…] is displayed and you may not be able to select a guest machine.

HyperStandby

• When Hyper-V is selected as target host:
  • HyperStandby task using an incremental backup failed in error -701.
  • HyperStandby task using a backup created by enabling split-images option (CHNK image) failed in error -999.

• When selecting storage server for the target and “Microsoft (VHD/VHDX)” for Convert Type, the HyperStandby task failed in Error -701.

• HyperStandby task using backup created by enabling split-images option (CHNK image) failed in Exit Code: -439.

• When selecting ESXi for the target and using backup of 32-bit system, adding NIC driver failed.

Virtual Conversion

• Virtual Conversion task using backup created by enabling split-images option (CHNK image) failed in Exit Code: -439.

• When selecting ESXi for the target and using backup of 32-bit system, adding NIC driver failed.

• Convert from Disk task enabling [Create virtual disk only] option, when selecting network shared folder as the destination, failed with Exit Code: -403.

• Convert from Image task using the backup image of Windows system by selecting a datastore on ESXi hypervisor as the conversion target, the default value for OS was not correctly configured.

File Backup

• Cancel task fails.

• File Backup task, when Azure is selected as the destination, fails in unknown error.

• When the system file is selected as the backup source, incremental backup task, after system restart, may fail in some cases.

• E-Mail Notification option cannot be enabled.

Recovery

• Recovery of dynamic discs is disabled.

• When mounting a backup image for File Recovery, a drive letter that cannot be used with robocopy is allocated and File Recovery fails.

Image Manager

• Verify task for agentless backup image created by using HyperBack fails.

• When selecting a recovery point of Amazon S3 compatible storage, unwanted menu is displayed.

Others

• Unwanted log information regarding MSPAgent is continually recorded.

• When browsing network shared folder in P2V adapter wizard, the service crashed.

• When Hyper-V is selected as target host to replicate virtual standby machine by using vStandby, if [Always keep 1 boot point] option is enabled, the task failed in Exit code: 32774.

• When enabling Replication and selecting WebDAV as the replication target, replication of 2048MB or larger backup image failed.

• [Shutdown / Reboot] event-triggered backup task did not normally behave on Windows 10 or later Home Edition.

• When the size of backup source disk is not integer in In-Cloud Recovery, the default value of the restored disk size is configured by truncating the decimal numbers.

• In some cases, backup task, when selecting LTO tape device as destination storage, failed in Exit Code: -640.

• In the installed Image Explorer, double-clicking a file backup image did not display the contents.

  This fix will be applied after restarting the system or Windows Explorer.

• When Amazon S3 compatible storage is selected as the backup destination or replication target, the value for Region cannot be set to empty.

• networkuser command does not run.

Version 6.0.0.7343 (December 21, 2021)

Released as IT Pro.

Added / Updated Features

• When the backup source and the destination is specified same as the preceding backup, incremental backup is now supported.

Version 6.0.0.7292 (November 12, 2021)

Please make sure you have the Version 2022 product key for installing Version 2022 and upgrading from Version 2018. For more detailed information, please contact Actiphy and speak with a sales rep. Upgrading to 2022 is limited from v5.1.11.6326 only.

Added / Updated Features

• Updated image file format. The image version is [301].

• Changed file naming convention for the image files created by execution of backup task.

• Implemented the following features.

  • Cloud Direct saves the created backup image files directly to cloud storage (Amazon S3 and Microsoft Azure), SFTP server.

  • Restore a backup image file saved / replicated in cloud storage (Amazon S3 or Microsoft Azure) to a virtual machine configured in the cloud environment

  • Backup feature supporting tape media as the destination storage and tape management feature

  • Create an MD5 file for the created backup image

  • Quick Verify (checks if internal tampering of backups has occurred.)

  • Extended Disk and Volume Copy

  • File Backup

  • Image Target Server

  • RescueBoot Builder
    Boot Environment Builder is integrated in Actiphy Boot Environment Builder

  • The stability of the operation and process speed are enhanced for the following features.

    • BootCheck

    • HyperRecovery

    • HyperStandby

    • Image Target Server

    • P2V Adapter

• The installer is improved so that MSI file can be generated for installing components.