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/private-5g-core/delete-resources.md
+31-2Lines changed: 31 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,15 +18,30 @@ If you want to delete your entire AP5GC deployment, you must complete all sectio
18
18
19
19
If you want to move resources instead, see [Move your private mobile network resources to a different region](region-move-private-mobile-network-resources.md).
20
20
21
+
If you want to delete a single site, see [Delete sites using the Azure portal](delete-a-site.md).
22
+
21
23
> [!CAUTION]
22
-
> This procedure will destroy your AP5GC deployment. You will lose all data associated with your AP5GC deployment. Do not delete resources that are in use.
24
+
> This procedure will destroy your AP5GC deployment. You will lose all data that isn't backed up. Do not delete resources that are in use.
23
25
24
26
## Prerequisites
25
27
26
28
- Ensure you can sign in to the Azure portal using an account with access to the active subscription you used to create your private mobile network. This account must have the built-in Contributor or Owner role at the subscription scope.
27
29
- Make a note of the resource group that contains your private mobile network, which was collected in [Collect the required information to deploy a private mobile network](collect-required-information-for-private-mobile-network.md).
28
30
- Make a note of the resource group that contains your Azure Stack Edge and custom location resources.
29
31
32
+
## Back up deployment information
33
+
34
+
All data will be lost when deleting your deployment. Back up any information you'd like to preserve. You can use this information to help set up a new deployment.
35
+
36
+
1. Refer to [Collect the required information for your SIMs](provision-sims-azure-portal.md#collect-the-required-information-for-your-sims) to take a backup of all the information you'll need to recreate your SIMs.
37
+
1. Depending on your authentication method when signing in to the [distributed tracing](distributed-tracing.md) and [packet core dashboards](packet-core-dashboards.md):
38
+
39
+
- If you use Azure AD, save a copy of the Kubernetes Secret Object YAML file you created in [Create Kubernetes Secret Objects](enable-azure-active-directory.md#create-kubernetes-secret-objects).
40
+
- If you use local usernames and passwords and want to keep using the same credentials, save a copy of the current passwords to a secure location.
41
+
42
+
1. If you want to retain any traces, [export and save](distributed-tracing-share-traces.md#export-trace-from-the-distributed-tracing-web-gui) them securely before continuing.
43
+
1. Refer to [Exporting a dashboard](https://grafana.com/docs/grafana/v6.1/reference/export_import/#exporting-a-dashboard) in the Grafana documentation to save a backed-up copy of your dashboards.
44
+
30
45
## Delete private mobile network resources
31
46
32
47
The private mobile network resources represent your private 5G core network. If you followed the recommendations in this documentation when creating your resources, you should have a single resource group containing all private mobile network resources. You must ensure that you do not delete any unrelated resources.
@@ -54,4 +69,18 @@ The Azure Kubernetes Service (AKS) cluster is an orchestration layer used to man
54
69
55
70
## Next steps
56
71
57
-
- To create a new AP5GC deployment, refer to [Commission the AKS cluster](commission-cluster.md) and [Deploy a private mobile network through Azure Private 5G Core - Azure portal](how-to-guide-deploy-a-private-mobile-network-azure-portal.md).
72
+
To create a new AP5GC deployment, refer to [Commission the AKS cluster](commission-cluster.md) and [Deploy a private mobile network through Azure Private 5G Core - Azure portal](how-to-guide-deploy-a-private-mobile-network-azure-portal.md).
73
+
74
+
Once you have created a new deployment, complete the following steps to restore the data you backed up in [Back up deployment information](#back-up-deployment-information).
75
+
76
+
1. Retrieve your backed-up SIM information and recreate your SIMs by following one of:
77
+
78
+
-[Provision new SIMs for Azure Private 5G Core - Azure portal](provision-sims-azure-portal.md)
79
+
-[Provision new SIMs for Azure Private 5G Core - ARM template](provision-sims-arm-template.md)
80
+
81
+
1. Depending on your authentication method when signing in to the [distributed tracing](distributed-tracing.md) and [packet core dashboards](packet-core-dashboards.md):
82
+
83
+
- If you use Azure AD, [reapply the Secret Object for distributed tracing and the packet core dashboards](enable-azure-active-directory.md#apply-kubernetes-secret-objects).
84
+
- If you use local usernames and passwords, follow [Access the distributed tracing web GUI](distributed-tracing.md#access-the-distributed-tracing-web-gui) and [Access the packet core dashboards](packet-core-dashboards.md#access-the-packet-core-dashboards) to restore access to your local monitoring tools.
85
+
86
+
1. If you backed up any packet core dashboards, follow [Importing a dashboard](https://grafana.com/docs/grafana/v6.1/reference/export_import/#importing-a-dashboard) in the Grafana documentation to restore them.
0 commit comments