Solved

Microsoft 365 Exchange Online - why only forever incremental backup?

  • 10 September 2021
  • 4 replies
  • 79 views

Badge +1

Hello everyone,

 

i’ve got a question to the backup from Microsoft 365 Exchange Online.

Why can we backup the mailboxes only as “forever incremental”?

 

Doesn’t it makes sense to be able to do a Synth Full from time to time?

I see why we can’t make a full backup over the internet. That makes totally sense to me.

The synthetic full however is performed directly on the Commserve and not over the internet.

Thats why i don’t understand that we are only able to do a forever incremental.

 

We already asked that our consultat, but he didn’t had an anwser either.

So maybe someone of you now the reasons for that.

 

Thanks,

Kilian

 

 

 

icon

Best answer by Chris Hollis 13 September 2021, 03:50

View original

4 replies

Badge +1

@Chris Hollis 

Thanks for your reply.

I asked because we usually only have our backups on our disks for a maximum of 6 weeks.

Older backups we have then only on tapes.

Now if we need to restore a mailbox whose backup is no longer on disk, I am concerned that we would have to request a lot of tapes then. 

With Synth Full backups, we would only need to request one tape.

 

Currently we have every incremental backup of Exchange Online on disk.

But this should not become a permanent state.

 

Thanks,
Kilian

Userlevel 6
Badge +14

Hi @Yoki 

Great question!

I’m discussing this internally with the teams and researching some internal resources so I can get you an answer on this one.

Thanks,

Stuart

Userlevel 4
Badge +7

Hi @Yoki 

Thanks for clarifying.

We have a CMR (#​256668) currently being worked on to provide support for a ‘Full’ archive job for selective copies with this agent. This doesn’t necessarily mean it’s going to be a full backup job type, for example, it’s possible it may be a workflow that grabs or compiles incrementals that are on a tape / or that cover a certain time period and makes them one job, development are still designing this and there is no ETA on when it will be available. 
 

In the meantime, for your current situation, yes, if you’re hosting everything after 6 weeks on tape, overtime you’ll need more and more tapes to recover data, this is true.

You’ll most likely find that your tapes will however be able to hold a lot more jobs as they’ll be smaller increments of data… unless of course you have a large amount of mailboxes to protect (10s of thousands) and the rate of change between archive jobs is exponential. 

Smaller increments of jobs hopefully means less tapes required to cover a larger period of time. 

Is the current setup primary = disk, secondary = tape? or is there another disk copy you could take advantage of for mid-long term retention on disk? 

What kind of retention will you be applying to your tape copy? 

Regards,


Chris  









 

Userlevel 4
Badge +7

@Yoki 

Hope you’re well.

With the exchange mailbox solution, the entire architecture of archiving has changed - the agent now leverages V2 indexing - https://documentation.commvault.com/commvault/v11_sp20/article?p=10774.htm 

If you were to include a synthetic full option, many of the benefits this feature provides will become  redundant. 

The primary benefits for this approach is:

  • Less ‘footprint’ on your storage device(s)
  • Better scalability & reliability
  • Faster browse/search and restore capabilities

May I ask what would be the reason for needing a synthetic full in your environment for this type of data? 

If you were concerned about not having a ‘FULL’ to refer to, we do have the option to ‘Convert to FULL’ as per: https://documentation.commvault.com/commvault/v11_sp20/article?p=29004.htm

Note however the job type remains the same ‘incremental’, you’ll just see a spike in amount of date (size of application) as we’ll be backing up everything in the users mailboxes at that time.

Reply