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
title: Configure NFSv4.1 default domain for Azure NetApp Files | Microsoft Docs
3
+
description: Describes how to configure the NFS client for using NFSv4.1 with Azure NetApp Files.
4
+
documentationcenter: ''
5
+
author: b-juche
6
+
manager: ''
7
+
editor: ''
8
+
9
+
ms.assetid:
10
+
ms.service: azure-netapp-files
11
+
ms.workload: storage
12
+
ms.tgt_pltfrm: na
13
+
ms.devlang: na
14
+
ms.topic: conceptual
15
+
ms.date: 11/08/2019
16
+
ms.author: b-juche
17
+
---
18
+
# Configure NFSv4.1 default domain for Azure NetApp Files
19
+
20
+
NFSv4 introduces the concept of an authentication domain. Azure NetApp Files currently supports root-only user mapping from the service to the NFS client. To use the NFSv4.1 functionality with Azure NetApp Files, you need to update the NFS client.
21
+
22
+
## Default behavior of user/group mapping
23
+
24
+
Root mapping defaults to the `nobody` user because the NFSv4 domain is set to `localdomain`. When you mount an Azure NetApp Files NFSv4.1 volume as root, you will see file permissions as follows:
25
+
26
+
27
+
28
+
As the above example shows, the user for `file1` should be `root`, but it maps to `nobody` by default. This article shows you how to set the `file1` user to `root`.
29
+
30
+
## Steps
31
+
32
+
1. Edit the `/etc/idmapd.conf` file on the NFS client.
33
+
Uncomment the line `#Domain` (that is, remove the `#` from the line), and change the value `localdomain` to `defaultv4iddomain.com`.
34
+
35
+
Initial configuration:
36
+
37
+
38
+
39
+
Updated configuration:
40
+
41
+
42
+
43
+
2. Unmount any currently mounted NFS volumes.
44
+
3. Update the `/etc/idmapd.conf` file.
45
+
4. Restart the `rpcbind` service on your host (`service rpcbind restart`), or simply reboot the host.
46
+
5. Mount the NFS volumes as required.
47
+
48
+
See [Mount or unmount a volume for Windows or Linux virtual machines](azure-netapp-files-mount-unmount-volumes-for-virtual-machines.md).
49
+
50
+
The following example shows the resulting user/group change:
51
+
52
+
53
+
54
+
As the example shows, the user/group has now changed from `nobody` to `root`.
55
+
56
+
## Behavior of other (non-root) users and groups
57
+
58
+
Azure NetApp Files supports local users (users created locally on a host) who have permissions associated with files or folders in NFSv4.1 volumes. However, the service does not currently support mapping the users/groups across multiple nodes. Therefore, users created on one host do not map by default to users created on another host.
59
+
60
+
In the following example, `Host1` has three existing test user accounts (`testuser01`, `testuser02`, `testuser03`):
61
+
62
+
63
+
64
+
On `Host2`, note that the test user accounts have not been created, but the same volume is mounted on both hosts:
65
+
66
+
67
+
68
+
## Next step
69
+
70
+
[Mount or unmount a volume for Windows or Linux virtual machines](azure-netapp-files-mount-unmount-volumes-for-virtual-machines.md)
Copy file name to clipboardExpand all lines: articles/azure-netapp-files/azure-netapp-files-create-volumes.md
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@ ms.workload: storage
13
13
ms.tgt_pltfrm: na
14
14
ms.devlang: na
15
15
ms.topic: conceptual
16
-
ms.date: 10/12/2019
16
+
ms.date: 11/08/2019
17
17
ms.author: b-juche
18
18
---
19
19
# Create an NFS volume for Azure NetApp Files
@@ -38,7 +38,7 @@ A subnet must be delegated to Azure NetApp Files.
38
38
Support for UNIX mode bits (read, write, and execute) is available for NFSv3 and NFSv4.1. Root-level access is required on the NFS client to mount NFS volumes.
39
39
40
40
* Local user/group and LDAP support for NFSv4.1
41
-
Currently, NFSv4.1 supports root access to volumes only.
41
+
Currently, NFSv4.1 supports root access to volumes only. See [Configure NFSv4.1 default domain for Azure NetApp Files](azure-netapp-files-configure-nfsv41-domain.md).
42
42
43
43
## Best practice
44
44
@@ -110,6 +110,7 @@ A subnet must be delegated to Azure NetApp Files.
110
110
111
111
## Next steps
112
112
113
+
*[Configure NFSv4.1 default domain for Azure NetApp Files](azure-netapp-files-configure-nfsv41-domain.md)
113
114
*[Mount or unmount a volume for Windows or Linux virtual machines](azure-netapp-files-mount-unmount-volumes-for-virtual-machines.md)
114
115
*[Configure export policy for an NFS volume](azure-netapp-files-configure-export-policy.md)
115
116
*[Resource limits for Azure NetApp Files](azure-netapp-files-resource-limits.md)
Copy file name to clipboardExpand all lines: articles/azure-netapp-files/azure-netapp-files-solution-architectures.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@ ms.workload: storage
13
13
ms.tgt_pltfrm: na
14
14
ms.devlang: na
15
15
ms.topic: conceptual
16
-
ms.date: 08/26/2019
16
+
ms.date: 11/08/2019
17
17
ms.author: b-juche
18
18
---
19
19
# Solution architectures using Azure NetApp Files
@@ -34,6 +34,7 @@ This article provides references to best practices that can help you understand
34
34
*[High availability for SAP NetWeaver on Azure VMs on SUSE Linux Enterprise Server with Azure NetApp Files for SAP applications](https://docs.microsoft.com/azure/virtual-machines/workloads/sap/high-availability-guide-suse-netapp-files)
35
35
*[Azure Virtual Machines high availability for SAP NetWeaver on Red Hat Enterprise Linux with Azure NetApp Files for SAP applications](https://docs.microsoft.com/azure/virtual-machines/workloads/sap/high-availability-guide-rhel-netapp-files)
36
36
*[SAP HANA scale-out with standby node on Azure VMs with Azure NetApp Files on SUSE Linux Enterprise Server](https://docs.microsoft.com/azure/virtual-machines/workloads/sap/sap-hana-scale-out-standby-netapp-files-suse)
37
+
*[SAP HANA Azure virtual machine storage configurations](https://docs.microsoft.com/azure/virtual-machines/workloads/sap/hana-vm-operations-storage)
Copy file name to clipboardExpand all lines: articles/backup/backup-azure-afs-automation.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -271,7 +271,7 @@ Azure file share snapshots are used while the backups are taken, so usually the
271
271
272
272
### Using on-demand backups to extend retention
273
273
274
-
On-demand backups can be used to retain your snapshots for 10 years. Schedulers can be used to run on-demand PowerShell scripts with chosen retention and thus take snapshots at regular intervals every week, month, or year. While taking regular snapshots refer to the [limitations of on-demand backups](https://docs.microsoft.com/azure/backup/backup-azure-files-faq#how-many-on-demand-backups-can-i-take-per-file-share-) using Azure backup.
274
+
On-demand backups can be used to retain your snapshots for 10 years. Schedulers can be used to run on-demand PowerShell scripts with chosen retention and thus take snapshots at regular intervals every week, month, or year. While taking regular snapshots, refer to the [limitations of on-demand backups](https://docs.microsoft.com/azure/backup/backup-azure-files-faq#how-many-on-demand-backups-can-i-take-per-file-share) using Azure backup.
275
275
276
276
If you are looking for sample scripts, you can refer to the sample script on GitHub (<https://github.com/Azure-Samples/Use-PowerShell-for-long-term-retention-of-Azure-Files-Backup)> using Azure Automation runbook that enables you to schedule backups on a periodic basis and retain them even up to 10 years.
Copy file name to clipboardExpand all lines: articles/backup/backup-azure-arm-userestapi-backupazurevms.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -163,7 +163,7 @@ In the example, the above values translate to:
163
163
164
164
### Enabling protection for the Azure VM
165
165
166
-
After the relevant VM is "cached" and "identified", select the policy to protect. To know more about existing policies in the vault, refer to [list Policy API](https://docs.microsoft.com/rest/api/backup/backuppolicies/list). Then select the [relevant policy](https://docs.microsoft.com/rest/api/backup/protectionpolicies/get) by referring to the policy name. To create policies, refer to [create policy tutorial](backup-azure-arm-userestapi-createorupdatepolicy.md). "DefaultPolicy" is selected in the below example.
166
+
After the relevant VM is "cached" and "identified", select the policy to protect. To know more about existing policies in the vault, refer to [list Policy API](https://docs.microsoft.com/rest/api/backup/backuppolicies/list). Then select the [relevant policy](https://docs.microsoft.com/rest/api/backup/protectionpolicies(2019-05-13)/get) by referring to the policy name. To create policies, refer to [create policy tutorial](backup-azure-arm-userestapi-createorupdatepolicy.md). "DefaultPolicy" is selected in the below example.
167
167
168
168
Enabling protection is an asynchronous *PUT* operation that creates a 'protected item'.
6. In the **certs** folder, right-click the root certificate file > **Rename**.
67
66
@@ -77,7 +76,7 @@ Set up a secure channel as follows:
77
76
78
77
10. On the **Certificate Store** page, select **Place all certificates in the following store**, and then click **Browse** to choose the certificate store.
11. In **Select Certificate Store**, select **Trusted Root Certification Authorities** as the destination folder for the certificates, and then click **OK**.
83
82
@@ -95,11 +94,11 @@ If you have secure boundaries within your organization, and don't want to use th
95
94
96
95
1. Copy and paste the following text into a .txt file.
97
96
98
-
```text
97
+
```text
99
98
Windows Registry Editor Version 5.00
100
99
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Data Protection Manager\VMWare]
101
100
"IgnoreCertificateValidation"=dword:00000001
102
-
```
101
+
```
103
102
104
103
2. Save the file on the Azure Backup Server machine with the name **DisableSecureAuthentication.reg**.
105
104
@@ -125,7 +124,7 @@ The Azure Backup Server needs a user account with permissions to access v-Center
125
124
- To select the VirtualMachine privileges, you need to go several levels into the parent child hierarchy.
126
125
- You don't need to select all child privileges within a parent privilege.
2. In the **vCenter Users and Groups** panel, select the **Users** tab, and then click the add users icon (the + symbol).
162
161
163
-
162
+
164
163
165
164
3. In **New User** dialog box, add the user information > **OK**. In this procedure, the username is BackupAdmin.
166
165
@@ -216,7 +215,7 @@ Add the vCenter Server to Azure Backup Server.
216
215
217
216
2. In **Production Server Addition Wizard** > **Select Production Server type** page, select **VMware Servers**, and then click **Next**.
218
217
219
-
218
+
220
219
221
220
3. In **Select Computers****Server Name/IP Address**, specify the FQDN or IP address of the VMware server. If all the ESXi servers are managed by the same vCenter, specify the vCenter name. Otherwise, add the ESXi host.
222
221
@@ -261,7 +260,7 @@ Add VMware VMs for backup. Protection groups gather multiple VMs and apply the s
261
260
- When you select a folder, or VMs or folders inside that folder are also selected for backup. You can uncheck folders or VMs you don't want to back up.
262
261
1. If a VM or folder is already being backed up, you can't select it. This ensures that duplicate recovery points aren't created for a VM.
263
262
264
-
263
+
265
264
266
265
1. In **Select Data Protection Method** page, enter a name for the protection group, and protection settings. To back up to Azure, set short-term protection to **Disk** and enable online protection. Then click **Next**.
267
266
@@ -285,40 +284,40 @@ Add VMware VMs for backup. Protection groups gather multiple VMs and apply the s
285
284
-**Automatically grow:** If you turn on this setting, if data in the protected group outgrows the initial allocation, Azure Backup Server tries to increase the disk size by 25 percent.
286
285
-**Storage pool details:** Shows the status of the storage pool, including total and remaining disk size.
287
286
288
-
287
+
289
288
290
289
1. In **Choose Replica Creation Method** page, specify how you want to take the initial backup, and then click **Next**.
291
290
- The default is **Automatically over the network** and **Now**.
292
291
- If you use the default, we recommend that you specify an off-peak time. Choose **Later** and specify a day and time.
293
292
- For large amounts of data or less-than-optimal network conditions, consider replicating the data offline by using removable media.
1. In **Consistency Check Options**, select how and when to automate the consistency checks. Then click **Next**.
298
297
- You can run consistency checks when replica data becomes inconsistent, or on a set schedule.
299
298
- If you don't want to configure automatic consistency checks, you can run a manual check. To do this, right-click the protection group > **Perform Consistency Check**.
300
299
301
300
1. In **Specify Online Protection Data** page, select the VMs or VM folders that you want to back up. You can select the members individually, or click **Select All** to choose all members. Then click **Next**.
1. On the **Specify Online Retention Policy** page, indicate how long you want to keep the recovery points that are created from the daily/weekly/monthly/yearly backups to Azure. then click **Next**.
313
312
314
313
- There's no time limit for how long you can keep data in Azure.
315
314
- The only limit is that you can't have more than 9999 recovery points per protected instance. In this example, the protected instance is the VMware server.
0 commit comments