Skip to main content

Hello Team,

We have recently configured Exchange and File level backup using block-level option.

Our clarification that the indexing information (disk space) will keep on Media agent or client side.

I hope the first backup will use full indexing and next backup will use only meta data of indexing, Is it correct?

 

Is it File-level block will reduce scanning of backup time window?

Is it good to enable block-level for exchange granular level recovery or any other option will use it?

 

One more clarification that where will change the Exchange rights access account on CommCell coonsole in client level. While agent installation we have used minimum level rights account. For backup & restore will use respective Exchange permission account.

 

Please advise.

Hi @Anandha K 

 

Thank you for posing your questions in the Commvault community.

 

Block-level backups and snapshot backups provide granular restore capability through live browse 

Recovering Messages from an Exchange Database (Live Browse)
https://documentation.commvault.com/2022e/expert/17124_recovering_messages_from_exchange_database_live_browse.html 

 

Indexing information will be stored on the Media Agent and storage target.

Indexing: Overview
https://documentation.commvault.com/2022e/expert/10708_indexing_overview.html 

 

Block-level backups integrate snapshot technology with efficient block storage mechanisms to speed up backups.By default, block-level backups use native software snapshot engines by taking the snapshots of logical volumes (LVMs) and physical volume partitions. You can also use hardware snapshot engines supported by IntelliSnap for taking snapshots.

Block-Level Backups https://documentation.commvault.com/2022e/expert/11731_block_level_backups.html 

 

Please use the below documentation to change the account used for Exchange database backup, 

Changing User Accounts for Backups
https://documentation.commvault.com/2022e/expert/17034_changing_user_accounts_for_backups.html

 

Take a look at the documentation shared for more information on this subject.

Reply


Terms & ConditionsCookie settings