badua.blogg.se - Backblaze b2 s3 compatible

Transaction log backup after differential backup forces full backup.

Log sequence number does not change after a full backup.

Log sequence number chain breaks upon sync or consistency check.

Hyper-V backup: Backup fails if VM config file is in use at the moment of backup.

File backup: Legacy backup format backup plans fail on listing of files containing unsupported characters.

Restore Verification for virtual environments (VMware, Hyper-V).

MS SQL restore: Restore job restores one excess transaction log file.

Backup: 'Large files must have at least 2 parts' error upon uploading compressed files to Backblaze B2 storage.

Backup: High memory consumption upon deep sync.

Intelligent Retention for Forever Forward Incremental backups.

Restore: Issue with filenames upon restore to a specific location.

Backblaze B2: Deep sync fails due to the 'Unknown file size' error.

Reporting: Some files are missing in the detailed report.

Image-based backup: First full backup is interrupted by the scheduled full backup.

File backup: Incorrect behavior of the 'Do not back up files used by other processes' option.

Ability to re-init the repository database in case it is corrupted.

Diagnostic: Event logs can be sent until the app is running under the administrator account.Reporting: Detailed report generation improvement for backup plans with large numbers (millions) of files.Memory performance improvement on million folders to file system destinations (local disk/network share).VMware backup: Error upon editing VM list using the quick edit.Forever Forward Incremental: 'Unnecessary restore point was found' error after re-enabling Forever Forward Incremental backup.Consistency check: 'Sequence contains more than one element' error upon consistency check in the new backup format.SQL backup: Sync fails after the failed backup plan execution.Backup storage: Block-level backup is displayed instead of full from another computer.Upon rollback from version 7.8.3 to 7.8.2 or earlier, all passwords (storage accounts, network credentials, encryption passwords) are reset and require manual re-entering.Immutability feature renamed to Object Lock.Retention policy: Scheduled full backup is mandatory to apply the retention policy in the new backup format.Backup plan upgrade from the legacy backup format to the new backup format (via CLI).

Export configuration: functionality is restored.Hyper-V Backup: Processing of virtual machines in invalid state was improved.