public:edition:cloudbacko_lite:release_note:v4103

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Last revision Both sides next revision
public:edition:cloudbacko_lite:release_note:v4103 [2020/04/06 11:45]
ronnie.chan
public:edition:cloudbacko_lite:release_note:v4103 [2020/04/06 11:50]
ronnie.chan
Line 125: Line 125:
   * backup error Failed to initialize RemoteBDB.Cloud …caused by [SQLiteException][SQLITE_CONSTRAINT] Abort due to constraint violation (ref: DBS-560-83649,​ OAD-215-96573,​ T-25451)   * backup error Failed to initialize RemoteBDB.Cloud …caused by [SQLiteException][SQLITE_CONSTRAINT] Abort due to constraint violation (ref: DBS-560-83649,​ OAD-215-96573,​ T-25451)
   * Get [FileAttributeIterator.reiterate] Failed to list … [SocketTimeoutException] Read timed out on Backup & DIC after upgrade (ref: FMX-824-64917,​ IUM-634-68988,​ MBO-445-38626,​ MXR-663-34563,​ T-25479)   * Get [FileAttributeIterator.reiterate] Failed to list … [SocketTimeoutException] Read timed out on Backup & DIC after upgrade (ref: FMX-824-64917,​ IUM-634-68988,​ MBO-445-38626,​ MXR-663-34563,​ T-25479)
-  * Cannot run backup on CentOS since “Failed to load native library:​sqlite-3.27.2.1” with “Error…org.sqlite.core.NativeDB._open_utf8([BI)V” (ref: PEJ-507-95874,​ WVE-381-21536,​ T-25492) 
   * After running data integrity check / space freeing up, index.db file is not found in the current folder of backup destination (ref: T-25502)   * After running data integrity check / space freeing up, index.db file is not found in the current folder of backup destination (ref: T-25502)
   * Massive “exists already” and “Failed to retain non-empty directory” errors occur on backup jobs on multiple users after upgrade (ref: CSA-289-75260,​ LUV-505-71246,​ PTD-107-12026,​ ULZ-650-26955,​ T-25589)   * Massive “exists already” and “Failed to retain non-empty directory” errors occur on backup jobs on multiple users after upgrade (ref: CSA-289-75260,​ LUV-505-71246,​ PTD-107-12026,​ ULZ-650-26955,​ T-25589)
Line 144: Line 143:
   * Some updated files that does not show on backup report (ref: QJD-389-38452,​ T-25747)   * Some updated files that does not show on backup report (ref: QJD-389-38452,​ T-25747)
   * When running advanced retention policy, Delete message is NOT updated with last modified time, size, backup by job information (ref: T-25344)   * When running advanced retention policy, Delete message is NOT updated with last modified time, size, backup by job information (ref: T-25344)
-  * When performing file backup, Error “Failed to synchronize log files to servernull” is logged in .cbp\log\System (ref: T-25057) 
  
 === Restore / Decrypt === === Restore / Decrypt ===
Line 155: Line 153:
 === System Maintenance === === System Maintenance ===
   * Fail to new /update file with Error=[ReadAheadInputStream.readNext]@1417399903 READ_ TIMEOUT=5400000 exceeded (ref: ZWB-310-24443,​ T-26147)   * Fail to new /update file with Error=[ReadAheadInputStream.readNext]@1417399903 READ_ TIMEOUT=5400000 exceeded (ref: ZWB-310-24443,​ T-26147)
-  * CloudBacko UI & Service could not be started “Error 1067: The process terminated unexpectedly” after upgraded to v8.1.0.50, causes backup not working (ref: VRX-394-40311,​ T-23286) 
   * Office application slowness and screen flickering after CloudBacko installed (ref: VLS-805-40430,​ ITZ-205-44053,​ SOW-380-20119,​ VUA-649-72676,​ T-23361)   * Office application slowness and screen flickering after CloudBacko installed (ref: VLS-805-40430,​ ITZ-205-44053,​ SOW-380-20119,​ VUA-649-72676,​ T-23361)
  
public/edition/cloudbacko_lite/release_note/v4103.txt · Last modified: 2020/04/06 12:13 by ronnie.chan