cancel
Showing results for 
Search instead for 
Did you mean: 

Backup Exec 2010 IDR component fails to install on Windows Server 2008 R2

brandonm
Level 2

Hi. I am having issues adding the IDR component to Backup Exec on several servers, all of which experiencing the exact same issue. I recently upgraded Backup Exec 12.5 to 2010 on these servers. This upgrade was prior to upgrading the server from Windows Server 2008 x64 to Windows Server 2008 R2. The IDR component was installed and configured when the servers ran Backup Exec 12.5. After upgrading the servers to Windows Server 2008 R2, I went to update the IDR ISO, but discovered that the IDR component was not installed. I guess I was foolish to think that by upgrading Backup Exec 12.5 (with IDR installed) to 2010, the IDR would have been installed/upgraded as well. Well that was not the case. So I went through the Backup Exec 2010 options menu to add the IDR and as it is copying the files from either the DVD or a network share (I tried installing from both), it comes up with the following error, and the installation fails. I was able to browse to the file MSVCDlls.cab and it seems to be fine (I can open and view containing files).

be_error.jpg

This is from the install log:

03-09-2010,14:42:06 : C:\Program Files\Symantec\Backup Exec\idr\disk4\I386\w2k\04mmdat.sy_
<br />
<b><font color="red">03-09-2010,14:42:06 : FATAL ERROR: Error 1334.The file '_4mmdat.sy_.1B15BB01_8E2D_4A12_A3E6_175864F3EF67' cannot be installed because the file cannot be found in cabinet file 'MSVCDlls.cab'. This could indicate a network error, an error reading from the CD-ROM, or a problem with this package.
</font></b>
<br />
03-09-2010,14:44:13 : Action ended 14:44:13: InstallExecute. Return value 3.
<br />
03-09-2010,14:44:13 : Action 14:44:13: Rollback. Rolling back action:

Upon the rollback process, it states that installation fails, but the strange thing is that the Intelligent Disaster Recovery component is selected in the options as if it were installed. I tried building a new IDR as is, but it still does not work.

1 ACCEPTED SOLUTION

Accepted Solutions

Colin_Weaver
Moderator
Moderator
Employee Accredited Certified

This is a known issue with a fix

http://entsupport.symantec.com/docs/346929

View solution in original post

2 REPLIES 2

Colin_Weaver
Moderator
Moderator
Employee Accredited Certified

This is a known issue with a fix

http://entsupport.symantec.com/docs/346929

brandonm
Level 2

Thanks. That did it.