Install new Vesion Repository Backup directories distributed

[Peano]

Hello everyone,

we installed the new version 7 and wanted to start the BackupJob, then we found that we cannot use the license in the new version.

Now we have found:

1. the repository data is distributed across multiple directories
2. we can no longer access the backups before March 20, 2023
3. the data before March 20, 2023 is in the “Backup_$Year$_$GUID$” directories.
4. There are 2 directories for each year.

Can we merge the data again?

Best regards
Peano

[Mildur]

Hello Peano

we installed the new version 7 and wanted to start the BackupJob, then we found that we cannot use the license in the new version.

Did you have downloaded a new license from the license portal? Those licenses must work with our product versions.

1. the repository data is distributed across multiple directories
2. we can no longer access the backups before March 20, 2023
3. the data before March 20, 2023 is in the “Backup_$Year$_$GUID$” directories.
4. There are 2 directories for each year.

Can we merge the data again?

Sounds like a technical issue, which requires a case number. Please open a case and let our support team check your installation and investigate the log files. Guessing a solution over the forum may make the issue more worse. Please don't forget to share the case number.

Best,
Fabian

[Polina]

@Peano

When you do backups to local block-based storage, data is stored in databases, each in a separate folder named by year when the data was last modified.

Your backup job should be pointed to a repository that has all these folders inside (there's no need to merge any data); and to browse existing backups, you can simply open a Veeam Explorer from the organization level (right-click the org).

Thanks,
P.

[Peano]

Hello everyone,

Unfortunately we no longer have a support license, so we can't get help from Veeam Support.

We didn't download a new license, we tried with the old license, which wasn't accepted by the new version.

The backup structure is defective, that's for sure

for each year there are 3 backup directories:

2020
Backup__2020_b1ae6768-3047-4061-84a0-ebd12bb4bac4
Backup__2020_ba1b7d4a-81ac-4f4d-a834-869f30232bb0

only the 2020 directory is in the database

Best regards
Peano

[Polina]

Hi Peano,

Unfortunately, this forum is not an alternative way to get support (kindly check out the rules) and troubleshooting technical issues requires logs inspection.

If you're using the product in a Community Edition mode, you can open a support case and get assistance on a best-effort basis.

Thanks!

[Peano]

Our guess is that the engineer didn't continue the existing repository as it should be in the image, he clicked the "No" button.

Is there a way to merge the backups back?

[Mildur]

Unfortunately not.
We would have a move PowerShell command. But it requires the target repository to not have any data associated with the items you want to move.
Example: Don't move a backup of a mailbox when the target repository already has data of this mailbox. In such case the move command cannot be used.

Best,
Fabian

[Peano]

Many thanks for your help