Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I like keeping my home workstations up as long as possible without a reboot. But, for a Linux box running production I feel it is better to give it what I call a sanity check by rebooting it on a regular schedule. Reboot every 30, 60 or 90 days.
The shop I'm woking in now has never done this. So that brought up the question, do you reboot your production servers on a scheduled interval? If so what's the interval? ...or do you think it is a dumb holdover type of idea from the days of older more troublesome hardware etc.
I agree it helps more often than not for Windoze, but this is a holdover from late eighties early ninties running AT&T 3b2's with System V os. Also a UNIX dirivitive named Gould made hardward and a custimized os which was a mix of System V and BSD that performed much better if we rebooted once a month.
Curently I'm running RHEL AS-3. We have big oracle databases housed on a SAN. We fracture (break the mirror) the DB every night for backup. Timing must be just right or all LUNS on the SAN do not remount. The only way we've fouond to get passed this is to reboot. After a reboot the nightly process works 80% better for a few weeks, then the problem comes up again. Thus the reason for my question. Thanks for the replies.
Most databases have the ability to unload the data to a flat file specifically for backup with integrity. I'm not familiar with Oracle, but I'd be amazed if it doesn't have this functionality. It also avoids the redundancy exposure and subsequent degradation from a split/rejoin for a mirror.
Another alternative is LVM2's snapshot capability which, again, is specifically designed for backups.
We have big oracle databases housed on a SAN. We fracture (break the mirror) the DB every night for backup. Timing must be just right or all LUNS on the SAN do not remount. The only way we've fouond to get passed this is to reboot.
OMG! What a nightmare! There has got to be a better way.