Move to S3 - still want to use tape

[mkretzer]

Hello,

currently we still use jet databases which mean we can just backup our Veeam 365 VM with "normal" Veeam and then move that to tape.

Since S3 is the future we want to migrate but still want to have this feature. Our idea was the following:
- Create a linux VM with Seaweedfs which is backed up together with the Veeam365 server
- When we need an old restore we have to stop the current server, instant recover both, before we can use Veeam365 explorers

Would that work? Since the backup time would be different for the server and the repo is there a possibility to rescan? Would it perhaps be useful to host the Veeam 365 Postgres database on the linux S3 system?

Markus

[DaStivi]

HI, i would even say, install another vb365 instance and attach the instant restore S3 repo and add it there and rescan/restore from this instance...

[mkretzer]

Good idea - is that a supported way?
What about adding the S3 as a second repo to the original Server - will that cause chaos? If yes this would be a nice feature request - "allow an older S3 repo to be attached to the original Veeam 365 Server for restore of older backups".

[DaStivi]

I don’t think it’s a good idea to add a repository with the same data to another server.

First of all, you would need to edit or delete a file inside the repository before you could (re-)add it.
From my experience migrating from Jet to S3, there is no differentiation between repositories and restore points. This means things could easily get mixed up.

The more interesting question is: What’s the actual goal of having the tape-out?

In theory, nothing in the repository itself should change. However, if individual S3 items are moved or deleted, I would expect Veeam Support to classify the repository as corrupted. I can’t imagine that restoring or recovering single S3 items would be possible just because you can't find out whats missing or corrupted at all...

So the only real use case left is disaster recovery. In that scenario, I assume you would also have the VB365 server included in the same backup or tape-out. Then you could simply start both servers together without additional hassle.

[mkretzer]

Its nearly always for individual items. Some mail is missing from 5 years back and so on. Why should this not work if the S3 restore point is fine?