Hi Fariborz, We are super heavy users of Autoscale Groups.
Each VM created as a result of the ASG is its own individual VM with is own storage. Under the hood, how it works is that it uses a VM Template (you specify) that is created via a Volume Snapshot of an existing VM. That way, the VM Template has the applications you develop. The process looks like this: #1. Create a Temporary VM, and deploy your desired applications #2. Do a Volume Snapshot #3. Convert Volume Snapshot to VM Template #4. Attach VM Template to an Autoscale Group Policy Then, when the rules set in your Autoscale Group policy, ACS will create a new VM using this ‘Master VM Template’. It can scale up or scale down (destroy) automatically. So its best not to use it for services with data inside, cause it will be lost. Autoscale is best for VMs with services like Website Ui, API Servers etc. Not suitable for VMs with message queues, databases, etc Give it a spin and everything will make sense. Regards, Bryan On 15 Nov 2024 at 5:24 AM +0800, Fariborz Navidan <mdvlinqu...@gmail.com>, wrote: > Hi everyone, > > Today I just came across a question regarding Auto-scale VM groups feature > in ACS. Could someone clarify whether VMs inside a Auto-scale group share > the same virtual disk or each VM which is automatically created , will have > an independent virtual disk created from base template? So, if each VM > operates independently, then how do you replicate files (e.g. application > files and databases)? > > Your ideas are highly appreciated. > > Thanks.
