Re: Design NAS DR solution

I would like to inquire about the design of a NAS DR solution.

I currently have two Unity 400s and would like to implement a replicated CIFS service in the booth of the second CPD.

The communications between both CPDs are made through an extended LAN with the same IP address.

My design questions arise mainly during configuration;

I create the NAS service in the primary CPD, the replication interfaces with their corresponding IPs in each of the centers.

Do I have to register another NAS server in the secondary CPD?

Is information replicated from both files and NAS/CIFS service?

When a failover is executed. Will users access without making changes to the original file path, such as \NASShare?

Best regards

Related:

Design NAS DR solution

I would like to inquire about the design of a NAS DR solution.

I currently have two Unity 400s and would like to implement a replicated CIFS service in the booth of the second CPD.

The communications between both CPDs are made through an extended LAN with the same IP address.

My design questions arise mainly during configuration;

I create the NAS service in the primary CPD, the replication interfaces with their corresponding IPs in each of the centers.

Do I have to register another NAS server in the secondary CPD?

Is information replicated from both files and NAS/CIFS service?

When a failover is executed. Will users access without making changes to the original file path, such as \NASShare?

Best regards

Related:

How To Change the Unidesk / App Layering appliance IP addresses

Connect to the appliance from either the hypervisor’s console or through SSH. Login with the following credentials (please note this password can be changed by the user):

User: administrator

Password: Unidesk1

On an App Layering ELM you will see the following menu:

########################################

# App layering appliance configuration #

########################################

# (S)how current config

# (C)onfigure networking

# (P)assword change

# (T)imezone change

# (N)TP servers change

# (Q)uit

########################################

Action (c/n/q/p/s/t):


Unidesk Management Appliance:

#############################

# Unidesk virtual appliance

# static networking config

#############################

# (S)how current config

# (C)onfigure networking

# (P)assword change

# (Q)uit

#############################

Action ? (S/C/P/Q):


Unidesk Cachepoint Appliance:

#############################

# Unidesk virtual appliance

# static networking config

#############################

# (S)how current config

# (C)onfigure networking

# (P)assword change

# (M)odify MA IP Address

# (Q)uit

#############################

Action ? (S/C/P/M/Q):


NOTE: The cachepoints have an additional option to set the management appliance IP address. Each cachepoint needs to know which IP to talk to when they first power on. If the IP address is changed on the management appliance then each cachepoint needs to be updated with this IP as well under option M.

Related:

How to install NMAS on VMware ESXI or VSphere


How to install NMAS on VMware ESXI or VSphere

To Install NMAS on VMware and VSphere below 6.5 version:

1. Start the VMware vSphere client on your workstation.

2. In the IP address / Name text box, type the IP address of the VMware ESXi server that you want to connect to.

3. In the User Name and Password text boxes, type the administrator credentials, and then click Login.

4. On the File menu, click Deploy OVF Template.

5. In the Deploy OVF Template dialog box, in Deploy from a file or URL, browse to the location where you saved the NetScaler MAS setup files, select the .ovf file, and click Next.

Note:If a warning message appears with the following text: The operating system identifier is not supported on the selected host, check to see if the VMware server supports FreeBSD operating system. Click Yes.

6. On the OVF Template Details page, click Next.

7. Type a name for the NetScaler MAS virtual appliance, and then click Next.

8. Specify the Disk Format by selecting either Thin provisioned format or Thick provisioned format.

9. Click Finish to start the installation process.

To install NMAS in vSphere 6.5 and newer, you’ll need to upgrade the VM Compatibility. After following the above steps which are for VM ESXI and Vspehere below 6.5. Follow below additional steps for configure compatibility

1. Right-click the NetScaler MAS appliance, expand Compatibility, and click Upgrade VM Compatibility.

2. Click Yes.

3. Select at least hardware version 7 (such as ESX/ESXi 4.0 or later).

4. Review the settings.

5. Power on the Instance. Ignore the Guest OS warning.

Note: If you see a message about Invalid guestid in Configinfo, then you’ll have to upgrade the VM hardware version first. VM hardware version 4 is old for vSphere 6.5.

Related:

Re: Unity FS question

In VNX the following command is used to export a CIFS to NFS



server_export server_2 -Protocol nfs -option access=x.x.x.x,rw=x.x.x.x,root=x.x.x.x -comment ‘Example Export NFS’ /root_vdm_1/path1/path2



But how can it be done in UNITY?



I converted the NAS SERVER into multiprotocol,



uemcli -u admin -p <yourpassword> /net/nas/server -name Myname set -mpSharingEnabled yes -unixDirectoryService local



but it did not solve me, I have an access error!



Could you help me, please?

Related:

Re: VNX File to Unity Import

It’ll import VDMs only, and only 1 CIFS server per VDM is supported, since once the data lands on Unity you have NAS servers which cannot contain multiple CIFS servers, and are instead 1:1. There are other limitations, and of course there are other options for doing the file migrations including free host-based tools, or better-yet commercial tools. I’m biased of course, because I work for a company that makes the best of the commercial tools on the market (IMHO).

Chris Klosterman

Principal SE, Datadobi

chris.klosterman@datadobi.com

Related:

Re: An existing pool configuration has been detected

I’m having a problem with a recent virtual unity appliance I deployed (of course after I moved data onto it). The esx host I had the appliance running on decided to kernel panic and I have been having problems with the unity server ever since. After the host came back online the unity appliance booted into service mode. I was not able to reach the management IP and tried restarting the appliance several times. I was finally able to get back into unity by running the initial setup wizard from the cli. This might have been my fatal mistake? I assumed the setup wizard would have just defaulted the management interface ip settings, etc, but would not default all other existing configs?

Long story short…it appears that my unity config was completely wiped! While I am now able to get back into the appliance and everything seems to be happy none of my existing configurations remain i.e. pools, vvols, smb, etc.

When I look at the system view I can see the Virtual disks and a warning telling me that an existing pool configuration has been detected on the virtual disk. Does this mean that the data still exists? Is there a way to re-associated the existing pool configuration with a new pool without destroying the data? This is the community edition so all in all I can’t complain too much if I loose the data. That being said, I have some data that I would really like to restore if at all possible.

unityvsa-error1.jpgunityvsa-error2.jpg

Thanks

-LED

Related: