08-07-2009
Live / DR failover, assumes shared storage, mutual SAN, or some sort of replication. Storage to oneside, zones will allow you to move the application, as would RSF / SunCluster clustering software. So, clustering would cater for your needs too.
Centralised storage might be a bigger problem, as the live and dr systems will be in different physical locations ? Different IP addresses ??
Containers / zones - containers has some sort of resource control i.e. number of cpus / memory, zones are like containers but a more fluid set of resource controls.
Im currently do the same thing as you, looking at creating a DR of my live server, using zones / RSF.
SBK
4 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
I have compiled binary file using "cc" on SunOS 5.8 and the same binary file i have copied to SunOS 5.9 and it is giving me core dump error.I want to know whether migration of compiled code from lower version to higer version created this problem. how can i solve this problem.I am pasting the core... (1 Reply)
Discussion started by: Arvind Maurya
1 Replies
2. Virtualization and Cloud Computing
HPL-2008-72 Facebook Meets the Virtualized Enterprise - Curry, Roger; Kiddie, Cameron; Markatchev, Nayden; Simmonds, Rob; Tan, Tingxi; Arlitt, Martin; Walker, Bruce
Keyword(s): social networking, Web 2.0, cloud computing
Abstract: "Web 2.0" and "cloud computing" are revolutionizing the... (0 Replies)
Discussion started by: Linux Bot
0 Replies
3. Solaris
Good day, everyone, and thanks first off for reading my question.
So, I have been Googling and reading oracle documentation for the past couple weeks, and I am just getting more and more confused as to what I need to do, and I would really appreciate some guidance or at least pointing me to... (4 Replies)
Discussion started by: Lyxix
4 Replies
4. Linux
Hi
I need to know what is the unique identifier for Linux OS even in a virtualized environment?
eg like Machine GUID for windows. I need to know something similar for linux, AIX, Solaris in virtualized environment.
Thanks (6 Replies)
Discussion started by: skyineyes
6 Replies
LEARN ABOUT SUNOS
zoneadmd
zoneadmd(1M) zoneadmd(1M)
NAME
zoneadmd - zone administration daemon
SYNOPSIS
/usr/lib/zones/zoneadmd
zoneadmd is a system daemon that is started when the system needs to manage a particular zone. Because each instance of the zoneadmd daemon
manages a particular zone, it is not unexpected to see multiple zoneadmd daemons running.
This daemon is started automatically by the zone management software and should not be invoked directly. The daemon shuts down automati-
cally when no longer in use. It does not constitute a programming interface, but is classified as a private interface.
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWzoneu |
+-----------------------------+-----------------------------+
|Interface Stability |Private |
+-----------------------------+-----------------------------+
svcs(1), zlogin(1), svcadm(1M), zoneadm(1M), attributes(5), smf(5), zones(5)
The zones(5) service is managed by the service management facility, smf(5), under the service identifier:
svc:/system/zones:default
Administrative actions on this service, such as enabling, disabling, or requesting restart, can be performed using svcadm(1M). The ser-
vice's status can be queried using the svcs(1) command.
1 Nov 2004 zoneadmd(1M)