SMB full back up login problem

[marcinw]

HI,

I created backup on SMB 1550 that was connected via VPN to SMS in Azure, I took the 2nd 1550 and uploaded this backup onto this one. When I plug in the 2nd 1550 into the network VPN tunnel is created automatically, I don't have to even re-establish SIC , that is fine. The only problem is I can't log onto device I tried credentials from from "backuped" 1550  also from the 2nd... no joy . 

I see the message on the login screen (Operation failed server error)

 DO someone know how to fix it? Thanks

[PhoneBoy]

Might want to get the TAC involved here

[Tom_Hinoue]

Are both 1550's have same firmware version and build number installed?
Such issue can occur if you restore a backup that is from a different version/build.

[marcinw]

 Good point! And you are absolutely right! not it's working . thanks

[G_W_Albrecht]

Uhhh uhhhh.... Should that be possible at all ? Afaik in R77.20.xx, only same firmware version backups could be restored. Which versions led to he issue ?

[marcinw]

 I was able to upload backup from 80.20.15 to 80.20, everything was working the only issue was https access 

[G_W_Albrecht]

That just should not be possible - @Amir_Ayalon , @Vincent_Chu , what do you think ?

@PhoneBoy - can you move this to SMB ?

[Vincent_Chu]

It's possible some validation checks before restoring a file are not running. 

We started to support restore from R77.20.87 firmware on R80.20.15 officially.  I know the gateway let you do it since initial release I think, but lots of things broken and maybe this is why the validation was left out.

I don't know if any changes will be made on the older builds but this might be something that can be reviewed moving forward.

[G_W_Albrecht]

Looks like a good reason for the issue ! But strange that the credentials are not working - i would have assumed that R80.20 and R80.20.15 do not differ much in handling credentials...

[Vincent_Chu]

The database is very delicate. Might have been something to do with the tables used changed. 

between HFA10 and 0 there was a major change which was to add MFA for VPN users. 

Maybe that caused a change in the user table. Just a guess here.