Hi @iConsultant
Thank you for the question, I have checked documentation:
https://documentation.commvault.com/11.23/expert/29004_running_exchange_mailbox_agent_archiving_job.html
https://documentation.commvault.com/11.23/expert/100609_archive_options_for_subclient_archive_options.html
And there are very few details around “convert to full” option to explain this.
I’ll follow up with our Messaging team internally in support and see if I can get some clarity for you.
My end goal will be: once I have some more detail for you posted in here, I will put in a request to our Documentation team to expand those pages and add some extra detail.
Thanks,
Stuart
My understanding is that is still marked as incremental, and when you run the next job it will re-download everything with a new index. I believe it is there in case there is an indexing/archiving issue that needs a re-baseline.
Just to clarify, the whole purpose of this option is to provide the capability for customers to 'rebaseline' their users mailbox data.
You should only want or need to do this in certain situations... e.g.
1. You've changed your exchange policies and want to ensure all the data within the users mailbox has been updated and re-protected as per these changes.
2. You've lost the storage device housing this data (no seconday copies available) and need/want to re-archive everything that current exists in your users mailboxes.
3. You want to manually aux copy certain jobs to tape for long term retention (and these jobs need to contain everything in the users mailbox @ time of archive).
It's not designed to be used in the 'traditional full' sense that we used in previous editions of the mailbox agent - hence the option to run a 'FULL' job is not supported or available as a 'backup type' for this agent.
Hopefully this helps.