Руководство по резервному копированию ПО «zVirt Max»

hosted-engine --set-maintenance --mode=global

hosted-engine --vm-status

!! Cluster is in GLOBAL MAINTENANCE mode !!:

systemctl stop ovirt-engine.service

engine-backup --scope=all --mode=backup --file=backup.bck --log=backuplog.log

systemctl start ovirt-engine.service

hosted-engine --set-maintenance --mode=none

hosted-engine --vm-status

hosted-engine --set-maintenance --mode=global
hosted-engine --vm-shutdown

hosted-engine --vm-status

...
!! Cluster is in GLOBAL MAINTENANCE mode !!:

Engine status     : {"vm": "down_unexpected", "health": "bad", "detail":
                    "Down", "reason": "bad vm status"}

dnf install -y ovirt-engine-appliance

tmux

hosted-engine --deploy --restore-from-file=backup.bck

[ INFO  ] Stage: Environment setup
        During customization use CTRL-D to abort.
        Continuing will configure this host for serving as hypervisor and will create a local VM with a running engine.
        The provided engine backup file will be restored there,
        it's strongly recommended to run this tool on an host that wasn't part of the environment going to be restored.
        If a reference to this host is already contained in the backup file, it will be filtered out at restore time.
        The locally running engine will be used to configure a new storage domain and create a VM there.
        At the end the disk of the local VM will be moved to the shared storage.
        The old hosted-engine storage domain will be renamed, after checking that everything is correctly working you can manually remove it.
        Other hosted-engine hosts have to be reinstalled from the engine to update their hosted-engine configuration.
Are you sure you want to continue? (Yes, No)[No]:  - выбрать Yes;

[ INFO  ] skipping: [localhost]
        Renew engine CA on restore if needed?
        Please notice that if you choose Yes, all hosts will have to be later manually reinstalled from the engine.
  Renew CA if needed? (Yes, No)[No]:  - выбрать Yes;

[ INFO  ] skipping: [localhost]
        Pause the execution after adding this host to the engine?
        You will be able to connect to the restored engine in order to manually review and remediate its configuration.
        This is normally not required when restoring an up to date and coherent backup.
        Pause after adding the host? (Yes, No)[No]:  на данном этапе необходимо выбрать ответ исходя из конфигурации среды виртуализации.
        Если на хосте необходимо произвести дополнительные настройки (например, добавить неосновные сети VLAN) выберите - Yes, если в этом нет необходимости выберите - No.

FATAL: Provisioning database 'engine' failed, please check the log for details
         You can now connect from this host to the bootstrap engine VM using ssh as root and the temporary IP address - 192.168.222.91 - and fix this issue. Please continue only after the backup is restored.
         To retry the command that failed, you can run, on the bootstrap engine VM:
         engine-backup --mode=restore --file=/root/engine_backup --provision-all-databases --restore-permissions

engine-backup --mode=restore --file=/root/engine_backup --provision-all-databases --restore-permissions

Please specify the storage you would like to use (iscsi, fc, nfs)[nfs]:

hosted-engine --set-maintenance --mode=global
hosted-engine --vm-shutdown

hosted-engine --vm-status

!! Cluster is in GLOBAL MAINTENANCE mode !!:

Engine status     : {"vm": "down_unexpected", "health": "bad", "detail":
                    "Down", "reason": "bad vm status"}

dnf install -y ovirt-engine-appliance

tmux

hosted-engine --deploy --restore-from-file=backup.bck

[ INFO  ] Stage: Environment setup
        During customization use CTRL-D to abort.
        Continuing will configure this host for serving as hypervisor and will create a local VM with a running engine.
        The provided engine backup file will be restored there,
        it's strongly recommended to run this tool on an host that wasn't part of the environment going to be restored.
        If a reference to this host is already contained in the backup file, it will be filtered out at restore time.
        The locally running engine will be used to configure a new storage domain and create a VM there.
        At the end the disk of the local VM will be moved to the shared storage.
        The old hosted-engine storage domain will be renamed, after checking that everything is correctly working you can manually remove it.
        Other hosted-engine hosts have to be reinstalled from the engine to update their hosted-engine configuration.
Are you sure you want to continue? (Yes, No)[No]:  - выбрать Yes;

[ INFO  ] skipping: [localhost]
        Renew engine CA on restore if needed?
        Please notice that if you choose Yes, all hosts will have to be later manually reinstalled from the engine.
  Renew CA if needed? (Yes, No)[No]:  - выбрать Yes;


