Migration from a QNAP NAS to another newer QNAP NAS in a Windows Server 2008 Domain Environment

A client just purchased an upgrade to their existing 5 years old QNAP NAS Storage and they are interested in moving the existing NAS data from the old NAS to the new, and cutting over without (or with very-minimal downtime).

The Old NAS will then be converted to an offsite remote backup storage so that we can keep a copy of all their data in case the building gets burned down.

We will be employing the use of RSYNC and replicating data across WAN, most, probably through a PPTP VPN tunnel. Oh well, PPTP is not very secure, but it is still better than nothing, unless I can encrypt the RSYNC data before transferring it across WAN.

I'll be naming the NAS-es as NAS-1 (current) and NAS-2 (new). I have about 5-TB of data, and both NAS-es are joined to an Active Directory Domain (Windows Server 2008r2).

Overall Plan:

1. Set-up new NAS
2. Transfer data from current NAS to new NAS
3. rename current NAS to a new name (backup)
4. Set new NAS with current NAS name
5. Change DNS settings on server to ensure IP address is set correctly (or change IP of NAS too)
6. Users will then log-in to the new NAS as though they are connecting to the current NAS

Procedure:

1. Set-up new NAS2 in the network (disk, volume, network, name... etc)
2. Join the NAS2 to the same domain as NAS1, verify that the name of the NAS2 appears in Active Directory Users and Computers console
3. Create shared folders with the same name from the current NAS (file shares)
4. Configure Backup - Rsync on NAS1, from NAS1 >> NAS2
1. Ensure that delete extra files on remote destination is ticked.
2. Ensure that ACL is copied over to save time. ( i removed this because it doesn't work well. )
3. I did not configure the delete extra files on remote destination, the result was I had 0.3-TB of extra files on NAS2. Reconfiguration and re-sync took 11-hr for the entire data storage of 3.2-TB.
4. If you miss out option 1, the process of deleting the files that were already removed is quite fast in my case. For 12-GB of data, it took less than 1-min when NAS2 is not busy.
5. Let Rsync run and complete the transfer within the same network from NAS1 >> NAS2 for all of the network shared folders
6. Side project - we want to utilize dual LAN with Trunking for the data access to the NAS2, so we enabled IEEE 802.3ad on port 3 and 4, with a different set of IP address so that we can use that for faster access to the NAS2, while retaining the admin access using the address set in step-1.
7. I then re-configured the Rsync settings with the new IP address that has been configured with the trunk - 192.168.10.4
1. Not a significant difference in replicating speed because the NAS1 output is going through a single gigabit LAN connection.
8. ============== Not yet done ==================
9.  After sync is all completed and when I am ready to cut-over, now I proceed with disabling the Rsync from NAS1 >> NAS2 (to be safe, I'll recommend deleting the jobs)
10. Rename NAS1 to NAS1-BKP
11. Rename NAS2 to NAS1
12. Configure Rsync backup from NAS1 to NAS1-BKP the same steps taken in STEP-4 above.

 
Additional Notes:

• I wanted to test if changing NAS2 (new nas) name after joining to Windows AD will auto configure the name registered in the AD. Unfortunately, although the name change works, the name change did not register at AD.
• Unfortunately, I was required to re-join the NAS2 to the domain because I couldn't set user permissions for the shared folders based on my AD groups.
• I had to re-connect the NAS2 to the domain one more time, and then AD users and computers console displayed the newly renamed NAS2 to the domain. The old NAS2 name is still registered and had to be manually removed.
• then after i have re-joined the NAS to the domain, I proceed with deleting the NAS 2 prev name from the console.
• re-joining to the domain did not affect the network connection and my rSync seems to be working as per norm albeit the transfer time now extends to 2 days instead of the original 12-hours.
• Good news is that previously configured shared folder domain permissions will not be lost when the active directory connection is lost. (However, I did not restart NAS-2 after the change of name-before the rejoining. As such, I am not sure if a restart would possibly cause a shared folder permission reset if the shares are configured with domain permissions.)
• Re-configuring rsync from the NAS2 to NAS1 works flawlessly. There's no re-copying of files, only changed files are copied from NAS to NAS.