Skip to content

Commit dee6993

Browse files
committed
finish Ram feedback
1 parent 8ce111e commit dee6993

File tree

1 file changed

+16
-16
lines changed

1 file changed

+16
-16
lines changed

azure-local/manage/trusted-launch-vm-import-key.md

Lines changed: 16 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -61,34 +61,34 @@ The steps below involve copying VM guest state protection keys from the local ke
6161
6262
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.
6363
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.
6565
6666
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.
6767
6868
> [!NOTE]
6969
> Don't modify the backup folder.
7070
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:
7272
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.
7474
7575
1. Run `Import-Module .\TvmBackupUtils.psm1 -force`.
7676
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).
7979
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`
8181
82-
1. Delete `AzureStackTvmAKRootKey` as follows:
82+
1. Delete `AzureStackTvmAKRootKey` as follows:
8383
8484
> [!NOTE]
8585
> 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).
8686
87-
`Remove-MocKey -name  AzureStackTvmAKRootKey -group AzureStackHostAttestation -keyvaultName AzureStackTvmKeyVault`
87+
`Remove-MocKey -name  AzureStackTvmAKRootKey -group AzureStackHostAttestation -keyvaultName AzureStackTvmKeyVault`
8888
8989
1. Restore the keys from backup:
9090
91-
`Import-TVMKeys -WrappingKeyName <WrappingKeyName> -BackupPath <path to timestamped backup folder>`
91+
`Import-TVMKeys -WrappingKeyName <WrappingKeyName> -BackupPath <path to timestamped backup folder>`
9292
9393
> [NOTE!]
9494
> 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
9797
9898
1. Delete both `public.pem` and `private.pem` files from the Azure Local instance.
9999
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.
102102
103103
1. Run `Remove-MocKey -name WrappingKeyName -group AzureStackHostAttestation -keyvaultName AzureStackTvmKeyVault`
104104
105105
106106
## For Azure Local releases prior to 2505
107107
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.
109109
110110
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.
111111
@@ -131,13 +131,13 @@ Follow these steps to copy the VM guest state protection key from the local key
131131
132132
`Get-ClusterGroup <VM name>`
133133
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:
135135
136-
`(Get-VM -Name <VM name>).vmid`
136+
`(Get-VM -Name <VM name>).vmid`
137137
138-
1. Export the VM guest state protection key:
138+
1. Export the VM guest state protection key:
139139
140-
`Export-MocKey -name <VM ID> -wrappingKeyName wrappingKey -wrappingPubKeyFile wrappingKey.pem -outFile <VM ID>.json -group AzureStackHostAttestation -keyvaultName AzureStackTvmKeyVault -size 256`
140+
`Export-MocKey -name <VM ID> -wrappingKeyName wrappingKey -wrappingPubKeyFile wrappingKey.pem -outFile <VM ID>.json -group AzureStackHostAttestation -keyvaultName AzureStackTvmKeyVault -size 256`
141141
142142
1. On the Azure Local system with the backup key vault, run the following steps on the Azure Local system:
143143

0 commit comments

Comments
 (0)