… or so Computerworld UK said on Monday. Something that I’ve been saying for 3 years – but, hey, what do I know? According to Computerworld UK the consumerisation of IT is an unavoidable phenomenon that will force businesses to rethink their security policies. What about all that stuff some poor soul will have to back up? CIOs need to deal with consumerisation. For many years we were able to say to our end users – “no you can’t have that”, or “no we don’t support this”. But those days are over. The security of this phenomenon is certainly a concern, but IDC reckon that 80% of data created by individual consumers will end up on corporate networks. This will inevitably cause a overload on our already overloaded systems. Until we have the management capabilities for streaming applications to the desktop (oh, sorry Symantec already does that). OK, so when we get around to migrating to this model where all our data is help inside the network consumerisation won’t be nearly as scary – until then data growth will continue on its upward curve.
That’s why deduplication and archiving are key to our backup strategies. We are challenged with managing and protecting the ever-increasing amounts of data. Backup Exec offer deduplication across physical and virtual machines to reduce the length and size of backups. Deduplication has the power to transform information management; it is great for backup, it is great for archiving, and can even make virtualised server backup manageable. Symantec believes that deduplication should live in every part of the information architecture.
Much of the content produced now consists of email, documents, presentations, and other types of unstructured information. This explosion of information has a significant impact on storage spending and IT’s ability to meet the needs of its internal customers and business units. Backup Exec’s integrated archiving option is focused on reducing the amount of information backed up. Together with Enterprise Vault (EV), Backup Exec’s Agent for EV helps organisations to unify content sources, apply retention policies, reduce backup windows, shorten recovery times, and optimise storage resources making it easier for companies of all sizes to store, manage, and protect all unstructured data.
Backup Exec 12.5 released an Agent for Enterprise Vault, which is designed to offer complete protection for Enterprise Vault 7.5 implementations. When Enterprise Vault 8.0 was released, architectural changes in EV 8.0 made the Backup Exec 12.5 Agent for Enterprise Vault unable to automatically protect all aspects of Enterprise Vault. An integrated solution will be in the next version of BE. In the meantime …
For customers who have not purchased the Agent for Enterprise Vault, and wish to protect Enterprise Vault manually with a combination of Backup Exec Agent for SQL Server and Agent for Windows Systems, refer to the following Tech Note: http://seer.entsupport.symantec.com/docs/312327.htm
The Backup Exec 12.5 Agent for Enterprise Vault contains all of the building blocks necessary to protect Enterprise Vault 8.0. Customers who have purchased the Agent for Enterprise Vault do not need to purchase any additional Agents/Options to fully protect Enterprise Vault with Backup
The following procedure will create several jobs which will result in complete protection for the Enterprise Vault 8.0 infrastructure.
When the Agent for Enterprise Vault is installed on each member server in the Enterprise Vault infrastructure, the Enterprise Vault entities shown in the Backup Browse view will form the core of the first job. From the Backup View, expand the “Enterprise Vault” icon, and select the Sites,
Vault Stores, Vault Store Databases, Partitions, Index Locations, Directory Databases, and Monitoring Databases to be backed up in this first job.
This will create a single job that protects these specific entities. This job will keep the EV Services in read-only mode for database consistency purposes.
Create a series of SQL jobs to protect the additional databases introduced in EV 8.0. These databases are the Auditing Database (AuditDB), the FSA Reporting Database (FSAReportingDB), Fingerprint Database (FingerPrintDB), Compliance Accelerator, and Discovery Accelerator databases.
Administrators will need to browse to the appropriate physical server where these databases run in order to select them for protection. The Agent for Enterprise Vault must be licensed and the Remote Agent for Windows Systems must to be installed on any system that hosts an Enterprise Vault database.
These databases do not require Enterprise Vault to be put into ReadOnly or backup mode, and as such can be protected while they are online. The Agent for Enterprise Vault includes all features and functions necessary to consistently protect running Microsoft SQL databases.
1. Create a SQL backup job to protect the Auditing Database (EnterpriseVaultAudit) and the FSA Reporting Database (EnterpriseVaultFSAReporting)
a. Use Full or Incremental (backup transaction log and truncate) backup method.
2. Create a SQL backup job to protect the Fingerprint Database and ExpressVaultStore Databases
a. Use Full, Differential, or incremental (backup transaction log and truncate) backup method.
b. Symantec advises customers to backup the FingerPrint databases after every VaultStore backup. This is to ensure that backup copies of the Fingerprint Database and the physical VaultStore are consistent. In case of a recovery, the closer the FingerPrint Databases and VaultStores are in time will make for a faster recovery process.
3. Create a SQL backup job to backup Compliance Accelerator and Discovery Accelerator databases (i.e. ConfigurationDB, CustomerDB and CustodianDB) if present.
a. Protect Configuration, Customer, Custodian, and other databases using Full, Differential, or Incremental (backup transaction log and truncate) backup methods.