BOBcloud Pro and Your Storage (Ahsay) backup software change log


#1

Special note from Ahsay - https://www.ahsay.com/jsp/en/home/index.jsp?pageContentKey=ahsay_products_backup-software_whats-new&location=topbar

Refer to this link for more information about the OS’ and databases you can backup Link

Refer to this link for more information about the models of Synology devices you can backup link


Ahsay™ Cloud Backup Suite, v7.17.0.50 (rolled out in November 2018)

AhsayOBM is a server OS
AhsayACB is a desktop OS

Please update your device(s) if they require one of the fixes shown below. It isn’t necessary to upgrade if you aren’t experiencing any issues.

The update can be downloaded from the reseller portal

Limitations / Known issues of this version

Backup / Restore

  1. For MSSQL/MS Exchange (Server)/Lotus Domino/Oracle backup sets upgraded from v6 to v7, a database backup (with in-file delta, if in-file delta is enabled) will be performed in the first backup job after the upgrade.
  2. AhsayOBM is not able to backup SQL databases with special characters for MS SQL Backup Set in ODBC mode.

Note
Best effort support is provided for Windows Xp and Windows 2003 in v7.

Enhancements

Misc.

  1. Office 365 Exchange backup performance tuning (ref: XKA-505-12590, PPB-581-61654, T-20768)
  2. Office 365 Exchange backup source listing performance tuning (ref: T-16274)
  3. Add restore filter for Office 365 Exchange Run on Server backup set (ref: T-19869)
  4. Improve Backup Performance on CBS Run On Server Backup Set (Office 365 & Cloud Backup) with Windows Defender ON (ref: T-21774)
  5. NAS / Synology OBM. Support on TS431 Pro (Arm 32 bit) (ref: QVC-611-15673, T-22339)
  6. Support of QNAP Module (ref: T-21628)
  7. Support CA DigiCert Global Root G2 cert (ref: IEY-325-28755, XGG-728-22174, QVX-327-27408, T-21632)
  8. Multi-Domain (SAN) Certificates (ref: MNZ-669-87181, CCO-917-34745, T-19704)
  9. Better tool tip text shown to explain “User Group” during Add New User wizard in CBS (ref: T-17710)

Backup Destination

  1. Support of new Aliyun Bucket Regions - China North 5 (Huhehaote), Asia Pacific SE 3 (Kuala Lumpur), Asia Pacific SE 5 (Jakarta), Asia Pacific SOU 1 (Mumbai) (ref: LJR-148-61911, T-21596, T-19746, T-21047)
  2. Support new Amazon S3 Regions - EU (Paris) (ref: T-19913)
  3. Backup upload to MS Azure blob storage is being timed out on customers with slow internet lines (ref: VAQ-359-80177, JPH-105-78694, NOJ-520-91751, OMP-528-22469, NCH-442-56786, T-21959)

Operating systems

  1. Support of FreeBSD 10.4, 11.1 and 11.2 (ref: T-18929, T-21738)
  2. Support of Ubuntu 18.04LTS (ref: T-21364)

