Crash Archive Repository

[kbouchard]

Hi everyone,

I have some problems when I try to do a monthly backup with the archive repository. I don't have an error when I do backup to cool or hot repository. The error message comes from a policy that blocks the VM type, but my workers are configured with a type that is allowed in the policy. I don't see why backing up to a cold repository works, but not to an archive repository. I see the worker creates with an archival purpose.

Does someone have ideas about where the problem comes from?

[nielsengelen]

Hi Kevin,

It's hard to troubleshoot what you are facing from your description. I would suggest to open a support case to better understand what error message you are receiving and to troubleshoot it. Once you've opened one, can you let us know the case ID for future reference?

[kbouchard]

I think I find my problem.
Do you know if the size of the vm is hard coding to the solution when we do the Archiving?
Actually, I have limit SKU for one of my policy and I block the size Standard_E2_v4 and I configure my worker to use the size E4s_v4.

[22.06.2022 08:26:01] 34 (1) Reconfiguring the worker VM size for Archive purpose to use in region canadaeast
[22.06.2022 08:26:02] 67 (1) Worker VBA-0834a185-8a25-4a73-9e7b-2900d381a3bb: assigning the new VM size Archive for canadaeast purpose to use in region Standard_E2_v4
[22.06.2022 08:26:02] 67 (1) Worker VBA-0834a185-8a25-4a73-9e7b-2900d381a3bb: setting up the network
[22.06.2022 08:26:03] 67 (1) Error: Worker VBA-0834a185-8a25-4a73-9e7b-2900d381a3bb: failed deploying worker virtual machine
[22.06.2022 08:26:04] 50 (1) Error: Worker VBA-0834a185-8a25-4a73-9e7b-2900d381a3bb: Failed to create a new VM of size Standard_E4s_v4 in region canadaeast. Deleting the VM...

[nielsengelen]

The worker size is fixed but you can modify it via support. We are looking at enhancing our product so this becomes a feature as well in the nearby future.

[kbouchard]

Perfect!