|
现在项目客户使用的是exchange 2010 ,前两天给他们升级完成sp2,今天例行检查中发现如下错误:
Cmdlet failed" Event Errors are generated on the Exchange Server during Exchange 2010 backups using Backup Exec
Log Name: MSExchange Management
Source: MSExchange CmdletLogs
Date: xx/xx/xxxx xx:xx:xx
Event> Task Category: General
Level: Error
Keywords: > User: N/A
Computer: SERVERNAME
Description:
Cmdlet failed. Cmdlet Get-MailboxDatabaseCopyStatus, parameters {Identity=MAILBOX DATABASE\*}.
Event Xml:
The description part of the above event error will vary according to the database as shown below:
=======================================================================================================
Cmdlet failed. Cmdlet Get-PublicFolderDatabase, parameters {Identity=Mailbox Database 0815803670}.
Cmdlet failed. Cmdlet Get-MailboxDatabaseCopyStatus, parameters {Identity=Public Folder database\*, Active=True}.
Cmdlet failed. Cmdlet Get-PublicFolderDatabase, parameters {Identity=Mailbox Database 1127421131, Status=True}.
Cmdlet failed. Cmdlet Get-MailboxDatabaseCopyStatus, parameters {Identity=Mailbox Database 1127421131\*, Active=True}.
=======================================================================================================
想想哪里访问出现问题了,尝试了几种不同的方法,结果发现是symantec的已知问题,可以安全的不理睬他了
简单说下原因:
During the backups of Exchange 2010, Backup Exec queries the Exchange database with two commands - "Get-MailboxDatabaseCopyStatus" and "Get-PublicFolderDatabase".
So if "Get-MailboxDatabaseCopyStatus"query runs against the Public folder database or "Get-PublicFolderDatabase"query against the Mailbox database then these event errors are generated as the Cmdlet failed.
http://www.symantec.com/business/support/index?page=content&id=TECH169638
具体链接参考如上。做人难啊。 |
|