login as: root
Using keyboard-interactive authentication.
Password:
Last login: Mon Dec 3 21:22:47 2012 from 10.152.39.133
Oracle Corporation SunOS 5.11 11.1 September 2012
You have new mail.
root@samplectrldom04:~#
root@samplectrldom04:~#
root@samplectrldom04:~# ldm ls
NAME STATE FLAGS CONS VCPU MEMORY UTIL UPTIME
primary active -n-c-- UART 64 261632M 0.1% 4d 3h 46m
root@samplectrldom04:~#
root@samplectrldom04:~#
root@samplectrldom04:~# ldm list-services primary
root@samplectrldom04:~#
root@samplectrldom04:~#
root@samplectrldom04:~# ldm add-vds primary-vds0 primary
root@samplectrldom04:~# ldm add-vcc port-range=5000-5100 primary-vcc0 primary
root@samplectrldom04:~# dladm show-link
LINK CLASS MTU STATE OVER
net1 phys 1500 up --
net4 phys 1500 up --
net3 phys 1500 up --
net0 phys 1500 up --
net2 phys 1500 up --
aggr1 aggr 1500 up net0 net1 net2 net3
root@samplectrldom04:~# ldm add-vsw net-dev=aggr1 primary-vsw0 primary
root@samplectrldom04:~# ldm list-services primary
VCC
NAME LDOM PORT-RANGE
primary-vcc0 primary 5000-5100
VSW
NAME LDOM MAC NET-DEV ID DEVICE LINKPROP DEFAULT-VLAN-ID PVID VID MTU MODE INTER-VNET-LINK
primary-vsw0 primary 00:14:4f:f9:ec:02 aggr1 0 switch@0 1 1 1500 on
VDS
NAME LDOM VOLUME OPTIONS MPGROUP
primary-vds0 primary
root@samplectrldom04:~# ldm set-mau 1 primary
1 crypto units exceeds the system capacity of 0 crypto units
root@samplectrldom04:~# ldm set-vcpu 8 primary
root@samplectrldom04:~# ldm set-memory 15g primary
Only 236G of memory could be removed from the primary domain
because the rest of the memory is in use.
root@samplectrldom04:~# Dec 4 21:23:26 samplectrldom04 ldmd[726]: [ID 574227 us
root@samplectrldom04:~# ldm ls
NAME STATE FLAGS CONS VCPU MEMORY UTIL UPTIME
primary active -n-cv- UART 8 19968M 0.2% 4d 4h 17m
root@samplectrldom04:~# ldm set-memory 15G primary
root@samplectrldom04:~# ldm ls
NAME STATE FLAGS CONS VCPU MEMORY UTIL UPTIME
primary active -n-cv- UART 8 15G 1.6% 4d 4h 18m
root@samplectrldom04:~#
root@samplectrldom04:~# ldm list-spconfig
factory-default [next poweron]
root@samplectrldom04:~# ldm add-config initial
root@samplectrldom04:~# ldm list-spconfig
factory-default
initial [current]
root@samplectrldom04:~#
root@samplectrldom04:~# w
9:27pm up 4 day(s), 4:19, 1 user, load average: 0.02, 0.09, 0.05
User tty login@ idle JCPU PCPU what
root pts/1 8:53pm w
root@samplectrldom04:~# reboot -- -r
#svcadm enable vntsd
1. configure ASR
2. configure cfg2html and monitor scripts
You can find solutions to issues for various UNIX operating systems Cloud and DevOps here. Also this site provides you career guidance to the beginners looking for a career as UNIX/ DevOps Engineers/ Administrator.
Host based Replication Solution for Disaster Recovery
High Availability Replication Solution

High Availability Replication Solution
The pace and
competitiveness of global commerce requires a flexible, resilient and available
IT infrastructure that provides 24 x 7 x 365 access to applications and information.
Any data, system or application downtime poses a threat to business operations
and can have serious repercussions for your organization’s profitability,
potentially impacting customers, reputation and revenue.
Achieving the new
levels of high availability required to support mission-critical systems puts
increased demands on IT and data center professionals.
The critical
prevailing question that arises after a system disaster is, how quickly applications
and data can be restored.
Many storage area
networks (SANs) today can replicate data across distances between similar
models of storage hardware and this can be an important part of any business
continuity or disaster recovery strategy. Our solution is a software-based
solution that also replicates data but at the host level, providing higher
availability when systems are at the same location and disaster protection and
recovery when they are not. Host-level file system replication occurs at the
byte-level which is almost always more efficient than block-level SAN
replication technologies and the application-aware monitoring and failover
capabilities of this solution make it an excellent choice for critical applications
such as Exchange and SQL Server. But what about organizations that have already
made significant investments in SANs and SAN based replication? Are these
solutions simply redundant? Do they provide no additional value or can they
serve a complementary function?
A disaster can take
many forms. Natural disasters like hurricanes, tornadoes, floods, fires and
earthquakes first come to mind. But the destruction of computer hardware is the
least likely cause of data loss. Less apparent disasters are statistically far
more prevalent. The number one culprit in data loss is the failure of computer
hardware components – power supplies, motherboards, disk drives, disk
controllers, network interfaces, etc. You can’t perform accounting functions if
the SQL Server-based system that hosts these applications fails, or email
important reports if you loose an Exchange server

