Failed to create persistent connection to ADMIN$ Error

Encountered an error message "Failed to create a persistent connection to ADMIN$" when try to add managed server become a proxy. Particular Proxy is a stand-alone and not join to the domain.

Product:- Veeam Backup & Replication

[Resolution]
Try to disable UAC from registry

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System.

Create a DWORD value called LocalAccountTokenFilterPolicy and assign it a value of 1.

Part 2-Setting Up DR Orchestration Using Veeam Availability Orchestrator

Ready for Part 2...
In previous post we have look into how to configure VAO. Next, we will start to use VAO.

BUILD

• Start by build a failover plan with one VM
• Create a failover plan by selecting VM Group
• Assign step that you want it to perform. 
• In VAO, have several step that you can use and few test to perform for Microsoft workload.

Example:-

• Shutdown VM
• Process Replica VM
• Verify SQL Database
• Verify SQL Port

etc...

To backup VM after failover, select Template Job that you have created in Part 1.

Once created a failover plan, you can perform "Run Readiness Check" to verify that step is working fine.

Once  verification passed, you can add more VM Group

TEST

Next step is to put the DR Plan to test in isolated environment. You can manual run or schedule to run a test.

On VAO UI, you can view the test status

On Veeam Console, you can view from history

DOCUMENT 

Lastly, you can generate report. Here is one of the sample report on readiness check report.

That's all for today. Give VAO a try if you're interested to orchestrate DR Plan.

Part 1-Setting Up DR Orchestration Using Veeam Availability Orchestrator

In this post we are going to look into how to build DR orchestrate using Veeam Availability Orchestrator (VAO).

VAO is an add-on for Veeam Availability Suite to orchestrate disaster recovery task, allowing DR plan creation, testing and execution and documentation in Vmware vSphere environment.

At this moment, it won't work for Hyper-V environment.

You can use VAO to

[Pre-requisite]

• Environment :- Vmware 5.x, 6.x
• Vcenter with vm tag
• Veeam Backup & Replication v9.5 update 3 -Enterprise Plus
• Installation of the VAO server on a machine already running Veeam products is not supported
• SQL Server

[Lab Environment]

• Single VAO environment - mean multiple Production sites, but one DR site
• Install VAO on a single server
• will install embedded VBR 
• will install embedded Veeam One
• VAO components
• Use SQL Express

[Access VAO Server]

Use browser to access VAO UI:

https://<vao server>:9898

Once access, you can follow the configuration wizard to perform initial configuration.
1st step, set as DR site for 1st VAO Installation.

You can set initial setting to connect to standalone VBR Server & Vcenter. Else skip first.
To add these settings later, you can use the wizard to configure.

STEP 1:- Connect to Infrastructure

• Connect to VBR Server to inventory Veeam data
• Connect to vCenter to inventory Vmware vsphere infrastructure object

STEP 2:- Manage Access
Then enable the component before it visible for use.

• Enable VM Group

• Enable Plan Steps

• Enable Credential

• Enable Virtual Lab

 After you create a virtual lab on any Veeam Backup & Replication server in the DR VAO site, VAO will discover the virtual lab and make it available in the VAO UI.

VAO will not discover virtual lab which located in Production Site.

• Enable Templates Job

To protect VM included in the plan after failover, you need to create a backup job at the DR Site.

Criteria:-

a) Create an empty folder in VM & templates - in VCenter

b) put [VAO Template] text in Job description

c) Select the folder that you've created earlier

d) The backup job must not contain any VMs

After job created, VAO will collect and display in the VAO UI.

STEP 3:- Add Users to Roles

We assigned Domain Admins Group with the role: Site Administrators.

STEP 4: Configure an email notification

That should do the trick. We have complete setup VAO and ready for use.
Stay tuned for Part 2- Click here (ready soon)