Arcserve error E1056 Invalid file header when trying to merge a tape

We are running Netware 6.5 SP5 and Brightstor Arcserve 11.1 with SP2.  We are trying to get our disaster recovery working correctly.  We have run a backup at our corporate office and then we have sent the tapes to our disaster location.  When we put the tapes in the remote server, we are able to scan the tapes, but when we try to merge the tapes into the database, we receive the error:

"Failed to find catalog file."
"E1056 Invalid file header []  signature=5555aaaa"
"Recover file"

And the merge never merges any information into the Arcserve DB.  I then decided to check and see what happens if I try to merge a tape on our Corporate backup server.  A tape that we backed up at the Corporate server, can not be merged on our Corporate server either.  It kicks back the same error, even though it was the server that originally did the backup.

Anyone have any ideas on how to solve this problem?  Computer Associates had me place this line in my ASCONFIG.INI


That seemed to resolve the header issues, but our Merge took 16 hours for a 200/400 GB LTO Tape.  That can't be right.  I can't believe that a special setting needs to be in the ASCONFIG.INI file in order for me to merge a tape.

Who is Participating?
Nilesh RoySenior Manager - Technology ManagementCommented:
Hi Mike,

Try this, your path may be a little different but under Base it will be the same.

Open regidt32.exe
Go to HKEY_LOCAL_MACHINE on Local Machine
Open it to
Highlight Task and select Edit Add Key from the menue bar.
Key Name: Merge
Class: <leave blank>
Hightlight Merge and select Edit Add Value
Value Name: DonotUseCatalogMerge
Data Type: REG_DWORD
click OK
Data: 1         *// 1 = Enabled, 0 = Disabled

Let me know if it worked.


Nilesh Roy.
michreynAuthor Commented:
This is running on Netware, but I would think it essentially does the same thing that the entry "MergeUsingCatFile=False" seems to do.  I am beginning to think that there is no Catalog file in Netware.  Can anyone verify that?
The database information is written to a catalog file, the catalog file is written to tape as the last file in that session. Merge will restore that file and then merge the data in it into the database. That fails so the ini hack forces it to read through the whole session to build the  database information and that is why it is so slow.

The problem could be that either the file header really is invalid or it failed to position the tape to the correct location. In either case you will have to go back to CA support to track that down.

First check out to see if this with all sessions. Does it happen with sessions backed up via an agent, or local backups with no agent, these type of questions will help narrow down the nature of the problem.

What about the DR site, does it have the problem? don't know? so Have them run a small backup and try the merge to see if this problem is universal or server specific.

Also try a backup with Verify Compare enabled.

If you do decide to go back to CA on this, you don't have to open a new issue, just reopen the old one since they gave you a temporary work-around and not a solution. You know India support is all about the #s so they are quick to close issues, and it is not just CA I worked with support from other companies and it is always the same. So reopen the issue and push for it to be escalated state side.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.