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: articles/hpc-cache/configuration.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -76,7 +76,7 @@ Consider using a test cache to check and refine your DNS setup before you use it
76
76
77
77
### Refresh storage target DNS
78
78
79
-
If your DNS server updates IP addresses, the associated NFS storage targets will become temporarily unavailable. Read how to update your custom DNS system IP addresses in [Manage storage targets](manage-storage-targets.md#update-ip-address-custom-dns-configurations-only).
79
+
If your DNS server updates IP addresses, the associated NFS storage targets will become temporarily unavailable. Read how to update your custom DNS system IP addresses in [View and manage storage targets](manage-storage-targets.md#update-ip-address-custom-dns-configurations-only).
Copy file name to clipboardExpand all lines: articles/hpc-cache/hpc-cache-edit-storage.md
+3-3Lines changed: 3 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@ ms.author: v-erkel
13
13
You can modify storage targets with the Azure portal or by using the Azure CLI. For example, you can change access policies, usage models, and namespace paths for an existing storage target.
14
14
15
15
> [!TIP]
16
-
> Read [Manage storage targets](manage-storage-targets.md) to learn how to delete or suspend storage targets, or make them write cached data to back-end storage.
16
+
> Read [View and manage storage targets](manage-storage-targets.md) to learn how to delete or suspend storage targets, or make them write cached data to back-end storage.
17
17
18
18
Depending on the type of storage, you can modify these storage target values:
19
19
@@ -68,7 +68,7 @@ To change a blob storage target's namespace with the Azure CLI, use the command
68
68
69
69
For NFS storage targets, you can change or add virtual namespace paths, change the NFS export or subdirectory values that a namespace path points to, and change the usage model.
70
70
71
-
Storage targets in caches with some types of custom DNS settings also have a control for refreshing their IP addresses. (This kind of configuration is rare.) Learn how to refresh the DNS settings in [Manage storage targets](manage-storage-targets.md#update-ip-address-custom-dns-configurations-only).
71
+
Storage targets in caches with some types of custom DNS settings also have a control for refreshing their IP addresses. (This kind of configuration is rare.) Learn how to refresh the DNS settings in [View and manage storage targets](manage-storage-targets.md#update-ip-address-custom-dns-configurations-only).
72
72
73
73
Details are below:
74
74
@@ -174,6 +174,6 @@ The configuration for ADLS-NFS usage models is identical to the NFS usage model
174
174
175
175
## Next steps
176
176
177
-
* Read [Manage storage targets](manage-storage-targets.md) for information about stopping, deleting, and flushing individual storage targets.
177
+
* Read [View and manage storage targets](manage-storage-targets.md) for information about stopping, deleting, and flushing individual storage targets.
178
178
* Read [Add storage targets](hpc-cache-add-storage.md) to learn more about storage target options.
179
179
* Read [Plan the aggregated namespace](hpc-cache-namespace.md) for more tips about using virtual paths.
Copy file name to clipboardExpand all lines: articles/hpc-cache/manage-storage-targets.md
+35-12Lines changed: 35 additions & 12 deletions
Original file line number
Diff line number
Diff line change
@@ -1,14 +1,23 @@
1
1
---
2
2
title: Manage Azure HPC Cache storage targets
3
-
description: How to suspend, remove, force delete, and flush Azure HPC Cache storage targets
3
+
description: How to suspend, remove, force delete, and flush Azure HPC Cache storage targets, and how to understand the storage target state
4
4
author: ekpgh
5
5
ms.service: hpc-cache
6
6
ms.topic: how-to
7
-
ms.date: 07/12/2021
7
+
ms.date: 09/22/2021
8
8
ms.author: v-erkel
9
9
---
10
10
11
-
# Manage storage targets
11
+
# View and manage storage targets
12
+
13
+
The storage targets settings page shows information about each storage target for your HPC Cache, and gives options to manage individual storage targets.
14
+
15
+
> [!TIP]
16
+
> Instructions for listing storage targets using Azure CLI are included in the [Add storage targets](hpc-cache-add-storage.md#view-storage-targets) article. Other actions listed here might not yet be available in Azure CLI.
17
+
18
+

19
+
20
+
## Manage storage targets
12
21
13
22
You can perform management actions on individual storage targets. These actions supplement the cache-level options discussed in [Manage your cache](hpc-cache-manage.md).
14
23
@@ -30,7 +39,7 @@ Some storage targets also have a **Refresh DNS** option on this menu, which upda
30
39
31
40
Read the rest of this article for more detail about these options.
32
41
33
-
## Write cached files to the storage target
42
+
###Write cached files to the storage target
34
43
35
44
The **Flush** option tells the cache to immediately copy any changed files stored in the cache to the back-end storage system. For example, if your client machines are updating a particular file repeatedly, it is held in the cache for quicker access and not written to the long-term storage system for a period ranging from several minutes to more than an hour.
36
45
@@ -42,15 +51,15 @@ You could use this option to make sure that the back-end storage is populated be
42
51
43
52
This option mainly applies to usage models that include write caching. Read [Understand cache usage models](cache-usage-models.md) to learn more about read and write caching.
44
53
45
-
## Suspend a storage target
54
+
###Suspend a storage target
46
55
47
56
The suspend feature disables client access to a storage target, but doesn't permanently remove the storage target from your cache. You can use this option if you need to disable a back-end storage system for maintenance, repair, or replacement.
48
57
49
-
## Put a suspended storage target back in service
58
+
###Put a suspended storage target back in service
50
59
51
60
Use **Resume** to un-suspend a storage target.
52
61
53
-
## Force remove a storage target
62
+
###Force remove a storage target
54
63
55
64
> [!NOTE]
56
65
> This option can cause data loss for the affected storage target.
@@ -64,7 +73,7 @@ There also is no guarantee that the back-end storage system will be accessible a
64
73
Usually, force remove is used only when a storage target has become unresponsive or otherwise is in a bad state. This option lets you remove the bad storage target instead of having to take more drastic action.
You can use the Azure portal or the AZ CLI to delete a storage target.
70
79
@@ -74,11 +83,11 @@ Deleting a storage target removes the storage system's association with this Azu
74
83
75
84
If there is a large amount of changed data stored in the cache, deleting a storage target can take several minutes to complete. Wait for the action to finish to be sure that the data is safely stored in your long-term storage system.
76
85
77
-
### [Portal](#tab/azure-portal)
86
+
####[Portal](#tab/azure-portal)
78
87
79
88
To remove a storage target, open the **Storage targets** page. Click the '...' next to the storage target and choose **Delete** from the menu.
80
89
81
-
### [Azure CLI](#tab/azure-cli)
90
+
####[Azure CLI](#tab/azure-cli)
82
91
83
92
[Set up Azure CLI for Azure HPC Cache](./az-cli-prerequisites.md).
## Update IP address (custom DNS configurations only)
109
+
###Update IP address (custom DNS configurations only)
101
110
102
111
If your cache uses a non-default DNS configuration, it's possible for your NFS storage target's IP address to change because of back-end DNS changes. If your DNS server changes the back-end storage system's IP address, Azure HPC Cache can lose access to the storage system.
103
112
104
113
Ideally, you should work with the manager of your cache's custom DNS system to plan for any updates, because these changes make storage unavailable.
105
114
106
115
If you need to update a storage target's DNS-provided IP address, use the **Storage targets** page. Click the **...** symbol in the right column to open the context menu. Choose **Refresh DNS** to query the custom DNS server for a new IP address.
107
116
108
-
<!-- update screenshot if possible -->
117
+

109
118
110
119
If successful, the update should take less than two minutes. You can only refresh one storage target at a time; wait for the previous operation to complete before trying another.
111
120
121
+
### Understand storage target state
122
+
123
+
The storage target list shows two types of status: **State** and **Provisioning state**.
124
+
125
+
***State** indicates the operational state of the storage target. This value updates regularly and helps you understand whether or not the storage target is available for client requests and which of the management options are available.
126
+
***Provisioning state** tells you whether the last action to add or edit the storage target was successful. This value is only updated if you edit the storage target.
127
+
128
+
The **State** value affects which management options you can use. Here is a short explanation of the values and their effects.
129
+
130
+
***Ready** - The storage target is operating normally and available to clients. You can use any of the management options on this storage target (except for **Resume**, which only is valid for suspended storage targets).
131
+
***Busy** - The storage target is processing another operation. You can delete or force remove the storage target.
132
+
***Suspended** - The storage target has been taken offline. You can still flush, delete, or force remove this storage target. Choose **Resume** to put the target back in service.
133
+
***Flushing** - The storage target is writing data to the back-end storage.
134
+
112
135
## Next steps
113
136
114
137
* Learn about [cache-level management actions](hpc-cache-manage.md)
0 commit comments