How long should verify process take??

[mquinn0908]

I recently took over our backups and have noticed that the backup job had verify after backup completes turned off. My question is if I select for the verify after backup completes to run then how long does this process usually take? I know that a lot of veriables go into this but as a general can you give some idea? We backup 4 servers and around 130GB and the job currently takes about 5 hours. I have a script that runs after the job finishes to start up some important services that we have to stop before the backup runs so the job is finishing about an hour before everyone comes in which is perfect. If the verify process will take several hours then this will cause major problems if the services that we have to stop don't get started before everyone comes in. Thank you.

Mandy
MCP/A+/Network+

 

[LawnBoy]

Running BE 9.1 on Netware with a Quantum SDLT2 600GB Ultra160 SCSI single deck (external). 3 Remote servers involved.

Total devices: 10
Total bytes: 197,222,434,395 (188085.9 Megabytes)
Total time: 04:20:28
Throughput: 12,619,812 bytes/second (722.1 Megabytes/minute)

Total devices: 10
Total bytes: 197,222,434,395 (188085.9 Megabytes)
Total time: 01:29:17
Throughput: 36,815,836 bytes/second (2106.6 Megabytes/minute)

hth.

 

[JJDiver]

Mandy,

Ran across your post while perusing the forum, trying to find answers to my questions.

According to the following article (as I understand it,)

http://seer.entsupport.symantec.com/docs/245177.htm

verify does not check the data which Backup Exec wrote to the tape or disk, to the origonal source. The article mentions why it doesn't. Since verify does not check agaisnt the origonal source, you could restart the services after the backup portion of the job completes, before the verify runs. You should enable the writing of checksums during the backup, and this may slow down the backup operation (perhaps try it first on a weekend, presuming you operate five days a week.) I don't have to stop services, so I am not sure, but you may need to break the job into two different parts, backup and verify so you can start the services after the backup complets, before the verify starts.

Another thought, what services are you stopping? SQL databases? If so, you could buy the SQL remote agent, and then you would not have to stop the services. I would venture a guess that the proper remote agent would allow you to discontinue stopping services.

Hope this helps, and hopefully you found this out in the last month,

JJDiver.

 

[mquinn0908]

JJDiver,

Thanks for the info and I found out (after the first time I ran a backup with verify) that the command to restart the needed services acually runs right after the actual back up ends and right before the verify starts so it really dosen't cause us any problems as the backup with verify is acually taking about 1 1/2 longer than backing up with no verify but since the services start up before the verify then it can run a little longer and not affect anyone. Thanks again!

Mandy
MCP/A+/Network+

 

[JJDiver]

Question for you, that might help me as well...

What services are you stopping? Could you avoid stopping the service by using a remote agent? If so, are you not using a remote agent to save money, or ?

Thanks,

Jeff

 

[willjwill]

I spoke to the people at Veritas before and they claim that you don't have to verify your backups if you backup to disk. We backup to removable disk and stopped using the verify a while ago. All is peachy.

 

[mquinn0908]

We are stoping SQL services and we do have the SQL remote agent but we have found that we still have to stop the services which isn't a big deal like I mentioned in an earlier post as the services start back before the verify starts which is about an hour before people start getting in.

Mandy
MCP/A+/Network+