On Feb 10, 2017 3:21 PM, "Nathanaël Blanchet" <blanchet@abes.fr> wrote:

Le 09/02/2017 à 19:48, Yaniv Kaul a écrit :

On Thu, Feb 9, 2017 at 6:00 PM, Doug Ingham <dougti@gmail.com> wrote:

On 9 February 2017 at 12:03, Dan Yasny <dyasny@gmail.com> wrote:

On Thu, Feb 9, 2017 at 9:55 AM, Doug Ingham <dougti@gmail.com> wrote:

Hi Dan,

On 8 February 2017 at 18:26, Dan Yasny <dyasny@gmail.com> wrote:

But seriously, above all, I'd recommend you backup the engine (it comes with a utility) often and well. I do it via cron every hour in production, keeping a rotation of hourly and daily backups, just in case. It doesn't take much space or resources, but it's more than just best practice - that database is the summary of the entire setup.

If you don't mind, may I ask what process you use for backing up your engine? If you use HE, do you keep one server dedicated to just that VM?

I've not had that particular issue in the restore process yet, however I read that it's recommended the HE host is free of virtual load before the backup takes place. And as they need to be done frequently, I'm reading that as a dedicated host...

If you use a dedicated host, you might as well abandon self hosted. HE is nice for small setups with the HA built in for extra fun, but once you scale, it might not be able to cope and you'll need real hardware. You're running a heavy-ish java engine plus two databases after all.

I'd be interested to know what type of scale needs a real hardware for engine, rather 100 vms or 1000 vms? it may be about the hosts number?

It depends on many factors. Just saw someone who is running the engine as a VM on a hefty hardware, and his setup had 50 hosts and 2500 VMs. I don't know all the details and specifically what I'd be interested to know is the underlying storage performance and how it's connected.

In any case, as you scale up the system you will need more vCPUs and memory.

Lastly, in 4.1 we've made various improvements to the engine and its database usage, so I expect somewhat improved performance and scale.

So as I said, all I do is add the engine-backup command to cron on the engine, and then my backup server comes in and pulls out the files via scp, also through cron. Nothing fancy really, but it lets me sleep at night

This particular project has 10 new maxed out servers to back it, and I don't see it outgrowing that for at least a year or so. It's hardly a full DC.
I presume the DB will become the heaviest part of the load, and I'm already planning a separate high I/O environment for dedicated HA DB hosts.

See the top section of this page:

http://www.ovirt.org/documentation/self-hosted/chap-Backing_up_and_Restoring_an_EL-Based_Self-Hosted_Environment

It seems that I'll always have to keep at least one host free to be able to avoid restore problems. If not, and I were to keep hourly backups, then migrating VMs off the host every hour would just be a pain.

I don't see the point in an hourly backup. Of what? The DB? The VM? What storage will it be based on?

I suggest revising the strategy.

--

Doug

_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
-- Nathanaël Blanchet Supervision réseau Pôle Infrastrutures Informatiques 227 avenue Professeur-Jean-Louis-Viala 34193 MONTPELLIER CEDEX 5 Tél. 33 (0)4 67 54 84 55 Fax 33 (0)4 67 54 84 14 blanchet@abes.fr
_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users