VBO Server Install

[neon_nico]

Support Case #04884768

Veeam Support Are Looking Into This As Well!

Hi, I've Had A Main VEEAM B&R V11.0 Server Crash And I May Have To Restore The Windows Server 2012 R2 (x64) Server From Scratch. It Currently Holds Our Multi Tenant VBO Server (V5.0.1.252) (Which Still Works)

What Is The Quickest Way To Transfer All Of The VBO Data To The New Newly Formatted Server i.e Power shell Scripts? Or Any Other Way Please , May Be Somebody Out There Has Had The Same Thing Happened To Them So They Could Point Me In The Right Direction?

Any Help Would Be Appreciated, Thanks (In Advance)

Nick.

[neon_nico]

Foget To Mention Using AWS S3 As Object Storage

Thanks.

[Mildur]

Have a look at this Kb.
It explains how to move vbo365 to a new server.

https://www.veeam.com/kb2649

Configuration cannot be exported. You will have to configure each organization again. The new backup jobs can reuse the old backup data and a full backup isn‘t required.

From the KB:

At the time of writing this article, there is no way to export the configuration of Veeam Backup for Microsoft Office 365. As such, on the new server, all organizations and jobs will have to be recreated. If the steps below are performed correctly, the first run on the new server will be "incremental."

[neon_nico]

Thanks Mildur!

Nick.

[Mildur]

Glad to help

[neon_nico]

Hi Mildur, Have You Tried This Procedure? is it a question of:-

1. Fresh Copy Of Windows Server 2012 R2 (x64)
2. New Install Of VBO V5.0.1.252
2. Copy Across Old Backup Repo's On New Server Disk
3 Reconfigure AWS, Repos And Backup Proxy
4. Away You Go ?

is Is That Simple As It Will Bring Across Customer Old Veeam Backups From The Old Server To The New?

Your Thought's Would Be Appreciated!

Many Thanks, Nick.

[Mike Resseler]

It is more or less indeed like that Nick.

You won't need to copy the data on a new server disk (you have the data on the object storage) but you will need to rerun the synchronization on the repositories so the cache metadata is being recreated

[Mildur]

I have never used the procedure by myself. I‘m sure, that Veeam has tested the steps in their lab, because they published this article.

1. Fresh Copy Of Windows Server 2012 R2 (x64)

Why not use Windows Server 2019 right away? Do you have legacy Backup repos (local disks) beside your AWS Backup Repo for VBO365 data?
If you have only AWS Backup Repos, you don‘t need the same OS for the migration.

Copy Across Old Backup Repo's On New Server Disk

Cache disks for the object Storage Repo doesn‘t need to be copied over to the new server. It is not mentioned in the KB article.

[neon_nico]

Hi Mildur,

I Have No Problems With WIn 2019 But All REPO Data At the Moment is Stored On Local Disks, The Main Aim Will Be To Get Everything Running In The Cloud On Either AWS Or AZURE (Not Decided Which Yet)
The Only Issue Is How Do I Miiror The Local Repo On The Server In AWS or AZURE Server Disks Or Do They Rebuild From The AWS S3 Data? After A Re-Sync, This is What I Have Never Tried? Any Help Would Be Great ?

Many Thanks
Nick.

[Mildur]

There is a KB for everything
https://www.veeam.com/kb3067

You will need a working vbo server for that. Moving the data will need powershell commands. Have a look at the kb article.

[neon_nico]

Hi Mildur,

Thanks A Lot For All Your Help!

Much Appreciated.

Nick.

[neon_nico]

Is There Any Problems (Performance etc.?) Having The VEEAM VBO Server And All Data Proxies\Repositories On The Same Drive : i.e. C:\

Any Idea's Would Help.

Many Thanks.

Nick.

[nielsengelen]

It highly depends on how many repositories u plan to use. I suggest you read up on our best practices as well as it may help in answering open questions.

[neon_nico]

Thanks Niels

Nick.