NVBackup failure...

Well it 'cured' itself. I hot-synced as I mentioned (to at least get my main data off the device onto my desktop) and then NV'd to another card. It worked fine. Then I tried just for the heck of it to try the 2 GB card again. It worked fine. I'll leave it as is for the moment.

Thanks for all the help.
 
It's been a long time since I have had to think about this.
I think the suggestions already mentioned are the best first steps but if they don't work then ....

Any new apps or changes to your LifeDrive ?
Is Wi-Fi Off when you make the backup ? (not sure if this will affect it but...)
If you have an older backup on the card that you can play with (doesn't matter if you lose it) then try doing an Update and see if that is successfull.

I believe the last (bottom) item you see on the NVBackup screen while the backup is happening is the last one that was successfully backed up and the 'problem' file is not shown yet.
To find the 'problem' file try this:
? Put the card in your PC (or check a recent backup you already have on your PC)
? Go to PALM > Programs > NVBackup
? Open the folder of a recent backup that was completed successfully
? Select View and select Details
? Select View again and select Arrange icons by > Created
? Click on Date Created to arrange them in that order
? Look for Lifedrive and see what is the next file under that

Good luck :)

All the best, woz of oz
 
I suggest you dive into the archive itself that NVBackup did and that you are now using. Try to determine if there is some element there named LifeDrive, in the first place. Cause if not, then I reckon that NVBackup is having a tough time restoring user metadata, namely Saved Prefs, that you already know are a common headache in Palm OS backups and syncs.
 
Regarding uninstall/reinstall, when you reinstall NVBackup to your device be sure that you also replace the copy of the app that resides on the SD card so that they are exactly the same file. In a new installation the app will ask if you wish to copy it to the card. This time you may not be asked if the app detects the existing copy already on the card. An easy way to handle this would be to select the app on the device and choose Copy to Card (if you aren't asked) and let the app be replaced with the new version. :)
 
Ah, OK. I though there was a proven diagnose or something. But you're totally right. It's a factor to consider.

Regarding these modern smallish storage cards, I haven't had that many, but IME, however limited, there's a couple of situations I've seen one time after the other, with my cards and those of people around me:

1. Whether a card works or not, it's all down to find out with a specific device. Sometimes the very same card will work with one device and won't work with another. Technical research of any reason is pointless, and all standards of sorts of the industry stop working at a given point, pretty much it's what my dad calls the malice of inanimate objects.

2. Within the un-reliability of small storage media, there is one factor I've seen 100% of the times, and conversely turns itself into a factor of reliability: if a card so wishes not to work with a given digital device, it'll do so since day one. Perfectly operational cards may show some "wear" throughout time (I'm not even sure if such a mechanical term applies here, but you get the picture), and therefore their performance may decay. But nonworking cards announce their reluctance to comply with some gadget since the day you pull them off the blister.
 
hal, although I can't think of a reason why it should matter, I've gone through enough trouble shooting exercises that I've learned to ask about anything that *might* be related -- 99% of the time, it's not, but then that helps rule out possible factors.
 
Thanks for all the chiming in.

I haven't tried it with a different card yet. I want to hotsync as a fallback first.

I typically backup to a single, 2 GB SD (not SDHC) card, and then manually copy those files to several different places (laptop, desktop, NAS, and a backup card). I don't backup directly to my 4GB non-standard SD cards because a) they don't read on my laptop for some reason and b) since they're non-standard, I think of them as 'less reliable,' although they haven't been so far. (I've been too lazy to set up Jig's FTP backup and the other fancy things I've seen described.)

As for the file, it stops at the same point: The line item is 'Lifedrive.' I don't know if that means the whole hard drive on the LD though. There are a few other items with 'LifeDrive' in the name.

I did soft-reset a few times; but it didn't do anything.

I think Lelisa is probably right. I'll have to probably uninstall and reinstall it. Are there any caveats I should know about?

Rick: By the way, I haven't tried that emulator yet. That's why I was going to do an extra backup before loading it.
 
I suppose it is possible that there is a specific file which causes the freeze; if you can move it out of the main memory (just to test) and backup successfully, that might be useful to know. of course, this shouldn't happen, so Lauren's idea sounds good to me, as does Hook's.

and just "for the record" is the card SDHC?
 
The first thing that occurs to me is to remove/reinstall NVBackup with a soft reset between actions. Your previous backup sets are saved on the SD card so they're safe. Others may have more ideas to try.
 
This is the first time this has happened to me. I went to do a full manual backup (no compression, with checksum).

It seemed to hang about half-way through. The Lifedrive had a full charge and the SD card had plenty of room. I soft reset the device and then tried again. It hung at exactly the same place (I checked the line item).

I've never had this problem before in 2 years or so of using NVBackup. What's the next step?

Thanks.
 
Back
Top