You mentioned in one of the posts that you enabled Debug level logging. Are you still on Debug logging? That would explain the troubles with sending logs to us..
They are numerous and extra heavy, being extra detailed.. Please consider switching back to lower level logging.

Where do you publish full release notes? — Keith

For 2.5 the post is this one : Link

This is addressed in the 4.2.1 which was published recently.

Fixed that title for you.
And regarding this situation - no idea, can you get our support a set of logs from the machine where the plan isn't picked up to check? Please refer to this post when sending the logs.

Let me know if I missed something in my reply :)
Yes, with S3 we can do Synthetic backup unlike the situation with B2. We do plan to implement it for B2 too, but no sure dates can be said at the moment.

With S3 there is no such problem with unfinished multipart uploads and to be on the safe side you can always configure a Lifecycle Rule "Action on Incomplete Multipart Uploads" or apply a Bucket Policy like this one:
<LifecycleConfiguration>
<Rule>
<ID>sample-rule</ID>
<Prefix></Prefix>
<Status>Enabled</Status>
<AbortIncompleteMultipartUpload>
<DaysAfterInitiation>7</DaysAfterInitiation>
</AbortIncompleteMultipartUpload>
</Rule>
</LifecycleConfiguration>
(policy taken from https://docs.aws.amazon.com/AmazonS3/latest/dev/mpuoverview.html)

No, currently there are no issues with Online Access work when the data is in S3.

Overall since S3 is there longer compared to B2, we have various things done fro S3 that are still being implemented for B2. The above mentioned Synthetic Backup is a fine example of such situation.

This is currently something that is being discussed to be added to our roadmap.
So the plans will have a separate option to ignore this "One or more backup paths don't exist" warning.
I have added you to the list of people interested in such option, so you should be updated once we have further info on it.

Why would you want to do that ?

to remove the last 7 — QiQQ

I cannot seem to think of a use case that would need any such manipulation, so please share what caused this question :)

Can you try running the executable from cmd? We've seen this happening on varius older OS like WIn2003 and other.

Sure, we've added you to the list too.

, Caleb, This is currently a known issue specific to B2 storage accounts, it's being checked on Dev side. No workaround at the moment.
I'll update you here once it is fixed or I have any other info..

In the CBBackup you can remove the data you have backed up from the Backup Storage tab, in the client itself. Please check the attached jpg.

If we are speaking some other data, not our backups, you might want to look into our CBExplorer. Just as long as you don't make changes to backup data outside of the backup client you are okay.

Yes, you are right he is a dev, I'm from support.
What sergeyv was saying is that you cannot delete a plan and by deleting the plan - simultaneously delete the data in cloud.
So you can remove a plan (on the Backup Plans tab) and you can delete the data (for example from the Backup Storage tab). But these are separate actions.
Hope this makes more sense :)

As per AWS documentation:
"You can delete an Amazon Glacier vault only if there are no archives in the vault as of the last inventory that Amazon Glacier computed and there have been no writes to the vault since the last inventory."
taken from:
https://docs.aws.amazon.com/amazonglacier/latest/dev/getting-started-delete-vault.html

Yes, we do have an option to restore to dissimilar hardware. And resizing the partitions is one of the things that is included into it.

While we are adding some finishing touches to our new KB, I suppose you can check this article for now: https://www.cloudberrylab.com/blog/how-to-resize-a-partition-during-image-based-restore/

Hope it helps.

Yes, since consistency check lists the data in cloud. This will generate the requests. And after listing it compares the data to the local repository.

Whats the rest of the error? Did you have a chance to look into the logs?
My educated guess would be that you are having this issue on VSS snapshot creation.
Please edit the plan and check these two options: Force using VSS and Use system VSS provider.
After that please try re-registering VSS core components following these instructions:
1) Create new text document at any place you want
2) Paste following code into it:

@echo off
net session >nul 2>&1
if %errorLevel% NEQ 0 (
echo Permissions are insufficient
echo Make sure to run this script with administrator privileges
set /p=Press ENTER to close
exit /b 1
)
REM echo on
REM enable string above for debugging only
cd /d %windir%\system32
net stop vss
net stop swprv
regsvr32 /s ole32.dll
regsvr32 /s oleaut32.dll
regsvr32 /s vss_ps.dll
vssvc /register
regsvr32 /s /i swprv.dll
regsvr32 /s /i eventcls.dll
regsvr32 /s es.dll
regsvr32 /s stdprov.dll
regsvr32 /s vssui.dll
regsvr32 /s msxml.dll
regsvr32 /s msxml3.dll
regsvr32 /s msxml4.dll
vssvc /register
net start swprv
net start vss

3) Please change the file extension from .txt to .bat
4) Execute this bat file and run the backup plan again.

You are doing a Group Report.

Please recheck what I suggested: I directed you to Remote Management, it is this page: https://mspbackups.com/Admin/Computers.aspx
And there to Group Actions.

Like this:


Let us know how it will go for you.

In MBS on the Remote Management under Group Actions you have a Plan Settings Report option. It will give you a csv detailing you all the plans for the machines you have in the current search on the Remote Management. So it can even be a single machine, or some Company you have or just remove all filters and have it generated for all your machines.
It will have this info:
Company,User,Login,Computer,Profile,Plan Name,Storage,Source,Excluded files,Encryption,Compression,Advanced Settings,Retention Policy,Notification,Schedule,Full Backup Schedule.

Compared to what you provided in the example, I suppose the only thing that is missing is the Ransomware protection filed, which I will suggest to add.