Question

Large repository inside Veeam VM


Userlevel 2
  • Comes here often
  • 9 comments

Hi all,

 

I have a followup question to

 

As I described before I’m “forced” (at least for the moment) to put the storage also on the Veeam server itself. Overall there might be the possibibility that there will by ~20-30TB on vib/vkb files.  Can this still be realized within the Veeam VM?

What are the alternatives if all data have to be on one physical server?

 

BR

Frank


3 comments

Userlevel 7
Badge +3

Hello @omfk,

as said in this KB2654

“If the server hosting the Veeam Backup & Replication configuration database is placed in a Backup or Replication job, that job will only run when no other tasks are running. Additionally, that job running will prevent all other tasks from starting until it completes.”

this can be a complication.

Best

Marco

Userlevel 7
Badge +6

If you are able to put the data on a VM as a VMDK file then when you are able split up the server to separate entities then you can move the VMDK file with the repo data to another server.

If you are using a physical box it would be slightly harder to move the data but possible using a SOBR where you add the physical server repo and then a new repo from a VM or other physical box.  Then you can use the maintenance mode and Evacuate backups to move them to the new repo.

Just some thoughts on this and if something else pops in my head I will reply here.  As Marco noted the backup of the Veeam server will run last due to it holding the configuration databases (SQL).

Userlevel 2

Hi all,

 

I have a followup question to

 

As I described before I’m “forced” (at least for the moment) to put the storage also on the Veeam server itself. Overall there might be the possibibility that there will by ~20-30TB on vib/vkb files.  Can this still be realized within the Veeam VM?

What are the alternatives if all data have to be on one physical server?

 

BR

Frank

 

I’ve got an additional question, as I realized that my description wasn’t clear enough probably.

 

Solution 1:

Hyper-V host with large VMDK file which hosts the Veeam VM (both the logic and the backup files)

 

Solution 2:

Hyper-V host with normal VMDK file which hosts the Veeam VM (only logic) and additional another share directly on the RAID on the host (Veeam VM needs then access to this share)

 

Any comments on these two options?

 

BR

Frank

Should the Hyper-V hosts

 

 

Comment