Hardware malfunctions
and the second most common cause of failure, human error, cause over two-thirds
of data loss. Even software corruption, theft and computer viruses are each two
to four times as likely to cause data loss as the destruction of computer
hardware. Only three percent of the time is hardware destruction the culprit.
Whatever the cause, a disaster is anything that keeps an organization from
meeting its objectives. An objective might be as simple getting the day’s work
done, or it might be as tactical as providing a report to managers or as
strategic as providing an analysis to the board of directors or the chief legal
officer regarding a lawsuit. Sooner or later, smaller objectives lead to global
objectives of generating revenue and making a profit. Perhaps a disaster is
best defined as a condition where you don’t have the information to accomplish
these objectives.
Regardless of whether
you’re running critical business applications on Linux, Windows, UNIX or
another mainstream operating system, every organization faces critical intervals
when system downtime is unwelcome—whether it’s planned or unplanned.
Increasingly, shops
that were able to accommodate modest periods of downtime for backups and system
maintenance are finding increased server demands are closing backup windows.
Globalization and expanding online business opportunities have been a big
contributor to the unwelcomed contraction of periodic backup opportunities.
Since nearly all
organizations need to keep their systems available for increasing amounts of
time, they are now realizing that a system outage of even a few hours will
result in disruption, chaos and wasted capital. For many companies, exposure to
anything more than an hour or two of downtime has become unpalatable.
Benefits of this Replication Solution:
Simplicity – Deploy and configure the solution
quickly using advanced features that automate the initial setup and the ongoing
management of your availability environment.
Any-to-Any Protection - Ensure availability
redundancy across physical, virtual, and cloud environments to provide a
single-vendor solution in a complex data center.
Real-time Replication - Ensure the uninterrupted
availability of critical application systems and virtually eliminate the
potential for data loss.
Near-Zero Downtime During Migrations -
Real-time replication technology allows users to remain active while the
Availability Solution recreates the production environment on the new system.
Platform Independence - The Availability Solution allows
you to protect more of your environment, while spending less than you would for
other options.
Simplified Management - A unified console makes it
easier to implement, manage and extract value from a powerful HA environment.
Advantages:
·
No requirement for Storage,
since the tool can replicate from host to host
·
No need for similar type of
storage on PR and DR, since this tool can replicate between heterogeneous
storages
·
This tool is easy to install, use and administer.
·
Customer can implement it on a new server in
about 10 minutes.
·
Not have to spend time monitoring the solution
because it emails alerts if any issues arise.
·
No labor costs to manage the solution
·
Hardware independence and bandwidth efficient replication
·
Real-time protection and rapid workload recovery on any combination of
physical, cloud or virtual servers.
·
Continuous replication
enables near-instant recovery of business applications, files & data
·
Protects Exchange, SQL, IIS,
SharePoint, File Server, Oracle, Blackberry, vSphere, Hyper-V, XenServer,
Linux, UNIX etc.
·
Automated DR testing and/or
push-button fail-over, fail-back
·
WAN optimized replication
& jumpstart data seeding, for remote sites
·
Supports P2P, P2V,
cross-hypervisor V2V & V2P
·
Supports DAS, SAN, NAS &
cloud storage
·
Reduce costs by using public
& private cloud
·
Reduce costs using virtual
servers
·
Single solution for both
physical & virtual servers
Platform Supported
■ UNIX: – IBM AIX 5.3
TL12, (32- and 64-bit) 6.1 TL7, 7.1 TL1(64-bit only)
– Oracle Solaris 10, 11 SPARC(kernel level
144488 and later)/x86 (64-bit) (kernel level 144489 and later)
■ Linux – Red Hat
Enterprise Linux version 4 through 6.2 (i386 and x86-64)
- Novell SuSE Linux
Enterprise Server 9 through 11 SP1 (i386 and x86-x64)
- CentOS version 4
through 6.2 (i386 and x86-x64)
|
||||
|
Summary
• The critical issue after
a disaster is how quickly users can again work productively. Replicating data
to other sites is one issue. More important is having programs and processes
start, as well as Active Directory and DNS changes made, so that users can
reach the targets just like before the disaster
when the sources failed.
• For many, an automated
failover process with minimal to no human
intervention is needed to get users working again in a matter of minutes. For
others, a more time intensive manual process may be acceptable.
• SAN array-based
replication methods may be perfectly acceptable for synchronizing data to other
locations.
• Our Availability Solution
can automate the failover process of the operating system, network, and
applications. These can be on non-SAN array (internal or directly attached)
storage or even on separate SAN volumes not configured for SAN array based
replication.
• Our Availability Solution
can accommodate the differences in brand, processor, operating system and
adapters that may occur with a replacement server or component. Both
application and full system state protection and failover are available to
achieve the diverse situations one may encounter.
• Our Availability Solution
works equally well protecting physical and virtual workloads to any type of
target. Even the virtualization technology can be different (e.g., a vSphere
virtual machine to a Hyper-V virtual machine).
• Our Availability Solution
can be used to initially move the data and even the operating system and
application configurations from dissimilar storage to a new production
environment.
The above solution is based on "Double Take and Arcserv"
Subscribe to:
Posts (Atom)
Installing Ingress Controller - Kubernetes
Installing the Ingress Controller Prerequisites Make sure you have access to the Ingress controller image: For NGINX Ingress controll...
-
Decommission of LDOM ========================= ldm stop samplepdtestsun08 ldm unbind samplepdtestsun08 ldm destroy samplepdtestsun08 ...
-
There are 2 different ways of doing iSCSI target and initiator configuration. In below example I have done it using "tgtd" on t...
-
root@scw-530499:~# ps -ef |grep -i vault root 14891 14679 0 20:18 pts/3 00:00:01 ./vault server -config=example.hcl root 1514...