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/virtual-machines/workloads/oracle/oracle-database-backup-azure-storage.md
+12-12Lines changed: 12 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,7 @@ ms.reviewer: dbakevlar
16
16
17
17
**Applies to:**:heavy_check_mark: Linux VMs
18
18
19
-
This article demonstrates the use of Azure Files as a media to back up and restore an Oracle database running on an Azure VM. The steps in this article have been tested against Oracle 12.1 and higher. You will back up the database using Oracle RMAN to an Azure file share mounted to the VM using the SMB protocol. Using Azure Files for backup media is extremely cost effective and performant. However, for very large databases, Azure Backup provides a better solution.
19
+
This article demonstrates the use of Azure Files as a media to back up and restore an Oracle database running on an Azure VM. The steps in this article have been tested against Oracle 12.1 and higher. You'll back up the database using Oracle RMAN to an Azure file share mounted to the VM using the SMB protocol. Using Azure Files for backup media is extremely cost effective and performant. However, for very large databases, Azure Backup provides a better solution.
@@ -64,10 +64,10 @@ This article demonstrates the use of Azure Files as a media to back up and resto
64
64
echo"export ORACLE_SID=test">>~oracle/.bashrc
65
65
```
66
66
67
-
6. Start the Oracle listener if it is not already running:
67
+
6. Start the Oracle listener if it isn't already running:
68
68
69
69
```bash
70
-
$ lsnrctl start
70
+
lsnrctl start
71
71
```
72
72
73
73
The output should look similar to the following example:
@@ -116,7 +116,7 @@ This article demonstrates the use of Azure Files as a media to back up and resto
116
116
sqlplus / as sysdba
117
117
```
118
118
119
-
9. Start the database if it is not already running:
119
+
9. Start the database if it isn't already running:
120
120
121
121
```bash
122
122
SQL> startup
@@ -168,14 +168,14 @@ To back up to Azure Files, complete these steps:
168
168
169
169
1. [Set up Azure Files](#set-up-azure-files).
170
170
1. [Mount the Azure file share to your VM](#mount-the-azure-storage-file-share-to-your-vm).
171
-
1. [Back up the database](#backup-the-database).
171
+
1. [Back up the database](#back-up-the-database).
172
172
1. [Restore and recover the database](#restore-and-recover-the-database).
173
173
174
174
### Set up Azure Files
175
175
176
-
In this step, you will back up the Oracle database using Oracle Recovery Manager (RMAN) to Azure Files. Azure file shares are fully managed file shares that live in the cloud. They can be accessed using either the Server Message Block (SMB) protocol or the Network File System (NFS) protocol. This step covers creating a file share that uses the SMB protocol to mount to your VM. For information about how to mount using NFS, see [How to create an NFS share](../../../storage/files/storage-files-how-to-create-nfs-shares.md).
176
+
In this step, you'll back up the Oracle database using Oracle Recovery Manager (RMAN) to Azure Files. Azure file shares are fully managed file shares that live in the cloud. They can be accessed using either the Server Message Block (SMB) protocol or the Network File System (NFS) protocol. This step covers creating a file share that uses the SMB protocol to mount to your VM. For information about how to mount using NFS, see [How to create an NFS share](../../../storage/files/storage-files-how-to-create-nfs-shares.md).
177
177
178
-
When mounting the Azure Files, we will use the `cache=none` to disable caching of file share data. And to ensure files created in the share are owned by the oracle user set the `uid=oracle` and `gid=oinstall` options as well.
178
+
When mounting the Azure Files, we'll use the `cache=none` to disable caching of file share data. And to ensure files created in the share are owned by the oracle user set the `uid=oracle` and `gid=oinstall` options as well.
179
179
180
180
# [Portal](#tab/azure-portal)
181
181
@@ -197,7 +197,7 @@ First, set up your storage account.
197
197
198
198

199
199
200
-
5. Click on ***+ File share*** and in the ***New file share*** blade name your file share ***orabkup1***. Set ***Quota*** to ***10240*** GiB and check ***Transaction optimized*** as the tier. The quota reflects an upper boundary that the file share can grow to. As we are using Standard storage, resources are PAYG and not provisioned so setting it to 10 TiB will not incur costs beyond what you use. If your backup strategy requires more storage, you must set the quota to an appropriate level to hold all backups. When you have completed the New file share blade, click ***Create***.
200
+
5. Click on ***+ File share*** and in the ***New file share*** blade name your file share ***orabkup1***. Set ***Quota*** to ***10240*** GiB and check ***Transaction optimized*** as the tier. The quota reflects an upper boundary that the file share can grow to. As we're using Standard storage, resources are PAYG and not provisioned so setting it to 10 TiB will not incur costs beyond what you use. If your backup strategy requires more storage, you must set the quota to an appropriate level to hold all backups. When you have completed the New file share blade, click ***Create***.
201
201
202
202

203
203
@@ -319,20 +319,20 @@ To set up your storage account and file share run the following commands in Azur
In this section, we will be using Oracle Recovery Manager (RMAN) to take a full backup of the database and archive logs and write the backup as a backup set to the Azure File share mounted earlier.
324
+
In this section, we'll be using Oracle Recovery Manager (RMAN) to take a full backup of the database and archive logs and write the backup as a backup set to the Azure File share mounted earlier.
325
325
326
326
1. Configure RMAN to back up to the Azure Files mount point:
327
327
328
328
```bash
329
-
$ rman target /
329
+
rman target /
330
330
RMAN> configure snapshot controlfile name to '/mnt/orabkup/snapcf_ev.f';
331
331
RMAN> configure channel 1 device type disk format '/mnt/orabkup/%d/Full_%d_%U_%T_%s';
332
332
RMAN> configure channel 2 device type disk format '/mnt/orabkup/%d/Full_%d_%U_%T_%s';
333
333
```
334
334
335
-
2. In this example, we are limiting the size of RMAN backup pieces to 1 TiB. Please note the RMAN backup MAXPIECESIZE can go upto 4TiB as Azure standard file shares and 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. In this example, we're limiting the size of RMAN backup pieces to 1 TiB. Please note the RMAN backup MAXPIECESIZE can go upto 4TiB as Azure standard file shares and 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).)
336
336
337
337
```bash
338
338
RMAN> configure channel device type disk maxpiecesize 4000G;
0 commit comments