Files to tape is painfully slow

[johndoe10110]

When is V8 going to be released with an appropriate performance profile for file to tape backups for VEEAM?

I don't believe there's a specific date just yet, but it's still being said Q3 of this year.

Source: http://www.veeam.com/blog/v8-feature-an ... ments.html

[foggy]

It's late Q3 for RTM now, so probably early Q4 for GA. We have decided to provide our partners with the RTM code a few weeks before GA, to let them prepare.

[nosecam]

Same here, file to tape makes the product unusable. Need to go back to BE?
Just for being part of upcoming notifications...

[foggy]

You can also sign up for notifications at http://go.veeam.com/availability-suite-v8 to be aware of all the news regarding Veeam Availability Suite v8.

[Gostev]

Happy to share these results I have just received from a beta tester.

Backing up the same folder:

v7 took 91 hours 47 minutes 36 seconds to process:
5250 directories and 96066 files backed up successfully (total size 65.5 GB)

v8 took 2 hours 10 minutes 50 seconds to process:
5733 directories and 95980 files backed up successfully (total size 67.7 GB)

Which makes v8 over 40 times faster than v7 processing when processing a bunch of small files

[johndoe10110]

Holy smokes has it improved! Works beautifully for my couple hundred thousand files (in v8).

Thanks Veeam!

[veremin]

Kudos to our R&D team for working hard to enhance our files to tape backup engine. The current version should work much faster with multiple small files, indeed. Thank you for confirming that!

[FXE]

Nice to read tape jobs in v8 seems to work speedier than in v7.
I'm downloading the v8 and I will install it soon.
I will give you feed back ASAP.

[Dima P.]

FXE,
How did it go? We recognized real improvements, for instance: In v7 we had a file to tape job, that took 7 days to complete and in v8 it takes 17 hours.

[FXE]

Hello,
I've not tested files backup to tape yet.
In fact, following the v7 to v8 migration many issues appeared (install issue, Veeam ONE issues, Catalog replication issue, ...). The Veeam support is working to resolve them.
As soon as my issues will be resolved, I will going to test backup to tape.

[Dima P.]

Got it. I hope our support team will get your environment up and running as soon as possible, thank you for keeping us posted!

[FXE]

Hi all,
Most issues impacted my Veeam environment are now resolved.
And I can appreciate the speed of "files to tape" backup. But even if the files seems to be correctly backed up, an error message appears for several files :
"Task full_file_path failed: Transaction (Process ID 51) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction."

It seems to be a SQL error message. What about that ?
Should I open a case for this ?
Thank you.

[Gostev]

Hi, it is not a know issue at this point, so yes - please open a support case for investigation. Thanks!

[habibalby]

<thumbs up> files to tape...got my support guys, I'd LOVE to get to ONE backup software, bye bye Symantec!

It's not bye bye Symantec until you pass your compliance period of Symantec backup and totally relying on Veeam with successful restoration of your backup.

[habibalby]

Job rate of Files to Tape using version 8.0.0.2018

[Dima P.]

Hello Hussain,
Please open a support case and post here the case ID, need to check you logs. I believe, File to tape job should run faster. In addition, what was the approximate throughput before the upgrade? Thanks

[habibalby]

Hi.. First time to integrate the backup to tapes and I thought to testing Files to tape..

[futureweb]

has there ever been any outcome what the reason was? We are too backing up (archiving) directories with lots and lots of files (millions) and I am not sure if the backup is done right this way?
As it's not a warning but error I wonder if we have to worry or should open a case?

22.09.2015 22:31:43 :: Task U:\GPIX\2010.07.07 (Gigapixel Horn von Sthof aus)\gigapan.data\tiles\r01\031\311\r0103131110.jpg failed: Transaction (Process ID 75) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.

That file to tape is slow on our end is because those are many small files, so that is something that's normal.

EDIT: i just noticed, that Veeam takes up 5 GB RAM, and total Usage is 9,5 GB RAM out of 10GB. So this problaby could be a RAM issue I believe, I will give Veeam more RAM and check again what happens. the Ram was used bei Veeam.Backup.Manager, is it because it's Million of Files?

[futureweb]

Just to update, I made a case and it was solved with a Hotfix, now Millions of files are backed up without any error.

[Dima P.]

Thanks for the heads up – good to know that we have a solution at the support side! From now, we’ll take care this hotfix is carefully merged into upcoming version.