Thursday, November 15, 2012
Very important troubleshooting step in case of cluster failure!
Go to command prompt and run following command: “cluster.exe /gen”
This command generates cluster log in the following location: c:\windows\cluster\reports\. If command is not ran – no cluster log generated.
Earlier this command ran, better chances it will have useful information to troubleshoot: default size of cluster logging is 100M, which is like 24hr of information before it gets overwritten.
I highly recommend increasing the cluster log size to maximum possible 1024M (if you can spare 1G C: drive for that).
Great article about the subject is here: http://blogs.technet.com/b/askcore/archive/2010/04/13/understanding-the-cluster-debug-log-in-2008.aspx
Friday, August 10, 2012
Restore from FlashBackup fails with error 2817 - Netbackup
Client name is case sensitive in Netbackup.
When specifying the client in "Backup, Archive and Restore" the name has to match the name in the client list of the backup policy (ie. serverA is not equal to SERVERA).
Failure to do so is another reason of error 2817 while restoring the file backed up by FlashBackup policy.
More on this: http://www.symantec.com/business/support/index?page=content&id=TECH188002
Monday, July 30, 2012
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
Monday, July 23, 2012
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
Thursday, July 12, 2012
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.
Wednesday, June 6, 2012
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)
Friday, May 18, 2012
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).
Subscribe to:
Posts (Atom)