Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (Cyborg)
  • No Skin
Collapse
Brand Logo

CIRCLE WITH A DOT

  1. Home
  2. Uncategorized
  3. Looks like I'm gonna exclude most of our #FCOS VMs from daily Proxmox #Backup Server.

Looks like I'm gonna exclude most of our #FCOS VMs from daily Proxmox #Backup Server.

Scheduled Pinned Locked Moved Uncategorized
fcosbackup
2 Posts 1 Posters 0 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • adhisimon@mastodon.kodesumber.comA This user is from outside of this forum
    adhisimon@mastodon.kodesumber.comA This user is from outside of this forum
    adhisimon@mastodon.kodesumber.com
    wrote last edited by
    #1

    Looks like I'm gonna exclude most of our #FCOS VMs from daily Proxmox #Backup Server.

    Those FCOS VMs tasks are running containers. All we need is just backup quadlet files and /etc/default. For most of container's data, I think we can use application level replication. If it's not available, I rather backup those container's volumes.

    Why?

    Because full backup of vm disk images is too expensive. Not talking about storage price, but about extraneous load on infrastructures (cpu, storage i/o).

    adhisimon@mastodon.kodesumber.comA 1 Reply Last reply
    0
    • adhisimon@mastodon.kodesumber.comA adhisimon@mastodon.kodesumber.com

      Looks like I'm gonna exclude most of our #FCOS VMs from daily Proxmox #Backup Server.

      Those FCOS VMs tasks are running containers. All we need is just backup quadlet files and /etc/default. For most of container's data, I think we can use application level replication. If it's not available, I rather backup those container's volumes.

      Why?

      Because full backup of vm disk images is too expensive. Not talking about storage price, but about extraneous load on infrastructures (cpu, storage i/o).

      adhisimon@mastodon.kodesumber.comA This user is from outside of this forum
      adhisimon@mastodon.kodesumber.comA This user is from outside of this forum
      adhisimon@mastodon.kodesumber.com
      wrote last edited by
      #2

      I can not accept when those of our machines can not response fast enough when I need to command them in the midnight because they storage too busy running backup.

      1 Reply Last reply
      0
      Reply
      • Reply as topic
      Log in to reply
      • Oldest to Newest
      • Newest to Oldest
      • Most Votes


      • Login

      • Login or register to search.
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • World
      • Users
      • Groups