Qtree SnapMirror (QSM)
- Logical replication
- Independent of the type of volume
- Source volume and qtree are online/writable
- Destination volume is online/writable
Requirements and Limitations for QSM
- Supports Async mode only
- Destination volume must have 5% extra space
- Destination qtree cannot be /etc name
- Cannot be initialized using a tape device
- Does not support cascading of mirrors
- Deep directory structure and large number of small files may impact performance
Migration task :
- Here iam going to copy one cifs shares from source filer to destination filler
- after migration user want to access his shares from destination filer
- so we need to do some changes on source and destination
- In destination side we need to configure cifs setup and others stuff
Other information:
share name : yogesh
username : yogesh
source> wrfile -a \etc\hosts 192.168.1.3 destination
source> ping 192.168.1.3
source> ping destination
source> license add ******* => license no
source> options snapmirror.enable on
source> options snapmirror.access host=destination
source> wrfile -a snapmirror.allow
192.168.1.3 # destination filer ip
destination # secondary filer name
Press CTRL-C to save and exit from the file
source> cifs shares
Name Mount Point Description ---- ----------- ----------- ETC$ /etc Remote Administration BUILTIN\Administrators / Full Control HOME /vol/vol0/home Default Share everyone / Full Control C$ / Remote Administration BUILTIN\Administrators / Full Control qtree /vol/vol1/qtree everyone / Full Control
Blue color are some input for cifs setup.
This is after installation
Note : As of now we copied the data from source filer to destination filer.
Now we need to load the qtree path in /etc/cifs_homedir_cfg.
source> ping destination
source> license add ******* => license no
source> options snapmirror.enable on
source> options snapmirror.access host=destination
source> wrfile -a snapmirror.allow
192.168.1.3 # destination filer ip
destination # secondary filer name
Press CTRL-C to save and exit from the file
source> cifs shares
Name Mount Point Description ---- ----------- ----------- ETC$ /etc Remote Administration BUILTIN\Administrators / Full Control HOME /vol/vol0/home Default Share everyone / Full Control C$ / Remote Administration BUILTIN\Administrators / Full Control qtree /vol/vol1/qtree everyone / Full Control
Switch to Destination Filer for Pre-Check
1. check the filler panic error
# Commands
> check_netapp.pl Hardware -H <hostname|IP> -u -o <temp|cool|power|nvram|disk>
> disk show -v
> disk show -v
2. check rlm/sp is working properly
3. check all the disks are added properly
destination> aggr create aggr1 20
destination> aggr status
destination> vol create vol1 aggr1 1g
destination> vol status
destination> wrfile -a \etc\hosts 192.168.1.2 source
destination> ping 192.168.1.2
destination> ping source
destination> cifs shares -add vol_qtree /vol/vol1/
destination> cifs shares # to check shares
destination> aggr status
destination> vol create vol1 aggr1 1g
destination> vol status
destination> wrfile -a \etc\hosts 192.168.1.2 source
destination> ping 192.168.1.2
destination> ping source
destination> cifs shares -add vol_qtree /vol/vol1/
destination> cifs shares # to check shares
destination > license add ******* => license no
destination> options snapmirror.enable on
destination> options snapmirror.access host=source
destination> wrfile -a snapmirror.allow
192.168.1.2 # source filer ip
source # source filer name
Press CTRL-C to exit and save the file
source> cifs shares
Name Mount Point Description ---- ----------- ----------- ETC$ /etc Remote Administration BUILTIN\Administrators / Full Control HOME /vol/vol0/home Default Share everyone / Full Control C$ / Remote Administration BUILTIN\Administrators / Full Control
vol1 /vol/vol1 everyone / Full Control
dst> vol restrict vol1 # please restrict qtree container volume.
CIFS Setup: we can setup cifs while ontap installation or after installation.
destination> options snapmirror.access host=source
destination> wrfile -a snapmirror.allow
192.168.1.2 # source filer ip
source # source filer name
Press CTRL-C to exit and save the file
source> cifs shares
Name Mount Point Description ---- ----------- ----------- ETC$ /etc Remote Administration BUILTIN\Administrators / Full Control HOME /vol/vol0/home Default Share everyone / Full Control C$ / Remote Administration BUILTIN\Administrators / Full Control
vol1 /vol/vol1 everyone / Full Control
dst> vol restrict vol1 # please restrict qtree container volume.
CIFS Setup: we can setup cifs while ontap installation or after installation.
Blue color are some input for cifs setup.
This is after installation
destination > cifs setup
This process will enable CIFS access to the filer from a Windows(R) system.
Use "?" for help at any prompt and Ctrl-C to exit without committing changes.
Your filer does not have WINS configured and is visible only to
clients on the same subnet.
Do you want to make the system visible via WINS? [n]:
A filer can be configured for multiprotocol access, or as an NTFS-only
filer. Since multiple protocols are currently licensed on this filer,
we recommend that you configure this filer as a multiprotocol filer
(1) Multiprotocol filer
(2) NTFS-only filer
Selection (1-2)? [1]: 1
IFS requires local /etc/passwd and /etc/group files and default files will be created. The default passwd file contains entries for 'root', 'pcuser', and 'nobody'. Enter the password for the root user []:****** Retype the password:*******
The default name for this CIFS server is 'NETAPP'. Would you like to change this name? [n]:
ata ONTAP CIFS services support four styles of user authentication. Choose the one from the list below that best suits your situation. (1) Active Directory domain authentication (Active Directory domains only) (2) Windows NT 4 domain authentication (Windows NT or Active Directory domains) (3) Windows Workgroup authentication using the filer's local user accounts (4) /etc/passwd and/or NIS/LDAP authentication Selection (1-4)? [1]:1
In order to operate correctly within an Active Directory-based Windows domain, CIFS must use the DNS resolver service. That service is currently not configured on the filer. You must either configure DNS resolver services or choose a different authentication style. Do you want to configure the filer's DNS resolver service? [y]: What is the filer's DNS domain name? []: netapp.com # windows domain name What are the IPv4/IPv6 address(es) of your authoritative DNS name server(s)? : 192.168.1.4 # windows ip address Would you like to specify additional DNS name servers? [n]:n What is the name of the Active Directory domain? [netapp.com]:y
In Active Directory-based domains, it is essential that the filer's time match the domain's internal time so that the Kerberos-based authentication system works correctly. If the time difference between the filer and the domain controllers is more than 5 minutes, authentication will fail. Time services are currently not configured on this filer. Would you like to configure time services? [y]:n
In order to create an Active Directory machine account for the filer, you must supply the name and password of a Windows account with sufficient privileges to add computers to the netapp.COM domain. Enter the name of the Windows user [Administrator@netapp.COM]:administrator Password for administrator: CIFS - Logged in as administrator@netapp.COM. The user that you specified has permission to create the filer's machine account in several (2) containers. Please choose where you would like this account to be created. (1) CN=computers (2) OU=Domain Controllers (3) None of the above Selection (1-3)? [1]:1
IFS - Starting SMB protocol... Sun May 19 19:01:25 GMT [netapp:passwd.changed:info]: passwd for user 'root' changed. It is highly recommended that you create the local administrator account (NETAPP\administrator) for this filer. This account allows access to CIFS from Windows when domain controllers are not accessible. Do you want to create the NETAPP\administrator account? [y]:y Enter the new password for NETAPP\administrator: ******
Retype the password: ******
"NETAPP\administrator"
Welcome to the netapp.COM (CORP) Active Directory(R) domain.
IFS requires local /etc/passwd and /etc/group files and default files will be created. The default passwd file contains entries for 'root', 'pcuser', and 'nobody'. Enter the password for the root user []:****** Retype the password:*******
The default name for this CIFS server is 'NETAPP'. Would you like to change this name? [n]:
ata ONTAP CIFS services support four styles of user authentication. Choose the one from the list below that best suits your situation. (1) Active Directory domain authentication (Active Directory domains only) (2) Windows NT 4 domain authentication (Windows NT or Active Directory domains) (3) Windows Workgroup authentication using the filer's local user accounts (4) /etc/passwd and/or NIS/LDAP authentication Selection (1-4)? [1]:1
In order to operate correctly within an Active Directory-based Windows domain, CIFS must use the DNS resolver service. That service is currently not configured on the filer. You must either configure DNS resolver services or choose a different authentication style. Do you want to configure the filer's DNS resolver service? [y]: What is the filer's DNS domain name? []: netapp.com # windows domain name What are the IPv4/IPv6 address(es) of your authoritative DNS name server(s)? : 192.168.1.4 # windows ip address Would you like to specify additional DNS name servers? [n]:n What is the name of the Active Directory domain? [netapp.com]:y
In Active Directory-based domains, it is essential that the filer's time match the domain's internal time so that the Kerberos-based authentication system works correctly. If the time difference between the filer and the domain controllers is more than 5 minutes, authentication will fail. Time services are currently not configured on this filer. Would you like to configure time services? [y]:n
In order to create an Active Directory machine account for the filer, you must supply the name and password of a Windows account with sufficient privileges to add computers to the netapp.COM domain. Enter the name of the Windows user [Administrator@netapp.COM]:administrator Password for administrator: CIFS - Logged in as administrator@netapp.COM. The user that you specified has permission to create the filer's machine account in several (2) containers. Please choose where you would like this account to be created. (1) CN=computers (2) OU=Domain Controllers (3) None of the above Selection (1-3)? [1]:1
IFS - Starting SMB protocol... Sun May 19 19:01:25 GMT [netapp:passwd.changed:info]: passwd for user 'root' changed. It is highly recommended that you create the local administrator account (NETAPP\administrator) for this filer. This account allows access to CIFS from Windows when domain controllers are not accessible. Do you want to create the NETAPP\administrator account? [y]:y Enter the new password for NETAPP\administrator: ******
Retype the password: ******
"NETAPP\administrator"
Welcome to the netapp.COM (CORP) Active Directory(R) domain.
CIFS local server is running.
********************************************************I************
destination > ping windows_ip
destination> snapmirror initialize -S source:/vol/vol1/qtree destination:/vol/vol1/qtree
destination >
destination > snapmirror status -l vol1
destination > ping windows_ip
destination> snapmirror initialize -S source:/vol/vol1/qtree destination:/vol/vol1/qtree
destination >
destination > snapmirror status -l vol1
Snapmirror is on.
Source: source:vol1 Destination: destination:vol1
Status: Transferring
Progress: 24 KB
Compression Ratio: 4.5 : 1
State: - Lag: - Mirror
Timestamp: - Base Snapshot: -
Current Transfer Type: Initialize
Current Transfer Error: -
Contents: -
Last Transfer Type: Initialize
Last Transfer Size: 132 MB
Last Transfer Duration: 00:00:32
Last Transfer From: source:vol1
destination > snapmirror update destination:/vol/vol1/qtree
destination >
destination > snapmirror status
Snapmirror is on.
Source Destination State Lag Status
source:/vol/vol1/qtree destination:/vol/vol1/qtree Snapmirrored 00:02:33 Idle
Note: Now both src and dst filer should have same size and files.
destination > snapmirror quiesce /vol/vol1/qtree #its file-level so we should quiesce before break
destination > snapmirror break /vol/vol1/qtree # check now dst volume should be read-write
destination > snapmirror migrate source:/vol/vol1/qtree destination:/vol/vol1/qtree
destination > snapmirror update destination:/vol/vol1/qtree
destination >
destination > snapmirror status
Snapmirror is on.
Source Destination State Lag Status
source:/vol/vol1/qtree destination:/vol/vol1/qtree Snapmirrored 00:02:33 Idle
Note: Now both src and dst filer should have same size and files.
destination > snapmirror quiesce /vol/vol1/qtree #its file-level so we should quiesce before break
destination > snapmirror break /vol/vol1/qtree # check now dst volume should be read-write
destination > snapmirror migrate source:/vol/vol1/qtree destination:/vol/vol1/qtree
Note : As of now we copied the data from source filer to destination filer.
Now we need to load the qtree path in /etc/cifs_homedir_cfg.
destination > wrfile -a /etc/cifs_homedir.cfg /vol/vol1/qtree
destination > cifs homedir load -f
destination > cifs homedir showuser yogesh
Note : delete the old share and recreate the new cifs share for destination qtree.
source > cifs shares -delete qtree # delete the old qtree share
destination> cifs shares -add qtree /vol/vol1/qtree # create new share in new filer
*********************************************************************************
Then go windows user profile properties and change old filer name to new filer name or if you using
DFS software please update for the same
Please write your valuable comments, about my blogspot.
Thanks yaar...
ReplyDelete