03-07-2009 08:10 AM
Can anyone confirm or deny that Backup Exec 12.5 EV Agent does not work with EV8.0 and if it is true will it work with EV8.0 SP1 due out in April?
Judy Glazier
Solved! Go to Solution.
03-08-2009 10:14 PM
As rewritten has stated 12.5 is not supported in the EV8 system as rightly suggested this is because of the fundamental changes to our storage architecture to vastly improve our single instancing.
The last communication that I saw on this was that the plan was to support EV8 in V12.6 which is scheduled for Nov 09 and this is due to the agent needing a rewrite to understand the new storage architecture and the new backup commands that come with EV8 and supercede the old way of stopping services changing registry keys and restarting services.
The agent still works using the legacy backup method (because it doesn’t understand the new command in EV 8), but will not detect the VSG or fingerprint databases, so you would need to backup these up separately from SQL. You could create a selection list in Backup Exec that had the EV resources (SQL DBs (excluding VSG DBs), indexes and Vault Stores), and then add the VSG SQL DBs to the selection list. This would then backup all the EV resources, and those VSG SQL DBs in the same job, but in the event of a restore, it would then mean you would have make sure you added the VSG SQL DBs to the restore selection list.
03-08-2009 07:12 PM
I can confirm that it does not support EV8.0. This is due to a number of changes in EV8.0 and the April timeline you stated is only tentative. I have been told that the Agent upgrade may not make it into BE 12.5 SP2 - it is a limitation of the BE Agent and not EV8.0 - so that would mean a November release. Why do i know this you ask?
Well a company I am doing some work for just purchase Backup Exec 12.5 on the advice of their Symantec Rep as they were an EV shop but were backing up with Commvault. The sales pitch was based around the "wonderful" integration between the 2 products. Well that would have been true if they then did not recommened the upgrade from their existing EV7.5 implmenetation to EV8.0 to take advantage of the new features. Only then after the purchase was completed and EV upgraded was the company informed of the "limited" support provided for BE12.5 and EV8.0 integration.
How this ever happened is beyond me.
03-08-2009 10:14 PM
As rewritten has stated 12.5 is not supported in the EV8 system as rightly suggested this is because of the fundamental changes to our storage architecture to vastly improve our single instancing.
The last communication that I saw on this was that the plan was to support EV8 in V12.6 which is scheduled for Nov 09 and this is due to the agent needing a rewrite to understand the new storage architecture and the new backup commands that come with EV8 and supercede the old way of stopping services changing registry keys and restarting services.
The agent still works using the legacy backup method (because it doesn’t understand the new command in EV 8), but will not detect the VSG or fingerprint databases, so you would need to backup these up separately from SQL. You could create a selection list in Backup Exec that had the EV resources (SQL DBs (excluding VSG DBs), indexes and Vault Stores), and then add the VSG SQL DBs to the selection list. This would then backup all the EV resources, and those VSG SQL DBs in the same job, but in the event of a restore, it would then mean you would have make sure you added the VSG SQL DBs to the restore selection list.
03-09-2009 06:21 AM
Thanks for the clarification Paul
Muchly appreciated.
Judy Glazier
04-24-2009 07:04 AM
04-24-2009 07:47 AM
08-04-2009 10:56 AM
08-06-2009 06:41 AM
I don't know when a new agent will be released, but there is documentation available that may be helpful:
Protecting Enterprise Vault 8.0 with Backup Exec for Windows Servers 12.5 Agent for Enterprise Vault
http://support.veritas.com/docs/321595
08-06-2009 09:28 AM