Essential Database Visibility for VMware Projects
IT needs additional visilibility when databases are moved from
physical to virtual servers. VMware tools do not cover the
database layer, and conventional database tools cannot capture
meaningful resource information from virtual servers. DBAs
cannot manage what they cannot see. IgniteVM removes the
availability and performance uncertainty that comes with shifting
critical databases from physical servers to VMware.
IgniteVM is the only monitoring tool that exposes the multiple
layers of the database and virtual machine architecture,
including database instance, virtual server and physical host
server resources. By knowing what changes in the virtual
server impact CPU, memory, or I/O, a DBA can ensure reliable
operations and service levels.
5 Key Risks of Running Databases on VMware
| VMware Obscures DBA Visibility - IgniteVM Restores
it |
| Inaccurate metrics |
All the server level statistics DBAs depend on, such as CPU,
I/O, and memory resources are no longer accurate on a virtual
server. IgniteVM shows the real resource pool. |
| Dynamically changing resources |
Physical resources can change fast, and without the DBA knowing
that resources have been re-allocated. IgniteVM gives the DBA
notice. |
| No control over host resources |
A new VM on the same host can steal resources and affect the
database. IgniteVM shows the DBA when this is happening. |
| No Management system visibility |
DBAs cannot see the vCenter console, but with IgniteVM they can
see essential parameters and statistics affecting their VM and
database, with no vCenter accees needed. |
| Silos between DBAs and VM administrators |
DBAs and VMware administrators often don't share information,
but IgniteVM brings the database layer and server layers together,
to improve communications and problem solving |
Agentless Architecture
IgniteVM on VMware takes advantage of the Ignite agentless
architecture to monitor database instances, virtual hosts, and
vCenter without installing any software on the monitored systems.
It is the lightest, least-intrusive method of capturing combined
database, physical server, and virtual server data.
How Does IgniteVM on VMware Work?
Ignite captures database performance and resource statistics
directly from the instance and stores them in the data warehouse
repository. Ignite uses read-only access to vCenter and to the
VMware ESX/ESXi server to capture data and store it in the same
way. Then Ignite correlates the samples and presents them to the
DBA in the browser based interface, tying the database and VMware
stats together in the easy to understand graphical display.
Important details:
- IgniteVM monitors all database instances simultaneously,
whether on physical or virtual servers.
- IgniteVM on VMware discovers the virtual server home and
details of each registered instance, and detects when virtual
servers move to different physical hosts.
- Data is stored in an Oracle or SQL Server instance, typically
non-production. Detailed history for any point in time stays
accessible, to answer the question 'what was going on with VMware
changes and database bottleneck' at a specific minute when we had a
problem.
- Read-only access to vCenter (recommended) and ESX and ESXi 4.0
and higher is needed. VMware admins can grant IgniteVM access to
vCenter without ever sharing VMware credentials with DBAs, and
credentials are encrypted to prevent DBA users from ever seeing
them.
- On its own, IgniteVM on VMware focuses on availability and
high-level instance performance. When used in combination with
Ignite8, it expands to provide a detailed database tuning and
monitoring solution along with virtual server data.
Download the free trial and be installed and
running in minutes.
Ignite System Requirements
A single Ignite installation can simultaneously monitor both
database instances ( Oracle, SQL Server, DB2, Sybase), physical
hardware, and virtual hardware. There are two choices for
download, depending on the type of server that Ignite will be
installed on: Windows or UNIX/Linux. For each, a single
download and packaged installation sets everything up, so you are
running in minutes.
Server Running Ignite Software
- The Ignite software can be installed on almost any Windows,
Unix or Linux server, either physical or virtual. It only needs an
operating system that can support Java JRE 1.5 or higher.
Repository hardware and configuration must meet minimum
requirements as shown below.
| # Number of monitored databases |
Minimum # of CPU |
RAM |
| <20 |
1 |
1 GB |
| 20-50 |
2 |
2 GB |
| 51-200 |
4 |
4 GB |
Ignite Repository Server:
- An Oracle or Microsoft SQL Server instance is utilized by
Ignite to collect and process data from monitored servers. A
dedicated instance is not required, but it cannot be the
"monitored" instance. The data collection server is defined as the
Ignite Repository server, and the requirements are listed
below.
- Ignite Repository requires either:
- Oracle 8.1.7 or higher (8i, 9i, 10g, 11g)
- Microsoft SQL Server 2000 SP3 or higher (2000, 2005, 2008,
2012)
- "Express" editions of both Oracle and SQL Server can hold a
repository but will likely run out of space due to the 4GB
limitations.
- Do not put the repository into an instance that will be
monitored. Doing so will affect the performance of that
instance.
- Installation requires access to a DBA (Oracle) or Sysadmin
(MSSQL) user for the install which will hold the repository.
- Repository hardware and configuration must meet minimum
requirements as shown below.
| # Number of monitored databases |
Repository Minimum # of CPU |
RAM |
| 1 |
1 |
512 MB |
| up to 5 |
2 |
1 GB |
| 5-200 |
4 |
4 GB |
Free Disk Space in Repository Instance: varies with number of
monitored database instances and level of activity on each:
| Monitored Database Activity |
Repository Disk Space per Monitored DB |
| Light |
1 GB to 3 GB |
| Medium |
3 GB to 5 GB |
| Heavy |
5 GB to 10 GB |
| Minimum Oracle Parameters |
| db_block_buffers (or db_cache_size) Note that this is a
critical parameter. |
>100 Mb per monitored database |
| shared_pool_size |
>50 MB |
| sort_area_size |
>4 MB |
| log_buffer |
>1 MB |
| session_cached_cursors |
>10 |
| Redo Log Size (select min(bytes) from v$log) |
>10 MB |
| Minimum SQL Server Configuration Parameters |
| Minimum Server Memory If monitoring more than 10 instances,
increase by 20 MB per additional monitored instance |
1 GB |
Client Browser
- Google Chrome 8.0 and higher
- Internet Explorer 6.0 and higher
- Firefox 3 and higher
Monitored Databases
These requirements apply to monitored database instances, hosted
on either physical or virtual servers.
Oracle Monitored Databases:
- Ignite for Oracle supports monitoring of Oracle 8.1.7
and higher (8i, 9i, 10g,11g)
-
- SYS user privileges are required for initial setup
- The server holding the Ignite software must be able to connect
to the monitored Oracle server
SQL Server Monitored Databases:
- Ignite for SQL Server supports monitoring of SQL Server 2000
SP3 and higher ( 2000, 2005, 2008, 2012)
- SYSADMIN privileges are required to setup Ignite
- The server holding the Ignite software must be able to connect
to the monitored MSSQL server.
Sybase ASE Monitored Databases:
- Ignite for Sybase supports monitoring of ASE 12.5.0.3
and higher.
- SA_ROLE privileges are required to setup Ignite
- The server holding the Ignite software must be able to connect
to the monitored Sybase server.
DB2 Monitored Databases:
- Ignite for IBM DB2 UDB supports monitoring of DB2 UDB 8.1
FixPack 13 and higher (8.2.2,...)
- SYSADM privileges are required to setup Ignite
- The server holding the Ignite software must be able to connect
to the monitored DB2 server.
VMware Monitoring
These requirements apply to monitoring of the vCenter server for
use with IgniteVM.
VMware vCenter Servers:
Confio supports connections to ESX/ESXi and/or vCenter.
vCenter is not required, but highly recommended.
- VMware ESX/ESXi 4.0 and higher
- VMware vCenter 4.0 and higher
- Ignite VM installs on any Windows, Linux, or UNIX server with
Java JRE 1.5 or higher
- One time entry of a read-only VMware password will be required.
Password is not visible to IgniteVM users.
Follow Us