Server/Database Issues: An Apology, the Challenges and How to Fix It.

[keep]

Well if you wouldnt talk so much

Boy, I've been hearing that a lot lately.

[Grayson]

I'm bringing this back up as a reminder, since we had an "episode" over night.

FYI, Scott has the server in hand and working on the configuration. The plan is to migrate the site in the next few days, probably over the weekend. Again, hopefully we can avoid extended down time, but we'll try to update as Scott progresses.

Thanks again for your patience and understanding.

Michael

I hope it's not the same Scott who "works on" my office computer. Sheesh, that guy....

[Ol Thumper]

Michael we just need to go fishing and forget about it for a while

[WCB]

For the record this post will be #9801 just so we have it after the crash

That's all?? wimp...

[Artos]

The site does just fine with you ladies and gentlemen buying an occasional cap, shirt or koozie. There is no need to solicit donations. Thanks for all the support.

and yet my check has not been deposited...gonna tell mary if you gents don't stay on top of the cash flow.

[keep]

That's all?? wimp...

I'd have the same amount as you if I posted in the Union threads.

[Tx625]

Michael, instead of typing all that out, wouldn't have just been easier to say Mary has been fooling around with things again? J/K Hi Mary!

[Michael]

I'm going to update this thread for those who might have missed it.

After experiencing another corruption last night, we made the decision to proceed with the migration to the new server/host. Although it was a bit ahead of schedule and Scott still wanted to do some additional testing, we decided that the 4-plus hours invested in a recovery on the existing server would be better spent making the move to the new.

The transition was made relatively smoothly...except for the images (including the header images and banner ads), which presented Scott with an unexpected challenge (of course, in these types of major moves, you always have to expect the unexpected!)

Scott's team is still working on that issue, and we hope to have it resolved within a few hours.

In the meantime, thank you for your continued patience and understanding! Feel free to work around the mess until we get things cleaned up.

[Artos]

no worries boss...weekends are usually low mileaga anyway.


thanks for the help scott & team...

[DorothyNotKeegan]

No more DT's for me...

[Duane]

Run a R1 for the OS/Application, R1 for the Transaction Logs and a R5,R6 or R10 for the data.

At the very least create a seperate volume on the OS/Appllication drives to keep the transaction logs seperated from the OS/Application and Data.

As for the Data...It all depends on the drives sizes, recovery point objective and budget as to R5/R6 or R10.

For a Mission Critical Application - such as TBH. I would go with R1/R1/R10....I realize this may not be feasible based upon budget.

Bare minimum I would do R1 (2 x 300GB 10K SAS HDD's) and create two 150GB Volumes...One for the OS/Application and the other for the transaction logs...then create a R5 (min 3 hdd's - one drive is for parity)

I don't really care for R6 as you loose two drives for parity but gain very little additional fault tolerance.

R10 (minimum 4 HDD's) a mirror stipe so you get great read and write speeds with great fault tolerance.

Well Bruce, that all SOUNDS good, but none of that matters if you've got a bad flux capacitor. HAS ANYONE CHECKED THE FLUX CAPACITOR???

[timbobowhunter]

Thanks For All You Guys Do....and Thanks For Keeping Things Up, and Running.



Sent From My EVO Using Tapatalk.

[keep]

9,877

[Heath]

hi

[blong]

was worried that i might not get my fix for a day or 2