Link to home
Start Free TrialLog in
Avatar of Pancomp60
Pancomp60

asked on

vRanger Error Message: 3208 - can't read cifs:xxxxxx

We have been using vRanger to backup our VMs to a local Seagate BlackArmor 8TB NAS.  Recently we decided to upgrade to a 12TBNAS.  When I went looking for a new NAS I found that Seagate "retooled" their BlackArmor line into their new Business Storage line.  Upon purchasing a 12TB Business Storage NAS and configuring it the same as the 8TB BlackArmor NAS, I ran into a problem.  We now get
Error Message: 3208 - can't read cifs:<domain>;<account>@<ip address>/vRanger/<folder>/<folder>/<filename>.prepared

I have been trying to increase the CIFS timeout rate, incrementing it by 300, but I've now gone from starting with 900 and am up to 1800 and still getting the same error.

Has anyone successfully implemented the new Seagate Business Storage NAS line with vRanger?
Avatar of David Johnson, CD
David Johnson, CD
Flag of Canada image

Could your backup software be looking for the older backups?  Can you copy them to the new NAS?
Avatar of Pancomp60
Pancomp60

ASKER

Software is not looking for previous backups, created a brand new repository and backup job on the new NAS so backups on the old NAS are not affected.

Found that vRanger creates a folder in which the temporary file is written.  This folder starts with a period "." which sets the Hidden property to on.  It appears that for whatever reason once the file is written inside this folder, vRanger cannot read it in order to finalize the backup file.  vRanger techs are as stumped as I am as this appears to be an issue that is solely related to the Seagate Business Storage 4-bay NAS.  The Seagate BlackArmor 4-bay NAS that we are wanting to replace, also is written too in the same manner, but there is no read error for that NAS.
ASKER CERTIFIED SOLUTION
Avatar of Pancomp60
Pancomp60

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Apparently there is no reason for the error I'm getting, at least according to Seagate.  Our final solution was to get rid of the Seagate NAS altogether and go with Synology.