Skip to main content
  • EN

Hi all,

Anybody faced issues with the usage of certain TIERs from a SOBR on another VBR server ?

 

Here’s what we want to achieve:

Customer is upgrading to brand new VBR server (new hardware)

Together with this shift, he want’s to move from S3 provider.

All configured well, but what with the existing SOBR were we only want to keep the archive tier. Both Capacity and Archive tier are S3 compatible repo’s (encrypted). We just want to break up the SOBR and mount the S3 Archive tier to the new VBR and perfrom a rescan. All backup points should then be visible as ‘imported’ backups.

This gives the customer the opportunity to keep the possibility to restore from his previous archive tier when necessary and get rid of the costly capacity tier.

 

Any things we should keep in mind ? I guess a rescan of the repo will populate the internal DB with the necessary info to perform restores via the new VBR.

 

 

 

If you just want to keep the archive tier why not as just a standard repo and then use a new SOBR?

HI Chris, thanks for your response,

 

We just want to keep the data in the archive tier of the current sobr ‘available’.

Every action on this storage generated egress which will come at a cost.

The new long term GFS / SOBR is already in-place on the new VBR.

 

HI Chris, thanks for your response,

 

We just want to keep the data in the archive tier of the current sobr ‘available’.

Every action on this storage generated egress which will come at a cost.

The new long term GFS / SOBR is already in-place on the new VBR.

 

Ok. So if not adding it to the new VBR then leave it where it is.  Otherwise if you want it on the new server I would add it as a standard repository.

Indeed, that’s also our way of thinking.

We’ll add it as a standard repo and rescan the repo to ‘import’ the backups.

Then they’re at the fingertips of the operator to perform a restore if necessary.

 

 

Indeed, that’s also our way of thinking.

We’ll add it as a standard repo and rescan the repo to ‘import’ the backups.

Then they’re at the fingertips of the operator to perform a restore if necessary.

 

 

Sounds like the easiest way.  Best of luck.

Sounds like a good plan to me @kristofpoppe . I’ve never tried that personally, but can’t think of any “gotchas” off hand. And I agree with Chris to remove added complexity of having an Archive tier transferred to new server, and rather just add it as a standard Repo. Since you already have a GFS in place on the new, no reason based off your description, as to why to not have it just as a standard Repo.

Comment


Terms & Conditions