virtualfranket

This may be an indicator of Vcloud DB performance issues and I would recommend performing some clean up of both Vcenter and Vcloud DB's. Befroe running any of these procedures please make a back up of your DB Vcenter DB Maintenance Run this on all Vcenter Instances 1. Stop the vCenter Server Service 2. Stop the vCloud Cell Services for all Cells (Service vmware-vcd stop) 3. Run the following against the vCenter DB: ALTER TABLE VPX_EVENT_ARG DROP CONSTRAINT FK_VPX_EVENT_ARG_REF_EVENT; ALTER TABLE VPX_EVENT_ARG DROP CONSTRAINT FK_VPX_EVENT_ARG_REF_ENTITY; ALTER TABLE VPX_ENTITY_LAST_EVENT DROP CONSTRAINT FK_VPX_LAST_EVENT_EVENT; truncate table VPX_TASK; truncate table VPX_ENTITY_LAST_EVENT; truncate table VPX_EVENT; truncate table VPX_EVENT_ARG; alter table VPX_EVENT_ARG add constraint FK_VPX_EVENT_ARG_REF_EVENT foreign key(EVENT_ID) references VPX_EVENT (EVENT_ID) on delete cascade; alter table VPX_EVENT_ARG add constraint FK_VPX_EVENT_ARG_REF_ENTITY foreign key (OBJ_TYPE) refe...

vSphere 5.0 uses a mirrored-mode approach for Storage vMotion. In this new architecture, Storage vMotion copies disk blocks between source and destination and replaces the need for the iterative pre-copy phase. This was used in the Changed Block Tracking (CBT) method in earlier versions of vSphere. With I/O mirroring, a single-pass copy of the disk blocks from the source to the destination is performed. I/O mirroring ensures that any newly changed blocks in the source are mirrored at the destination. There is also a block-level bitmap that identifies hot and cold blocks of the disk, or whether the data in a given block is already mirrored in the destination disk.