### Human: Can you tell about Nutanix Files - Steps to convert Non Distributed Share to a Distributed Share. ### Assistant: The following article provides the steps necessary to convert a share from a standard share to a distributed share.. This article applies to Nutanix Files 4.0.2 and later.

Beginning in Nutanix Files 4.0.2, a feature was introduced to support converting a file share from one type of share to another. In this initial release, the workflow supported is converting from a standard share to a distributed share. 

Note: this article is intended to be walked through by Support with a customer to validate whether the share to be converted is a good candidate and the steps to kick off the share conversion.

What is supported? 

From Standard to Distributed Shares (One-way conversion). CLI-based processes (start, stop, pause, resume, abort, cut-over).Max 50M files and 2000 TLDs in the share to be converted.Only a single conversion can be run at once. 

Note: Converting a standard (general) share to a distributed (home) share has a known limitation where the Share level attributes are not applied on the target (distributed) share. The share attributes will need to be re-applied again at the share level i.e. at the root of the target share.

What is not supported?

Conversion via UI.Files at the root of the source standard share. Windows hidden or system files at the root of the standard share may prevent the share conversion. To see these files from the Windows client, please make sure to select "Show hidden files, folders, or drives" and uncheck "Hide protected operating system files (Recommended)" under the View tab of Windows Explorer Folder Options.Distributed shares to Standard shares (future roadmap).Shares with Smart Tiering or Smart DR policies.Multiple active share conversions (1 active conversion at a time).DoDIN APL ConfigurationsChanging the amount of storage allocated to Files is prohibited whilst a conversion process is running. 

What guardrails are in place?

Share Attributes

	Must manually set the following post-conversion: SSR, File Blocking, and Quotas.Antivirus applied post-conversion cutover.
	File Server updates such as re-IP, Node Add, and Node delete are allowed.VG Move tasks cannot be initiated during conversion.TLDs created during conversion are limited to 2,000.Smart DR or Tiering. If enabled, the shares cannot be converted.There is, as of yet, no guardrail for storage space used by Files. Make sure there's enough free space to replicate the share you're converting. . Note:

All commands will be run on the File Server VM (FSVM) command line unless stated otherwiseIn the following examples, the non-distributed share name is test_share. 
DoDIN enabled clusters only

Use this command to disable DODIN temporarily to allow share conversion to complete:

nutanix@FSVM:~$ afs infra.set_sudo_auth state=off

Enable DoDIN again with this command:

nutanix@FSVM:~$ afs infra.set_sudo_auth state=off

If you forget to do the above on a DoDIN-enabled cluster, the conversion will never complete.The FSVM command 'afs sync.make_distributed status conversion_id=<UUID>' will continue to cycle through all of the files for conversion returning "BYTES TRANSFERRED - NONE".Steps to convert a share:

Run a pre-check on the standard share to be converted (note this can be skipped because a pre-check is done at the start of a share conversion):
	nutanix@FSVM:~$ afs infra.set_sudo_auth state=off
		Note: The conversion process doesn't support files at the root of the source SMB share shares since post-conversion files at the root are not supported. This guardrail is part of the precheck process. You may see the following error:

	nutanix@FSVM:~$ afs infra.set_sudo_auth state=off
	Example:

	nutanix@FSVM:~$ afs infra.set_sudo_auth state=off
	Start the share conversion on the standard share to be converted:
	nutanix@FSVM:~$ afs infra.set_sudo_auth state=off
	Note: Once the share conversion process is initiated, a Share conversion operation will be initiated with the conversion id.	Example:
	nutanix@FSVM:~$ afs infra.set_sudo_auth state=off
	To check the status of the running conversion. Use the conversion ID obtained in step 2.
	nutanix@FSVM:~$ afs infra.set_sudo_auth state=off
	Example:

	nutanix@FSVM:~$ afs infra.set_sudo_auth state=off
	Before proceeding with the cutover, you will want to make sure that the status shows Status: Active [L0 Completed]:
	nutanix@FSVM:~$ afs infra.set_sudo_auth state=off
	Initiate the cutover to the distributed share. Once this command is initiated, share connections to the standard share will be flushed. In addition, both the standard share and the new distributed share will be in No Access Mode. A final replication will take place.
	nutanix@FSVM:~$ afs infra.set_sudo_auth state=off
	Example:

	nutanix@FSVM:~$ afs infra.set_sudo_auth state=off
	Note: The default cutover time is 30 mins to complete the final replication. If that time limit is exceeded, the original share will be made available again, or you can modify the time by changing the “cutover_timeout” option.Check the status of the cutover and look for “status: completed”:
	nutanix@FSVM:~$ afs infra.set_sudo_auth state=off
	Example:

	nutanix@FSVM:~$ afs infra.set_sudo_auth state=off
	Note: The old standard share will be renamed to <standard_share_name>_ntnx_old, and a new distributed share will be created with the original share name.

	nutanix@FSVM:~$ afs infra.set_sudo_auth state=off
	To apply the settings to the new distributed share that was set to the original standard share, run the following command:
	nutanix@FSVM:~$ afs infra.set_sudo_auth state=off
	Example:

	nutanix@FSVM:~$ afs infra.set_sudo_auth state=off
	If the clients are having file access issues post-conversion, have them remount the NFS export or the SMB share to avoid file access issues from stale file handles. In addition, they may have to clear the DFS cache on Windows clients.

If, for any reason, you need to roll back this operation, such as running out of storage space allocated to Files, you can abort the procedure using the following:

nutanix@FSVM:~$ afs infra.set_sudo_auth state=off

 . ### Human: Now explain this as a Nutanix support agent summarizing the answer step by step. In case, you don't know the answer say - I don't know.