[Feature Request] Exchange multi-site DAG vs backup repos

[mrtomasz]

Hello,

Scenario:
Exchange DAG which spans over multiple sites connected with slower VPN links, let's say we have 3 sites and each site consists of a 2 nodes. Each site has its own backup repo for local backups.

Code: Select all

[site 1] = { [ex11, ex12], [repo1] }
[site 2] = { [ex21, ex22], [repo2] }
[site 3] = { [ex31, ex32], [repo3] }

Problem:
Exchange DAG backup job must contain all DAG nodes and single target backup repository, causing slow backups of DAG nodes located in other sites than backup repo is located.

Code: Select all

[BackupJob_EX_DAG] = {
    [ex11, ex12] ==[LAN]==> [repo1]
    [ex21, ex22] ==[VPN]==> [repo1]
    [ex31, ex32] ==[VPN]==> [repo1]
}

Solution proposal:
Add a way to specify multiple repositories per server/node, so we could select specific nodes and associate them with certain repos, thus having super fast local backups and not blocking whole backup pipeline.

Code: Select all

[BackupJob_EX_DAG] = {
    [ex11, ex12] ==[LAN]==> [repo1]
    [ex21, ex22] ==[LAN]==> [repo2]
    [ex31, ex32] ==[LAN]==> [repo3]
}

I am pretty sure I am not alone with this issue.

This solution probably could also fit other similar scenarios where single job for multiple elements is used.

[Mildur]

Hi Tomasz,

Thanks for the request. Noted.

Best,
Fabian