Community Edition - Move backups to new repository

[costasppc]

Hello,

In the Community Edition (12.1.2.172), we need to move backups (copy jobs) from one SMB repo to another SMB repo. Is the move option unavailable in the community edition? If so, how can we move the backups to the new repo, is changing the job target to the new repo enough?

Best regards

K

[david.domask]

Hi Kostas,

Correct, the Community Edition does not include the Move Backup functionality. You can use the solutions from this KB article to move the backups to the new repository, and then you will be able to map the backups as prescribed in the KB article.

Thanks!

[costasppc]

Thank you very much,

I will do the copy and get back for any issues (if any).

Best regards

K

[costasppc]

Hi again,

So, I have followed the KB, copied the whole folder, added the new repo and rescanned it. I had no errors. I mapped the copy job in question to the new repo, and started the job. I have now a full backup (which is mentioned in the KB), but I have only 1 restore point.
Since the old backup had 5 restore points, shouldn't i have the 5 restore points of the previous chain?

I have now the job (pointing to the new repo) with 1 restore point, a Disk Imported Job (pointing to the new repo, with my old 5 restore points) and a Disk (Orphaned), (pointing to the old repo, with the 5 restore points).

Is it the expected behavior?

Best regards

K

[david.domask]

Hi Kostas,

No, that doesn't sound correct and sounds like at some point the mapping was incorrect. I would advise try the re-mapping step once again, and ensure that the backups chosen are the one from the Imported section.

Ensure that you see it with a repository, and in the mapping step you should see it under the repository like so:



If you aren't seeing it there, try the re-import process again. You can do this on this tab of the Repository Wizard (step 2) and it should find and import the backups as long as the .VBM files are present.

If you have continued challenges, it will be best to open a Support Case, but please note that Free/Community edition cases are handled on a 'best-effort' basis.

[costasppc]

Thank you,

Noticed that: I created the new repository (in where I have copied the folder of one of the Backup Copy jobs), by pointing to the root folder (ex. \\192.xxx.xxx.xxx\backups). In there there are folders for each job. I have checked import existing backups. However, the job created another folder (with _1), and inside this folder it created the new full backup.
Do I need to point the new repo wizard to the folder of the job (meaning that we need to change different jobs to the new repo)?

P.S. its an SMB folder inside a NAS device.

EDIT: During new import, it mentions Backups skipped: 2

Best regards

K

[david.domask]

Hi Kostas,

Regrettably, it sounds like there is a technical issue and we will not be able to troubleshoot over the forums. The skipped part may be relevant, but this will require review of the logs, so it will be best to open a Support Case, but please note that Free/Community edition cases are handled on a 'best-effort' basis.