Skip to content

Commit f0cda2d

Browse files
committed
acrolinx updates and modify landing page
1 parent 5064043 commit f0cda2d

File tree

4 files changed

+42
-28
lines changed

4 files changed

+42
-28
lines changed

articles/modeling-simulation-workbench/disaster-recovery.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -10,26 +10,26 @@ ms.date: 08/21/2024
1010

1111
# Disaster recovery for Modeling and Simulation Workbench
1212

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.
1414

1515
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.
1616

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.
1818

1919
## Achieving business continuity for Azure Modeling and Simulation Workbench
2020
To be prepared for a data center outage, you can have a Modeling and Simulation workbench instance provisioned in a secondary region.
2121

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.
2323

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.
2525

2626
## Prerequisites
2727

2828
- Ensure that the services and features that your account uses are supported in the target secondary region.
2929

3030
## Verify Entra ID tenant
3131

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.
3333

3434
```powershell
3535
Get-AzSubscription -SubscriptionId <your-source-subscription>.TenantId
@@ -65,7 +65,7 @@ You can now do your work in the new workbench instance created in the backup reg
6565

6666
## Cleanup
6767

68-
Once your primary region is back up and operating, and you no longer need your backup instance, you can delete it.
68+
Once your primary region is up and operating, and you no longer need your backup instance, you can delete it.
6969

7070
## Related information
7171

articles/modeling-simulation-workbench/index.yml

Lines changed: 31 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ metadata:
1010
ms.reviewer: yochu
1111
ms.service: modeling-simulation-workbench
1212
ms.topic: index
13-
ms.date: 01/01/2023
13+
ms.date: 08/21/2024
1414

1515
# linkListType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | tutorial | video | whats-new
1616

@@ -24,20 +24,6 @@ landingContent:
2424
links:
2525
- text: What is Modeling and Simulation Workbench?
2626
url: ./modeling-simulation-workbench-overview.md
27-
- linkListType: concept
28-
links:
29-
- text: Workbench
30-
url: ./concept-workbench.md
31-
- text: User Personas
32-
url: ./concept-user-personas.md
33-
- text: Chambers
34-
url: ./concept-chamber.md
35-
- text: Connectors
36-
url: ./concept-connector.md
37-
- text: Data Pipeline
38-
url: ./concept-data-pipeline.md
39-
- text: License service
40-
url: ./concept-license-service.md
4127
# Card: Get started
4228
- title: Get started
4329
linkLists:
@@ -59,8 +45,36 @@ landingContent:
5945
url: ./how-to-guide-download-data.md
6046
- text: Manage chamber storage
6147
url: ./how-to-guide-manage-storage.md
62-
# - name: Disaster Recovery
63-
# href: ./how-to-guide-disaster-recovery.md
48+
# Card: Concepts
49+
- title: Concepts
50+
linkLists:
51+
- linkListType: concept
52+
links:
53+
- text: Workbench
54+
url: ./concept-workbench.md
55+
- text: User personas
56+
url: ./concept-user-personas.md
57+
- text: Chamber
58+
url: ./concept-chamber.md
59+
- text: Connector
60+
url: ./concept-connector.md
61+
- text: Data pipeline
62+
url: ./concept-data-pipeline.md
63+
- text: License service
64+
url: ./concept-license-service.md
65+
- text: Shared storage
66+
url: ./shared-storage.md
67+
- text: Disaster recovery
68+
url: ./disaster-recovery.md
69+
# Card: Resources
70+
- title: Resources
71+
linkLists:
72+
- linkListType: reference
73+
links:
74+
- text: Troubleshoot
75+
url: ./resources-troubleshoot.md
76+
- text: Get support
77+
url: ./resources-get-support.md
6478
# Card: Reference
6579
# - title: Reference
6680
# linkLists:

articles/modeling-simulation-workbench/shared-storage.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
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.
44
author: meaghanlewis
55
ms.author: mosagie
66
ms.service: modeling-simulation-workbench
@@ -10,13 +10,13 @@ ms.date: 08/21/2024
1010

1111
# Shared storage for Modeling and Simulation Workbench
1212

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.
1414

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.
1616

1717
## Key features of shared storage
1818

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.
2020

2121
**Scalability**: Users can adjust the storage capacity and performance tier according to their needs, just like chamber private storage.
2222

articles/modeling-simulation-workbench/toc.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ items:
3333
href: ./shared-storage.md
3434
- name: Business Continuity
3535
items:
36-
- name: Disaster Recovery
36+
- name: Disaster recovery
3737
href: ./disaster-recovery.md
3838
- name: How-to guides
3939
items:

0 commit comments

Comments
 (0)