[ INFO  ] skipping: [localhost]
        Pause the execution after adding this host to the engine?
        You will be able to connect to the restored engine in order to manually review and remediate its configuration.
        This is normally not required when restoring an up to date and coherent backup.
        Pause after adding the host? (Yes, No)[No]:  на данном этапе необходимо выбрать ответ исходя из конфигурации среды виртуализации.
        Если на хосте необходимо произвести дополнительные настройки (например, добавить неосновные сети VLAN) выберите - Yes, если в этом нет необходимости выберите - No.

FATAL: Provisioning database 'engine' failed, please check the log for details
         You can now connect from this host to the bootstrap engine VM using ssh as root and the temporary IP address - 192.168.222.91 - and fix this issue. Please continue only after the backup is restored.
         To retry the command that failed, you can run, on the bootstrap engine VM:
         engine-backup --mode=restore --file=/root/engine_backup --provision-all-databases --restore-permissions

engine-backup --mode=restore --file=/root/engine_backup --provision-all-databases --restore-permissions

Please specify the storage you would like to use (iscsi, fc, nfs)[nfs]:

hosted-engine --set-maintenance --mode=global

hosted-engine --vm-status

!! Cluster is in GLOBAL MAINTENANCE mode !!:

systemctl stop ovirt-engine.service

cd /etc/alternatives/
ln -s /usr/jatoba-4/bin/vacuumlo jatoba-vacuumlo
cd /usr/bin/
ln -s /etc/alternatives/jatoba-vacuumlo vacuumlo

[root@manager-drp ~]# engine-cleanup
[ INFO  ] Stage: Initializing
[ INFO  ] Stage: Environment setup
        Configuration files: /etc/ovirt-engine-setup.conf.d/10-packaging-jboss.conf, /etc/ovirt-engine-setup.conf.d/10-packaging.conf, /etc/ovirt-engine-setup.conf.d/20-setup-ovirt-post.conf
        Log file: /var/log/ovirt-engine/setup/ovirt-engine-remove-20221222123552-w6qn8l.log
        Version: otopi-1.9.6 (otopi-1.9.6-1.el8)
[ INFO  ] Stage: Environment packages setup
[ INFO  ] Stage: Programs detection
[ INFO  ] Stage: Environment customization
[ INFO  ] Stage: Setup validation
        During execution engine service will be stopped (OK, Cancel) [OK]: OK

[ INFO  ] Hosted Engine HA is in Global Maintenance mode.
        All the installed ovirt components are about to be removed, data will be lost (OK, Cancel) [Cancel]: OK

[ INFO  ] Stage: Clean up
        Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-remove-20221222123552-w6qn8l.log
[ INFO  ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20221222123722-cleanup.conf'
[ INFO  ] Stage: Pre-termination
[ INFO  ] Stage: Termination
[ INFO  ] Execution of cleanup completed successfully

engine-backup --mode=restore --file=/root/filename.bck --restore-permissions

sudo /usr/share/ovirt-engine/dbscripts/engine-psql.sh -c "select fn_db_delete_config_value('AdminPassword','general');"

Please note:
The engine database was backed up at 2024-XX-XX XX:XX:XX.
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.
- DWH database ovirt_engine_history
- Grafana database /var/lib/grafana/grafana.db
You should now run engine-setup.
Done

Setup can automatically configure the firewall on this system.
Note: automatic configuration of the firewall may overwrite current settings.
Do you want Setup to configure the firewall? (Yes, No) [Yes]: Yes

    If you choose to not back up the database, and Setup later fails for some reason, it will not be able to restore the database and all DWH data will be lost.
    Would you like to backup the existing database before upgrading it? (Yes, No) [Yes]: No
[WARNING] Are you sure you do not want to backup the DWH database?
    A positive reply makes sense only if you do not need the data in DWH, or have some other, external means to restore it to a working state.
    Are you sure you do not want to backup the DWH database?(Yes, No) [No]: No

This operation may take a while depending on this setup health and the
configuration of the db vacuum process.
(Yes, No) [No]: No
--== OVIRT ENGINE CONFIGURATION ==--
Perform full vacuum on the engine database engine@localhost?
This operation may take a while depending on this setup health and the
configuration of the db vacuum process.
(Yes, No) [No]: No

systemctl start ovirt-engine.service