Bug fix

  1. Unable to handle ‘’ and ‘/’ characters in Cloud Files Backup of Google Drive (ref: EAR-468-30240, BFA-204-98726, DEE-376-35601, T-21656)
  2. Unable to list Google Cloud Storage source files under folder name with space when creating cloud file backup set via CBS/OBM (ref: T-20729)
  3. Fails to backup to Azure through Proxy (ref: DQP-199-95631, T-20877)
  4. Cloud File Backup cannot list FTP files and directories (ref: WEQ-686-74107, JEO-113-88484, T-21034)
  5. Public folder content is not shown in Office365 backupset (ref: VJZ-865-43484, T-21107)
  6. Unable to restore Cloud File Backup to alternative SFTP location with “socket is not established” error (ref: PVY-106-98577, T-21620)
  7. Unable to list mails of Office 365 Exchange Online Backup Set on CBS web console if a folder contains mail WITHOUT sender (ref: T-21884)
  8. Change to show display path (decoded path) for Google Drive Cloud File Backup with the path contains “/” (ref: EAR-468-30240, T-21735)
    When performing Oracle backup via AhsayOBM encounter “Validation of archive log failed” messages (ref: BIG-215-43896, T-18636)
  9. Unable to generate delta using CBT for Hyper-V Backup Set…“The number of CBT log files do not match the number of virtual machine 's preferred owners.” (ref: UMS-656-73562, T-20632)
  10. Failed to generate delta file for Hyper-V Backup Set by using CBT. Reason = “Fail to parse offset -1 and the backup takes long time to complete” (ref: GBU-481-45485, T-22125)
  11. After deleting folder/file in mapped drive/network location backup source, error shown when doing back up (ref: T-22148)
  12. Users data will be deleted unexpectedly while performing two “move user home” actions simultaneously (ref: UWD-528-34171, T-21316)
  13. OBM/ACB is not able to perform schedule backup after the password is changed (ref: T-21352)
  14. “Client host quota exceed” error occurred even if client host quota is still sufficient (ref: NDQ-755-44173, GLO-858-97443, PCU-361-30771, YAF-698-50378, TMR-501-99550, T-21448)
  15. Unable to restrict user from adding new backup set / backup user when CBS has no client license available (ref: OYA-642-66138, WQS-468-14836, RRB-540-46507, FHJ-627-28466, T-21597>
  16. Invalid owner field in users.xml when created backup set by OBM v6 (ref: T-19667)
  17. Some help pages on CBS [Backup / Restore] > [Basic] is redirected to WRONG help page due to addition of the [Quota] Help page (ref: T-21813)
  18. Mis-alignment between CBS and OBM restore to alternate location UI causing users are able to use invalid path/filename (ref: T-14681)
  19. Cannot remove backup source/deselected source of backup sets on CBS (ref: MDX-945-47607, T-22056)

Others
Users are not able to add/update Custom Schedule when passing Integer values for “Year”, “Month” and “Day” to AddSchedule.do / UpdateSchedule.do API.

Refer to this link for more information about the OS’ and databases you can backup Link

Refer to this link for more information about the models of Synology devices you can backup link


Ahsay™ Cloud Backup Suite, v7.15.6.55 (rolled out in October 2018)

AhsayOBM is a server OS
AhsayACB is a desktop OS

Please update your device(s) if they require one of the fixes shown below. It isn’t necessary to upgrade if you aren’t experiencing any issues.

The update can be downloaded from the reseller portal

Limitations / Known issues of this version

Backup / Restore
For MSSQL backup sets upgraded from v6 to v7 (ODBC mode), a FULL database backup will be performed in the first backup job after the upgrade.
AhsayOBM is unable to backup SQL databases with special characters for MS SQL Backup Set in ODBC mode.
Hyper-V VMs with a Paused state will be restored as OFF state for Hyper-V Backup on Hyper-V 2016 Server.

Others

Users are unable to add/update Custom Schedules when passing Integer values for “Year”, “Month” and “Day” to AddSchedule.do / UpdateSchedule.do API.

Note

Best effort support is provided for Windows Xp and Windows 2003 in v7. The behaviour of the Auto Update feature is updated to allow upgrading OBM installed on Windows XP and Windows 2003 to upgrade to v7.

This release will contain the major features listed below

AhsayOBM / AhsayACB

  1. Bug fix - Fail to run VMware backup with erro “[erro] Skip backing up Virtual Machine”
  2. Bug fix - OBM crashes when running Exchange 2016 Database backupset
  3. Bug fix - Empty error message displayed when selecting the MSSQL database as backup source
  4. Bug fix - Skip backup / restore pass-through disks of VM with pass-through disk attached for Hyper-V backup
  5. Bug fix - VM backup encounter “Backup Failed. Virtual Machine = “Alberta Datacenter/Discovered virtual machine/MILKSHAKE””
  6. Bug fix - Hyper-V 2012 R2 backup encountered “Attempting to perform the InitializeDefaultDrives operation on the ‘FileSystem’ provider failed.” error
  7. Bug fix - Fail to run MSSQL backup with error “The SQL Server version and the version of Backupset doesn’t match”
  8. Bug fix - Fail to backup data from NAS after Windows 10 patch 1803 update
  9. Bug fix - VMware workstation backup got Skip backing up Virtual Machine xxx., Reason = “Shared VM is not supported to backup on current host” after upgrade

File backup

  1. Bug fix - Cannot backup files on network drive with folder named “#…” in its upper directory
  2. Bug fix - OBM could not reorder the backup destinations in both Concurrent Backup mode and Sequential
  3. Bug fix - Local destination was counted by backup quota

Restore / Decrypt

  1. Bug fix - VM restore having “[RestoreRunDirectVmUtils.publishVm] vmx file not found” error message
  2. Bug fix - VMware settings restore with error "Failed to restore “xxx”. Reason = “Item is not creatable”
  3. Bug fix - Failed to restore VM backup with error “Failed to obtain inputstream”
  4. Bug fix - MSSQL restore fails with “Backup file is corrupt”

Enhancement

Added Germany Azure cloud storage as a destination

Ahsay’s change log

Ahsay’s future roadmap


Ahsay™ Cloud Backup Suite, v7.15.4.41 (rolled out in May 2018)

AhsayOBM is a server OS
AhsayACB is a desktop OS

Please update your device(s) if they require one of the fixes shown below. It isn’t necessary to upgrade if you aren’t experiencing any issues.

The update can be downloaded from the reseller portal

Limitations / Known issues of this version

  1. For Exchange Mail-Level backup sets upgraded from v7.15.2.2 (or below) to v7.15.4.10 via auto upgrade, users are required to launch OBM GUI to perform a manual backup or browse to the backup source page of the Exchange Mail-Level backup set, and accept the update of “MapiWrapper.exe”/“MapiWrapper2010.exe”. Otherwise, schedule backup jobs for Exchange Mail-level backup sets will not be able to start up.
  2. AhsayOBM is not able to backup SQL database with special character for MS SQL Backup Set in ODBC mode.
  3. Hyper-V VMs with “Paused” state will be restored as “OFF” state for Hyper-V Backup on Hyper-V 2016 Server.

Note

Best effort support is provided for Windows Xp and Windows 2003 in v7. The behaviour of the Auto Update feature is updated to allow upgrading OBM installed on Windows XP and Windows 2003 to upgrade to v7.

This release will contain the major features listed below

AhsayOBM / AhsayACB

  1. Enhancement - Removed unsupported VMware version from the new backup set on OBMv7
  2. Enhancement - MSSQL backup log statement “Skip backing up xxx (Database is offline)” should be shown in warning type
  3. Bug fix - Office365 backup “[Bptree.KeyRangeIterator.hasNext] Error=[ExchangeStandardFolder.getOrdinal] Invalid ID: 14tknLeaf=[TreeKeyNode.toString]” error
  4. Bug fix - Fail to run Cloud File Backup with error “Error=[d] DropboxManager.newFolderIterator”: unexpected HTTP status code: 500 or 502
  5. Bug fix - Cannot create cloud file backup (FTP) backup-set with Sharefile FTP backup
  6. Bug fix - Hyper-V 2016 schedule backup error “Failed to take VM recovery checkpoint. Error = Object reference not set to an instance of an object”
  7. Bug fix - Hyper-V cluster 2012 backup “Unable to generate delta using CBT"The number of CBT log files do not match the number of virtual machine’s…”
  8. Bug fix - Exchange 2010 server backup with error “Cannot start shadow copy, reason =null”
  9. Bug fix - MS SQL Log backup gets “[Microsoft][ODBC SQL Server Driver][DBMSLPCN]SQL Server does not exist or access denied.” error after upgrade
  10. Bug fix - MS SQL Restore incorrectly due to wrong delta files merging
  11. Bug fix - OBM Hyper-V 2012 backup with “Failed to generate delta file by using CBT. Reason = Log sequence incorrect…”
  12. Bug fix - MySQL backup gets mysqldump: [Warning] Using a password on the command line interface can be insecure error
  13. Bug fix - MSSQL VSS backup always run with “The reference database is mismatched with backup database, backup will run in full backup type”
  14. Bug fix - VMware ESXi Restore "[Restorer.run] Path=xxx.vmdk Throwable= [F] [SFtpManager.getOutputStream.$1.close()] Failed to close ‘xxx.vmdk’ ERROR
  15. Bug fix - OBM 7.15.2.2 causes Java crash on Windows 2012 ShadowProtect MSP 5.27 backup jobs
  16. Bug fix - Hyper-V 2012 backup with Failed to generate delta file by using CBT. Reason = Offset to change: xxx is over the disk size yyy
  17. Bug fix - Hyper-V 2016 backup is stuck at downloading file list
  18. Bug fix - OBM create Hyper-V 2016 (Failover Cluster) backupset get error “Temporary directory must set to remote share or cluster shared volume”
  19. Bug fix - Hyper-V Restore error Delta file is corrupt ([DeltaFileMerger.process] Error=[DeltaUnit.readUnit][IOException]
  20. Bug fix - Fail to perform auto update until restarting the service/machine after AUA is not able to download index.xml from CBS
  21. Enhancement - Force to run a simple DIC before backup if the destination is AmazonS3 + GCS and the backup data is backed up by OBM v7.11.0.20
  22. Bug fix - Error "[d] Failed to access destination “OneDrive_droguerie” is shown when backing up to OneDrive for Business
  23. Bug fix - Fails to access predefined OpenStack destination after renewing the token
  24. Bug fix - Build process failed and Download Logs returned “[Error]Invalid file 'C:\Program Files\AhsayCBS\system\cbs\Installers\ROOT\obc-log.zip” error
  25. Bug fix - Cannot restart the Ahsay Online Backup Manager Services with error 1067
  26. Bug fix - Granular Restore failed with “Fail to Install Virtual File System Driver” and “Fail to install VMDK Mounter Driver” errors
  27. Bug fix - [Shadow Copy] The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.
  28. Bug fix - Unable to run schedule backup after updated the user password in Windows Active Directory
  29. Bug fix - File backup encounters “Failed to delete …because it is not empty. One of the existing files is…” error even with hotfix applied
  30. Bug fix - File backup error “The service cannot be started, either because it is disabled or because it has no enabled devices associated with it”
  31. Bug fix - ACB backup set index are negative number
  32. Bug fix - Backup gets “[ObsManager.logStartBackup] Failed to log start backup …” error
  33. Bug fix - Fail to start the OBM GUI on Windows 10 version 1703 with GodMode enabled
  34. Bug fix - Synology OBM prompts for encryption key for backup set with no encryption when performing restore on other NAS
  35. Bug fix - Synology OBM cannot create new backup set with “Failed - Error occured, please try again.” message and invalid XML error in console.log
  36. Bug fix - Hyper-V Backup Status and reports show “Missing Virtual Machine” which do not align with OBM backup logs
  37. Bug fix - Unable to retrieve MAC address when uploading backup log
  38. Bug fix - VMware restore job cannot be stopped properly when some files failed to upload when restore non-VDDK VM to ESXi server
  39. Bug fix - Restore of MSSQL encounters “Parameter is incorrect” issue
  40. Bug fix - User data restored but cannot be used due to error in index migration by XML rebuild
  41. Bug fix - File backup not does not run post-command when it is stopped by scheduler

Ahsay’s change log

Ahsay’s future roadmap


Ahsay™ Cloud Backup Suite, v7.15.2.2 (rolled out in March 2018)

AhsayOBM is a server OS
AhsayACB is a desktop OS

Limitations / Known issues of this version

  1. AhsayOBM is not able to backup SQL databases with special characters for MS SQL Backup Sets in ODBC mode.
  2. Hyper-V VMs with “Paused” state will be restored as “OFF” state for Hyper-V Backup on Hyper-V 2016 Server.

Note

Best effort support is provided for Windows Xp and Windows 2003 in v7. The behaviour of the Auto Update feature is updated to allow upgrading OBM installed on Windows XP and Windows 2003 to upgrade to v7.

This release will contain the major features listed below

AhsayOBM / AhsayACB

  1. Bug fix - Cloud File Backup to Google Drive get “[GDriveManager.getInputStream] Target is not a file, sParent=” error (ref: OXA-535-15212, T-17938)
  2. Bug fix - Better error message for issue(s) encountered when restoring Hyper-V VM to alternate host (ref: T-19446)
  3. Bug fix - Cloud file backup with OnedriveForBusiness files is failed with “429 TOO MANY REQUESTS” (ref: XZY-305-35378, KFI-130-96095, T-19747)
  4. Bug fix - Lotus Database backup set with error “The file name, directory name, or volume label syntax are not correct.” (ref: IRT-381-71062, T-19573)
  5. Bug fix - Unable to perform Hyper-v 2012R2 Granular restore with "Fail to install “Virtual File System Driver” error (ref: JZY-332-68909, T-19501)
  6. Bug fix - MSSQL Log backup runs with “The reference database is mismatched with backup database, backup will run in full backup type” (ref: IWN-195-10058, T-19581)
  7. Bug fix - MSSQL backup shows “Instance is offline” warning even if the database is actually online in MSSQL management studio (ref: YTC-177-43143, TXZ-756-61699, VAQ-580-52815, T-19599)
  8. Bug fix - OBM Hyper-v 2012R2 with Run Direct fails to start VM after restoring on another Hyper-v 2012R2 (ref: PJV-332-75792, EGF-108-97407, T-19601)
  9. Bug fix - Backup fails with reason = com.ahsay.afc.cloud.d: [ObsManager.mkdirs] Failed to mkdirs…Connection pool shut down" (ref: RQH-294-37800, EOL-468-59664, NVE-196-70249, ISU-761-54844, T-19660)
  10. Bug fix - Hyper-V 2008R2 backup error “Cannot start shadow copy, reason =Failed to get VM State. Error = Invalid namespace” (ref: XFJ-736-30159, FIU-318-70766, T-19727)
  11. Bug fix - BSOD when running HyperV backup with Bit Defender AV (ref: MEB-256-61297, T-19776)
  12. Bug fix - Exchange 2016 mail-level backup gets warning message: Backup source “Microsoft Exchange/Public Folders” does not exist ! (ref: SOB-113-30143, T-20211)
  13. Bug fix - MSSQL Backup getting “OK ( no files backed up )”) after migrated from v6 to v7 (Without Data Migration enabled) (ref: EHN-804-86919, T-19993)
  14. Bug fix - “Cannot start shadow copy, …Failed to get VM State. Error = The virtual machine…could not be found” is shown in Hyper-V 2008R2 Cluster backup (ref: T-20114)
  15. Bug fix - Failed to backup System Databases with MSSQL VSS mode backup set (ref: T-19614)

Auto upgrade agent

  1. Bug fix - OBM leaves a CMD opened after auto update (ref: BRL-311-88436, T-19583)
  2. Bug fix - Unable to auto-update on Mac OS X (ref: BOD-776-41465, T-19870)
  3. Bug fix - Cannot backup to local NAS (ref: NWD-733-77115, T-19698)
  4. Bug fix - OBM installation prompts FSRedirector.sys filter driver blocked on Windows Server 2016 (Shows Unsigned) (ref: NJW-209-81227, DOT-545-52836, T-19585)
  5. Bug fix - Move mail count are not displayed in backup log for Office 365 Online backup set (ref: T-20087)
  6. Bug fix - Client installers unable to be installed correctly if CBS hostname contains client products name (e.g. acb123.com) (ref: T-20216)

File backup

  1. Bug fix - Schedule backup “Failed to get FileAttribute: 1492465432158 from cache” error message in scheduler debug log (ref: IXK-428-12451, T-19788)
  2. Bug fix - Backup gets “[BlockDB.init][BlockFileCorruptedExpt] Error initializing bptree” error (ref: MUN-816-44970, SQD-690-40535, UJK-357-65797, JUW-280-63162, IKB-921-16411, MBY-836-82892, HAY-714-28754, UFP-352-32610, YEE-151-43507, RYC-460-55547, UTN-568-97983, XBY-766-34580, UON-359-48323, OHJ-380-36877, T-19018)
  3. Bug fix - cbpsx64.exe consumes high CPU without running backup (ref: T-18917)
  4. Bug fix - “[warn] …Path “xxx\My Documents” does not exist!” is shown after upgrade (ref: BTO-746-93990, YYX-781-97258, T-19619)

General / Miscellaneous

  1. Bug fix - Cannot Start OBM services > Error 1067: The process terminated unexpectedly (ref: UTW-540-17809, T-19114)
  2. Bug fix - Exchange 2010 mail level restore fails with “Unexpected IOException, error=[ObsManager.getInputStream] Target is not a file…” (ref: IWW-285-15804, T-19605)

NAS / Synology OBM

  1. Enhancement - Support Synology NAS OBM on model RS18017XS+ (ref: UHA-635-21218, SFZ-207-18347, T-17719)
  2. Enhancement - Support x18 Series Synology (ref: XKU-434-30118, KAY-286-13600, FCT-169-73480, T-19724)
  3. Bug fix - Synology Security Center recognise /usr/local/etc/rc.d/Eurobackup.sh as malicious startup script (ref: HJG-290-64443, DGC-508-89884, T-19461)

Restore / Decrypt

  1. Bug fix - Unable to restore backup files (ref: NRQ-857-89153, T-19140)

Ahsay™ Cloud Backup Suite, v7.15.0.20 (rolled out on December 1st 2017)

AhsayOBM is a server OS
AhsayACB is a desktop OS

Limitation / Known issues of this version

Deployment / Upgrade

Backup / Restore

  1. AhsayOBM is not able to backup SQL databases with special character for MS SQL Backup Set in ODBC mode.
  2. Hyper-V VMs with “Paused” state will be restored as “OFF” state for Hyper-V Backup on Hyper-V 2016 Server.

Reporting / Email / Statistics

  1. For Exchange Server (DAG) backup sets, the number of files is not counted correctly.

Others

  1. Users are required to select the Windows Common Folders (e.g. Documents, Favorites) via Custom Backup Source Page on AhsayOBM to create new file backup sets for Windows users without a password.
  2. Users are not able to add/update Custom Schedule when passing Integer values for “Year”, “Month” and “Day” to AddSchedule.do / UpdateSchedule.do API.

Note

Best effort support is provided for Windows Xp and Windows 2003 in v7, the behaviour of Auto Update feature is updated to allow upgrading OBM installed on Windows XP and Windows 2003 to upgrade to v7.

This release will contain the major features listed below

AhsayOBM / AhsayACB

  1. Enhancement - OBM VMware VDDK Restore to Raw file has 4-hour period without any I/O activities and no restore information shown (ref: TDG-513-18965, VOE-875-28986, T-19419)
  2. Bug fix - Exchange DB restore encounters "[PostRestoreExchangeTask.run(Exchange)]Path=…Throwable= Create Database…Public Folder Database…Failed"error (ref: YPM-438-26991, T-19144)
  3. Bug fix - OBM Failed to upload cached index file … back to …/blocks on AWSCompatible(…), Reason = "[CloudManager.mirrorUp] Failed to mirror (ref: MXX-527-96619, T-19091)
    General / Miscellaneous
  4. Bug fix - Empty error message while deleting data via OBM client application for Oracle Database Server Backup set (ref: MHC-547-84510, T-19400)

Ahsay’s change log

Ahsay’s future roadmap

Please note

We will normally upgrade our clusters to the latest version within 4-6 weeks of Ahsay releasing updates.
Service providers can choose their own upgrade date.


Change logs and support documentation