VERIFIED SOLUTION i
X

How to rollback a Vault indexerd index

UPDATED: April 28, 2017


In the rare event of a Vault indexerd index corruption, it may be advantageous to roll back the Vault indexerd index to a previous version using the following steps.  Please consult Technical Support before attempting this.

1)  Find an indexerd log file from before there were problems with the index.  It should look something like this:

17:20:51 open log, date [2017/03/02], file [/home/PBBI CCM/Vault/server/log/indexerd.20170302.172051.9256.log]

17:20:51 module [Vault Indexer], version [7.0M2p0039]

17:20:51 platform [Linux], version [#1 SMP Tue Jul 14 02:46:51 EDT 2015], release [2.6.32-573.1.1.el6.x86_64], node [SERVER], machine [x86_64]

17:20:51 Vault Indexer 7.0M2p0039

17:20:51 (C) Copyright 1993-2013 Pitney Bowes Software Inc.

17:20:51 descriptor limits: soft [8192], hard [65536], want [65536]

17:20:51 changed descriptor limit to [65536]

17:20:51 pid file [/home/PBBI CCM/Vault/server/log/indexerd.pid]

17:20:51 starting

17:20:51 Starting 1 worker threads, channel [/idxreq.shared:0], Version [1]

17:20:51 Queue size: 200000 commands. Cache element count: 14530

17:20:51 Total cache size: 1024 MB Flush: 60 secs - Full: 1440 min.

17:20:51 Vault key compression enabled.

17:20:51 Maintain rollback history for at least 30 days.

17:20:51 Maintain rollback history for at least 10 version(s).

17:20:51 index server start

17:20:51 Starting indexer server

17:20:51 opening /MainData/index/index.dr2 Cache mode = 1

17:20:51 Starting Logger thread

17:20:51 Starting IO thread 1

17:20:51 IO thread started, timestamp [1], flush request [0]

17:20:51 Starting timer thread 3

17:20:51 Starting Queue thread 0

17:20:51 Opening existing database, file [/MainData/index/index.dr2]

17:20:51 Load root 2402604:11499 [0B23033D-0B07584EC20F-0B1B24A92C2CEB-0B175D756F0000-04]

17:20:51 Root record loaded 2402604:11499 Version: 809 tree: 829

17:20:51 Root updated 2402604:11499 Version: 830 Time: 2016/12/12 11:28:15 size: 401402167296

17:20:52 starting to process queue requests

17:20:52 started

17:20:52 Database versions found = 30

17:20:52 Tree: 828 2016/12/12 11:15:8 [0B23033C-0B07584EBEFC-0B1B24A92C2CA5-0B175D756D0000-C9]

17:20:52 Tree: 827 2016/12/7 10:8:51 [0B23033B-0B07584817F3-0B1B24A92C2C91-0B175D756D0000-F2]

17:20:52 Tree: 826 2016/12/7 9:53:44 [0B23033A-0B0758481468-0B1B24A92C2C55-0B175D756B0000-81]

17:20:52 Tree: 825 2016/11/30 16:17:57 [0B230339-0B07583F33F5-0B1B24A92C2C41-0B175D756B0000-D1]

17:20:52 Tree: 824 2016/11/30 16:5:24 [0B230338-0B07583F3104-0B1B24A92C2BDD-0B175D74910000-28]

17:20:52 Tree: 823 2016/11/30 10:36:39 [0B230337-0B07583EE3F7-0B1B24A92C2BC9-0B175D74910000-E5]

17:20:52 Tree: 822 2016/11/25 14:12:14 [0B230336-0B0758387EFE-0B1B24A92C2B79-0B175D715F0000-95]

17:20:52 Tree: 821 2016/11/22 20:41:56 [0B230335-0B075834E5D4-0B1B24A92C2B47-0B175D715F0000-EE]

17:20:52 Tree: 820 2016/11/20 15:59:37 [0B230334-0B07583200A9-0B1B24A92C270F-0B175D5D020000-FD]

17:20:52 Tree: 819 2016/11/19 8:14:55 [0B230333-0B075830423F-0B1B24A92C2557-0B175D5D020000-EF]

17:20:52 Tree: 818 2016/11/19 5:12:31 [0B230332-0B075830177F-0B1B24A92C2453-0B175D5D000000-3B]

17:20:52 Tree: 817 2016/11/18 17:47:30 [0B230331-0B07582F76F2-0B1B24A92C2395-0B175D5D000000-6E]

17:20:52 Tree: 816 2016/11/17 5:6:12 [0B230330-0B07582D7304-0B1B24A92C2007-0B175D36480000-CA]

17:20:52 Tree: 815 2016/11/17 2:28:58 [0B23032F-0B07582D4E2A-0B1B24A92C1EC3-0B175D36460000-BA]

17:20:52 Tree: 814 2016/11/16 8:37:35 [0B23032E-0B07582C530F-0B1B24A92C1DED-0B175D36460000-04]

17:20:52 Tree: 813 2016/11/16 2:28:21 [0B23032D-0B07582BFC85-0B1B24A92C1BDF-0B175D30360000-38]

17:20:52 Tree: 812 2016/11/15 15:18:46 [0B23032C-0B07582B5F96-0B1B24A92C19DD-0B175D13DE0000-35]

17:20:52 Tree: 811 2016/11/15 3:5:53 [0B23032B-0B07582AB3D1-0B1B24A92C1911-0B175D0FFD0000-0C]

17:20:52 Tree: 810 2016/11/14 19:57:28 [0B23032A-0B07582A4F68-0B1B24A92C179B-0B175D0D100000-4D]

17:20:52 Tree: 809 2016/11/14 8:30:8 [0B230329-0B075829AE50-0B1B24A92C146C-0B175D08A20000-85]

17:20:52 Tree: 808 2016/11/14 2:4:40 [0B230328-0B07582953F8-0B1B4D1428FFC0-0B175D08A20000-66]

17:20:52 Tree: 807 2016/11/13 2:37:44 [0B230327-0B0758280A38-0B1B4D1428FEBC-0B175D08A20000-9B]

17:20:52 Tree: 806 2016/11/13 1:24:30 [0B230326-0B075827F90E-0B1B4D1428FDF4-0B175D08A00000-97]

17:20:52 Tree: 805 2016/11/12 2:36:32 [0B230325-0B075826B870-0B1B4D1428FD9A-0B175D089E0000-F9]

17:20:52 Tree: 804 2016/11/11 21:34:53 [0B230324-0B07582671BD-0B1B4D1428FC1E-0B175D03610000-BC]

17:20:52 Tree: 803 2016/11/11 16:45:34 [0B230323-0B0758262DEE-0B1B4D1428FA84-0B175CD47E0000-00]

17:20:52 Tree: 802 2016/11/11 2:17:20 [0B230322-0B0758256270-0B1B4D1428F890-0B175C8B690000-64]

17:20:52 Tree: 801 2016/11/10 16:10:10 [0B230321-0B075824D422-0B1B4D1428F75A-0B175C886B0000-D6]

17:20:52 Tree: 800 2016/11/10 11:41:7 [0B230320-0B0758249513-0B1B4D1428F6C4-0B175C88630000-BE]

17:20:52 Tree: 799 2016/11/10 8:11:20 [0B23031F-0B07582463E8-0B1B4D1428F458-0B175C708D0000-57]

Each "Tree" represents a rollback point.

To perform the rollback:

A) stop indexerd (or all vault services)

B) copy /MainData/index/index.dr2 to /MainData/index/ORIGINGAL.index.dr2

C) in the /MainData/index/ directory, create a file called indexerd.rollback

D) the indexerd.rollback file needs to contain the following line:

[0B23033C-0B07584EBEFC-0B1B24A92C2CA5-0B175D756D0000-C9]  <--representing a selected tree found above

E) start indexerd (and the rest of the vault services)

F) if the indexerd.rollback file disappears, try to load a new file into Vault

Step B) is really important, because if the rollback fails for some reason, or even if it seems to work but later on after new data is added there is a problem, it will be important to have the ability to revert back to the state of the file before the rollback was attempted.

Environment Details

Windows, Linux

Downloads

  • No Downloads