10-08-2008
If you have more than 15 minutes to plan for "emergency shut down" of your servers, I'd recommend:
1. All applications that are running have corresponding startup and shutdown scripts in rc.*
2. Identify the order that your hosts should be shutdown in - NIS or LDAP should shutdown last, NFS servers second last... NTP would go first...
3. Write scripts.
You need to send a wall to all users connected informing them of an impending outage.
You need to ensure that you send the right shutdown options to the right OS types.
You need to create for each command that you are sending - for audit and CYA purposes later.
4. Inform your business/clients/users that these are the "emergency shutdown" procedures. Get them to sign-off and buy into them. If they have special requirements, amend your policy to include those.
Ensure that you have adequate time to shutdown storage devices that may have a great deal of data in cache. Ensure that you have adequate time to shutdown tape storage systems, as the robotics may need more time to get to "home" than you might expect.
There is no shortage of things that you could do, but this should get you started.
Last edited by avronius; 10-08-2008 at 03:17 PM..
Reason: Grammer
8 More Discussions You Might Find Interesting
1. SCO
I need to boot an OpenServer 5.0.5 server but I don't have emergency boot disks for it. There are some boot disks of other servers.
Can I use these disks, changing defbootstr ?. How ?.
The fact is that administrator can't login as root and it seems to be a corrupted auth system issue. Other... (2 Replies)
Discussion started by: dags
2 Replies
2. Shell Programming and Scripting
I'm trying to write a script to push out to all our servers some Veritas add-ons. I want the script to push to all servers and if there server hardware matches the uname -i statement, it will install a additional add-on.. The script keeps giving me a error on line 29. Here is the script.... (3 Replies)
Discussion started by: soupbone38
3 Replies
3. UNIX for Dummies Questions & Answers
I have Oracle 9i R2 on AIX 5.2. My Database is running in shared server mode (MTS).
Sometimes when I shutdown the database it shutsdown cleanly in 4-5 mints and sometimes it takes good 15-20 minutes and then I get some ora-600 errors and only way to shutdown is by opening another session and... (7 Replies)
Discussion started by: aixhp
7 Replies
4. Ubuntu
Hi guys
i have some question about ubuntu(10.10)
1.what time scheduling & page replacement algorithm have been used in ubuntu
2.how to create a process
3.how to kill a process
4.how to send information to a process
5.how to see a process
6.how to increase priority of a process
7.how to... (1 Reply)
Discussion started by: mortez28
1 Replies
5. Solaris
Hi Guru's,
I am unable to mount NFS share on unix system (DG/UX) which is nfs client.
Error:
mount: /nfsshare: Invalid argument
mount: giving up on:
/mountpoint
i tried following commands
mount -t nfs remotehost:/nfsshare /mountpoint
Error:
mount: /nfsshare: Invalid... (1 Reply)
Discussion started by: Justin John
1 Replies
6. Solaris
Dear all,
Kinda lame question but i'd like to hear your experiences and advice.
Question in short
-----------------
What permission should a mount point "ideally" have - i think it's root.
Ex:- /usr/app/ i'd set the app to be owned by root and within /usr/app i would create another... (1 Reply)
Discussion started by: ossupport55
1 Replies
7. Shell Programming and Scripting
can anyone please tell me that how can i boot unix from a cd? full procedure.
it's an emergency. reply asap (1 Reply)
Discussion started by: niket agarwal
1 Replies
8. Linux
Hello admins and gurus
I have a controversial topic: now we are investing in a new Linux OS that will hold our Sybase database. The server will virtualized on a VMware server hosted on SAN storage. Now the question is, when we install the database engine is it better - in terms of performance -... (1 Reply)
Discussion started by: abohmeed
1 Replies
LEARN ABOUT OPENSOLARIS
shutdown
shutdown(1B) SunOS/BSD Compatibility Package Commands shutdown(1B)
NAME
shutdown - close down the system at a given time
SYNOPSIS
/usr/ucb/shutdown [-fhknr] time [warning-message]...
DESCRIPTION
shutdown provides an automated procedure to notify users when the system is to be shut down. time specifies when shutdown will bring the
system down; it may be the word now (indicating an immediate shutdown), or it may specify a future time in one of two formats: +number and
hour:min. The first form brings the system down in number minutes, and the second brings the system down at the time of day indicated in
24-hour notation.
At intervals that get closer as the apocalypse approaches, warning messages are displayed at terminals of all logged-in users, and of users
who have remote mounts on that machine.
At shutdown time a message is written to the system log daemon, syslogd(1M), containing the time of shutdown, the instigator of the shut-
down, and the reason. Then a terminate signal is sent to init, which brings the system down to single-user mode.
OPTIONS
As an alternative to the above procedure, these options can be specified:
-f Arrange, in the manner of fastboot(1B), that when the system is rebooted, the file systems will not be checked.
-h Execute halt(1M).
-k Simulate shutdown of the system. Do not actually shut down the system.
-n Prevent the normal sync(2) before stopping.
-r Execute reboot(1M).
FILES
/etc/rmtab remote mounted file system table
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWscpu |
+-----------------------------+-----------------------------+
SEE ALSO
fastboot(1B), login(1), halt(1M), reboot(1M), syslogd(1M), sync(2), rmtab(4), attributes(5)
NOTES
Only allows you to bring the system down between now and 23:59 if you use the absolute time for shutdown.
SunOS 5.11 11 Oct 1994 shutdown(1B)