0 Directories and 0 files backed up successfully

[mephisto]

Sorry guys but I've got a case open already for this and I believe no enough attention is being given to this on my support case

I had a problem before running backup jobs to tape, I selected the repository and it came out a minute alter like this "0 Directories and 0 files backed up successfully"

I was asked to install the windows drivers in place of backup exec which was removed earlier. It ran a few times fine and then stopped again with the same reason. No feedback why it doesn't backup the files or anything, very frustrating to say the least.

I tried backup files to tape, backup jobs to tape, nothing works.

Has anyone else experienced the same problem?

Thanks!

[Vitaliy S.]

Mephisto, what is your support case number so I could follow up the latest status of your ticket?

[mephisto]

Mephisto, what is your support case number so I could follow up the latest status of your ticket?

00438226

[veremin]

Also, sometimes you might get this issue when the library/drive has become offline prior to the job execution. So, it might be worth checking this, as well. Thanks.

[mephisto]

It is definitely up and the tape online.

I'll update the ticket now and then we post our findings here to help other people out that might have the same issue.

Thanks

[Patrick_S]

Same with me. HP G2 Autoloader 3000 (LTO5).

[veremin]

Hi, Patrick. I’m wondering what type of drivers you’re using. Are they by any chance software vendor-specific (like, Symantec, for instance) and not ordinary Windows ones? Thanks.

[mattdwyerva]

I am having a similar issue, but only for 1 of my 2 tape backups. Main tape backup of the server works fine (copying most recent vbk to tape). However, I use Windows Server Backup to put a disaster recovery backup of the backup server on a shared network nas. That WAS working, but suddenly it does the same thing as described above. Says SUCCESS but lists no files ("N/A").

Not sure if this information helps or not. I have tried a few tricks, but no luck so far.

[veremin]

Hi, Matt. So, you’re saying that you’ve encountered the same issue with Windows Server Backup, not with VB&R, that suddenly stopped copying files, though, throwing the "successful" message? Thanks.

[mattdwyerva]

I am saying that I have two VBR7 File to Tape jobs. One is executed after a VBR7 backup job and copies the most recent vbk to tape. This one takes 2 hours to execute and copied one 510 GB file from the backup server raid array disk "F" to my LTO5 tape drive.

9/21/2013 6:04:36 AM :: Job started at 9/21/2013 6:04:31 AM
9/21/2013 6:04:36 AM :: Building file tree
9/21/2013 6:04:46 AM :: Preparing next server for processing
9/21/2013 6:04:46 AM :: Processing This server
9/21/2013 8:07:48 AM :: All hosts have been queued for processing
9/21/2013 8:07:48 AM :: 1 directories and 1 files backed up successfully
9/21/2013 8:07:49 AM :: Load: Source 95% > Proxy 17% > Network 66% > Target 39%
9/21/2013 8:07:49 AM :: Primary bottleneck: Source
9/21/2013 8:07:49 AM :: Job finished at 9/21/2013 8:07:49 AM

I have another job that copies the RESULTS of the Windows Server Backup to tape. This one worked on 13 Sept 2013 (39 GB total), copying from an external ethernet connected Seagate BA disk array (NAS).

9/13/2013 9:37:23 AM :: Job started at 9/13/2013 9:37:21 AM
9/13/2013 9:37:24 AM :: Building file tree
9/13/2013 9:37:33 AM :: Preparing next server for processing
9/13/2013 9:37:33 AM :: Processing This server
9/13/2013 9:53:50 AM :: All hosts have been queued for processing
9/13/2013 9:53:50 AM :: 6 directories and 22 files backed up successfully
9/13/2013 9:53:50 AM :: Load: Source 98% > Proxy 11% > Network 10% > Target 7%
9/13/2013 9:53:50 AM :: Primary bottleneck: Source
9/13/2013 9:53:50 AM :: Job finished at 9/13/2013 9:53:50 AM

This second VBR7 Tape Copy job "succeeds" now in 5 minutes without copying ANYTHING to tape (Processed: N/A Read: N/A Transferred: N/A ). N/A? Checking the source, there is still 38 GB there.

9/23/2013 2:41:23 AM :: Job started at 9/23/2013 2:41:21 AM
9/23/2013 2:41:23 AM :: Building file tree
9/23/2013 2:41:28 AM :: Preparing next server for processing
9/23/2013 2:41:28 AM :: Processing This server
9/23/2013 2:46:18 AM :: All hosts have been queued for processing
9/23/2013 2:46:18 AM :: 0 directories and 0 files backed up successfully
9/23/2013 2:46:18 AM :: Job finished at 9/23/2013 2:46:18 AM

