That's a bug and it's happening because you only have a single file in the folder. Add a second file - just a dummy file is fine and you should be able to select the file you need without triggering the parent folder.

You're having that issue because you are checking the parent folder and that causes the folder to be explicitly added for backup. Instead, you want to just check the file itself.

I did some testing and you can accomplish what you want using "Custom" backup mode. With this mode, all files are placed in the destination folder in a flat format with no subfolders. I would uncheck NTFS Fast Scan to speed up the backup and uncheck VSS unless you need it because the source file may be in use.

The only way to do this is to use the Simple backup mode. That's the only mode where the backup format would retain the source file as is. But I do not know if it's going to create the file in just a default folder or retain the folder structure. You'd have to test. https://help.msp360.com/cloudberry-backup/backup/cloud-to-cloud/step-5

Yes. You would need to purchase a licensed edition. You can find a comparison on this page: https://www.msp360.com/backup/windows.aspx

normally the backup format would not be an issue since it's in a proprietary backup format. But I'm guessing you have a completely different use case, and it would help to understand that a little bit better. Are you looking to just copy the file, leaving it in its native format, rather than a format that's specific to the backup product?

Did you check the event log on the virtual machine to see more about the error? I would check any event log entries for details and then have a look at this KB article for a possible solution: https://kb.msp360.com/standalone-backup/esxi-&-hyper-v/vm-quiescing-error

if you delete versions older than a time period, all the versions are removed when they age out, with the exception of the last version if you check the keep last version option. The number of versions you keep for each file is up to you and as long as they haven't aged out you'll have that many versions, assuming there have been that many changes and that many backups. If you decide you want to keep three versions, after the fourth version is backed up, the first version is removed. Also keep in mind that if you're doing block level backups you need to be aware that versions are going to be tied to the full backup of the file . So if you change your file every day and back it up every day and are running full backups once a month, you'll have 30 versions of that file that must be kept at a minimum before they can be removed because of the need to keep that full in order to restore the block-level file backups.

If you're not using block-level backups to back up changes within files rather than the entire file every time it is changed, then there's only one backup type to schedule since the product backs up all changed files in their entirety every backup. If you're using block-level, then you want the product to back up changes within files (helpful for large files that change little day-to-day). In that case, you need to schedule a recurring full (e.g., once a week or once a month) so those files are backed up in their entirety. That's needed to manage retention. If you can imagine a large file that is backed up using block-level backups forever - we would be unable to delete old versions since every backup contains only part of the entire file.

The team would like to see the logs for this particular machine. Can you submit them from the feedback option in the user interface?

no movement yet on this request. I'll check with the team again.

Can you verify your version while I check with Support?

Thanks Steve. At that size the file system uses 2 MB clusters. That could partly be the reason for the slower performance. What's more unusual is that the external hard drive was formatted with that file system, which is more traditionally used for removable media like SD cards and removable USB sticks.

A few points.

• You should not use the Keep BitLocker option on system volumes if you're backing them up using image backup. VSS cannot be used with BitLocker and that can lead to system volume corruption.
• If you back up a non-system volume using the Keep BitLocker option, then you end up backing up the entire volume - including unused space. That can greatly extend backup time and increase storage requirements (imagine a 4 TB volume with 200 GB of used space and 3.8 TB of unused space). That also means you cannot exclude folders for backup on the volume using that option as everything needs to be backed up
• As you've noted, you cannot perform file-level restores from volumes using the Keep BitLocker option

You can (and should) use our AES-256 encryption during backup to protect the backups.

Unless you have a specific need to keep the BitLocker encryption, I would not keep it for backup.

thanks for the update.

possibly during the server upgrade the ID on the volume changed. I would go through the backup wizard again and make sure the proper partitions are selected and then run the plan according to schedule to see if the message clears. It's possible one of your partitions is not getting backed up

No. Maintenance is not required and would never cause backups to stop running. As far as security software I'm asking what are you running on that computer? Windows Defender, Norton Antivirus, something else?

What security software are you running? I'm wondering if it's the cause of the issue. Can you also verify which version you're running? Also, please verify which account you're running the service under.

There’s an immutability feature coming (likely in the 7.2 version) that will lock the data for the duration specified in the GFS retention settings. So, you’ll need to use the new backup format in order to leverage immutability.

If you were using our Managed Backup, there are ways to disable the agent and lock it down with a master password. One thing you probably can do is run a backup to B2, object lock the data, change buckets and start backing up to an entirely different bucket to ensure the older backup is safe. You could also back up to an external HD and take it off site.

What security software are you running?