Solved

AFS Migration from Windows file server


Hi there,

I am new to Ntanix AFS(afs01) by which I would like to replace the existing window s file server(srv01).
AOS: v5.5.3.1 AFS: v2.2.2.1
All data and AD permission migrated to afs01 already. As all current users mapped drive by DNS srv01, Here is my plan to cut over:

1. Disconnect Windows srv01 from network
2. AFS afs01 leave AD
3. Rename AFS afs01 to srv01: https://portal.nutanix.com/#/page/docs/details?targetId=Acropolis-File-Services-Guide-v22:afs-file-server-rename-cluster-t.html
4. Join the AFS srv01 to AD again

by doing so, I hope all users don't need to map all the drives again The AFS top level share folders are the same as window file server.

Some more questions here about AFS I would like to ask:

1. After changing the name of AFS would all the related objects like Container, volume group FSVM and etc will change their name correspondingly?

2. Any way I would setup self service restore with specific time schedule(like everyday at 8AM, 12PM and 6PM) instead of regular time of intervals like every 4/6/12hours? would I restore a single file from data protection snapshot as well?

Any advice on the both steps and questions will be much appciated!!. Thanks!

Don
icon

Best answer by mmcghee 22 August 2018, 06:01

Hi @Don NG

The cutover steps make sense to me. I'd make sure dns records are cleared for srv01 and the AD entry is removed before renaming and adding the AFS server back using the same name.

The rename I believe is mainly for the file server name (the file server vms are renamed too) but will not change the container, VGs or protection domains. These don't need to be renamed to continue to function.

To my knowledge the SSR schedules are based on intervals and not time of day. You could try multiple hourly schedules with staggered snapshot times depending on your needs.

Protection domain snapshots require recovering the whole file server instance. The clone workflow will create a unique instance where you can grab the file(s) you need and then you can delete that instance. Everything is a thin (fast) clone, so it doesn't take up space to recover then delete.

Thanks,
Mike

View original

3 replies

Userlevel 4
Badge +18
Hi @Don NG

The cutover steps make sense to me. I'd make sure dns records are cleared for srv01 and the AD entry is removed before renaming and adding the AFS server back using the same name.

The rename I believe is mainly for the file server name (the file server vms are renamed too) but will not change the container, VGs or protection domains. These don't need to be renamed to continue to function.

To my knowledge the SSR schedules are based on intervals and not time of day. You could try multiple hourly schedules with staggered snapshot times depending on your needs.

Protection domain snapshots require recovering the whole file server instance. The clone workflow will create a unique instance where you can grab the file(s) you need and then you can delete that instance. Everything is a thin (fast) clone, so it doesn't take up space to recover then delete.

Thanks,
Mike
Thanks mmcghee,

For The cut over, after leave and rejoining the AD, will all the AD permission lost fro all AFS shares?

For the Name of container, Volume group, they will stay as Nutanix_afs01_ctr and NTNX-afs01-XXXX and also the protection domain after renaming of AFS?

Don
No permissions are applied to the files and don't disappear when a system is removed from the domain at most you will see invalid SIDs when the afs is being renamed.

Reply