Knowledge Base Article
Was this article helpful?
----EDIT----
I just re-read your post and found out I over-read "cluster".....
Backing up a DFS-R cluster with backup exec has to be done with a workaround:
- back up the active node.
As I posted some weeks ago, there's an article from symantec describing the problem:
http://www.symantec.com/business/support/index?page=content&id=TECH164777
So please overread the rest of my post below regarding connection problems between Server and RAWS! ;-)
----EDIT----
Hi,
there are two problems with your pst-files:
- using PST-files with Outlook which are located on a network share are not supported by Microsoft:
--> http://support.microsoft.com/kb/297019/EN-US
--> http://blogs.technet.com/b/askperf/archive/2007/01/21/network-stored-pst-files-don-t-do-it.aspx
- replicating PST-files with DFS-R can lead to data corruption and replication problems
--> http://technet.microsoft.com/en-us/library/cc773238(v=ws.10).aspx#BKMK_050
- PST-files stay open with R/W access even when outlook is started only - the file gets modified by just starting Outlook and has to be replicated!
- Imagine 50 users opening Outlook in the morning, having a 2 GB PST-file - that's 100 GB of data to be replicated (first, staged, then replicated via RDC, so WAN traffic will be kind of low, but you will see high I/O utilization on the servers running DFS-R (100 GB only by opening and closing Outlook without changing anything inside the PST!!)).
- imagine a user who starts Outlook (PST-file is modified), closes it and opens it again - the PST-file will be replicated one time (after closing Outlook) and stay open (and locked) while Outlook is running and will be replicated again after closing Outlook at the end of the day when the user logs off...
So opening PST-files from a file share is a problem for itself, but replicating it will get you in trouble.
Even your errors seem to come from a communication problem between Backup Exec Server and the RAWS Remote Agent (check your firewall logs between the sites, try to configure your Agent Communication to a fixed port and allowing it through firewalls) backing up PST-files which are opened from a file share means backing up possibly corrupted data.
That may be the reason your PST-files are corrupted - maybe Backup Exec shouldn't be blamed here!
If you get your Remote Agents working (or the communication between Server and RAWS) and your PST-files are still corrupt after backing them up, think about getting rid of PST-files and you'll be fine.
I know that's not easy, but with Microsoft behind your back (e.g. the lacking support of PST-files opened from file shares) it should be more easy to get it done.
One of my customers had PST-files opened from network shares, and with implementation of DFS-R we excluded all *.PST-files from replication.... Users had to stop using PST-files or move them to the local disk and manually back them up to an external drive or as a ZIP-file on the network share.
Many users stopped using PST-files actively, and with Exchange 2010 they should be gone forever (thank god!!!).