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
Copy file name to clipboardExpand all lines: azure-local/manage/trusted-launch-vm-import-key.md
+16-16Lines changed: 16 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -61,34 +61,34 @@ The steps below involve copying VM guest state protection keys from the local ke
61
61
62
62
The steps below involve restoring VM guest state protection keys from a folder containing the backup copy to the local key vault of an Azure Local instance where the VMs need to be restored.
63
63
64
-
1. Copy both private and public key files for the wrapping key that you created during step 1 to the Azure Local instance.
64
+
1. Copy both private and public key files for the wrapping key that you created during Backup step 1 to the Azure Local instance.
65
65
66
66
1. Copy the timestamped backup folder to the Azure Local instance. Pick the folder under the backup root folder with the latest timestamp as that folder will have the most recent copy.
67
67
68
68
> [!NOTE]
69
69
> Don't modify the backup folder.
70
70
71
-
1. Import the wrapping key that you created during backup step 1 to the Azure Local instance:
71
+
1. Import the wrapping key that you created during Backup step 1 to the Azure Local instance:
72
72
73
-
1. Download `TvmBackupUtils.psm1` script at <add hyperlink> to your Azure Local instance.
73
+
1. Download `TvmBackupUtils.psm1` script at (add hyperlink) to your Azure Local instance.
74
74
75
75
1. Run `Import-Module .\TvmBackupUtils.psm1 -force`.
76
76
77
-
> [!NOTE]
78
-
> Make sure the WrappingKeyName you specify doesn't match the name of a key already existing in the timestamped backup folder. Otherwise, this will cause a failure during import (see Restore step 5).
77
+
> [!NOTE]
78
+
> Make sure the WrappingKeyName you specify doesn't match the name of a key already existing in the timestamped backup folder. Otherwise, this will cause a failure during import (see Restore step 5).
79
79
80
-
1. Run `Import-TvmWrappingKeyFromPem -KeyName <WrappingKeyName> -PublicKeyPath <path to public.pem> -PrivateKeyPath <path to private.pem> -KeySize 2048`
80
+
1. Run `Import-TvmWrappingKeyFromPem -KeyName <WrappingKeyName> -PublicKeyPath <path to public.pem> -PrivateKeyPath <path to private.pem> -KeySize 2048`
81
81
82
-
1. Delete `AzureStackTvmAKRootKey` as follows:
82
+
1. Delete `AzureStackTvmAKRootKey` as follows:
83
83
84
84
> [!NOTE]
85
85
> Do this step only if you're restoring the VM to the same Azure Local instance (the Azure Local instance where the VM resided before failure).
`Import-TVMKeys -WrappingKeyName <WrappingKeyName> -BackupPath <path to timestamped backup folder>`
91
+
`Import-TVMKeys -WrappingKeyName <WrappingKeyName> -BackupPath <path to timestamped backup folder>`
92
92
93
93
> [NOTE!]
94
94
> If the local key vault of the Azure Local instance already has a VM guest state protection key with the same name or already has an `AzureStackTvmAKRootKey`, you will receive an `InvalidVersion` error for that key. You can ignore this, as the key is already in the key vault.
@@ -97,15 +97,15 @@ The steps below involve restoring VM guest state protection keys from a folder c
97
97
98
98
1. Delete both `public.pem` and `private.pem` files from the Azure Local instance.
99
99
100
-
> [!IMPORTANT]
101
-
> Remove the wrapping key from the local key vault of the Azure Local instance using `Remove-MocKey`. This will help avoid collisions later.
100
+
> [!IMPORTANT]
101
+
> Remove the wrapping key from the local key vault of the Azure Local instance using `Remove-MocKey`. This will help avoid collisions later.
102
102
103
103
1. Run `Remove-MocKey -name WrappingKeyName -group AzureStackHostAttestation -keyvaultName AzureStackTvmKeyVault`
104
104
105
105
106
106
## For Azure Local releases prior to 2505
107
107
108
-
To backup, this approach copies VM guest state protection keys from the local key vault of your Azure Local instance to the local key vault of another Azure Local instance that is used for key backup purposes.
108
+
To backup, this approach copies VM guest state protection keys from the local key vault of your Azure Local instance to the local key vault of another Azure Local instance that is used for key backup purposes.
109
109
110
110
To restore, this method restores VM guest state protection keys from the local key vault (backup key vault) of the Azure Local instance that is used for key backup purposes to the local key vault of an Azure Local instance where the VMs need to be restored.
111
111
@@ -131,13 +131,13 @@ Follow these steps to copy the VM guest state protection key from the local key
131
131
132
132
`Get-ClusterGroup <VM name>`
133
133
134
-
1. Run the following cmdlet on the owner node to determine the VM ID:
134
+
1. Run the following cmdlet on the owner node to determine the VM ID:
0 commit comments