A weekly OACI backup has been scheduled but it has not been created for a long period of time.
No free space on backup nodes or a OACI DB misconfiguration.
Backups on OACI IM are run according to settings in
<!-- backup job details --> <backups batchSize="10" intervalInMin="1" maxDurationInMin="200"/>
by default OACI runs backups in 10 VEs batches. It means that free space on Backup node is checked using the sum of 10 VEs that should be backed up.
In this case, try to 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; sum ----- 1625
In this example, ~1.65 T of free space is required for performing 10 biggest VEs backup batch. Please verify that Backup nodes have enough space.
As a workaround, change batchSize to "5", for example. In this case the backup task will run smaller batches that will require less space. Please note that any changes in
IM-config.xml require PACI-IM service restart.
service PACI-im restart
Another kind of cause is a misconfiguration in OACI DB:
backups_to_removetable - there should not be many backups. If there are, it is an indication of some problems with backups removal. In this case, OACI IM logs should be checked.
active_backupstable for long running backups (more than 1-2 days). Those are the indication of terracotta or dispatcher failures.