Jump to content

Recommended Posts

The following log is for a media set copy beetween FW disks.


Log for Script: daily_user_rotate_last_tmp_copy

Date: 2/1/2015

+ Executing daily_user_rotate_last_tmp_copy at 2/1/2015 2:37 AM (Execution unit 2)

To Backup Set v9_daily_user_last_tmp...

- 2/1/2015 2:37:44 AM: Transferring from v9_daily_user_last

!Bad Backup Set header found (0x044801bf at 1867514)

2/1/2015 3:37:41 AM: 1 execution errors

Completed: 507563 files, 103.6 GB

Performance: 1782.9 MB/minute

Duration: 00:59:56 (00:00:29 idle/loading/preparing)


- 2/1/2015 3:37:41 AM: Verifying v9_daily_user_last_tmp

2/1/2015 3:59:59 AM: Execution completed successfully

Completed: 507563 files, 103.6 GB

Performance: 4753.2 MB/minute

Duration: 00:22:18


2/1/2015 4:00:03 AM: Script "daily_user_rotate_last_tmp_copy" completed with 1 errors



I see no evidence that the "error" reported has caused any problems. The source verifies without error, and so does the copy.


What, exactly, doe the error mean? Is this likely to be a transient error caused by the inherent less-than-perfect electronics and the enormous amount of data being transferred? Are the "headers" re-calculated" when the new file is written? If transient, when getting such an error, does Retro re-read the data to ensure that the subsequent read does not get the error?


Do tell. I would like to know more about exactly what this error means. I do not want to lose confidence in the media sets with this error. OTOH, if this IS a real error, I want to re-do the operation and/or track it down.



Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now