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/modeling-simulation-workbench/disaster-recovery.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,26 +10,26 @@ ms.date: 08/21/2024
10
10
11
11
# Disaster recovery for Modeling and Simulation Workbench
12
12
13
-
This article explains how to configure a disaster recovery environment for Azure Modeling and Simulation Workbench. Azure data center outages are rare but can last anywhere from a few minutes to hours. Data Center outages can cause disruption to the environments hosted in that data center. By following the steps detailed in this article, Azure Modeling and Simulation workbench customers can continue to operate in the cloud in the event of a data center outage for the primary region hosting your workbench instance.
13
+
This article explains how to configure a disaster recovery environment for Azure Modeling and Simulation Workbench. Azure data center outages are rare but can last anywhere from a few minutes to hours. Data Center outages can cause disruption to the environments hosted in that data center. By following the steps in this article, Azure Modeling and Simulation workbench customers will continue to operate in the cloud in the event of a data center outage for the primary region hosting your workbench instance.
14
14
15
15
Planning for disaster recovery involves identifying expected recovery point objectives (RPO) and recovery time objectives (RTO) for your instance. Based upon your risk-tolerance and expected RPO, follow these instructions at an interval appropriate for your business needs.
16
16
17
-
A typical disaster recovery workflow starts with a failure of a critical service in your primary region. As the issue gets investigated, Azure will publish an expected time for the primary region to recover. If this timeframe is not acceptable for business continuity, and the problem does not impact your secondary region, you would start the process to fail over to the secondary region.
17
+
A typical disaster recovery workflow starts with a failure of a critical service in your primary region. As the issue gets investigated, Azure publishes an expected time for the primary region to recover. If this timeframe is not acceptable for business continuity, and the problem does not impact your secondary region, you would start the process to fail over to the secondary region.
18
18
19
19
## Achieving business continuity for Azure Modeling and Simulation Workbench
20
20
To be prepared for a data center outage, you can have a Modeling and Simulation workbench instance provisioned in a secondary region.
21
21
22
-
These Workbench resources can be configured to match the resources which exist in the primary Azure Modeling and Simulation workbench instance. Users in the workbench instance environment can be provisioned ahead of time, or when you switch to the secondary region. Chamber and connector resources can be put in a stopped state post deployment to invoke idle billing meters when not being used actively.
22
+
These Workbench resources can be configured to match the resources that exist in the primary Azure Modeling and Simulation workbench instance. Users in the workbench instance environment can be provisioned ahead of time, or when you switch to the secondary region. Chamber and connector resources can be put in a stopped state post deployment to invoke idle billing meters when not being used actively.
23
23
24
-
Alternatively, if you do not want to have an Azure Modeling and Simulation Workbench instance provisioned in the secondary region until an outage impacts your primary region, you can follow the provided procedures in the Quickstart but stop before actually creating the Azure Modeling and Simulation Workbench instance in the secondary region. That step can be executed when you choose to create the workbench resources in the secondary region as a fail over.
24
+
Alternatively, if you don't want to have an Azure Modeling and Simulation Workbench instance provisioned in the secondary region until an outage impacts your primary region, follow the provided steps in the Quickstart, but stop before creating the Azure Modeling and Simulation Workbench instance in the secondary region. That step can be executed when you choose to create the workbench resources in the secondary region as a failover.
25
25
26
26
## Prerequisites
27
27
28
28
- Ensure that the services and features that your account uses are supported in the target secondary region.
29
29
30
30
## Verify Entra ID tenant
31
31
32
-
The workspace source and destination can be in the same subscription. If source and destination for workbench will be different subscriptions, the subscriptions must exist within the same Entra ID tenant. Use Azure PowerShell to verify that both subscriptions have the same tenant ID.
32
+
The workspace source and destination can be in the same subscription. If source and destination for workbench are different subscriptions, the subscriptions must exist within the same Entra ID tenant. Use Azure PowerShell to verify that both subscriptions have the same tenant ID.
Copy file name to clipboardExpand all lines: articles/modeling-simulation-workbench/shared-storage.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
2
title: Shared storage for Modeling and Simulation Workbench
3
-
description: This article provides an overview of disaster recovery for Azure Modeling and Simulation Workbench workbench component.
3
+
description: This article provides an overview of shared storage for Azure Modeling and Simulation Workbench workbench component.
4
4
author: meaghanlewis
5
5
ms.author: mosagie
6
6
ms.service: modeling-simulation-workbench
@@ -10,13 +10,13 @@ ms.date: 08/21/2024
10
10
11
11
# Shared storage for Modeling and Simulation Workbench
12
12
13
-
To enable cross team and/or cross-organization collaboration in a secure manner within the workbench, a shared storage resource allows for selective data sharing between collaborating parties. It is an Azure NetApp Files based storage volume and is available to deploy in multiples of 4TB’s. Workbench owners can create multiple shared storage instances on demand and dynamically link them to existing chambers to facilitate secure collaboration.
13
+
To enable cross team and/or cross-organization collaboration in a secure manner within the workbench, a shared storage resource allows for selective data sharing between collaborating parties. It's an Azure NetApp Files based storage volume and is available to deploy in multiples of 4 TB’s. Workbench owners can create multiple shared storage instances on demand and dynamically link them to existing chambers to facilitate secure collaboration.
14
14
15
-
Users who are provisioned to a specific chamber can access all shared storage volumes linked to that chamber. Once users get de-provisioned from a chamber or that chamber gets deleted, they lose access to any linked shared storage volumes.
15
+
Users who are provisioned to a specific chamber can access all shared storage volumes linked to that chamber. Once users get deprovisioned from a chamber or that chamber gets deleted, they lose access to any linked shared storage volumes.
16
16
17
17
## Key features of shared storage
18
18
19
-
**Performance**: A Shared storage resource within the workbench is high-performance Azure NetApp Files based, targeting complex engineering workloads. It can be used to run simulations and is not limited to being used as a data transfer mechanism.
19
+
**Performance**: A shared storage resource within the workbench is high-performance Azure NetApp Files based, targeting complex engineering workloads. It isn't limited to being used as a data transfer mechanism. The resource can also be used to run simulations.
20
20
21
21
**Scalability**: Users can adjust the storage capacity and performance tier according to their needs, just like chamber private storage.
0 commit comments