XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Mirror backup: No new data to upload for this vm?

    Scheduled Pinned Locked Moved Backup
    12 Posts 4 Posters 236 Views 4 Watching
    Loading More Posts
    • 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.
    • ForzaF Offline
      Forza @olivierlambert
      last edited by

      I noticed too that both mirror backup and full backup do not actually copy all backups.

      This shows the source Remote on the left and destination remote on the right. I made sure the retention setting in the mirror backup is high enough to not exclude anything, yet we are not getting everything transferred:

      28e2782c-dd80-45f9-865f-c83d1152ce10-image.png

      Se also the same for full mirror backups: https://xcp-ng.org/forum/topic/11624/mirror-of-full-backups-with-low-retention-copies-all-vms-and-then-deletes-them/

      1 Reply Last reply Reply Quote 0
      • Bastien NolletB Offline
        Bastien Nollet Vates 🪐 XO Team @Forza
        last edited by

        Hi @Forza,

        Could you send us a screenshot of your backup job configuration so we can try to reproduce?

        ForzaF 1 Reply Last reply Reply Quote 0
        • ForzaF Offline
          Forza @Bastien Nollet
          last edited by

          @Bastien-Nollet

          Here is the incremental backup config. Originally we only had the remote called srv04-incremental. I have now added srv12-incremental and wanted to copy over all existing backups to the new remote. I did the same with full backups too. Now I have each backup job using both remotes.

          200dc1a4-d808-49b8-ac44-201b2226e215-image.png

          f46f5079-c10d-46e7-96dd-fd3a9fc76924-image.png

          Bastien NolletB 2 Replies Last reply Reply Quote 0
          • Bastien NolletB Offline
            Bastien Nollet Vates 🪐 XO Team @Forza
            last edited by

            Thanks @Forza,
            I'll try on my own with a similar configuration.

            1 Reply Last reply Reply Quote 0
            • Bastien NolletB Offline
              Bastien Nollet Vates 🪐 XO Team @Forza
              last edited by Bastien Nollet

              @Forza

              As the named are greyed-out, could you confirm that the delta backup job saves the backup to remotes srv04-incremental and srv12-incremental, and the mirror backup job copies the backups from srv12-incremental to srv04-incremental? (or at least confirm these are the same couple of remotes)

              Also, could you tell me if the VM with which you got the "No new data to upload for this VM" message was backed up by your backup job "Incremental backup every 4 hours - 8 days retention"?

              ForzaF 1 Reply Last reply Reply Quote 1
              • ForzaF Offline
                Forza @Bastien Nollet
                last edited by Forza

                @Bastien-Nollet

                The delta backup job saves to srv04-incremental and srv12-incremental.
                The incremental mirror job has srv04-incremental as source and srv12-incremental as destination.

                The VM that showed no data to copy message was a the "Incremental backup every 4 hours - 8 days retention" backup job.

                Originally I only had one remote, srv04. I created srv04-incremental and renamed srv04 to srv04-full and used the mirror backup feature to copy all delta backups to srv04-incremental (as I did not want to attempt to move the data on the NFS backend side). Then, I set up srv12-incremental and srv12-full and created mirror jobs to copy from srv04-full and srv04-incremental. Once the mirror backups were completed I switched the normal backup jobs to store backups on both backup servers.

                I can set up a support connection if you want to remotely check this.

                Bastien NolletB 2 Replies Last reply Reply Quote 0
                • Bastien NolletB Offline
                  Bastien Nollet Vates 🪐 XO Team @Forza
                  last edited by

                  @Forza

                  Thanks for the details, I managed to reproduce after a few trials.

                  I'll try to fix it and keep you informed.

                  1 Reply Last reply Reply Quote 2
                  • Bastien NolletB Offline
                    Bastien Nollet Vates 🪐 XO Team @Forza
                    last edited by

                    Hi @Forza,

                    I made a fix to prevent the "No new data to upload for this VM" message from appearing if it is only true for a part of the backup jobs of one VM.

                    It's available here: https://github.com/vatesfr/xen-orchestra/pull/9286

                    You can test it by switching branch if you're running XO from sources, otherwise you'll need to wait for the next end of month release.

                    b-Nollet opened this pull request in vatesfr/xen-orchestra

                    open fix(backups): fix incorrect info on mirror backups #9286

                    ForzaF 1 Reply Last reply Reply Quote 0
                    • ForzaF Offline
                      Forza @Bastien Nollet
                      last edited by

                      @Bastien-Nollet Thanks. I am on Stable channel as I use XOA Premium.

                      P 1 Reply Last reply Reply Quote 0
                      • P Offline
                        Pilow @Forza
                        last edited by

                        @Forza you will have to switch to LATEST to profit from end month release
                        STABLE is one version behind LATEST

                        both are production ready.

                        1 Reply Last reply Reply Quote 1
                        • First post
                          Last post