vRanger Backup Error 2258 “cifs_cant_mkdir”: Check Your Repository Path Case

After upgrading to vRanger Backup and Replication 7.0.0.37394, I ran into a confusing bug. We’d been running fine on 6.1.0.35402 until we lost a drive in the SAN and, with it, the database that held our backup logs. Since the logs were gone anyway, it seemed like the perfect time to upgrade. Then the new backups started failing.

The Error

Backup failed: Error: 2258 - FATAL cifs_cant_mkdir CIFS can't create the directory cifs:localhost;admin@backupdevice/public/backup/* (No such file or directory) [at cifs_mkdir:615]

The Cause: Capitalization in the Repository Path

When you create a new repository in vRanger, the path is case-sensitive, over both NFS and CIFS. \\backupdevice\dir\backupfolder is not the same as \\backupdevice\dir\BackupFolder. In my case the path should have been backupdevice/public/Backup, with a capital B.

What makes it maddening is that vRanger validates the wrong path as correct during setup. This happens on the vRanger Virtual Appliance (vRanger-VA).

The Fix

If you see error 2258 on a fresh install, check that the capitalization of your repository path exactly matches the share. Or avoid the problem entirely by using all lowercase folder names.