Hallo Thomas,
Wie versucht ihr die Backups zu verschieben? Nutzt ihr die “Move Backup” Option?
VG
Chalid
Moin @thomas_s,
wie genau versuchst du, den Move zu machen? Üblicherweise gehst du mit einem Rechtsklick auf die Backups (natürlich alles in Veeam, auf gar keinen Fall über den Windows-Explorer), dann auf “Move Backup”. Veeam sollte den Rest automatisch machen.
Backup Move - User Guide for VMware vSphere
(der Punkt “Move to another Repository)
Viele Grüße
Lukas
Hallo, ich ändere das Ziel im Backupjob direkt und dann wird “Move Backup” getriggert. Anschließend wird im Normalfall immer noch die DB angepasst und der Move-job beendet.
Versuch mal, das über das Repo bzw. den Reiter “Backups” manuell zu starten und den Job vorher zu deaktivieren.
Wenn das nicht funktioniert empfehle ich in jedem Fall, ein Veeam Support Ticket zu öffnen.
I just got exactly the same error moving backups where the move took more than 48 hours. The job reports that all backups (these are endpoint backups for manufacturing machines, so there are about 50 of them) were moved successfully. However, it then reports status of “User action required” then says
“Failed Updating configuration database records Error: Failed to import new backups“ My only option is “UNDO” - but I don’t want to undo, as the move was successful, and all my backup history is now on the new storage unit. Unfortunately, the job is permanently in ‘running’ condition, and STOP isn’t an option. As a result, no more backups are being made with this job.
Unfortunately, it seems that all Veeam problem report threads end up in “there is nothing you can do as a user. Submit a ticket.” This is most annoying. Opening a ticket now...
I just got exactly the same error moving backups where the move took more than 48 hours. The job reports that all backups (these are endpoint backups for manufacturing machines, so there are about 50 of them) were moved successfully. However, it then reports status of “User action required” then says
“Failed Updating configuration database records Error: Failed to import new backups“ My only option is “UNDO” - but I don’t want to undo, as the move was successful, and all my backup history is now on the new storage unit. Unfortunately, the job is permanently in ‘running’ condition, and STOP isn’t an option. As a result, no more backups are being made with this job.
Unfortunately, it seems that all Veeam problem report threads end up in “there is nothing you can do as a user. Submit a ticket.” This is most annoying. Opening a ticket now...
I recommend to open a Veeam support case to investigate this. Maybe there is a but that has to be troubleshooted.
Please feel free to keep us posted.
i had same issue “User action required” - have fixed that that i add to all backup files to full permission like chmod 777 and then re-try, and then finished successfully
another view - yes, job is automatically disabled during “move” and after enabled
would recommend to disable copy job as well during this action.
Entschulding von english …
ich hatte das selbe Problem “User action required” - ich habe das geloest, indem ich allen Sicherungsdateien volle Berechtigung wie chmod 777 hinzugefügt habe und es dann erneut versucht habe, und dann erfolgreich abgeschlossen habe
eine andere Ansicht - ja, der Auftrag wird automatisch während des „move“ deaktiviert und danach aktiviert
Ich würde empfehlen, den Kopierauftrag während dieser Aktion ebenfalls zu deaktivieren.
i had same issue “User action required” - have fixed that that i add to all backup files to full permission like chmod 777 and then re-try, and then finished successfully
another view - yes, job is automatically disabled during “move” and after enabled
would recommend to disable copy job as well during this action.
This works.
Auf Deutsch: genau so, und dann funktionierts.
