Re: [Samba] Re: Best practices for long-running Samba server
On Thu, 27 Jan 2005 14:14:46 -0800, Spike Burkhardt <[EMAIL PROTECTED]> wrote: > Paul & David, > > Good points that I agree with but at least at three managers I've had want > to the uptime get bigger & bigger. Something about the 99.95% uptime > "industry standard." :-((( Ridiculous. They are wrong. Tell them gently that they should not confuse uptime with availability. A planned reboot at 03:00 that has no effect on the availability of the server is much better than an unexpected outage at 14:25 because a leaking database backend ate all your shared memory segments. That does wonders for availability. If you can't trust your machines to reboot themselves unattended and bring themselves back up to operational status then you have shall have to bring a pair of pyjamas into work and set up a cot in the machine room. 99.95% is about 4 and half hours per year. Ask your managers to cover you for the allowance of having a server being offline one whole afternoon per year. Ask for it in writing. David -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Re: Best practices for long-running Samba server
The client running our first Samba3 PDC production server had an uptime of 115 days, then the uptime got spoiled by them moving to a new building. I'm not quite sure what the fascination is with long uptimes. It's good to reboot the system from time to time, not because it needs it, but just to prove that you still can. Here here. I've seen it posted elsewhere and it makes a good point - long uptimes show that the machine hasn't had its updates run on the core OS. Until you can find a way to reload the kernel without rebooting (oxymoron) long uptimes are a mark of lazyness. What I'd rather see is longest stretch of not having to be rebooted between the hours of 7am and 6pm. Unfortunately the uptime command doesn't tell us that ;) bigger. Something about the 99.95% uptime "industry standard." :-((( Ridiculous. I tell ya, if 99.95, or 5-9s or whatever metric you use is that standard, perhaps they should talk to my cable company :-P Point somewhat taken. I say somewhat because if you're offering that type of reliability guarantee (which is what it is, says nothing about uptime really) then you need redundancy, redundantly. People that sell that kind of uptime have dual/quad/N+1 servers that they provision from and that fail over nicely. People that buy that kind of service pay for it, one way or another. Can't speak about telco numbers, I think you can buy that on your OC-X line if you want to pay enough, but I'm not sure how THEY do it. I for one prefer to reboot my machines in the off hours from home and drive in to the office when the fertilizer hits the ventilator. I think it's been 2 years since I caused some mid-day downtime on the main server in my particular office :-P -- -- Paul GiengerOffice: 701-281-1884 Applied Engineering Inc. Systems Architect Fax:701-281-1322 URL: www.ae-solutions.com mailto: [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Re: Best practices for long-running Samba server
Paul & David, Good points that I agree with but at least at three managers I've had want to the uptime get bigger & bigger. Something about the 99.95% uptime "industry standard." :-((( Ridiculous. spike Paul Gienger wrote: > David Landgren wrote: > > >>The client running our first Samba3 PDC production server had an uptime of > >>115 days, then the uptime got spoiled by them moving to a new building. > >> > >> > > > >I'm not quite sure what the fascination is with long uptimes. It's > >good to reboot the system from time to time, not because it needs it, > >but just to prove that you still can. > > > > > Here here. I've seen it posted elsewhere and it makes a good point - > long uptimes show that the machine hasn't had its updates run on the > core OS. Until you can find a way to reload the kernel without > rebooting (oxymoron) long uptimes are a mark of lazyness. > > What I'd rather see is longest stretch of not having to be rebooted > between the hours of 7am and 6pm. Unfortunately the uptime command > doesn't tell us that ;) > > -- > -- > Paul GiengerOffice: 701-281-1884 > Applied Engineering Inc. > Systems Architect Fax:701-281-1322 > URL: www.ae-solutions.com mailto: [EMAIL PROTECTED] > > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Re: Best practices for long-running Samba server
David Landgren wrote: The client running our first Samba3 PDC production server had an uptime of 115 days, then the uptime got spoiled by them moving to a new building. I'm not quite sure what the fascination is with long uptimes. It's good to reboot the system from time to time, not because it needs it, but just to prove that you still can. Here here. I've seen it posted elsewhere and it makes a good point - long uptimes show that the machine hasn't had its updates run on the core OS. Until you can find a way to reload the kernel without rebooting (oxymoron) long uptimes are a mark of lazyness. What I'd rather see is longest stretch of not having to be rebooted between the hours of 7am and 6pm. Unfortunately the uptime command doesn't tell us that ;) -- -- Paul GiengerOffice: 701-281-1884 Applied Engineering Inc. Systems Architect Fax:701-281-1322 URL: www.ae-solutions.com mailto: [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Re: Best practices for long-running Samba server
> The client running our first Samba3 PDC production server had an uptime of > 115 days, then the uptime got spoiled by them moving to a new building. I'm not quite sure what the fascination is with long uptimes. It's good to reboot the system from time to time, not because it needs it, but just to prove that you still can. There's nothing like sweating profusely when a server crashes at 9:25 one morning and refuses to come back up and you don't know where to start looking to make you think that uptimes aren't the be-all and end-all. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Re: Best practices for long-running Samba server
The client running our first Samba3 PDC production server had an uptime of 115 days, then the uptime got spoiled by them moving to a new building. I have all client side needs automated, so maybe since they do not use Windows Explorer to rove the network we have the lack of issues? I have seen the warning in the docs to back up those TDB files each time you stop the daemons... but I never stop them! ;-) So, would be interested in reading suggested best practices just in case life gets interesting here at some point. -- Michael Lueck Lueck Data Systems Remove the upper case letters NOSPAM to contact me directly. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
