Error Message: FATAL cant_write can't write cifs: (at var_friendly_mkdir:96)
Make sure all needed ports are open between your Esx Host and the repository..
TCP ports that should be open:
TCP 22 - SSH
TCP 443 - SSL
TCP 137 - CIFS
TCP 138 - CIFS
TCP 139 - CIFS
TCP 445 - CIFS
1)Check that the share has proper share AND folder/file perms for the user used to create the repository.
2)vRangerPro will bind to the first network card that is listed in the binding order: ie:
a.Network Connections, Advanced, Advanced Settings, Adapters and Binding.
b.The “public” network MUST be first on the binding order.
*****Any Repositories must be recreated if the binding order was incorrect when setup*****
***** If DataDomain, be sure that the cifs add command has been used to allow access from each service console IP and be sure that proper DNS resolution exists.*****
***** DataDomain often utilize multiple IP's to the same destination, so make sure vRanger and the Hosts resolve the same IP. ******
Run ping commands from hosts to make sure you are resolving to the correct IP & FQDN.
To verify connectivity from the Host to the Repository:
1.SSH to the ESX host as root
2.Run ping commands from hosts to make sure you are resolving to the correct IP & FQDN.
3. .Run the command 'mkdir /mnt/backup'
4.Run the command 'esxcfg-firewall -e smbClient'
5.Run the command 'mount -t smbfs //<repositoryservernameorIP>/<share>
/mnt/backup -o username=<useraccount>(if domain useraccount“domain\username” quotes are required)
***for vSphere 4.0- replace smbfs with cifs in the above command ****
If you are unable to mount the share on the ESX host, then you will need to adjust the share and NTFS permissions until it is successful.
6.If mount is successful, run the command 'touch /mnt/backup/testfile'
If you are unable to touch, then you will need to adjust the share (Full
Control) and NTFS permissions (minimum Change/Modify)
If touch is successful, then the ESX host should be able to perform a backup to the repository.
7.Run the command 'umount /mnt/backup to clean up mount.
KB Article: 00000299
Updated: Jul 31, 2009
vRanger Pro DPP
Expires on: 365 days from publish date