Object storage fallback scenario

[DHuppertz]

Hello together,

we're locking for a fallback scenario for our on premise object storage.
In case object storage layer is no longer working, we're still able to access M365 backup files over SMB-share.

Is there any tool to copy/move these files to a new object storage without using object storage integration for source data and to recover restore points?
While simply copying these files to a new object storage and redirecting backup to this one not allows to recover older backups.

Thank you

[Mildur]

Hi Dieter

I don't understand the part with SMB-Share. Do you have a second backup job which points to an SMB-Share?
Jet db based repository files cannot just be copied to object storage. The backup format on object storage is different. We have a command to migrate backup data from jet db based repositories to object storage. But I don't recommend it if you have a large amount of backup data.

If you want to have a second copy of data from your object storage repository, I suggest to use a backup copy job to a second object storage appliance or cloud service. This copy can be made immutable.

Best,
Fabian

[DHuppertz]

Hi Fabian,

thank you for your quick reply!
I will try to explain a bit in depth what we're looking for.

First of all, this will be a worst case fallback scenario!
We had a local QNAP-storage with QuObjects-App servicing S3-compatible object storage.
If QNAP fails or QuObjects-App is no longer available and we're still able to access backup files by mapping the share on which the backup files are stored,
do we have the possibility to copy/migrate these files on another storage device and having all restore points available (a function like "Importing Backup..." on VBR)?

Kindly and have a nice WE
Dieter

[Mildur]

Hi Dieter

So you can see those objects from QuObjects via SMB?
You may try to copy the content of the entire "QuObjects folder" with the original structure to a new bucket on another object storage appliance. Then connect that new bucket to VB365. If the M365 organization is still configured, you can do a restore of the data.
VB365 must see the exact same structure. And it has to be object storage. If not, the restore won't work. You can read more about the structure on object storage here: https://helpcenter.veeam.com/docs/vbo36 ... tml?ver=70

I cannot guarantee that this will work. It's also not supported because we never have tested it.
Please run tests on it before you use it as a DR plan.
And I still strongly recommend to use our backup copy jobs. This is the only supported way to still be able to restore in case QuObjects stops working somehow.

Best,
Fabian

[DHuppertz]

Hi Fabian,

everything went fine until it came to synchronisation of the new added repo. It failed with the following error:
"Padding is invalid and cannot be removed."
Any idea?

Thank you and kr
Dieter

[DHuppertz]

Hi Fabian,

because I ddin't get any reply, do you still have an idea or can I forget this method?

Kind regards
Dieter

[Mildur]

Hi Dieter

I apologize. Didn't saw your last answer.

Padding is invalid and cannot be removed.

A short research shows me, that this message may have something todo with encryption.
Did you have encryption enabled for this object storage repository?

Best,
Fabian

[DHuppertz]

Hi Fabian,

yes we have encryption enabled for this object storage...
For security reasons this is our standard strategy regarding backup repos.

This means it would not be possible?
If so, my next question: what happened if we had a "copy job" to an ObjectStorage on another QNAP and the primary QNAP fails/breaks: are these copies still available for restore?
Can these "copy jobs" be transformed as standard backup jobs, by using this ObjectStorage as the primary backup repo afterwards?

Really appreciate your reply...

Kind regards
Dieter

[Mildur]

I cannot say if it's possible. As stated before, our statement is "it is not supported".
That error must be troubleshooted by our support team. But because it's an unsupported scenario, you most likely won't get help to fix it.

If so, my next question: what happened if we had a "copy job" to an ObjectStorage on another QNAP and the primary QNAP fails/breaks: are these copies still available for restore?

Yes, you can restore from the copied restore points. Please note, if you configure a backup copy now, initial copy will only copy the newest restore point and not all previous restore points.

Can these "copy jobs" be transformed as standard backup jobs, by using this ObjectStorage as the primary backup repo afterwards?

No. This is not possible. The format of a backup copy job is not compatible to a backup job.

Best,
Fabian

[DHuppertz]

Hi Fabian,

thank you very much for clarifying these.
This will help us in our strategy of repo types to use.

Kr
Dieter

[Mildur]

Hi Dieter

You're welcome.

Best,
Fabian