In this lesson you can learn the difference between the different agent installations followed by the installation and configuration of the agent on source server.
- [Instructor] Our next step in configuring the Azure backup server is to install the agent on the servers that we want to protect. And to do so, make sure you're still in Management, and scroll on up to Production Servers, and then click Add. And we're presented with two choices here. We can either protect Windows servers or VMware servers. Protecting VMmware servers with the Azure backup server is out of scope for this course. Therefore, I'm just going to go ahead and click on Next.
And you'll notice we have another two options. We can install agents or attach agents to these servers. We would install agents for computers that are not behind firewalls, or for computers that have required exceptions already created in the firewall. If you have computers that are behind a firewall, then you'll use the Attach Agents options. These computers may also have an agent that is already installed on it, or the agent will be installed externally a little bit later.
When you select this option, you'll notice that you have another two options to choose from. The first one is Attach Agents on a Computer on a Trusted Domain. You would select this option when servers are in the same domain as the Azure backup server. Or you may sometimes hear it referred to as the DPM server. You would also use this option if the domain had a two-way trust with the domain that has the Azure backup server. If you do not have a two-way trust, or that server is not the same domain as the Azure backup server, then you would change a computer in a workgroup or untrusted domain.
I'm going to go ahead and click Install Agent. Now, full transparency here, I have dropped the firewall for the machines that we're going to install the agents on. And I did this for demonstration purposes. Now, in the real world, you wouldn't do this. And you would create exceptions. You would add exceptions to the firewall. In our next screen, we can go ahead and pick the servers that we want to install the agent on. And I'm going to do two of them here. I'm going to take our SQL server and our member server.
And go ahead and click Next. Now I need to provide the credentials for an administrative account. This final step is a little bit on the important side. Please note that your servers may restart. If you're doing this on production servers in the middle of the day, that might cause some hiccups within your environment, and you may want to select the second option, No, I will restart the selected computers later. As this is in our demo environment, I'll go ahead and have them restart if required.
Go ahead, click Next. And finally, on our summary page, we have a list of the tasks that are going to be performed. And you can go ahead and start installing the agents. And this will take a few minutes, so patience will be a virtue here. And in short order, the agents will have been installed on those servers. I'm going to go ahead and click Close. And you'll now see that we have the two servers listed here. And one thing I want to point out is it says Unprotected computers with the protection agent.
All we've done here is actually installed the agent. We haven't protected these servers as of yet. That's coming up in the next lesson.
- Creating a Recovery Services vault for Azure Backup
- Protecting virtual machines, files and folders, databases, workloads, and file shares
- Restoring virtual machines, files and folders, databases, workloads, and file shares
- Azure Site Recovery scenarios
- Running failover and failback tests
- Replicating an Azure virtual machine