Backup to NAS

[DED10]

That's the problem I encounter.
I am trying to backup a NAS.
I connected a network drive under windows. I go to the NAS correctly.

When I schedule a backup using Veeam he test backup using a UNC path? Is this normal?
I then the error:
Building path for backup Failed to create dir "\ \ 198.168.20.227 \ Backup \" Unable to find part of path '\ \ 198.168.20.227 \ Backup'.

Thank you

[Gostev]

Andre, I am not sure I fully understand what you are saying, but you should not use network drive in Windows as backup destination. Mapped drives are only available for users logged on to the computer interactively, they are created at logon and removed at logoff, and cannot be accessed by services.

You need to specify UNC path to target share in the backup destination instead, for example: \\NAS-IP\backup

[DED10]

Sorry for my English!

It does not work via the \ \ NAS-IP \ backup
I have the following error:
Details
Building path for backup Failed to create dir "\ \ NAS-IP \ backup \" Unable to find part of path '\ \ NAS-IP\ backup'.


Let me explain my setup
I make backup on a SAN which are going very well.
I also want to backup a NAS that is in another computer room.

You may know a better way?
Thank you

[Vitaliy S.]

Hello Andre,

Are you able to access that NAS device by IP address while being logged in to your backup server with the account which is specified as logon account in the Veeam Backup and FastSCP service?

Thank you!

[Gostev]

Also, why do you have spaces in the address between back slashes? This looks strange to me.

[murda]

I did it this way.

Veeam on VM and backup to a SAN.
Then I put a Rsync client for windows on the VM VEEAM and made a schedule towards the my NAS device.

Rsync then do a incremental backup from the backup made from Veeam on the SAN.

[DED10]

Hello

To answer all your answers:
I have no space in my path (UNC is when I paste my text in the forum they appear.)

Try configuring with Rsync but I found where was the problem with your suggestion.

Let me explain:
My NAS is integrated into my domain. There are bugs to access when it is integrated into a field. I did a updated firmware, but the problem is still there.
The solution currently is allowed public access to the NAS share and Veeam accesses properly.

I hope to be quite clear in my explanation and my English.

Thank you for your help

[cb-comfuse]

Hi everyone,

same problem here. I´d like to backup to an 2.5TB NAS. Veeam Backup 4.1.1. running on Server 2008 R2 x64. Thecus-NAS N5500 2.5TB free space, AD-integrated. I can access the share from the Backup-Server and add/delete Files and Directories without any problems but I can´t backup one VM.

Building path for backup
Failed to create dir "\\n5500\backup\"
Unable to find part of path "\\n5500\backup"

Same problem with IP-Adress!

Best practice or not, is there a way to make it working?

Thanks in advance!

[Vitaliy S.]

Christoph, have you've tried accessing your 2.5TB NAS device having logged on to Veeam Backup server with the account used by Veeam Backup and FastSCP service?

[cb-comfuse]

Good point! Now as I run the Veeam-Service with the appropiate account-information for accessing the NAS it works. Thank you very much

[rizks_2000]

I was hoping I would see the right answer here and sometimes it always is the logon creds for sure. I'm glad because I just ordered the Iomega Stor-Center, which is VMWare certified, etc. I need to back up to NAS from Veeam and I know I read out here that it worked. In fact, I got the idea about the iOmega device from this forum because I knew nothing about NAS but expect to learn quickly! Thanks again for all these posts!