Last post Nov 13, 2006 02:53 PM by Mustafa
Nov 09, 2006 05:22 AM|Mustafa|LINK
We deployed Hosted Exchnage 2003 based on HMC 3.5.
We have a big problem to backup the individual public folders, and then restore these separately without any Public Folder Store restore.
We discuss since August 2006 with Microsoft support team about this issue. Microsoft solution team wrote his last word:
> I don't want to commit anything from our team here in Redmond along the lines of a solution to this issue. We have never supported what is referred to as "Brick-Level" backups of private or public folders. This isn't a provisioning system issue this is a core Exchange issue, the Exchange team does not support this level of backup and restore. This has always been up to third party companies to support this. You might want to point the customer to the discussion on Brick-level backups from this article:
> Now the technical answer is the same as it would be for any exchange customer. If you have a "service" type account that needs to have MAPI access to every single public folder on a server then you need to create a mechanism to control this. This would probably be best accomplished through changing the way PFs and Mailboxes are ACL'd when created (this can be done through namespace changes that the customer would have to implement) or through a script that runs on a scheduled basis to ensure that this ACL'ing is not changed by customer administrators.
> The Hosting Solution delegation model as implemented through MPS does not allow for any single account or group to have access to all Mailboxes or Public Folder stores in an environment, this is by design. The only way around this is through custom solution.
Any comment or solution?
Nov 09, 2006 10:34 PM|DGaikovoi|LINK
Nov 10, 2006 04:48 AM|Mustafa|LINK
we speak here not about Exchange, but about HOSTED Exchange. If I develop any software for a HOSTED environment, I must consider backup procedures also, because the server is shared by many business organizations which are isolated from each other, and each
business org needs his own PF.
Consider that any company public folder should be restored. In this case the public folder store must be completely restored, it means the restore process overrides all other public folders of other customers.
OR you can perhaps propose any time intesive process, such as:
Install another Exchnage Server + restore public folders to this new Exchange + copy the restored PFs to hosted Exchange + configure the permissions again!!!
That is really unprofessional.
Nov 10, 2006 10:10 AM|DGaikovoi|LINK
"HOSTED Exchange" is just a set of methods and procedures of how to run Exchange in multi-tenant environment. All backup/restore procedures have a purpose of disaster recovery, not value-add features. And it is up to you what and how add to "HOSTED Exchange"
to be more attractive for customers. In your case, you have 3 options:
As a solution I can offer you an idea to replicate public folder over IMAP4 to file system. Or probably some backup software can do what you want. But be ready that demand for public folder restoration will be extremely low.
Nov 10, 2006 10:28 AM|Ilya_f|LINK
I am not sure, but it seems it could be useful “backing up Exchange mailboxes and public folders” feature of Veritas Backup Exec, Agent for
Microsoft Exchange Server.
Nov 13, 2006 02:53 PM|Mustafa|LINK
thanks for your response.
We use NetVault backup software from Bakbone for Hosted Exchange. NetVault has also brick-level plug-in for mailboxes and public folders. We can backup mailboxes on brick-level without any problem. The problem is with public folders. NetVault backup account cannot list
any business public folders if this account has no list access on the public folders. Microsoft support team has analyzed the problem for 2.5 months, and told us that such kind of backup (brick-level backup) is not supported in Exchange / Hosted Exchange.
The only was to do it is to change ACLs in Hosted Exchange environment. On the other hand, Microsoft does not support and recommend any permission changes in the Hosting environment. That is really very contrast.