Netbackup 7.5 - accelerator + de-dupe - error enabling to use accelerator

When using the option “Use accelerator” on the policy screen, you may get the error that the storage unit can’t be used for accelerator type of the backup. Fix is to manually enable storage server and disk pool for accelerator type of backup by manually adding flag OptimizedImage: the procedure is explained in details on the following post: http://www.symantec.com/connect/forums/unable-select-use-accelerator-msdp-storage-unit

HOWTO reactivate the employee in Enterprise Vault Compliance Accelerator v9sp3

Find the AddressOwnerID of the reactivated employee by running following query on the customer DB: SELECT AddressOwnerID, DisplayName FROM tblAddressUser WHERE Surname='Last Name' After findng AddressOwnerID, supply it into the following query and run on the customer DB: UPDATE tblAddressUser SET Deactivated=0 WHERE AddressOwnerID=AddressOwnerID from the query above

Exchange GRT backup failure (Netbackup) caused by name resolution

The most common problem with backup using Netbackup is name resolution. Servers/clients have to be resolvable by the computer name (not fqdn), which in multi-domain environment brings some challenges (servers have to be added to the hosts file on the client). Most recent problem: Exchange GRT backup finishes with status 1 (ie. not good for single item restore), which was fixed by fixing the name resolution.

Netbackup VM client file restore – error 2817

Restore file from “FlashBackup-Policy” backed up client fails with error 2817 when started not from the master or media server. Solution: Start restore from master or media server or add the workstation the restore is being started from to the client server list in the Netbackup Admin Console (per http://www.symantec.com/business/support/index?page=content&id=HOWTO51780)

Netbackup and DFSR

Netbackup client v 7.5 does not work properly with Windows DFSR: it does not recognize archived bit in DFSR folders, which result all backups run as Full. Workaround: downgrade client to v.7.0.1 with couple of eebs (ie. hotfixes) installed (or v.7.1 – which I did not have a chance to test/confirm).

Journaling Rule for Exchange 2007 requires internal SMTP address

Creating Journaling Rule on Hub Transport that forwards emails to the external SMTP address (by creating Mail enabled Contact and configure Journaling Rule to send emails to that Contact) fails. To fix add internal SMTP address to Contact.

Symantec Enterprise Vault v9.0.x and Microsoft clustering

Failing over to the second node of Microsoft Cluster does not work if you use Enterprise Vault v.9.0.2. To fix this problem must upgrade to Enterprise Vault v.9.0.3.