You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am looking at a number of ways to take a copy of my Production. This is mainly for DR and any other scenario where we might need to create a copy of our existing environment.
I am using Azure NetApp Files. So in my deployment I am choosing nfs-byo. I can take a snapshot of my existing NetApp volume and restore it to a new Volume.
To change the mount point for the controller is relatively easy. I understand I can just amend /etc/fstab. However, I am having some difficulty trying to work out how to do this for the VMSS.
I understand on creation of a new instance the VMSS creates /var/lib/cloud/instance/moodle_on_azure_configs.json with all the relevant values. However after the first deploy, where are all the values stored? How would we edit them if we needed to?
The text was updated successfully, but these errors were encountered:
ChrisLopezUK
changed the title
Changing values in an existing deployment. DB, Files system etc.
Changing values in an existing deployment. DB, File System etc.
Feb 19, 2021
Hi All.
I am looking at a number of ways to take a copy of my Production. This is mainly for DR and any other scenario where we might need to create a copy of our existing environment.
I am using Azure NetApp Files. So in my deployment I am choosing nfs-byo. I can take a snapshot of my existing NetApp volume and restore it to a new Volume.
To change the mount point for the controller is relatively easy. I understand I can just amend /etc/fstab. However, I am having some difficulty trying to work out how to do this for the VMSS.
I understand on creation of a new instance the VMSS creates /var/lib/cloud/instance/moodle_on_azure_configs.json with all the relevant values. However after the first deploy, where are all the values stored? How would we edit them if we needed to?
The text was updated successfully, but these errors were encountered: