Skip to content

Commit 9bb4211

Browse files
committed
Update Azure file share information to reflect 4TiB limit
1 parent e332e79 commit 9bb4211

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/virtual-machines/workloads/oracle/oracle-database-backup-azure-storage.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -332,10 +332,10 @@ In this section, we will be using Oracle Recovery Manager (RMAN) to take a full
332332
RMAN> configure channel 2 device type disk format '/mnt/orabkup/%d/Full_%d_%U_%T_%s';
333333
```
334334

335-
2. Because Azure standard file shares have a maximum file size of 1 TiB, we will limit the size of RMAN backup pieces to 1 TiB. (Note that Premium File Shares have a maximum file size limit of 4 TiB. For more information, see [Azure Files Scalability and Performance Targets](../../../storage/files/storage-files-scale-targets.md).)
335+
2. Because Azure Standard and Premium file shares have a maximum file size of 4 TiB, we will limit the size of RMAN backup pieces to 4 TiB. (For more information, see [Azure Files Scalability and Performance Targets](../../../storage/files/storage-files-scale-targets.md).)
336336

337337
```bash
338-
RMAN> configure channel device type disk maxpiecesize 1000G;
338+
RMAN> configure channel device type disk maxpiecesize 4000G;
339339
```
340340

341341
3. Confirm the configuration change details:

0 commit comments

Comments
 (0)