Failover steps for the SMB protocol

Use the following steps on a protocol node in the secondary cluster to fail over the SMB protocol configuration.

Before stopping the SMB services, make a note of the node number that will be used to restore TDB files because the node numbers are not available when SMB services are stopped.
Stop the SMB services using the following command:
```
mmces service stop SMB --all
```
Issue the following command to stop the NFS service:
```
mmces service stop NFS --all
```
Remove the contents of the /var/lib/ctdb/persistent directory on all protocol nodes.
Restore the previously saved TDB files to one of the protocol nodes and place them in the /var/lib/ctdb/persistent directory for the node where the node number was saved.
However, when copying the files to that directory on the node, replace the X.bak, where X represents the node number where the files were copied from, with the new node number. It is crucial that each of these files ends with .tdb.Y, where Y is the node number that was saved and the node number where the files are being restored. These files only need to be put into one of the nodes and when the SMB processes are started again they are copied around to the other nodes properly.
Remove the contents of the /var/lib/samba/smb_krb5 directory on all the protocol nodes.
Restore the saved contents of smb_krb5 to the /var/lib/samba/smb_krb5/ directory on one of the protocol nodes. No special extension needs to be altered in this case.
Start the SMB services using the following command:
```
mmces service start SMB --all
```
Issue the following command to start the NFS service:
```
mmces service start NFS --all
```
Remove the SMB shares that are not protected using AFM DR independent filesets.