Skip to content

Commit fc28649

Browse files
Y0CossY0Coss
committed
Proofreadig & Duplication
1 parent 55df649 commit fc28649

File tree

15 files changed

+713
-11
lines changed

15 files changed

+713
-11
lines changed

‎pages/public_cloud/compute/classic_block_multi_az_limitations/guide.de-de.md

Lines changed: 54 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,54 @@
1+
---
2+
title: Proper Usage and Limitations of Classic Multi-Attach Block Storage in 3AZ Regions
3+
excerpt: 'Learn how to safely use Classic Multi-Attach Block Storage in 3AZ regions, understand its limitations, and avoid data corruption'
4+
updated: 2025-05-06
5+
flag: hidden
6+
---
7+
8+
## Introduction
9+
10+
Classic Multi-Attach 3AZ is a regional multi-zone volume type, available exclusively in Public Cloud regions with three Availability Zones (3AZ). This volume type allows a single volume to be attached simultaneously to multiple instances within the same region, enabling increased resilience and high availability for critical applications.
11+
12+
This feature is designed specifically for active/active or active/passive use cases, where multiple instances need coordinated access to shared data.
13+
14+
To better understand the underlying architecture for multi-zone deployments using regional Block Storage, refer to the following [documentation](/pages/public_cloud/public_cloud_cross_functional/3az_ref_architecture#2az-with-regional-block-storage).
15+
16+
> [!warning]
17+
>
18+
> It is the user's responsibility to ensure that a cluster-aware file system is used with Classic Multi-Attach volumes.
19+
>
20+
> Failure to do so can result in data corruption.
21+
>
22+
> Use only file systems designed for shared access, such as GFS2 or OCFS2.
23+
>
24+
> Standard file systems (e.g., XFS, EXT4, NTFS) are not supported unless proper fencing mechanisms are in place.
25+
>
26+
27+
## Usage
28+
29+
Creating and attaching a Classic Multi-Attach volume follows the same process as described in the [OVHcloud documentation on volume creation](/pages/public_cloud/compute/starting_with_managing_volumes_openstack_api). The key difference is that the volume type is "classic-multiattach", not just "classic".
30+
31+
If the volume type is omitted during creation, OpenStack will default to "classic-multiattach" (similar to how "classic" is set by default in regular regions).
32+
33+
In the OVHcloud Control Panel, simply select the classic volume available in the 3AZ region.
34+
35+
![classic 3az block volume](images/create_volume_type.png){.thumbnail}
36+
37+
## Considerations
38+
39+
When working with Classic Multi-Attach in 3AZ regions, the following points should be taken into account:
40+
41+
- Classic 3AZ Multi-Attach volumes can be attached to up to 16 instances simultaneously within the same region.
42+
- The multi-attach feature is only available with this specific volume type and exclusively in 3AZ regions, such as the Paris region.
43+
- Using cluster-aware file systems is required, but may result in performance degradation depending on the workload and configuration.
44+
45+
## Limitations
46+
47+
Classic Multi-Attach volumes come with specific limitations that should be considered before deployment:
48+
49+
- Volume retyping is not supported while the volume is in use — switching from a multiattach-capable type to a non-multiattach-capable type (or vice-versa) is not allowed.
50+
- Encryption is not available for multiattach-capable volumes.
51+
52+
## Go further
53+
54+
Join our [community of users](/links/community).

‎pages/public_cloud/compute/classic_block_multi_az_limitations/guide.en-asia.md

Lines changed: 54 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,54 @@
1+
---
2+
title: Proper Usage and Limitations of Classic Multi-Attach Block Storage in 3AZ Regions
3+
excerpt: 'Learn how to safely use Classic Multi-Attach Block Storage in 3AZ regions, understand its limitations, and avoid data corruption'
4+
updated: 2025-05-06
5+
flag: hidden
6+
---
7+
8+
## Introduction
9+
10+
Classic Multi-Attach 3AZ is a regional multi-zone volume type, available exclusively in Public Cloud regions with three Availability Zones (3AZ). This volume type allows a single volume to be attached simultaneously to multiple instances within the same region, enabling increased resilience and high availability for critical applications.
11+
12+
This feature is designed specifically for active/active or active/passive use cases, where multiple instances need coordinated access to shared data.
13+
14+
To better understand the underlying architecture for multi-zone deployments using regional Block Storage, refer to the following [documentation](/pages/public_cloud/public_cloud_cross_functional/3az_ref_architecture#2az-with-regional-block-storage).
15+
16+
> [!warning]
17+
>
18+
> It is the user's responsibility to ensure that a cluster-aware file system is used with Classic Multi-Attach volumes.
19+
>
20+
> Failure to do so can result in data corruption.
21+
>
22+
> Use only file systems designed for shared access, such as GFS2 or OCFS2.
23+
>
24+
> Standard file systems (e.g., XFS, EXT4, NTFS) are not supported unless proper fencing mechanisms are in place.
25+
>
26+
27+
## Usage
28+
29+
Creating and attaching a Classic Multi-Attach volume follows the same process as described in the [OVHcloud documentation on volume creation](/pages/public_cloud/compute/starting_with_managing_volumes_openstack_api). The key difference is that the volume type is "classic-multiattach", not just "classic".
30+
31+
If the volume type is omitted during creation, OpenStack will default to "classic-multiattach" (similar to how "classic" is set by default in regular regions).
32+
33+
In the OVHcloud Control Panel, simply select the classic volume available in the 3AZ region.
34+
35+
![classic 3az block volume](images/create_volume_type.png){.thumbnail}
36+
37+
## Considerations
38+
39+
When working with Classic Multi-Attach in 3AZ regions, the following points should be taken into account:
40+
41+
- Classic 3AZ Multi-Attach volumes can be attached to up to 16 instances simultaneously within the same region.
42+
- The multi-attach feature is only available with this specific volume type and exclusively in 3AZ regions, such as the Paris region.
43+
- Using cluster-aware file systems is required, but may result in performance degradation depending on the workload and configuration.
44+
45+
## Limitations
46+
47+
Classic Multi-Attach volumes come with specific limitations that should be considered before deployment:
48+
49+
- Volume retyping is not supported while the volume is in use — switching from a multiattach-capable type to a non-multiattach-capable type (or vice-versa) is not allowed.
50+
- Encryption is not available for multiattach-capable volumes.
51+
52+
## Go further
53+
54+
Join our [community of users](/links/community).

‎pages/public_cloud/compute/classic_block_multi_az_limitations/guide.en-au.md

Lines changed: 54 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,54 @@
1+
---
2+
title: Proper Usage and Limitations of Classic Multi-Attach Block Storage in 3AZ Regions
3+
excerpt: 'Learn how to safely use Classic Multi-Attach Block Storage in 3AZ regions, understand its limitations, and avoid data corruption'
4+
updated: 2025-05-06
5+
flag: hidden
6+
---
7+
8+
## Introduction
9+
10+
Classic Multi-Attach 3AZ is a regional multi-zone volume type, available exclusively in Public Cloud regions with three Availability Zones (3AZ). This volume type allows a single volume to be attached simultaneously to multiple instances within the same region, enabling increased resilience and high availability for critical applications.
11+
12+
This feature is designed specifically for active/active or active/passive use cases, where multiple instances need coordinated access to shared data.
13+
14+
To better understand the underlying architecture for multi-zone deployments using regional Block Storage, refer to the following [documentation](/pages/public_cloud/public_cloud_cross_functional/3az_ref_architecture#2az-with-regional-block-storage).
15+
16+
> [!warning]
17+
>
18+
> It is the user's responsibility to ensure that a cluster-aware file system is used with Classic Multi-Attach volumes.
19+
>
20+
> Failure to do so can result in data corruption.
21+
>
22+
> Use only file systems designed for shared access, such as GFS2 or OCFS2.
23+
>
24+
> Standard file systems (e.g., XFS, EXT4, NTFS) are not supported unless proper fencing mechanisms are in place.
25+
>
26+
27+
## Usage
28+
29+
Creating and attaching a Classic Multi-Attach volume follows the same process as described in the [OVHcloud documentation on volume creation](/pages/public_cloud/compute/starting_with_managing_volumes_openstack_api). The key difference is that the volume type is "classic-multiattach", not just "classic".
30+
31+
If the volume type is omitted during creation, OpenStack will default to "classic-multiattach" (similar to how "classic" is set by default in regular regions).
32+
33+
In the OVHcloud Control Panel, simply select the classic volume available in the 3AZ region.
34+
35+
![classic 3az block volume](images/create_volume_type.png){.thumbnail}
36+
37+
## Considerations
38+
39+
When working with Classic Multi-Attach in 3AZ regions, the following points should be taken into account:
40+
41+
- Classic 3AZ Multi-Attach volumes can be attached to up to 16 instances simultaneously within the same region.
42+
- The multi-attach feature is only available with this specific volume type and exclusively in 3AZ regions, such as the Paris region.
43+
- Using cluster-aware file systems is required, but may result in performance degradation depending on the workload and configuration.
44+
45+
## Limitations
46+
47+
Classic Multi-Attach volumes come with specific limitations that should be considered before deployment:
48+
49+
- Volume retyping is not supported while the volume is in use — switching from a multiattach-capable type to a non-multiattach-capable type (or vice-versa) is not allowed.
50+
- Encryption is not available for multiattach-capable volumes.
51+
52+
## Go further
53+
54+
Join our [community of users](/links/community).

‎pages/public_cloud/compute/classic_block_multi_az_limitations/guide.en-ca.md

Lines changed: 54 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,54 @@
1+
---
2+
title: Proper Usage and Limitations of Classic Multi-Attach Block Storage in 3AZ Regions
3+
excerpt: 'Learn how to safely use Classic Multi-Attach Block Storage in 3AZ regions, understand its limitations, and avoid data corruption'
4+
updated: 2025-05-06
5+
flag: hidden
6+
---
7+
8+
## Introduction
9+
10+
Classic Multi-Attach 3AZ is a regional multi-zone volume type, available exclusively in Public Cloud regions with three Availability Zones (3AZ). This volume type allows a single volume to be attached simultaneously to multiple instances within the same region, enabling increased resilience and high availability for critical applications.
11+
12+
This feature is designed specifically for active/active or active/passive use cases, where multiple instances need coordinated access to shared data.
13+
14+
To better understand the underlying architecture for multi-zone deployments using regional Block Storage, refer to the following [documentation](/pages/public_cloud/public_cloud_cross_functional/3az_ref_architecture#2az-with-regional-block-storage).
15+
16+
> [!warning]
17+
>
18+
> It is the user's responsibility to ensure that a cluster-aware file system is used with Classic Multi-Attach volumes.
19+
>
20+
> Failure to do so can result in data corruption.
21+
>
22+
> Use only file systems designed for shared access, such as GFS2 or OCFS2.
23+
>
24+
> Standard file systems (e.g., XFS, EXT4, NTFS) are not supported unless proper fencing mechanisms are in place.
25+
>
26+
27+
## Usage
28+
29+
Creating and attaching a Classic Multi-Attach volume follows the same process as described in the [OVHcloud documentation on volume creation](/pages/public_cloud/compute/starting_with_managing_volumes_openstack_api). The key difference is that the volume type is "classic-multiattach", not just "classic".
30+
31+
If the volume type is omitted during creation, OpenStack will default to "classic-multiattach" (similar to how "classic" is set by default in regular regions).
32+
33+
In the OVHcloud Control Panel, simply select the classic volume available in the 3AZ region.
34+
35+
![classic 3az block volume](images/create_volume_type.png){.thumbnail}
36+
37+
## Considerations
38+
39+
When working with Classic Multi-Attach in 3AZ regions, the following points should be taken into account:
40+
41+
- Classic 3AZ Multi-Attach volumes can be attached to up to 16 instances simultaneously within the same region.
42+
- The multi-attach feature is only available with this specific volume type and exclusively in 3AZ regions, such as the Paris region.
43+
- Using cluster-aware file systems is required, but may result in performance degradation depending on the workload and configuration.
44+
45+
## Limitations
46+
47+
Classic Multi-Attach volumes come with specific limitations that should be considered before deployment:
48+
49+
- Volume retyping is not supported while the volume is in use — switching from a multiattach-capable type to a non-multiattach-capable type (or vice-versa) is not allowed.
50+
- Encryption is not available for multiattach-capable volumes.
51+
52+
## Go further
53+
54+
Join our [community of users](/links/community).

‎pages/public_cloud/compute/classic_block_multi_az_limitations/guide.en-gb.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: Proper Usage and Limitations of Classic Multi-Attach Block Storage in 3AZ Regions
3-
excerpt: 'Learn how to safely use Classic Multi-Attach Block Storage in 3AZ regions, understand its limitations, and avoid data corruption.'
3+
excerpt: 'Learn how to safely use Classic Multi-Attach Block Storage in 3AZ regions, understand its limitations, and avoid data corruption'
44
updated: 2025-05-06
55
flag: hidden
66
---
@@ -26,11 +26,11 @@ To better understand the underlying architecture for multi-zone deployments usin
2626
2727
## Usage
2828

29-
Creating and attaching a Classic Multi-Attach volume follows the same process as described in [OVHcloud documentation on volume creation](/pages/public_cloud/compute/starting_with_managing_volumes_openstack_api). The key difference is that the volume type is "classic-multiattach", not just "classic".
29+
Creating and attaching a Classic Multi-Attach volume follows the same process as described in the [OVHcloud documentation on volume creation](/pages/public_cloud/compute/starting_with_managing_volumes_openstack_api). The key difference is that the volume type is "classic-multiattach", not just "classic".
3030

3131
If the volume type is omitted during creation, OpenStack will default to "classic-multiattach" (similar to how "classic" is set by default in regular regions).
3232

33-
In the OVHcloud Manager, simply select the classic volume available in the 3AZ region.
33+
In the OVHcloud Control Panel, simply select the classic volume available in the 3AZ region.
3434

3535
![classic 3az block volume](images/create_volume_type.png){.thumbnail}
3636

‎pages/public_cloud/compute/classic_block_multi_az_limitations/guide.en-ie.md

Lines changed: 54 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,54 @@
1+
---
2+
title: Proper Usage and Limitations of Classic Multi-Attach Block Storage in 3AZ Regions
3+
excerpt: 'Learn how to safely use Classic Multi-Attach Block Storage in 3AZ regions, understand its limitations, and avoid data corruption'
4+
updated: 2025-05-06
5+
flag: hidden
6+
---
7+
8+
## Introduction
9+
10+
Classic Multi-Attach 3AZ is a regional multi-zone volume type, available exclusively in Public Cloud regions with three Availability Zones (3AZ). This volume type allows a single volume to be attached simultaneously to multiple instances within the same region, enabling increased resilience and high availability for critical applications.
11+
12+
This feature is designed specifically for active/active or active/passive use cases, where multiple instances need coordinated access to shared data.
13+
14+
To better understand the underlying architecture for multi-zone deployments using regional Block Storage, refer to the following [documentation](/pages/public_cloud/public_cloud_cross_functional/3az_ref_architecture#2az-with-regional-block-storage).
15+
16+
> [!warning]
17+
>
18+
> It is the user's responsibility to ensure that a cluster-aware file system is used with Classic Multi-Attach volumes.
19+
>
20+
> Failure to do so can result in data corruption.
21+
>
22+
> Use only file systems designed for shared access, such as GFS2 or OCFS2.
23+
>
24+
> Standard file systems (e.g., XFS, EXT4, NTFS) are not supported unless proper fencing mechanisms are in place.
25+
>
26+
27+
## Usage
28+
29+
Creating and attaching a Classic Multi-Attach volume follows the same process as described in the [OVHcloud documentation on volume creation](/pages/public_cloud/compute/starting_with_managing_volumes_openstack_api). The key difference is that the volume type is "classic-multiattach", not just "classic".
30+
31+
If the volume type is omitted during creation, OpenStack will default to "classic-multiattach" (similar to how "classic" is set by default in regular regions).
32+
33+
In the OVHcloud Control Panel, simply select the classic volume available in the 3AZ region.
34+
35+
![classic 3az block volume](images/create_volume_type.png){.thumbnail}
36+
37+
## Considerations
38+
39+
When working with Classic Multi-Attach in 3AZ regions, the following points should be taken into account:
40+
41+
- Classic 3AZ Multi-Attach volumes can be attached to up to 16 instances simultaneously within the same region.
42+
- The multi-attach feature is only available with this specific volume type and exclusively in 3AZ regions, such as the Paris region.
43+
- Using cluster-aware file systems is required, but may result in performance degradation depending on the workload and configuration.
44+
45+
## Limitations
46+
47+
Classic Multi-Attach volumes come with specific limitations that should be considered before deployment:
48+
49+
- Volume retyping is not supported while the volume is in use — switching from a multiattach-capable type to a non-multiattach-capable type (or vice-versa) is not allowed.
50+
- Encryption is not available for multiattach-capable volumes.
51+
52+
## Go further
53+
54+
Join our [community of users](/links/community).

‎pages/public_cloud/compute/classic_block_multi_az_limitations/guide.en-sg.md

Lines changed: 54 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,54 @@
1+
---
2+
title: Proper Usage and Limitations of Classic Multi-Attach Block Storage in 3AZ Regions
3+
excerpt: 'Learn how to safely use Classic Multi-Attach Block Storage in 3AZ regions, understand its limitations, and avoid data corruption'
4+
updated: 2025-05-06
5+
flag: hidden
6+
---
7+
8+
## Introduction
9+
10+
Classic Multi-Attach 3AZ is a regional multi-zone volume type, available exclusively in Public Cloud regions with three Availability Zones (3AZ). This volume type allows a single volume to be attached simultaneously to multiple instances within the same region, enabling increased resilience and high availability for critical applications.
11+
12+
This feature is designed specifically for active/active or active/passive use cases, where multiple instances need coordinated access to shared data.
13+
14+
To better understand the underlying architecture for multi-zone deployments using regional Block Storage, refer to the following [documentation](/pages/public_cloud/public_cloud_cross_functional/3az_ref_architecture#2az-with-regional-block-storage).
15+
16+
> [!warning]
17+
>
18+
> It is the user's responsibility to ensure that a cluster-aware file system is used with Classic Multi-Attach volumes.
19+
>
20+
> Failure to do so can result in data corruption.
21+
>
22+
> Use only file systems designed for shared access, such as GFS2 or OCFS2.
23+
>
24+
> Standard file systems (e.g., XFS, EXT4, NTFS) are not supported unless proper fencing mechanisms are in place.
25+
>
26+
27+
## Usage
28+
29+
Creating and attaching a Classic Multi-Attach volume follows the same process as described in the [OVHcloud documentation on volume creation](/pages/public_cloud/compute/starting_with_managing_volumes_openstack_api). The key difference is that the volume type is "classic-multiattach", not just "classic".
30+
31+
If the volume type is omitted during creation, OpenStack will default to "classic-multiattach" (similar to how "classic" is set by default in regular regions).
32+
33+
In the OVHcloud Control Panel, simply select the classic volume available in the 3AZ region.
34+
35+
![classic 3az block volume](images/create_volume_type.png){.thumbnail}
36+
37+
## Considerations
38+
39+
When working with Classic Multi-Attach in 3AZ regions, the following points should be taken into account:
40+
41+
- Classic 3AZ Multi-Attach volumes can be attached to up to 16 instances simultaneously within the same region.
42+
- The multi-attach feature is only available with this specific volume type and exclusively in 3AZ regions, such as the Paris region.
43+
- Using cluster-aware file systems is required, but may result in performance degradation depending on the workload and configuration.
44+
45+
## Limitations
46+
47+
Classic Multi-Attach volumes come with specific limitations that should be considered before deployment:
48+
49+
- Volume retyping is not supported while the volume is in use — switching from a multiattach-capable type to a non-multiattach-capable type (or vice-versa) is not allowed.
50+
- Encryption is not available for multiattach-capable volumes.
51+
52+
## Go further
53+
54+
Join our [community of users](/links/community).

0 commit comments

Comments
 (0)