automatic FULL backups since some update?!

[DaStivi]

Hello,
I just noticed that M365 Jobs are doing FULL Syncs since 8.2 update? at least some random times...
for one customer in my Service Provider Environment, every run is a FULL for others it was like a few days ago 4 times in a row a FULL then again only INCREMENTALS ...

has there been a change a in 8.2 or any update before to have automatic FULL (or FULL done, when some specific issues happens?)

br

[Mildur]

Hi Stephan,

Such important changes would be documented in the release information or release notes.
Since there’s no mention of this, please open a case with Customer Support and have them review the log files to determine why a “regular full sync” is occurring in your environment. Don’t forget to share your case number.

Thank you,
Fabian

[DaStivi]

ok, thanks for verification, i thought allready...
created a case now for support to check: Case #07918291

[track1044]

I got this information from support in Case # 07875645

Code: Select all

Thank you for your continued patience on this. 
Kindy be informed that we just got the recent update from our internal RnD team, that Starting from v8.2 VBO uses new method for determining if the job is full or incremental.
 
If a job begins as incremental but later (during resolve) identifies at least one new object within its scope, the job type will change to "Full" in Shell. 
That doesn’t mean, that all other objects are processing like “full”, but it just indicates that at least one of the objects in the job scope doesn’t have a first full completed yet, or is newly added.

[andre.simard]

Hi David,
Thank you for sharing the information from your support case. We’ve noticed that many of our clients’ jobs also start full periodically, and we were just about to open a case to ask the same question.

[mjr.epicfail]

I got this information from support in Case # 07875645

Code: Select all

Thank you for your continued patience on this. 
Kindy be informed that we just got the recent update from our internal RnD team, that Starting from v8.2 VBO uses new method for determining if the job is full or incremental.
 
If a job begins as incremental but later (during resolve) identifies at least one new object within its scope, the job type will change to "Full" in Shell. 
That doesn’t mean, that all other objects are processing like “full”, but it just indicates that at least one of the objects in the job scope doesn’t have a first full completed yet, or is newly added.

You've got to be kidding me....
Can R&D revert this change immediately?

[Mildur]

Hi all,

I discussed this situation with our product team, and we’re counting it as a bug. It shouldn’t be displayed as a “full” session when only a few objects are new.
The goal is to introduce a different session type for cases where new objects are detected during a job run — though the <name> is still under discussion. I’ll try to keep you updated as soon as new information is shared internally.

Keep in mind that even though it’s labeled as “full,” it only performs a full rescan on the newly discovered objects, not on those that were already processed in the previous backup session.

Best,
Fabian

[mjr.epicfail]

Hi Fabian,

Thats comforting to hear!
Improvements like this are welcomed ofcourse, but the support feedback read like its a new feature and the behavior is as expected.

[Mildur]

Hi Danny,

Running a full sync for newly added objects in Microsoft 365 will remain unchanged — we need to fully scan and download new items like new mailboxes or SharePoint sites created between two job runs.
Similar to VBR, when a new VM is detected during an incremental run, it triggers an Active Full backup for this single VM within the incremental job session.

The difference is that VBR would show it as incremental job session, while VB365 shows a full job session — that’s what the team plans to enhance.

Best,
Fabian