Forum Discussion

John_Matteson's avatar
John_Matteson
Level 3
13 years ago

Backup Exec 2010 Agent for Enterprise Vault 10.0.1

I have a customer that is currently running Backup Exec 2010 R2 and Enterprise Vault 10.0.1 in a medium sized business enviornment.

The EV site is one site, one server running a single archive (no rollovers) one set of indices.

The customer is convinced that he does not need the Backup Exchange Agent for Enterprise Vault, that all the functions that the agent provide can be accomplished by manually setting the EV site into backup mode prior to the backup and then turning off backup mode at the EV site level once the backup is completed.

I think there is more to getting a clean, full backup that just turning on backup mode and letting BE rip.

However, the documentation that I've been able to find is a bit thin on what functions/benifits the EV agent actually provides.

Can anyone provide this information?

 

Thanks.

 

John M.

Agents
Backing Up
Documentation
Enterprise Vault
Information Governance
  • TonySterling's avatar
    TonySterling
    13 years ago

    Your customer is correct, you don't need the agent but it does make things simpler.

    The Agent automatically puts EV in backup mode and lets you target the VS partitions and Index locations and I think also the SQL db's through the GUI in one job.

    Without the Agent you will need to set up the pre and post backup scripts to put EV in backup mode and then create the BE job to target the data sources and manually call the scripts to put EV in backup mode.  It adds a layer or two of complexity to the process.

  • TonySterling's avatar
    TonySterling
    Moderator
    13 years ago

    Your customer is correct, you don't need the agent but it does make things simpler.

    The Agent automatically puts EV in backup mode and lets you target the VS partitions and Index locations and I think also the SQL db's through the GUI in one job.

    Without the Agent you will need to set up the pre and post backup scripts to put EV in backup mode and then create the BE job to target the data sources and manually call the scripts to put EV in backup mode.  It adds a layer or two of complexity to the process.

  • AmolB's avatar
    AmolB
    Moderator
    13 years ago

    FYI... 

    As of now EV10.0.1 does not appear in the software compatibility list of BE.

    Refer to the BE2012SP1a (latest) software compatibility list

    http://www.symantec.com/docs/TECH175581

  • Jeff_Shotton's avatar
    Jeff_Shotton
    Level 6
    13 years ago

    By the way, Backup Exec 2010 R2 does NOT support Enterprise Vault 10.

    BE SCL : http://www.symantec.com/docs/TECH137682

    For that, you need Backup Exec 2010 R3

    EV Compatibility Guide (p23) : http://www.symantec.com/docs/TECH38537

    Agent best practices: http://www.symantec.com/docs/HOWTO21774

    As Tony says - it just makes Backup simpler (open partitions and vault store databases are done as one job, as per best practice, etc etc)

    It does NOT deal with migrated data though.

    Regards,

    Jeff

  • John_Matteson's avatar
    John_Matteson
    Level 3
    13 years ago

    Thanks for all the information Jeff, and everyone else.

     

    Not sure what you mean by "it does not deal with migrated data though."

     

    Sorry for the probably silly questions, but I'm a rather complete novice when it comes to working with EV.

     

    John M.

  • Jeff_Shotton's avatar
    Jeff_Shotton
    Level 6
    13 years ago

    Migrated data is data migrated to 2nd tier storage by the configuration set on the migration tab of the partition.

    Once data is migrated it is deemed out of the control of Enterprise Vault so is not covered by the backup agent. Eg below I have configured the Enterprise Vault Migrator...

    Regards,

    Jeff