Document 6503094

Transcription

Document 6503094

Anbefalinger rundt maskinvare og
programvare for Cloud Control i
forhold til SLA krav
Trond Brenna
Senior Sales Consultant
Core-Tech
June 06, 2014
Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Oracle Confidential – Internal/Restricted/Highly Restricted
Safe Harbor Statement
The following is intended to outline our general product direction. It is intended for
information purposes only, and may not be incorporated into any contract. It is not a
commitment to deliver any material, code, or functionality, and should not be relied upon
in making purchasing decisions. The development, release, and timing of any features or
functionality described for Oracle’s products remains at the sole discretion of Oracle.
3
Agenda
1
Meeting Hardware requirements
2
EM12c High Availability
3
Best Practices
4
References
4
Agenda
1
2
3
Best practices
4
References
5
Hardware requirements for OMS server
Simple Installation
Advanced Installation
(small)
1 OMS,
<100 Targets,
<10 Agents,
<3 Concurrent Usre
Sessions
1 OMS,
<1000 Targets,
<100 Agents,
<10 Concurrent User
Sessions
2
2
4
8
4 GB
6 GB
8 GB
16 GB
Oracle WebLogic
Sever JVM Heap
Size
800 MB
1.7 GB
4 GB
8 GB
Hard Disk Space
15 GB
15 GB
15 GB
15 GB
Configuration
CPU Cores/Host
RAM
(medium)
(large)
2 OMSes,
> 2 OMSes,
>=1000 but <10.000
>=10.000 Targets, >=1000
Targets,
Agents,
>=100 but <1000 Agents, >=25 but <=50 Concurrent
>=10 but <25 Concurrent
User Sessions
User Sessions
6
CPU, RAM, and Hard Disk Space Requirements for Oracle
Management Agent
• For a standalone Management Agent, ensure that you have 2 CPU cores
per host, 512 MB of RAM, and 1 GB of free hard disk space.
• For a Master Agent, ensure that you have 2 CPU cores per host, 512 MB of
RAM, and 1 GB of free hard disk space.
• For a Shared Agent, ensure that you have 2 CPU cores per host, 512 MB of
RAM, and 15 MB of free hard disk space.
7
Hardware requirements for Management Repository
Simple Installation
(small)
1 OMS,
<100 Targets,
<10 Agents,
<3 Concurrent User
Sessions
1 OMS,
<1000 Targets,
<100 Agents,
<10 Concurrent User
Sessions
CPU Cores/Host
-
2
4
8
RAM
-
6 GB
8 GB
16 GB
15 GB
50 GB
200 GB
300 GB
Configuration
Hard Disk Space
(medium)
(large)
2 OMSes,
> 2 OMSes,
>=1000 but <10.000
>=10.000 Targets, >=1000
Targets,
Agents,
>=100 but <1000 Agents, >=25 but <=50 Concurrent
>=10 but <25 Concurrent
User Sessions
User Sessions
8
Customer examples
Customer 1
Customer 2
In
use
No. of
targets
DB
targets
OS on
OMS
and
EMREP
host
2 yrs
1170
150
Red Hat
5.x
550
RHEL/OL
5.9
2 yrs
1547
Memory
on OMS
host
Memory
on
EMREP
host
SGA on
EMREP
DB
Size
EMREP
DB
12 GB
12 GB
3 GB
30 GB
EM11g, OMS and
EMREP share host
95 GB
EM12c, 2 OMS,
RAC 2 node
EMREP
48 GB
48 GB
5 GB x2
Number
of jobs
daily
200
Comment
9
Agenda
1
2
3
Best practices
4
References
10
How important is EM12c for your business?
• Criteria's for choosing HA level
– Number of users
– 24/7 helpdesk
– Backup scheduled from EM12c
– Self Service
– Data Movement jobs
– Can you diagnose without EM12c?
• Choose HA level for your needs
11
Enterprise Manager High Availability Levels
Level
Min
number of
nodes
Description
Recommended
Load Balancer
number of
requirements
nodes
Level 1
OMS and repository database. Each resides on their
own host with no failover.
1
2
None
Level 2
OMS installed on shared storage with a VIP based
failover. Database is using Local Data Guard.
2
4
None
Level 3
OMS in Active/Active configuration. The database is
using RAC + Local Data Guard
3
5
Local Load Balancer
Level 4
OMS on the primary site in Active/Active Configuration.
Repository deployed using Oracle RAC.
Duplicate hardware deployed at the standby site.
DR for OMS and Software Library using Storage
Replication between primary and standby sites.
Database DR using Oracle Data Guard.
4
8
Required: Local Load
Balancer for each
site.
Optional: Global
Load Balancer
12
Adding an OMS
• You can clone only an existing, running Oracle Management Service 12c that is associated with an AdminServer host. The patches
applied on the source OMS are automatically carried over to the cloned instance.
• You can clone only one OMS at a time and to only one destination host at a time. If you want to add multiple OMS instances, then
you must repeat the installation procedure on each host.
• You can clone only when the source host and the destination host are running on the same operating system and architecture. For
example, if the source host is a Linux 32-bit host, then the destination host must also be a Linux 32-bit host. Similarly, if the source
host is a Linux 64-bit host, then the destination host must also be a Linux 64-bit host.
• All general purpose file systems, including OCFS2 and ACFS, are acceptable for storing Enterprise Manager Cloud Control
12c software binaries and OMS instance home files (configuration files in gc_inst). However, OCFS is not considered a general
purpose file system, and therefore is not considered acceptable for this use.
• You must not install the additional OMS on an NFS-mounted drive. Installing it on an NFS-mounted drive causes the Oracle HTTP
Server to restart frequently, which in turn makes the OMS inaccessible. If you are forced to install on such a shared drive, then
ensure that the OMS instance base directory (gc_inst) is created in a non-NFS-mounted location.
• You can find the OMS and Management Agent entries in the /etc/oragchomelist file for all UNIX platforms except HPUNIX, HPia64,
Solaris Sparc. On HPUNIX, HPia64, Solaris Sparc platforms, the entries are present in /var/opt/oracle/oragchomelist.
13
Server Load Balancer Requirements
In order to configure your OMS's in an active/active configuration behind an SLB, your SLB must meet the
following requirements:
• The SLB must provide support for multiple virtual server ports.
Enterprise Manager typically requires that up to 4 ports are configured on the SLB
(Secure Upload, Agent Registration, Secure Console, Unsecure Console)
• Support for persistence.
HTTP and HTTPS traffic between the browser and the OMS requires persistence.
• Support for application monitoring.
The SLB must be capable of monitoring the health of the OMSs and detecting failures,
so that requests will not be routed to OMSs that are not available.
14
Disaster Recovery Topology
The solution has two sites. The current
production site is running and active, while
the second site is serving as a standby site
and is in passive mode.
Oracle Data Guard Physical Standby is used
to replicate Repository transaction from
primary site to standby site.
OMS hosts on each site have mount points
defined for accessing the shared storage
system for the site.
15
Backing Up and Recovering Enterprise Manager
Software Components
• Oracle Management Services (OMS)
• Management Agent
• Management Repository
• Software Library
16
Software Components
• Oracle Management Services (OMS)
• Management Agent
• Management Repository
• Software Library
Each component, being uniquely different in composition
and function, requires different approaches to backup and recovery.
17
Software Components - Software Library Backup
• The software library is a centralized media storage for Enterprise Manager software entities such as software
patches, virtual appliance images, reference gold images, application software, and
their associated directive scripts.
• The software library storage locations should be backed up periodically using file system backup.
• Oracle recommends the backup be performed at a frequency of 1 to 24 hours.
18
Software Components - Management Repository Backup
• Database should be in archivelog mode. Not running the repository database in archivelog mode leaves
the database vulnerable to being in an unrecoverable condition after a media failure.
• Perform regular hot backups with RMAN using the Recommended Backup Strategy option via
the Cloud Control console. Other utilities such as DataGuard and RAC can also be used as part of a
comprehensive strategy to prevent data loss.
19
Software Components - Oracle Management Service Backup
• Software Homes
Composed of Fusion Middleware Home, the OMS Oracle Home and the WebTier (OHS) Oracle Home and
multiple Management Plug-in Oracle Homes.
Software Homes changes when patches or patchsets are applied or updates are applied through the new
Self Update feature. For this reason, filesystem-level backups should be taken after each patch/patchset
application or application of updates through Self Update. You should back up the Oracle inventory files along
with the Software Homes and save the output of opatch lsinventory –detail to make it easy to determine which
patches are applied to the backed up Oracle Homes.
• Instance Home
The gc_inst directory, composed of WebLogic Server, OMS and web tier configuration files.
The Instance Home can be backed up using the emctl exportconfig oms command.
• Administration Server
The Administration Server operates as the central control entity for the configuration of the entire OMS instance
domain. The Administration Server is an integral part of the first OMS installed in your Cloud Control deployment
and shares the Software Homes and Instance Home.The Administration Server is backed up at the same time
as the Instance Home, the emctl exportconfig oms command
20
Software Components - Management Agent Backup
• There are no special considerations for backing up Management Agents. As a best practice, reference
Management Agent installs should be maintained for different platforms and kept up-to-date in terms
of customizations in the emd.properties file and patches applied. Use Deployment options from the
Cloud Control console to install and maintain reference Agent installs.
• If a Management Agent is lost, it should be reinstalled by cloning from a reference install.
21
Software Components – Recovery steps and scenarios
Oracle® Enterprise Manager Cloud Control Administrator's Guide
12c Release 3 (12.1.0.3)
E24473-27
Chapter 31 Backing Up and Recovering Enterprise Manager
http://docs.oracle.com/cd/E24628_01/doc.121/e24473/ha_backup_recover.htm#BGBCCIJC
22
Agenda
1
2
3
Best practices
4
References
23
Best practices for EM12c
• Install according to
documentation
• Create EMREP DB with
templates
• Use Oracle Linux
• Minimum 4 GB memory
per WLS instance
• Use HA level 1 or 3 for
simplicity
• Minimum 12 GB memory
on EMREP DB
• Recommended physical
host
• Read maintaining EM12c
Best practices notes on
MOS.
24
Agenda
1
2
3
Best practices
4
References
25
References
• Basic installation guide chapter 3
http://docs.oracle.com/html/E22624_20/preinstall_req_hw.htm#BACDDAAC
• Oracle® Enterprise Manager Cloud Control Administrator's Guide
12c Release 3 (12.1.0.3)
E24473-27
• OEM 12c: Troubleshooting OMS and UI Performance Issues (Doc ID
1460408.1
26
27

Document 6503094

Transcription

Similar documents

10559 Adv_spread Woestijn.indd

Elogix – Oracle Practice - Elogix Software Pvt Ltd

UNITASK DIRECT PRINT

uu tn fllu [rnrln - School of Computing

Planning Xtream - MindStream Analytics

Oracle Audio

Providing comPrehensive, Personalised solutions for high net worth

Oracle 10g release 2

QuickStream