I have been trying to find a way to clone ARM VM without deallocating it , so that the VMs can be replicated for different user groups on a need basis. Looks like Azure Recovery Services Vault can be used to achieve my goal though the intended purpose of the service is not really to clone a new VM. So my question is on the design side of these two services.
Could anyone shed light as to why ARM VM clone procedure mandates de-allocation of the cloned ? Which use cases are actually solved by that service ?
If I use Recovery Service Vault to create a new VM from an existing one , is there any side effect to it (technical/financial) ?
The AWS way of getting a copy of VM - Get a snapshot , create one from it - sounded simpler and user friendly to me. The Azure way of providing two different services for similar goals - Any insight to that kind of design decision making ?
Thank you in advance !
probably by design. it cant access page blob that is leased.
well, you install vm agent, you pay for ASR, you pay for protected VM.
You can create snapshots from managed disks no problem.
Related
I am relatively new to learning ADF; while creating linked-service for 'blob' data store, with the default settings:
'using connection string' for authentication type, at the end of creation step, I got the following recommendation:
Linked service will be published immediately
As Data Factory cannot store credentials in a Git repository, this change will be published immediately.
This may cause issues on the Master branch and on published resources that depend on this linked service. To avoid immediately publish of linked services, we recommend using Azure Key Vault.
I have attached screenshot of the recommendation to this post.
My concern is, what should be the ideal approach?
Further, if I publish the created 'linked service' directly with connection string as authentication type, how do I use it to run and test the pipeline? As of now, I haven't run a pipeline yet; everything I have created so far, I did it in Git-Repository mode of ADF.
Would anyone please help me guide through the process and best practice?
Thank you for giving your valuable time and support.
In Azure it is best to leverage managed identity wherever possible rather than having credentials stored in key vault as it adds to another security and maintainence layer
I am planning to migrate my Azure resources from EA type of subscription to C-S-P subscription. I found a tool called as Migrate Azure(sorry cannot write the short form as this does not allow me to post). I am aware of its working, however i am just worried about one that.
Can the migration cause a downtime into any working of any resources like Azure Virtual machine, storage...etc. Point is i will be directly working on the production resources to migrate to the C-S-P subscription.
Can anyone give me an idea ?
As indicated by #HariHaran, you should follow the documentation mentioned in here
The subscription switching should not affect your workloads, since it's a subscription migration and not workload related(Assuming that all of your resources already reside in Azure). The safe approach to follow during your migration process is to do it incrementally. Then if all functions as normal, increase the migration rate. Do it all at once may not be the best. Redeployment issues can occur at times.
I'm in charge of provisioning a new Sitecore system on Azure as PaaS. I want to provision 3 environments in as many different regions. Still I want to have a main region which will provision a full XP installation, while the other 2 regions (slave) will provision only the CD. Each slave CD-DB will be configured as a publish target in the main region and will be feeding XDB and forms database.
So the question is: how can I achieve this?
I already provisioned the main region with the ARM templates and it's working fine. Now I need to provision the slave regions, but I can't find enough information on how to achieve this.
Can I use the clone function in Azure and modify config files later?
Thanks in advance
I would approach it like this:
Left side of your diagram provision as-it-is from the original Sitecore ARM template – XP scaled.
For the right side of your diagram will:
a. provision instance Sitecore XM single ARM template (delete master and forms database, reconfigure the web app role to be CD)
b. or customized a bit the XM scaled ARM template (removed CM and not needed database)
Fix configuration – add traffic manager, connection strings as needed etc.
as reference:
https://doc.sitecore.net/sitecore_experience_platform/setting_up_and_maintaining/sitecore_on_azure/deploying/sitecore_configurations_and_topology_for_azure
We signed up to BizSpark and have different Azure accounts. Our idea is to set up 2 VM on different accounts: first for backend and other for database, but for security reasons we need to make them work in one VPN.
Is it possible to do so or maybe there's any workaround?
I'm not much familiar with that so really don't know how to do it better.
P.S. Ideas about using same subscription for holding both VMs (or using 1 VM instead of 2) isn't applicable, 'cause we need rather much resources, so we cannot allow this.
We have a few servers in Azure that are running the same service. We would like them to be part of the same availability set. How do you add these servers together in the same availability set if they were not created in the same cloud service when they were created?
It looks like I would need to rebuild these VM's? If so that kinda sucks.
Please let me know if anyone knows a better way.
Thanks in advance.
Once a VM is created, it can't join an availability set.
However, the image for the VM is available in storage. So, new VMs can be spun up, using the image, this time adding them to the set. And rebuilding the VM from scratch is not needed.
Edit:
I've used the method above to bring up a VM, but I had forgotten that if your VM is running already, capture is the way to go. I'd suggest these steps:
Capture the image of your current VM. This will run sysprep on it, so you will want to be careful with it. (spin up a test VM and play with the steps until you feel confident to move to a production box)
Then when you create a new VM, specify your captured image and your availability set. Then the machine will come up with all your services running in the new set.