So, I am noting what appears the same issue, but only when I copy from NAS to tape, not from the array to tape. Either my result is random (I guess I will try rebooting a few things?) or that is a clue.

[Patrick_S]

Hello, v.Eremin. I am using HP drivers. I have also tried windows drivers with no change in the Success 0 of 0 files backed up though.

[veremin]

Providing that you’re using Windows drivers and the library/drive hasn’t become offline prior to the job execution, it’s a high time to open a ticket with our support team, letting them investigate this behavior directly. Thanks.

[mattdwyerva]

fyi, mine is working now, which is nice, although I can't explain it.

[veremin]

Matt, have you had a chance to open a ticket on this, since our support team might be interested in what has been the cause of this issue and what, actually, has fixed it up? Thanks.

[fmt1962]

I raised an issue with the exact description (case #00451774) and support found that this occurs if the last backup tape media that was used for this job has been removed from the library, whilst one would expect that a "Free" tape would be used if the original media is removed, it does not happen.

I had to add "Create new media set for every backup session". immediately it will load from the "free" tapes and work.

There is no error message generated by B&R when it does not find the original media in this case, the result is a 'successful job' with 0 directories and 0 files backed up successfully.

I expect this would be a problem if I take a tape out to archive offsite, it will not then load a new tape! This could be a problem, as I also do not want to load a new tape / media set for each job.....

Support did indicate this behiour is flagged for a "fix".

Maybe this the is problem you are seeing, it certainly generates the error indicated.

[mattdwyerva]

I did not open a support ticket, as I did not want to spend much time on it if restarting fixed it. If it recurs, I will open a ticket.

My media is set to never create/always continue, fwiw.

[enettekoven]

This issue is still not fixed. Support told me that files to tape job is a workaround, but it is not!

Still waiting for a fix, this is getting really annoying (especially because the errors regarding the job are not giving any reasons why the tape job fails. You have to dig into the logs to get more info).

Case number: 482559

[ccatlett1984]

I'm seeing the same thing, setting it to create a new media set did not work.

Case: 00484935

[Dima P.]

Daryl, Matt, Erik and Chris,

Please, download the last available patch - R2а, I was told that your issues should be addressed in this patch. Thank you.

[ccatlett1984]

I was informed through my case to install that patch, I can verify it has resolved the issue.

[mlucien]

I installed the patch and I am getting the same issues. The patch didn't fix anything for me.

[andrewpetre]

I have a backup to tape job set to only process Full backups for a set of machines. I set the job to run on Monday, well after the Full synthetics are completed over the weekend.

Today, the tape job filled one tape, then failed after waiting for a tape and not taking a Free tape (case open). Now that there are Free tapes, I need to re-run the job to get those Full backups to tape. When I run it, it does not process all of the listed machines, and I get the 0 directories 0 files problem.

I need to fully rerun this job to make a consistent tape set. How can I make the tape job do what's intended?

Ultimately, why do jobs report success when they have not succeeded?

[andrewpetre]

This is Veeam build 771 and the open case is 00488973.

[andrewpetre]

Support reply was that the tape job will keep trying to finish the old job. I can live with that if it's by design. It's far from ideal to not be able to start over the job.

Far more important, though is this problem with the job reporting Success when it doesn't do anything. I was told "known bug to be resolved in a future version". Until then, I am required to review logs and dig into job status every day, because the dashboard is not trustworthy.

[Dima P.]

Hello,
Yes, this bug is in fixing state right now, however there is no need to dig in to the logs - you can view the job history, and if there was no traffic generated ( or resource metric diagram is empty) that means nothing was moved to the tape.

[martin-j]

I have the exact same problem. And no tapebackup for days.

The e-mail reported successfull backup, but tape is blank.

When will the patch/fix be available.

Regards, Martin

[veremin]

Hi, Martin, there are few things to check first:

1) State of tape library/drive. Whether or not the library/drive hasn’t become offline prior to the job execution.
2) Drivers. Absence of drivers provided by backup vendor is must.
3) Product version. What product version you're using? Some of these issues have been fixed in the VB&R v7 R2.

Thanks.

[horst]

Hi,

I had configured a copy to Tape job, that ran every day (mo - sa) pretty well.
But after I installed the latest R2a update the job doesn`t run any more. It starts at the sceduled time, ejects the tape and then hangs at "waiting for tape". But the correct tape was already inserted in the LTO drive.



any hints for me?

[Dima P.]

Hello,
Please, open a support case for this issue it has already been confirmed and the fix should be out soon. Thank you.

[horst]

I opened the Case: 00502929