Formal workaround for standalone 'server' Backup Vault name collisions.
I want to backup files from lots of standalone (non-domain) Windows 2008+ servers and Windows 7 workstations distributed across many independent sites to a single subscription within our EA Azure, however there are too many identically named computers names to put one in each of the maximum 25 Backup Vaults in a single subscription. Spreading them across multiple subscriptions will make the overall management in Azure too difficult. It is not logistically or culturally feasible to fix this problem by neatly renaming the computers to have new unique names.
I see two potential solutions:
1) Getting these computers to talk to a WSUS server also caused name collision problems, however that was solved by configuring a unique primary DNS suffix on each computer. The WUA client appends the primary DNS suffix to the computer name to produce the lengthier dotted 'FQDN' it then uses when reporting to the WSUS server. The MARS agent doesn't appear to do this now, but it could do the same trick.
2) I have discovered a MARS agent test registry setting that can override the FQDN used with Azure in this scenario e.g. from 'mycomp.' to 'mycomp.some.unique.domain'. This happily solves my problem, however the setting it is clearly for MS testing purposes. This test registry setting could be changed to a formal, supported method and I much prefer this approach because it and avoids potential conflicts with normal use of the primary DNS suffix.
Please do not remove the test FQDN registry setting functionality from MARS agent without providing some alternative for my scenario.
We are expereicing the same problem with Azure workstation backups, what is this registry setting that you have found as I would like to use it also?
I prefer CloudBacko software for backing up my data. Best software for file duplication & incremental backup, because CloudBacko software gives us Zero loss of data because duplication of the data takes place in Cloudbacko at multiple destination. So due to which data remains protected and secured because healthy encryption is done, which is impossible to break. Try at least one time CloudBacko software.