Error connecting to the mount

[DCIM_Support]

Hi I am receiving an error when trying to do a backup restore.

using DCE 7.4.1

this type of restore has worked in the past, what can be wrong?

(CID:124527032)

[DCIM_Support]

Victor,

From what I can tell with the provided information, you will need to adjust some of your slashes in your path.  Some are forward slashes and some are reverse slashes.

Best Regards,

Cory

(CID:124527117)

[DCIM_Support]

Hi Cory,

I don’t think the slashes are the problem, the path was the same before.

Reading some other posts lead me to believe the issue is with security settings.

Particularly with the NTLM setting.

The share where the backup file is, uses NTLMv2, and for some reason when trying to mount with NTLMv2, it will give the same error.

I created another VM with NTLMv1 and I am able to mount the share.

Problem I have is that I cannot keep a VM with NTLMv1.

Is there a setting on the DCE that I need to change so it can mount the share with NTLMv2 ?

(CID:124527184)

[DCIM_Support]

Victor,

In Version 7.4.1, you should have settings to change the security of the backup / restore settings.  These options were added in 7.3.X.  You can change them by selecting your backup within the list and clicking on Edit Backup.  There will be a drop-down asking for the for the security level.  

Did you ensure to update this since NTLMv1 was disabled on your systems?

Best Regards,

Cory

(CID:124527186)

[DCIM_Support]

Editing the backup does not fix the problem, same error.

I copied the backup folder to the VM I created with NTLMv1, however when I try to restore from this new location, it does not see the files.

Question is, can you restore from a backup created in an older version 7.3.x to version 7.4.1?

or version 7.4.1 cannot see files from a previous version?

(CID:124527227)

[DCIM_Support]

You can only restore to the same version as where the backup was created.

(CID:124527315)

[DCIM_Support]

HI Cory, is there a way to restore to a previous firmware version? if I can bring the DCE to the same version as the backup, it may help resolve my issue.

(CID:124527877)

[DCIM_Support]

Victor,

Your local technical support can provide you with the necessary link to restore an old version of Data Center Expert on your appliance.  You would then have to set the IP address and then make the connection to your backup share and you should be able to see the backup from the same version you are then running.

Best Regards,

Cory

(CID:124527880)

[DCIM_Support]

Cory,

I have the path to the 7.3.1 version, just need confirmation I can load it on top of the 7.4.1 version and it should work?

(CID:124527927)

[DCIM_Support]

Hi victor,

Have you solved this problem or not?

With respect.

(CID:125208259)

[DCIM_Support]

victor,

You can use the 7.3.1 ISO and restore the appliance back to that version, just keep in mind that it will wipe anything that is currently on the server and put on a fresh copy of the 7.3.1 version of StruxureWare Data Center Operation.  You will then have to assign the network settings via the console using the username/password of apcsetup/apcsetup.

Best Regards,

Cory

(CID:125208845)

[DCIM_Support]

Hi victor,

A similar topic on DCIM Support has been repeatedly discussed: unfortunately, at the moment the only solution as John Thompson said in the topic  is:

Only SMBv1 is supported on DCE at the monent, but there is a feature request to have support added for newer versions of SMB. As a workaround, you could use a NFS share instead.

With respect.

(CID:124527177)

[DCIM_Support]

spezialist,

This should not be the issue with this scenario as everything works fine with NTMLv1 enabled.  Therefore the SMB settings should not be an issue as they were not altered between the two scenarios.

Regards,

Cory

(CID:124527188)

[DCIM_Support]

Hi Cory McDonald,

From victor's answer, I realized that his backup to Windows resource until recently worked normally with the initial settings in the DCE-server. He did not change these settings in the DCE-server. At the same time, after a while, its backup to Windows resource stopped working. Therefore, I concluded that some changes were made on the Windows resource side and in particular the disabling of NTMLv1 with the forced use of exclusively NTMLv2 due to security risks.

victor, did I understand you correctly?

With respect.

(CID:124527457)

[DCIM_Support]

Hi Spezialist, you are correct, the changes was made on the Windows resources to MTMLv2 due to security risks.

(CID:124527876)

[DCIM_Support]

This question is closed for comments. You're welcome to start a new topic if you have further comments on this issue.