cancel
Showing results for 
Search instead for 
Did you mean: 

How does the verify in BE 2010 R2 work?

aos-stade
Level 3

Hi,

 

our backup-strategy is to run a daily incremental backup to disk and after that a duplicate to tape. Once a week we run a full backup.

This fullbackup or rather the verify in this job takes very long since last week. Two weeks ago the complete job for our file-server took 6 hours. 5 hours for the backup and 1 hour for the verify. Last week and this week the verify took a huge amount of time. The backup took again about 5 hours, but the verify which is included by this backup-job took 6 (!) hours. The verify time of the other jobs (email-server etc.) also greatly increased.

As we made some changes on a few servers I am now investigating if this links with our verify-problem. For a wonder even the servers where we did not change anything are affected. So I am not sure if this is a Backup Exec problem. The jobrate of the backup is not affected, the backup is not faster or slower as the last working backup/verify-job two weeks ago. So it's only the verify which is affected. ..

 

To take a closer look I would like to know how the verify in BE 2010 R2 works. Where is the verify executed, on the BE media server or on the server where the backup runs? Who has more usage/load the agent or the media server? Is there a lot of traffic/bandwidth used when the verify runs or does it run entirely on the Backup Exec media server? How complex is the verify for the media server? Could a duplicate to tape job affect the verify (for instance a running verify of the file-server and a duplicate job of the already finished mail server at the same time)?

 

These are a lot of questions but I hope that someone has a reply for these.

 

Thanks in advance and best regards

1 ACCEPTED SOLUTION

Accepted Solutions

Hywel_Mallett
Level 6
Certified

A verify is where Backup Exec reads the data it's written for the backup, and ensures that it's consistent. It doesn't compare it with the original backup data or anything like that

 

Where is the verify executed, on the BE media server or on the server where the backup runs?

On the Backup Exec media server.

Who has more usage/load the agent or the media server?

The media server - the agent isn't doing anything during a verify.

Is there a lot of traffic/bandwidth used when the verify runs or does it run entirely on the Backup Exec media server?

No bandwidth is used during the verify, as there's no need to communicate with the Remote Agent.

How complex is the verify for the media server?

Not very.

Could a duplicate to tape job affect the verify (for instance a running verify of the file-server and a duplicate job of the already finished mail server at the same time)?

I would imagine it could. If you're trying to verify a backup job on a Backup-to-Disk device at the same time as writing another backup job to it, you may be getting poor disk perfomance.

What configuration do you have for the disk holding your Backup-to-Disk folder?

View solution in original post

5 REPLIES 5

VJware
Level 6
Employee Accredited Certified

Try these KB articles - http://www.symantec.com/docs/TECH18698& http://www.symantec.com/docs/TECH5407

Hywel_Mallett
Level 6
Certified

A verify is where Backup Exec reads the data it's written for the backup, and ensures that it's consistent. It doesn't compare it with the original backup data or anything like that

 

Where is the verify executed, on the BE media server or on the server where the backup runs?

On the Backup Exec media server.

Who has more usage/load the agent or the media server?

The media server - the agent isn't doing anything during a verify.

Is there a lot of traffic/bandwidth used when the verify runs or does it run entirely on the Backup Exec media server?

No bandwidth is used during the verify, as there's no need to communicate with the Remote Agent.

How complex is the verify for the media server?

Not very.

Could a duplicate to tape job affect the verify (for instance a running verify of the file-server and a duplicate job of the already finished mail server at the same time)?

I would imagine it could. If you're trying to verify a backup job on a Backup-to-Disk device at the same time as writing another backup job to it, you may be getting poor disk perfomance.

What configuration do you have for the disk holding your Backup-to-Disk folder?

aos-stade
Level 3

Thanks for your fast replies.

This helps alot. I thought the verify compares the backup with the source. So if I understood you right, I can except the network as a source of error and it seems that the problem is on the media server? This is kinda evident as the jobrate during the backup is still steady.

What exactly do you mean with configuration for the disk?

It is a 1.36TB large partition with about 600GB backup-to-disk data on it and the remaining space is free. In BE the settings are as follows:

Folder & media-set settings -> see attachments

 

Maybe the antivirus software thwarts the verify. I think there has been a minor update of the product which could fit with the date where the trouble with the verify began. Or it's some kind of error or huge fragmentation on the partition containing the b2d-data.

 

Hywel_Mallett
Level 6
Certified

So if I understood you right, I can except the network as a source of error and it seems that the problem is on the media server?

Yes.

What exactly do you mean with configuration for the disk? 

Is it RAID 10? Or a single spindle. Is it SAS disks? Or connected by USB?

In other words, how fast is it, and how good is it?

aos-stade
Level 3

The server is a DELL PowerEdge 2900 (from 2008) with with a DELL PERC 6/i SAS controller and it ought to be a RAID 5. I think it's not so bad in performance and there where no performance issues until one week ago wink

 

I will disable the antivirus guard on the next full backup to see if due to small product update the search engine was probably changed and now handicaps the verify.