[Users] Lost our management server.. have DB backup but no /etc/pki/

[Alexandru Vladulescu]

Hi,

Because I have foreseen this situation on my side for future upgrades 
and fail-over cases, I did a simpler .sh script with a crontab to run on 
a nightly basis.

I have attached the script here for you and others to use it and don't 
bump in the future in such problems with your sistem.

In a recovery case, you just need to stop ovirt-engine, jboss and insert 
the saved db dump, and overwrite /etc/pki/ovirt-engine directory with 
the certificates from the dump archive.

Of course the script could be developed even further to send email or 
SMS text notifications in case of a trouble but this was written in less 
then 10 minutes. Adapt it for you needs ! I use NFS share and paths.

Hope it helps !

Cheers,
Alex.

On 02/17/2013 04:17 AM, Saint Keimond wrote:
> Hello,
>   We lost our Fedora 17 server with ovirt 3.1 on it. We have a good 
> database backup but do not have have any certificates. From what I 
> read, it is possible to still do a restore.. we just have to rejoin 
> all the nodes so that they get a new certificate.
>
> I've tried to bring the database in to a fresh 3.1 install and a fresh 
> 3.2 install.. with no success on either. I need some helping figuring 
> this out :)
>
>
> Thanks,
>    David
> _______________________________________________
> Users mailing list
> Users at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users


-- 
Alexandru Vladulescu
Platform System Engineer
---------------------------------------------------------------------------------
Bright Future Project Romania
Web url : www.bfproject.ro
Skype :   avladulescu
Mobile :  +4(0)726.373.098
---------------------------------------------------------------------------------

-------------- next part --------------
A non-text attachment was scrubbed...
Name: engine-backup.sh
Type: application/x-shellscript
Size: 1573 bytes
Desc: not available
URL: <http://lists.ovirt.org/pipermail/users/attachments/20130218/544276ca/attachment.bin>