Hide Forgot
Description of problem: engine should alert the user that object might be missing since last backup in a DR use case. This is to let the admin know that more step are needed for a full state restoration like importing unregistered VMs and disks.
IOW, one or more components (engine-backup --mode=restore, engine-setup, the engine itself) should compare the time of restore with the time of backup (as seen in the backup file or in the db) and alert if the difference is "too large".
If it's the engine that should alert, looks more like a infra issue than an integration issue. Oved?
According to comment #1 it can be neither or both. To be honest, don't really see the purpose of this RFE. Anyone who knows what backup is knows that when restoring then you go back to what was there at the time of the backup.... If the purpose is indeed to do what Didi said, then I see no reason to do that on the engine side. The restore option can compare dates.
I agree with Oved on this, I'm for not a bug.
Also, if I remember correctly, an engine-setup run is required as part of the restore procedure. So if something is missing in (terms of configuration), the setup might probably able to fix it.
This is about objects missing and there is no need to compare timestamps since any revert to backup means that something can be lost like VM, disks and so on. This can be prompt in the restore as well.
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
Moving from 4.0 alpha to 4.0 beta since 4.0 alpha has been already released and bug is not ON_QA.
Verified with: ovirt-engine-4.1.0-0.0.master.20160620231314.git0453503.el7.centos.noarch ... ------------------------------------------------------------------------------ Please note: The engine database was backed up at 2016-07-01 10:08:21.000000000 +0200 . Objects that were added, removed or changed after this date, such as virtual machines, disks, etc., are missing in the engine, and will probably require recovery or recreation. ------------------------------------------------------------------------------ ...
oVirt 4.0.0 has been released, closing current release.