Sponsored Content
Operating Systems Solaris Clustering Solaris Zones/Containers Post 302187548 by DukeNuke2 on Monday 21st of April 2008 12:05:00 PM
Old 04-21-2008
imho this is no knowledge to serach in a forum. this is mission critical and should be done by specialised consultants!

however:
for a maximum on uptime you can use "liveupgrade". you need another disk in your server and can make a online copy of your running system. this copy can be patched and all you need as downtime is "one reboot" (which can take a long timeSmilie).
 

5 More Discussions You Might Find Interesting

1. Solaris

solaris containers/zones reboot order

Hi, I'm running containers/zones on Solaris 10: SunOS be2900 5.10 Generic_118833-33 sun4u sparc SUNW,Netra-T12 zoneadm list -vc gives: ID NAME STATUS PATH 0 global running / 1 bvsmapp01 running /zones/bvsmapp01 2... (3 Replies)
Discussion started by: jabberwocky
3 Replies

2. Solaris

need help on containers/zones

Hello, I have been using sparc workstations :SUNW,Ultra-5_10 Total 4 such machines. Users use it for mpich programming and all run solaris 8 but I always have hard time maintaining these machines. Authentication for these machines work from solaris 10 using NIS and there are nfs mounts on... (14 Replies)
Discussion started by: upengan78
14 Replies

3. Solaris

Solaris 8 Containers

While installing a Solaris 8 zone to a Solaris container I received this message. Anyone have this problem? Patchadd is terminating. Postprocess: Applying p2v module S31_fix_net Postprocess: Applying p2v module S32_fix_nfs Postprocess: Applying p2v module S33_fix_vfstab ... (1 Reply)
Discussion started by: cornsnap
1 Replies

4. Solaris

difference between zones and containers

Hi Expects, Can broadly explain difference between Zones and containers. (4 Replies)
Discussion started by: Rajesh_Apple
4 Replies

5. Red Hat

Looking for equivalent of Solaris containers/zones in RHEL7 Linux

Hi, I come from a legacy Solaris background with lots of experience with Solaris Containers/zones that we use for network and process isolation from each other. Currently we have a RHEL7 Linux VM running on VMWare, but we would like to segment that VM with some form of containers and achieve... (1 Reply)
Discussion started by: ckmehta
1 Replies
DOWNTIMES(1)						      General Commands Manual						      DOWNTIMES(1)

NAME
downtimes - display system downtime records made by downtimed(8) SYNOPSIS
downtimes [-d downtimedbfile] [-n num] [-s sleep] downtimes -v downtime [-d downtimedbfile] [-n num] [-s sleep] downtime -v DESCRIPTION
The downtimes command displays the contents of the downtime database in human readable format. The downtime database is maintained by down- timed(8). The singular form downtime displays details only about the last time the system was down, whereas the plural form downtimes displays all records in the database. The -n option can be used to specify the number of downtime records to display. OPTIONS
-d downtimedbfile Use the specified downtime database file instead of the system default. -n num Define how many latest downtime records to output. Default is all. -s sleep Calculate the approximate crash time by specifying what was the sleep value of downtimed(8). -v Display the program version number, copyright message and the default settings. EXIT STATUS
The program exits 0 on success, and >0 if an error occurs. SEE ALSO
downtimed(8), uptime(1), http://dist.epipe.com/downtimed/ BUGS
The reporting accuracy in case of a system crash depends on how often the time stamp is updated. 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 DOWNTIMES(1)
All times are GMT -4. The time now is 07:58 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy