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.

Exchange 2007 and ActiveSync. Which device?

To find out which device user utilizes to connect to Exchange 2007 following powershell command can be used:
Get-ActiveSyncDeviceStatistics -Mailbox domain\blye |
ft DeviceType, DeviceUserAgent, LastSuccessSync

Taken from here: http://www.simple-talk.com/sysadmin/exchange/identifying-exchange-activesync-users-with-powershell/ (with the small change you do have to use "domain\" in front of account name)

Symantec Enterprise Vault Compliance Accelerator v9 SP2 has synchronization with AD group broken

We noticed that employee group in EV CA v9 sp2 that synchronizes with AD group is empty after the upgrade from v8 sp4 to v9 sp2. Symantec Tech Support confirmed that issue is re-producible in their lab.

Let me note that the bug is VERY critical making the Compliance Accelerator scheduled searches return zero hits, because the target employee group has no employees.

The workaround is to synchronize the EV CA employee group with “Active Directory Container” and not “Windows group or distribution list”