Search Engine: Elastic

Article ID: 120906, created on Apr 5, 2014, last review on Jun 2, 2018

  • Applies to:
  • Operations Automation 7.0
  • Operations Automation 7.1
  • Operations Automation 7.2
  • Operations Automation 7.3
  • Operations Automation 6.0
  • Operations Automation 5.5
  • Operations Automation 5.4


No scheduled backups are getting created, despite the backup schedule is configured.

There are no errors recorded into Cloud Infrastructure Log.


2 possible causes:

  • No free space on Virtuozzo backups node(s)
  • Stuck DB entries of previous backup operations that were not ended/removed


OACI backups are scheduled according to the settings in /usr/local/share/PACI-im/IM-config.xml:

<!-- backup job details -->
<backups batchSize="10" intervalInMin="1" maxDurationInMin="200"/>

By default, OACI runs backups in 10 VE batches. Available free space on the backup nodes is checked using the sum of 10 VEs that should be backed up.

Calculate maximum size of the 10 biggest VEs:

im=# with topdisks as (select size from ve_storage where ve_ref in (select id from ve where template_id in (select id from templates where ((os_type in (select type from os_types where family='linux') and technology='CT')) or technology='VM')) order by size desc limit 10) select sum(size) from topdisks;

In this example, ~1.65 T of free space is required for performing 10 biggest VEs backup batch. Verify that OACI backup nodes have enough space to accommodate the backups.

As a workaround, change batchSize to "5". In this case the backup task will run smaller batches that will require less space. Note that any changes in IM-config.xml require PACI-IM service restart.

service PACI-im fast-restart

In case it did not help, contact your Technical Account Manager or Pooled Technical Associates team ( in order to check issue and apply internal workaround.

ac82ce33439a9c1feec4ff4f2f638899 caea8340e2d186a540518d08602aa065 5356b422f65bdad1c3e9edca5d74a1ae 2554725ed606193dd9bbce21365bed4e 5b048d9bddf8048a00aba7e0bdadef37 e12cea1d47a3125d335d68e6d4e15e07 956c448bddc7e1f3585373687602379f 6f1456866eed87488c0f02b298a741c0 0871c0b47b3b86ae3b1af4c2942cd0ce 1941880841f714e458ae4dc3d9f3062d 8c199f0ee4305da1a577740620df4a51 dd79f16c76b9dca75205ab5e9f5465ea 31987597efff5a3a9ce779cc203bbe5e

Email subscription for changes to this article
Save as PDF