Dell Rapid CIFS

Availability for the Always-On Enterprise

Dell Rapid CIFS

Veeam Logoby stevil » Mon Sep 05, 2016 9:58 pm

I've been playing with a couple of new Dell DR4300 NAS's as backup a repository. We're running backups over 1Gb at the moment so I thought I'd try the rapid CIFS driver that dell provide to do source side dedupe/compression to speed things up. The result was pretty impressive with effective throughput going from 1Gb to over 7Gb. This is all well and good but at the same time Dell don't officially approve the use of the driver with Veeam, and I have noticed some odd stalls in the backup job which at the moment I'm blaming on this driver. It's going to be hard not to use the driver given the massive impact it has on reducing our backup times.
Have any of you guys have a go with the rapid CIFS driver? Any comments?
stevil
Enthusiast
 
Posts: 94
Liked: never
Joined: Thu Sep 02, 2010 2:23 pm
Location: Manchester, UK
Full Name: Steve Buckley

Re: Dell Rapid CIFS

Veeam Logoby stevil » Fri Sep 09, 2016 1:42 pm

For those interested. Speaking to Dell, they've seen the same issues, hence why the driver isn't certified to use with Veeam. They are working with Veeam on this (where the proxy stalls and needs the driver reloading). No word on priority or ETA. It seems like an awesome addition if it can be productionised.
stevil
Enthusiast
 
Posts: 94
Liked: never
Joined: Thu Sep 02, 2010 2:23 pm
Location: Manchester, UK
Full Name: Steve Buckley

Re: Dell Rapid CIFS

Veeam Logoby enoch » Sun Sep 11, 2016 2:40 pm

Be aware that we dropped using the Dell Rapid CIFS driver because it was not supported by Dell and we got disk corruptions using it together with Veeam!
enoch
Service Provider
 
Posts: 107
Liked: 7 times
Joined: Sat Jun 29, 2013 12:14 pm
Full Name: Peter Enoch

Re: Dell Rapid CIFS

Veeam Logoby stevil » Mon Sep 12, 2016 12:47 pm

Did the backup jobs themselves become corrupt?
I've reduced our two proxies down to 4 threads each, this seems to have fixed the issue we were previously seeing. Apparently each CIFS container on the NAS can only handle 16 threads anyway. Previously I had 2 x 12 threads firing at it, so this may have made things worse. I've done a couple of test restores from the data, it seems OK so far.
What environment were you testing it in? 1Gb/10Gb? How many threads/proxies?

Thanks for your feedback. Interesting to hear someone else has been down this road :)
stevil
Enthusiast
 
Posts: 94
Liked: never
Joined: Thu Sep 02, 2010 2:23 pm
Location: Manchester, UK
Full Name: Steve Buckley

Re: Dell Rapid CIFS

Veeam Logoby enoch » Mon Sep 12, 2016 1:04 pm

It was back with Veeam 8.0 and with 2xDR4100

We only used them for Backup Copy jobs, but as I wrote we got disk corruptions when using the Rapid CIFS driver.

It was on 10 Gb network.
enoch
Service Provider
 
Posts: 107
Liked: 7 times
Joined: Sat Jun 29, 2013 12:14 pm
Full Name: Peter Enoch

Re: Dell Rapid CIFS

Veeam Logoby stevil » Tue Apr 11, 2017 12:23 pm

I notice that Dell have released a new version of firmware and driver for the DR series (V4). I'm in the process of upgrading the NAS's and the driver. I'll test it again over the coming days and see if it's still 'broken' with veeam.
stevil
Enthusiast
 
Posts: 94
Liked: never
Joined: Thu Sep 02, 2010 2:23 pm
Location: Manchester, UK
Full Name: Steve Buckley

Re: Dell Rapid CIFS

Veeam Logoby Rick_M » Tue Apr 11, 2017 11:23 pm

If you're going down this path - ensure Veeam is the only thing writing to the DR Device. We encountered the below errors causing Veeam job hangs when RDA connections were made to the DR Device at the same time from Netvault - It's worth noting Netvault didn't even need to write to the device for this to occur - having an active connection was enough (This added months to the troubleshooting process)

Error PrepStorageForWriteEx failed *.vib' at Veeam.Backup.AgentProvider.CBackupClient.PrepStorageForWriteEx(String storageFilename, Int32 kbBlockSize, Int32 blockAlignmentLogarithm) Error Exception of type 'Veeam.Backup.AgentProvider.AgentClosedException' was thrown. at Veeam.Backup.AgentProvider.CClientAgentProtocol.WaitUntilWorking(Int32 timeout) Error Failed to connect to agent's endpoint *. Host: ********.
Error No connection could be made because the target machine actively refused it ************ (System.Net.Sockets.SocketException)
Rick_M
Lurker
 
Posts: 1
Liked: never
Joined: Mon Aug 29, 2016 10:54 pm


Return to Veeam Backup & Replication



Who is online

Users browsing this forum: Bing [Bot], EIvanov and 14 guests