Sponsored Content
Operating Systems Solaris Contingency planning for System Failure Post 302351590 by incredible on Wednesday 9th of September 2009 04:47:44 AM
Old 09-09-2009
minimum downtime is still not achieved. your method of creating a flar image to be used on a new disk might work, but why dont you first think of getting a 2nd hdd to mirror the root disk. In case of any failures, recovery is easier and unlikely downtime is required at all.
 

8 More Discussions You Might Find Interesting

1. What is on Your Mind?

Planning to be certified , your advice?

Hi, I got 2 courses Intermediate and advanced Solaris 10 Administration before 1 month. I was studying the material of the 1st course I will finish it soon. I want to get the Exam. What is your advice? Which is the best Exam Quastion ( Testking or ,,,,,,,, Etc) .... Regards (1 Reply)
Discussion started by: adel8483
1 Replies

2. Solaris

tools for capacity planning

Hi All, What do you usually use for capacity planning tool on solaris 8 or later? Thanks in advance. (2 Replies)
Discussion started by: itik
2 Replies

3. AIX

Use of System Planning Tool (SPT)

How to use system Planning tool. I have installed it and trying to just design something but i dont know any thing ...is there any documentation or questions to practice the SPT ? (1 Reply)
Discussion started by: pchangba
1 Replies

4. SCO

file system not getting mounted in read write mode after system power failure

After System power get failed File system is not getting mounted in read- write mode (1 Reply)
Discussion started by: gtkpmbpl
1 Replies

5. AIX

Planning to prepare for AIX P5 system admin test 223

Hi - one of my frined suggested me to complete the certification for AIX test 223. However, i am not aware of Unix OS and neither has experience of sys admin. I would like to know whether i would be able to prepare for AIX certification and also is it a must to have unix/Sun knowledge to prepare... (2 Replies)
Discussion started by: kbalakrishna200
2 Replies

6. Debian

"Your system had a kernel failure"

Hello everybody, I've been using Debian stable (currently Lenny) for more than one year, this is my first Linux. Never experienced any problems like this: when I logged in this morning, I got a message that said my kernel had had a failure and prompted me to send a report to www.kerneloops.org.... (2 Replies)
Discussion started by: bikmakk
2 Replies

7. UNIX for Dummies Questions & Answers

boot up failure unix sco after power failure

hi power went out. next day unix sco wont boot up error code 303. any help appreciated as we are clueless. (11 Replies)
Discussion started by: fredthayer
11 Replies

8. Filesystems, Disks and Memory

Help needed! Raid 5 failure on a Debian System

Hello! I have a 4-disc Raid 5 server running Open Media Vault (Debian). The other day, it disappeared from OMV, which was reporting 3 drives failed. Panic Stations. However, using MDADM I can get info from 3 of the drives which suggests they are functioning ok (info below). The remaining 4th... (1 Reply)
Discussion started by: jonlisty
1 Replies
DOWNTIMED(8)						      System Manager's Manual						      DOWNTIMED(8)

NAME
downtimed - system downtime monitoring and reporting daemon SYNOPSIS
downtimed [-D] [-d datadir] [-l log] [-p pidfile] [-S] [-s sleep] downtimed -v DESCRIPTION
The downtimed daemon waits in the background, frequently updating a time stamp file on the disk. If the daemon is killed with a signal associated with a normal system shutdown procedure, it will record the shutdown time on the disk. When the daemon is restarted during the next boot process, it will report how long the system was down and whether it was properly shut down or crashed. The downtime report is output to the system log or to a specified log file. Also a record is appended to the downtime database. OPTIONS
-D Do not create nor update the downtime database. -d datadir The directory where the time stamp files as well as the downtime database are located. The default directory is determined at com- pile time. -l log Logging destination. If the argument contains a slash (/) it is interpreted to be a path name to a log file, which will be created if it does not exist already. Otherwise it is interpreted as a syslog facility name. The default logging destination is "daemon" which means that the messages are written to syslog with the daemon facility code. -p pidfile The location of the file which keeps track of the process ID of the running daemon process. The system default location is deter- mined at compile time. -S Normally fsync(2) is performed after each update of the time stamp. This option disables the fsync(2). It reduces the load on the disk system but makes the downtime measurement less reliable. This option is not available on all systems. -s sleep Defines how long to sleep between each update of the on-disk time stamp file. More frequent updates result in more accurate downtime reporting in the case of a system crash. Less frequent updates decrease the amount of disk writes performed. The default is to sleep 15 seconds between eacch update. If you are using a flash memory based SSD or other disk which has limited amount of write cycles per block, it might be a good idea to set the sleep time to a higher value to prolong the lifetime of the storage device. -v Display the program version number, copyright message and the default settings. SIGNALS
SIGHUP Close and re-open the output log. Use in case you want to rotate the log file. SIGTERM and SIGINT Terminate gracefully. These signals signify that a graceful system shutdown is in process. EXIT STATUS
The daemon exits 0 on success, and >0 if an error occurs. SEE ALSO
downtimes(1), syslog.conf(5), http://dist.epipe.com/downtimed/ BUGS
The reporting accuracy in case of a system crash depends on how often the time stamp is updated. Finding out the system startup time is very operating system specific. If the program does not have specific code to support your operat- ing system, it assumes that the system started when the daemon started. Reporting is inaccurate if the system clock changes during system downtime or startup process. Daylight saving time changes have no effect as all calculations are done using UTC. COPYRIGHT
Copyright (C) 2009-2011 EPIPE Communications. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBU- TORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCURE- MENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABIL- ITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. The views and conclusions contained in the software and documentation are those of the authors and should not be interpreted as represent- ing official policies, either expressed or implied, of EPIPE Communications. version 0.5 2011-03-02 DOWNTIMED(8)
All times are GMT -4. The time now is 07:43 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy