Re: [PLUG] Clone a Remote Server to Another Remote Server

[Rich Freeman via plug <plug@lists.phillylinux.org>]

On Wed, Aug 28, 2024 at 12:14 PM Keith C. Perry via plug
<plug@lists.phillylinux.org> wrote:
>
> dd is usually not the best thing to use on a live system and tar I'm can be hit or miss

++

Really doing anything like this live is hit and miss.  For an
application it depends on the application.  To do it with a whole OS
is definitely messy.

This sounds like some kind of VPS.  I've never actually used one so
I'm not sure how they're typically provisioned, but I'm guessing that
today they're just running as a big container.  Ideally you should try
to get a tarball of your entire environment and have it migrated as
such.  That can be done offline without the "server" running.
Hopefully your provider can facilitate this, either with some standard
interface, or via a support request.

If you do create anything new I would try to containerize it
completely and have something backed by configuration management, so
that you're not back in this same situation again.  I need to get
around to doing that with my own mail stack.

Just about any new service I create is running in k8s backed by flux.
Config files are all in configmaps in git, and then application state
is in a block device or cephfs directory tree per container.
Preserving state is just backups, and launching a new container
without state is just applying the configuration out of git.  Renovate
just sends me a pull request when something needs updating - often
this involves more than just hitting the merge button but having all
the state in git makes it WAY cleaner.

I really need to get multus working so that I can ditch nspawn entirely...

-- 
Rich
___________________________________________________________________________
Philadelphia Linux Users Group         --        http://www.phillylinux.org
Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce
General Discussion  --   http://lists.phillylinux.org/mailman/listinfo/plug