Friday, May 24, 2013

Enterprise Vault v10.0.x Index marked as failed 'The failed reason on the index volume indicates the sequence number of the index is higher than that in EV storage. Will check the sequence numbers before continuing with the synchronization.'

Index gets marked as failed and synchronization of the index job gets stuck.  When you open synchronization of the index report you see following in the job report:
………………
15/05/2013 22:02:53 Checking index volume for failed state.
15/05/2013 22:02:53 The failed reason on the index volume indicates the sequence number of the index is higher than that in EV storage. Will check the sequence numbers before continuing with the synchronization.
15/05/2013 22:02:53 The synchronize has been asked to stop and is stopping.
15/05/2013 22:03:03 The synchronize has resumed its processing.
15/05/2013 22:03:03 The synchronize has been asked to stop and is stopping.
………………
The problem was to just flip the status of the index in SQL by following queries ran against Directory DB:
update indexvolume
set Failed = 0 where Failed = 1 and foldername = '1126AEF7E8493C346B70D777F8A052E09_1592'
update indexvolume
set FailedVolumeReason = 0 where FailedVolumeReason = 3 and foldername = '1126AEF7E8493C346B70D777F8A052E09_1592'
where foldername is taken from the synchronization job report .

To monitor indexing catching up use following query against the Jounaling Vault database:
Select * from journalarchive where indexcommited = 0
This should return zero rows or more - number goes up and down when you constantly run it - less than 100.  When we had a problem it was 200,000 ish items waiting to be indexed.
For one of two Vaults it also needed reboot of the server to catch up.

Thursday, May 23, 2013

Enterprise Vault Discovery Accelerator Client is stuck on "Loading the item set"



 Symptom: DA user complaints that items are not loading for review with "Loading the item set" message is stuck on the screen
Following is the fix procedure - performed by knowledgeable sysadmin or dba admin on DA database::

1. Close the affected user's accelerator client
2. Find the PrincipalID of the affected user. Change 'smith' to that user's last name.
SELECT PrincipalID, PrincipalName FROM tblPrincipal WHERE PrincipalName LIKE '%smith%'
3. Find PrincipalIDs of users who have not used the DA Client:
SELECT PrincipalID, PrincipalName FROM tblPrincipal
WHERE ADSync = 1 AND SyncError = '' AND PrincipalID NOT IN (
SELECT PrincipalID FROM tblUserPreferences)
4. Update the user preferences table to change the PrincipalID of the affected user (A) to a user that does not have a DA client profile (B - one of the users found in step 3)
UPDATE tblUserPreferences SET PrincipalID = B where PrincipalID = A
5. Have the affected user log into the DA Client and then log out again. Logging out will create a new Profile in the user preferences table.
6. Have the affected user log back in and test the DA Client.
7. If this works remove the entry associated with user (B)
DELETE FROM tblUSerPreferences WHERE PrincipalID = B

If it doesn't fix the issue, Here is the query to revert the change:
DELETE FROM tblUSerPreferences WHERE PrincipalID = A
GO
UPDATE tblUserPreferences SET PrincipalID = A where PrincipalID = B

Wednesday, May 22, 2013

Exchange 2010 Hub/Cas Servers require space on C: drive or mail submission fails



Exchange 2010 Hub/Cas server needs extensive amount of free disk space on C: drive.  I had 1.8G free on C: drive, but it was not enough: mail submission from mailbox server was failing with event id 1009, none of emails sent from the mailbox server get processed.

Monday, May 6, 2013

How to change type of messages in the mailbox (Useful for dealing with Symantec Enterprise Vault)

DocMessageClass Utility allows changing type of messages from IPM.Note.PendingArchive (or PendingArchivePart) to IPM.Note (ie. normal message).  http://www.plustech.co.uk/Products/downloads/DocMessageClass.zip

I used it many times and found very useful. 

Wednesday, March 6, 2013

Restore from FlashBackup fails with error 2817 – Netbackup – transport mode



Another reason the restore from FlashBackup fails with error 2817 is wrong settings in the “Transport modes” section (second screen of the restore wizard).  Default settings are #1 and #2 – “san: Use san to move virtual disk data” and “nbdssl: Encrypt the virtual disk data for over-the-network transfers”.  In my environment the setting that works is #4: “nbd: Do not encrypt the virtual disk data for the over-the network trans..” (while having other 2 unchecked).

Wednesday, November 28, 2012

Restore Exchange 2007 Database to alternative forest Netbackup 7.5

I would like to share my experience/notes/tips restoring the user mailbox by restoring Exchange 2007 database to alternative forest when using Netbackup 7.5.

1. You will need to build alternative (restore) forest. You will need 2 servers – Domain Controller and Exchange Server – if you use x64 bit machines, you will also need workstation with Outlook
2. Install AD, Exchange 2007 Server
    2.1 Schema prep for Exchange should be run on DC; all other commands on Exchange server. Great link   on the subject: http://www.msexchange.org/tutorials/installing-exchange-2007-part1.html
    2.2 Exchange Org name in the restore forest must be identical to the production.
3. Create Storage Group and Mailbox Store in restore Exchange Server with names identical to production ones (if you have many SGs and MBs, create the one that you are going to restore)
4. Install Netbackup client on the restore Exchange Server
5. Follow article http://www.symantec.com/business/support/index?page=content&id=TECH57346 to create Recovery Storage Group (make sure you have enough disk space for restore both on data and log LUNs) and initiate restore
  5.1 On “Restore Marked Files/Microsoft Exchange” Tab (step 13 on the link above) uncheck “Mount database after restore”
 5.2 Make sure DNS resolution works between production and restore forests, use hosts file on restore Exchange Server and Netbackup master server if needed
6. Restore will run and fail with status 2850 (after committing logs on restore Exchange) – disregard the failure.
7. On restore Exchange in “Microsoft Exchange Troubleshooting Assistant” (you have it open following link in step 5) go back to task center “Go back to task center”
8. In the task list click: “Mount or dismount databases in the recovery storage group”, you should be offered the DB name that you just restored, and then complete task. DB should get successfully mounted.
9. Go back to task list
10. Click “Merge or copy mailbox Contents”
11. Mounted database should be selected by default, click “Gather merge information”
12. On next screen click “Perform pre-merge tasks”
13. After it runs, you should be able to see names of users in the restored database. Note to make sure you have the user you would like to restore listed. For example, we need to restore mailbox of ‘John Smith’, make sure you found ‘John Smith’ in the list of users.
14. Go back to Exchange Management Console and create a dummy user/mailbox that will be used to have mailbox content restored to “John Restored”
15. Go to Exchange Management Shell and run the command to restore mailbox content: Restore-Mailbox –rsgmailbox ‘John Smith’ –RSGDatabase ‘Recovery Storage Group\MB2’ –Identity “John Restored”
  15.1 Note: MB2 – Name of the database to restore
  15.2 –Identity – specifies the mailbox on restore Exchange where the content will be restored to.
16. You will be prompted to enter the “TargetFolder” – enter anything you like – that folder will be created under Inbox in the target mailbox (‘John Restored’)
17. After restore completes, login to the “John Restored” mailbox using Outlook on workstation (which was mentioned in step 1) and export mailbox content to pst.