For regulatory reasons we need access to historic backups. If for any reason we move away from Azure I need to know I can still access them so I would like to be given the option to recover the VM to an on premise location.4 votes
Azure VM Level Backups (announced March 26th, 2015) include a restore step that starts a VM with the same computer name on the network as the original VM. I recommend adding a checkbox that prompts the user whether they want the original VM shut down or turned off, as this would avoid having two computers on the network with the same computer name. Or in a batch environment, you would not want a batch to be fired off on two systems as this could contaminate data.2 votes
Since VM Agent is required for the new VM Level Backup feature to work, the recovery services register wizard should either provide a hyperlink to a TechNet article on how to manually install the VM Agent, or it should run the powershell command to set ProvisionGuestAgent value to true using Powershell or a REST call.5 votes
I am currently testing the Recover Service to backup Azure based servers and have discovered that the agent has a requirement for the server to not have FIPS encryption setting turned on (HKLM\System\CurrentControlSet\Control\Lsa\FIPSAlgorithmPolicy\Enabled = 1)
Turning this off reduces the security posture of the server and goes against our standard and security team requirements. Considering this is a show stopper for us is there any consideration to changing the requirement for FIPS to be turned off?3 votes
- Don't see your idea?