How to rebuild new cluster by retaining rest of the resources in the Resource Group

by | Jan 18, 2021 | Technology | 0 comments

This article is contributed. See the original author and article here.

Steps to recreate/rebuild SF cluster by retaining others resources(Eg: Load balancer, Public IP, Vnet and So on…) in the Resource Group when cluster state is lost due to some unsupported operations.


 


Step 1: Go to Resource Explorer, navigate to SF resource and copy the configuration content of SF resource from the right plane


reshmav_0-1610951745443.png


 


Step 2: Delete the SF resource in the Resource group:


reshmav_1-1610951759029.png


 


Step 3: Deploy a Custom Template:


Paste the copied SF configuration in Step 1 under the “resource : [ // Please copy here]


Remove below properties:



  • Cluster ID

  • etag

  • id


 


Add the API version under the type and modify the UpgradeMode to “Manual”



  • “apiVersion”: “2018-02-01”,

  • “upgradeMode”: “Manual”


reshmav_2-1610951770845.png


Save and Create the Resource, Post which SF resource gets created under Resource group.


reshmav_3-1610951791672.png


 


Step 4: Copy the new Cluster Id from Resource Explorer -> SF resource:


reshmav_4-1610951807967.png


Navigate to VMSS resource -> Replace the Cluster ID in ClusterEndpoint


reshmav_5-1610951817534.png


 


However VMSS update may result in below failure, Please ignore the Error.


If you go to Resource Group- > VMSS -> ClusterEndpoint will be updated with new Cluster ID


reshmav_6-1610951828781.png


 


Step 5: Scale the instance count by + 1( In case of Reliability is None, +3 if bronze , +5 if Silver and so on)


reshmav_7-1610951840781.png


Once Instance is created, SF Status would show as “Deploying” and newly added instances will start showing under Nodes.


reshmav_8-1610951852372.png


 


Step 6: Delete the old instance:


reshmav_9-1610951860365.png


 

Brought to you by Dr. Ware, Microsoft Office 365 Silver Partner, Charleston SC.

Submit a Comment