Invalid Data was Encountered in the Backup Data Stream

[ChrisTyrrell]

I've been using an Onstream DI30 for at least 3 years updating the Echo software as and when they've been posted. Since I've gone to WindowsXP home and therefore 1Safe Echo 3.6 and, more lately, 1Safe Echo 3.7, I've been seeing a lot of 'Invalid data was encountered in the backup data stream' messages against drive T:\ which I never saw in Win98SE. Now, I operate a weekly backup using two cassettes swaping them each week and during the week doing modified files backups. When I went from Win98SE to WinXP home I kept the latest Win98SE cassette and bought a brand new casseete. Both the old and new cassettes are associated with this invalid data message. Has anyone else encountered this?

 

[novascotia17]

I too have a problem on my OSX system backup using an OnStream FW30 unit, that gives me the same error box.

Did you ever find a solution to this Chris?

 

[ChrisTyrrell]

No, I haven't. OnStream's telephone technical support line seems to have colapsed, at least in the UK, and so does its on-line technical support. I'm told this is because OnStream has filed for bankruptcy for a second time. In any case I contacted 1Vision since they're the ones who wrote the software and they told me to check the suspect files by chosing compare files via the restore feature. I've found that my suspect files compare well doing that. That's cumbersome and they've told me that they're looking into it. I've found that a modified files backup straight after a computer restart, or a full backup, doesn't give rise to this error. But a second and subsequent modified files backups do. What do you find novascotia17?

 

[novascotia17]

I use a Media 100 video editing system, and need to back up my projects. That's a lot of data. I think, as you say, I will shut down, and after restart, only back up a limited amount of info. If that small portion works, then I will try 3 gigs of info. Since my projects are close to 20 Gigs, it takes awhile to finish, once started. Lemme get back with you on this with the results.

 

[novascotia17]

Well, for a bit it worked. (your suggestion of backing up immediately after restart) I initially backed up half a gig of info, and it worked fine. Execution Complete. Same with 1G of media. So I jumped to 2gigs. Alas. Error box with a long list of problem files. After each back up, I shut down, waited, restarted, and selected the files needed. I think it is time to switch to a new system ... perhaps AIT backup. That's it.

 

[ChrisTyrrell]

Actually, what I've been doing is switch-on the computer, do some work and then a modified files back up. Each week, I change cassettes and then do a full backup. That way I haven't had any 'Invalid data was encountered in the backup data stream' messages.

Maybe those new messages are real. Try doing a compare files manually by starting a restore now, selecting the backup media currently in use, navigating to one of the files against which an 'Invalid data was encountered in the backup data stream' message is associated, select it (you need to tick the little box) then click NEXT. You will be presented with a message box entitled 'Restore options'. Check 'Compare files with originals (Don't restore)' and then read the log. If the error messages you've been seeing latest are phantom the manual compare will report a good compare. If the errors are real, then even the manual compare will report an error in the log.

Please let me know how you get on.

 

[gwootton]

Alright, I'll be the one to break it to you. 1Safe and Echo must be some of the worst software ever made. The ONLY advantage is having drive letter access to the drive, and that makes the access time really long. As far as these 'invalid data' messages you've been getting, make sure you're not backing up over ANY sort of network, since 1Vision's software is not good at handling network permissions. If you aren't, I would recommend trying with XP's native backup application (ntbackup) just to see whether it works in that. If it does, you know you have a software problem, if not, it's more than likely a problem with the file, or possibly that the file is being accessed by something else.

-Greg