Hey, all, this is probably a very basic question, but I wanted to check with folks who probably know.
Commvault uses many terms internally that have different uses/meanings in many other clients/environments. One I'm very cautious about here is how it uses 'archiving'. I am attempting to create a backup of an Exchange 2013 mailbox store, but Commvault use of archiving seems dramatically different from Microsoft's, so I wanted to confirm that I understand their usage here.
I have created a Client Computer that is the Exchange Mailbox server, with the usermailbox having been auto-generated as the sub-client. I have an Exchange Backup Archiving Policy configured under Configuration Policies with a start date of today. I have a storage policy configured for the Mailbox. I have created an index server and access node.
But the use of the term 'archiving' makes me nervous. Is that simply how Commvault refers to backing up a user mailbox? I realize that it can clear the mailbox based on policy settings (which I have turned off), but in Exchange an Archive Mailbox is a term of art and I just want to make sure that it has no relation to what Commvault means. I don't want my clients to suddenly find their user mailboxes empty after a backup job.
On a related note, I'm not actually sure how to start the backup of the user mailboxes, despite having all these policies, sub-clients, servers and related items. To be honest, I'm beginning to think that Commvault may be too big a solution for our relatively small company. It clearly is designed to scale to huge installations, but I really just want a consistent system to reliably backup my reltaively small infrastructure.
Regardless, any suggestions would be appreciated. Thanks!