Jase, The FTS reindexing finished this morning, thankfully! So I guess we still don't know for sure if a DB reboot would corrupt the index or not. Just thought I'd update you.
Thanks, Thad On Wed, Feb 18, 2015 at 2:37 PM, Jase Brandon <[email protected]> wrote: > ** > Hi Thad, my experience has been that the FTS index becomes corrupt and I > have to start the whole thing over. I hope it finishes before your DB > restart. Please let us know if it doesn't. I'd be interested to see if your > FTS index up to the point if restart is retained. Mine are not. Thanks ~ > Jase > > On Feb 18, 2015, at 1:20 PM, Thad Esser <[email protected]> wrote: > > ** > Jase, > > So I asked BMC the same questions, and they seemed to think that the > reindexing will weather the reboot fine. > > * How will this impact the FTS Reindex if it is still in progress? > > BMC : It will break your FTS Reindex for that time period. > > * Will the reindexing pick up where it left off once the DB connection > is re-established? (the AR Server usually recovers just fine these days) > > BMC : Yes the Reindex should attempt to pick up from where it left off. > > * Would shutting down the AR Server first make things worse, or better > (in terms of the re-indexing operations)? > > BMC : Either way, AR Server or DB being down breaks the FTS Reindex, so > it doesn't matter whoever is first down. > > * Are there any preventative steps I can take to keep the FTS index > from becoming corrupted (which seems to happen really easily and is my main > concern)? > > BMC : We do not expect any corruption to occur, But you can enable FTS > logs before server goes down to see any errors. > > I guess we'll see. I've got my fingers crossed that it just finishes > before then so I don't have to worry about it. > > Thanks, > Thad > > On Tue, Feb 17, 2015 at 3:22 PM, Jase Brandon <[email protected]> > wrote: > >> Hi Thad, short answer is you're screwed. I've been fighting this for >> months. There is an FTS fortification available if you're on the right >> version. See the link in my post I put up about 30-45 mins ago. Hope this >> helps - Jase >> >> > On Feb 17, 2015, at 5:07 PM, Thad Esser <[email protected]> wrote: >> > >> > ** >> > Hello, >> > >> > I find myself in a situation where I have an FTS reindex in progress >> that I don't think will be complete by this weekend, which is when our >> database server will be restarted. Due to other circumstances, I can't >> stop the rebooting of the database server. >> > * How will this impact the FTS reindex if it is still in progress? >> > * Will the reindexing pick up where it left off once the DB >> connection is re-established? (the AR Server usually recovers just fine >> these days) >> > * Would shutting down the AR Server first make things worse, or >> better (in terms of the re-indexing operations)? >> > * Are there any preventative steps I can take to keep the FTS index >> from becoming corrupted (which seems to happen really easily and is my main >> concern)? >> > * Or am I just screwed, and am going to have to restart the FTS >> indexing again after the DB reboot? >> > >> > Thanks, >> > Thad >> > >> > Environment: ARS 8.1.0 on Windows with a remote SQL Server 2008 DB. >> Full 8.1 ITSM suite. >> > _ARSlist: "Where the Answers Are" and have been for 20 years_ >> >> >> _______________________________________________________________________________ >> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org >> "Where the Answers Are, and have been for 20 years" >> > > _ARSlist: "Where the Answers Are" and have been for 20 years_ > > _ARSlist: "Where the Answers Are" and have been for 20 years_ > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
