Sounds great. Thanks.

if you provide specifics, assuming you have them at this time, I can provide additional guidance. But your assessment is accurate in their operation. The new backup format also has performance benefits like deduplication and improved performance with large numbers of files.

If the extra backup has nothing to back up because the files finished earlier it will detect this and end very quickly without impact to the managed machine. But I’ll enter your request into the system to automatically continue backups after an interruption. Thanks.

Right now, the best estimate is Q3 this year for some of those features.

legacy retention can be set to keep any number of versions. It could also be said to keep every version, if needed. What's your goal with retention?

Are you referring to version 7 features about the new backup format and GFS retention? Or are you asking about deployments as they relate to settings and backup plans?

I don't think there's any way to really know. The metadata needs to be read from storage and we do not know how much data will be read until we're done reading. But I'll check with the team just in case. Thanks.

if you're concern is that someone might turn off a laptop in the middle of a backup, say at night when they work day ends, and you want to make sure that that backup kicks off immediately when the user starts the laptop the next morning, then you can use the run missed scheduled plan immediately option on the scheduling tab, and also schedule an additional backup to run in the middle of the night, say at 3:00 a.m. . When the laptop boots in the morning it'll detect the 3:00 a.m. backup was missed, and it will continue and start up immediately.

I would recommend you open a support case. I don't see that issue documented anywhere in our system.

because in order to keep a week a backups with a weekly full backup schedule you need to have at least two weeks in storage before the initial and oldest backup can be removed. If, for example, we ran a second full backup on the 8th day and deleted the initial full backup on day one, there would be 7 days of backups, but six of them would be unrestorable because the full pack up that's related to them has been removed. You are running a weekly full backup and you want to keep a week worth of backups. In that case, you'll need two full sets in storage meaning two full weeks, before the oldest backup can be removed.

As far as I'm aware backups do not continue automatically if interrupted. They would resume on the next schedule assuming they can be resumed. if not, they would restart the last backup and any unfinished data from the previously failed backup would be removed. I am checking with Support to see if your particular use case is workable with the new backup format. It's possible using the legacy format will be preferable, but I'll let you know when I hear back.

I'm having trouble understanding if you're doing file folder backups or you're asking about image based backups. You mentioned file backups but then you also talked about synthetic full backups which apply only to image backups. File backups can always be restarted in any way and they'll pick up from where they left off since everything is file based. Image based backups can be restarted but it requires no changes to the volume to properly resume, and that's unlikely on a boot volume. So please clarify and I'll try to update my answer.

The freeware version does not support multi-threaded operations, so that could be the reason why you are not seeing progress from the files. It could also be that the Chunk size you are using in Options - Multi-Part Uploads is larger than most files and so the progress would not update until each file is complete. Speed depends on your latency to the cloud provider and your broadband bandwidth available.

Is the screensaver set to require a login when the user returns? Just curious. You could also try updating to the latest version.

I need to know what backup options you are using. When you create the backup plan, there are a lot of options. Please refer to this page and tell me which Backup Mode you are using and what Retention settings you are using and also how many Versions of each file you need to keep in backup storage and for how long? https://help.msp360.com/cloudberry-backup/backup/back-up-files-folders

Are you able to look at the queue to see progress (View - Show Queue)?

We do not support cloud-based versioning. If you want to maintain multiple file versions then you need to use our retention features. Using retention, we will manage all the versions for you as separate objects within the cloud storage. I think I would need to know more about how you're trying to do the backup with the product. What type of backup are you running? Even with versioning enabled on the cloud side we would still maintain the separate versions ourself. That makes me thinks you're either copying files to the cloud or doing some type of backup which doesn't even support our retention. So please be explicit about what type of backup you're running with the product so I can assist.

Synthetic Fulls integrate current changes since the last incremental with existing incremental information in storage. The process requires far less local IO and far less internet transfer. The total backup time can be twice as fast or better, but it depends on the amount of work required at Wasabi.

You'd register the new external HD as a target and synchronize the repository. You can then restore.

That's just a generic article about incremental backups, and is nothing to do with our products. It's for education. File folder backups do not implement that scheme. That article is more appropriate for our image based backups.