ビデオヘルプ
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Test/Edit Credentials fails on Shadow Copy on Media Server after migrating from BE2010 to BE 2012

作成: 03 Oct 2013 • 更新: 04 Oct 2013 | コメント数: 3
この問題は解決されました。 ソリューションを参照してください。

Hi

I have upgraded from Backup Exec 2010 R3 to 2012 with the latest service pack and hot fixes applied. The server is 2008 R2.

During the 2012 installation the jobs were migrated and I have the error regarding the Shadow Copy Components appearing and causing errors when testing server credentials.

I have removed all my remote servers and re-added them which has fixed the issue however I am unable to remove the media server itself.

I have followed the Tech Article TECH179966 (http://www.symantec.com/business/support/index?page=content&pmv=print&impressions=&viewlocale=&id=TECH179966) and the shadow copy components do not appear in under the selection list or the selection details.

I have removed all backup definitions for this server and created a brand new definition from scratch not using any previously defined definitions and the Shadow Copy Components is still being displayed.

If I click on the server and then view the Credentials without opening any backup definitions the Shadow Copy Components appear there and I am unable to remove them.

Yes, I basically have the same exact issue another user posted...if there is a way to fix this without having to reinstall the whole thing, the help would be appreciated.

オペレーティングシステム

コメント コメント数: 最新のコメントを表示

lmosla の写真

Hello CCounty,

Have you ran the Backup Exec Live updates until they were all installed (and then pushed the agent to the remote servers also) ?

EDIT:  see this forum for a workaround suggested by Bobinazee             http://www.symantec.com/connect/forums/shadow-copy...

ソリューション
CCounty の写真

As stated in my post, Service Pack and hotfixes applied....servers and jobs were recreated (which prompts you to install any agent updates). Someone else had this EXACT issue, and no solution was provided other than that a Symantec rep called the user, and fixed the issue (some change was made to the DB on the media server).