Home > Computers and Internet, Every Day is a Learning Day > Symantec Backup Exec 12.5 SP4 incompatibility with Windows Server 2008 R2 persists

Symantec Backup Exec 12.5 SP4 incompatibility with Windows Server 2008 R2 persists


We installed a single Windows Server 2008 R2 DC in our W2k3 domain to extend the schema and manage our new windows 7 desktops, and now there is a problem. Symantec Backup Exec 12.5 is incompatible, or so it seems. I patched SBE 12.5 to SBE 12.5 SP4, plus hotfixes, and still some of the jobs error out with complaints, “A failure occured querying the Writer status.” The data is being backup, as the job status lists a byte count, but errors occur at the end of each job. These are multi target jobs, and when the backup targets have either an MSExchange or MS SQL agent running, the jobs seems to end in failure. The job status log has more red than black, and that annoys me immensely.

All I did was extend the schema in the forest and domain, all my member servers remain Windows 2003, but the media server is Windows Server 2003 R2, but Research suggested that the incompatibility was isolated to SBE 12.5 where installed on a W2k8R2 platform, not merely within a mixed W2k3(R2) / W2k8R2 domain.

I’m in the proces of breaking jobs into smaller targeted jobs, but It seems clear thet servers running an agent will hang after the job completes after querying the Writer status. The “Writer” is associated with VSS, and I have tried adjusting the options in the job configuration without success.

I have been rereading the documentation hoping to find some scripting or logic mechanism that might permit me to branch around error conditions… Still researching this!

Advertisements
  1. bob morlock
    24 January 2012 at 6:55 pm

    You’ll find the issue is related to the System Reserved partition.on 2008R2 servers. BEX 12.5 doesn’t like the fact that there is a partition there with no assigned drive letter. I found when I assigned a drive letter to that partition (like Z: or X:) then BEX 12.5 will stop giving those writer metadata errors, just don’t bother backing it up 🙂

  2. 26 January 2012 at 11:09 am

    Thanks, I will look into that, but the servers with which the errors are concerned are W2k3 rigs.

  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: