Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mirror backup job failed - nothing reported #7688

Open
cairoapcampos opened this issue May 24, 2024 · 4 comments
Open

Mirror backup job failed - nothing reported #7688

cairoapcampos opened this issue May 24, 2024 · 4 comments

Comments

@cairoapcampos
Copy link

Are you using XOA or XO from the sources?

XO from the sources

Which release channel?

stable

Provide your commit number

990c2

Describe the bug

When a "Mirror Incremental Backup" type backup is performed, the message below is displayed:

2024-05-24_14-10

Is this really a bug? Well, nothing happens.

Error message

["821539cc-381a-8dbe-7c5b-7121a168da5b","a97b9ad6-f607-6f63-d918-394d4d3412c2","fd232c67-c6da-d4ad-d815-25e8cbe87019"]

To reproduce

Using Xen Orchestra:

  1. A simple backup (full backup) was performed on an NFS 1 server.
  2. A "Mirror Incremental Backup" backup was performed on an NFS 2 server.
  3. In step 2 the message above was shown.

See the video:

2024-05-24.14-31-40.4.mov

Expected behavior

I expected that after the backup was performed a success message would be shown.

Screenshots

No response

Node

I don't know how to specify.

Hypervisor

8.2

Additional context

No response

@julien-f julien-f changed the title Backup job failed Mirror backup job failed - nothing reported May 31, 2024
@julien-f
Copy link
Member

The vms info is not an error but it indicates the list of VMs that are planned to be backed up during this run.

The issue is that there is no sub-tasks after that and that the backup run still shows as success.

Maybe the issue is that we should add a warning in a VM subtask if there is nothing to transfer.

@julien-f
Copy link
Member

Also there should likely be a warning if there is nothing to transfer for the whole backup run.

@julien-f
Copy link
Member

@cairoapcampos The issue on your side appears to be that you are configuring an Incremental Mirror Backup but your original backups are Full VM backups. Either both should be full or both should be incremental, do not mix them.

@cairoapcampos
Copy link
Author

@julien-f You are sure. I was making the wrong backups. Do you want to change the system to show a more user-friendly message? My doubt has been resolved. If you wish, you can close this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants