When I do this, I am lucky enough to have a physical spare server, so I run everything on the backup server as a mirror of the master.
I then rebuild and update the jails on master, if there was ever a problem, I could just switch local dns records to the slave. All of my last 4 jail rebuilds have been done on my master without any effect to users or services, then I just schedule a reboot for a time the server isn't in use. To date I have had no problem at all, and the whole process of rebuilding base jail image and all packages from source is easy (just time consuming). Some of these jails server Web applications and databases handling some quite heavy traffic. Just seems to work on FreeBSD flawlessly. On 11 Nov 2017 20:43, "Michael Grimm" <[email protected]> wrote: > Hi -- > > [FYI: I am running some service jails with an ezjail-type basejail > approach.] > > Until now I did stop all jails before updating and restarting them > afterwards. Now I am wondering if that is necessary at all. > > Wouldn't it be sufficient to update basejail with running jails and > restart them after this updating? (In analogy to a "make installworld; make > installkernel; reboot") > > Background of my question: Until now I do have two identical servers > running in parallel (simple failover approach), but I am thinking about > migrating both servers to a single cloud instance, and keeping downtimes of > my service jails whilst updating the OS to a bare minimum. > > Thanks for your input in advance, > Michael > > _______________________________________________ > [email protected] mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-jail > To unsubscribe, send any mail to "[email protected]" > _______________________________________________ [email protected] mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-jail To unsubscribe, send any mail to "[email protected]"
