The job framework and event systems are optional which are intend for expert
administration who need to automate large complex operation in Oracle VM.

You can suppress events toward excessive notification messages to pages and to
emails.

The lock iconthat appears in your object icon in the VM manager indicate that the object
is the part of the job. This is a process you cannot perform action on locked object.

Every Oracle VM management action dispatched to an Oracle VM server agent is
performed as ajob.

Event provide accountability and an audit trail to identify which job performed by whom,
when they were performed and that the status of the operation.

Oracle VM 3.x has multiple identical storage repositories. Additional identical
repositories can be added as needed. A best practice is to select a medium size for the
repository based on your usage.

The way to grow an Oracle VM 3.x storage repository is to add additional space to the
rootrepository as needed. A best practice is to only configure additional space when
determined it is needed.

Oracle VM 3.x has a single fixed storage repository. A best practice is to configure the
repository with 30%-40% headroom forgrowth.

The way to grow an Oracle VM 3.x storage repository is to add sub-repositories beneath
the root repository. A best practice is to provision one or more larger repositories to avoid
the management overhead of numerous sub-repositories.

VM exist in a clusterserver pool with high availability feature turned on.

The VM to be migrated has the high availability flag enabled.

The target server should have enough free space to run the VM.

VM should be running or in pause state.

The source and target servers should be in same server pool.

Avoid installing additional software in dom0.

Enable firewalling in dom0.

Install virus checking software in dom0.

Use Trusted Computing Modules for Xen0.

Do not share physical network cards between hosts that are on a different subnet.

Option A

Option B

Option C

Option D

Option E

Each repository will create mount point under /OVS, with a directory named using the
UUID of the respiratory.

Each repository will create a mount point under /var/ovs, In a directory named using the
UUID ofthe repository.

Each repository will create a mount point under /var/ovs/mount, in a directory named
using theUUID of the repository.

Each repository willcreate a mount point under /OVS, with a directory named using a
sequencenumber starting at 0.

Each repository will create a mount point under /var/ovs, with a directory named using a
sequence number starting at 0.

The repository will be unmounted, and the virtual machines will remain on the
unmounted volume.

The repository will be unmounted, and all virtual machines on the unmounted volume
will be deleted.

The repository will be unmounted, andall virtual machines on the repository will be
migrated to other available repositories.

The repository will remain mounted, but all files in the volume will be deleted.

The repository will remain mounted, but it will no longer be available using therepos.py --
list command.

High Availability Mode

Server Pool Virtual IP

Live Migration

02CB service

OCFS service