I think it is way better to get baby Data Domain (DD160) and replicate it to DC.  But, if tapes are your cup of tea, I suspect connection between branch office and DC is not fastest one so this will be challenge.  Not sure if you have storage node in BO which is served by server in DC, but with BO I would either use dedicated backup server onsite or disk backup with replication to DC.

If you are having a tape library unit at BO, and want to continue with tape only solution then, i think it would be best to configure the hyper-V server as storage/dedicated storage node managed by one of the backup servers in DC. This will give you ease of management and data recovery across sites, as you will have only two datazones to configure and manage.

Alternatively you can also promote the BO server as a backup server and configure it to manage its own backups.

Dear Singhmridul

Thank you for your quick reply,

The BO server is a Hyper-V host, thus it cannot use as a Backup
server and NMM client.

Another element that I have to care is the communication line
between DC and BO, if the line is down, my BO backups will not initiate or
failed if they already started when the Backup Server is on the DC.

I would like to know if the Backup Server Can be a VM?

if so can it be something like a active server on the BO and Passive server on the DC?