VisorCentral.com (http://discussion.visorcentral.com/vcforum/index.php)
- Springboard Modules (http://discussion.visorcentral.com/vcforum/forumdisplay.php?forumid=10)
-- backup module problems...can anyone relate? (http://discussion.visorcentral.com/vcforum/showthread.php?threadid=13147)

I'm on my second backup module for my Platinum already. The first one was defective and had to be returned after I tried everything including a Visor replacement. The second on I have _seemed_ to work fine for some time & I actually used it to do a restore once. I recently had a hard reset and tried to use the backup module for a restore. I got 2 garbled to-do entries in place of my 100+ existing entries. The record count in the info screen showed the 100+ records, but they wouldn't display.

My question is: Does it make sense for a backup module to "go bad?" why would this happen?

I removed hackmaster (I used the backlight hack) and still have the problem.

I removed SilverScreen (I was told alternate desktops that hijack the PalmOS's startup _may_ cause problems by Handspring tech support) and still have the problem.

I'm using the Lotus EasySync conduit to sync my PIM info w/my corporate Notes account. I hope this isn't the root of the problem b/c I really need this ability & cannot sacrifice it just to get my backup module to work.

I'm going to get a replacement unit, but if I can't rely on the backup working when I really need it, what's the point?

Has anyone else had a similar issue that they've come to grips with? I'd like a solution or my money back from Handspring (I bought the original module 5 months ago) so I can pursue an alternative (mempplug, perhaps?)

Thanks & regards, all,
-Jake

I can relate...

jakemonO

I have had only one problem with the backup module(s) since I got my first visor 1 and 1/2 years ago. But that one problem was a doozy.

Ever since I got my Minstrel S modem I have been having occasional crashes. Sometimes the well known problems, sometimes the crashes were things I had never seen before. So, I had gotten into the habit of backing up to the backup module before I inserted the modem. And in case of a crash I could easily restore my Prism without loss of data. I lost track of how many times I have had to perform the restore routine. Needless to say I believe in the backup module because it has saved my arse on more than one occasion.

But about two weeks ago my opinion changed (slightly). It had been about a week since I hotsync'd with my desktop and I wanted to use the modem so I was preparing to back up my system first. I pulled out the current module (Pocket Express) and my system crashed and went into the flashing Palm screen that I have come to know so well. Without even thinking about doing a 'warm reset', I pulled out the stylus and did a 'hard reset' knowing that I could restore from my last backup from the backup module. However, when I put in the backup module it reported that the backup module was 'empty'. This could not be?!? I called Handspring to find out what was wrong, why couldn't the Prism read the backup module that had worked so many times before??? After a painfully long talk with Handspring and after 'checking' the backup module in a Visor Deluxe that I had, I came to the conclusion that the module had failed. Thus began the painful process of restoring all of my lost data.

I had relied on the backup module time and time again, and this time it let me down.

I have since rebuilt my Prism and purchased another backup module to use with it. But since Handspring didn't want to close my case until they found out what happened to the original backup module, I decided to try it one more time. Backup the Prism to the backup module that had failed. Hard reset my Prism and then restore it from the backup module... This time it worked!!!

My only clue at this time as to the cause of the original failure was that for some reason my battery indicator was not moving and I had not realized how low the charge was on the battery. I suspect that the Prism did some sort of power save while trying to backup to the module, and in the process corrupted the backup.

I have since removed all 'hacks' and have upgraded all of my commercial software and have not had any more crashes.

In short... if it is electronic it can fail. But I still believe in the backup module.

I have found out the hard way that the backup module doesn't work with some mail/calendar/todo/address/memo conduits.. specifically Lotus Note's Easy Sync conduit.. If I have to restore my visor from a hard reset with the backup module, all I get in my email, calendar,addressees, memo's and to-do's is just garbled junk..

The only solution I have found to fix it is, when I back up my visor with the backup module, to then (manually) put a copy in (any) springboard that has flash memory a copy of the following files: SyncMailDb, SyncCalendarDB, SyncMemoDb, SyncAddressDB and SyncTODODB files. When I restore from the backup module, afterwards, I then have to copy these files back (manually) from the module that I copied them to previously.

__________________
"One of the most important things you learn from the internet is that there is no �them� out there. It�s just an awful lot of �us�." -- Douglas Adams

I also have had one instance when the backup module showed to be empty when I know that it had data in it. Maybe the chip they use lost power briefly once or twice. I had to rebuild my Prism and then back up again.

The solution for this is to use BackupBuddy. It is a hard drive based backup so it can not get lost unless your drive goes kaput.

__________________
Jeff Schaffer
[email protected]

In my case it restores everything, except the items mentioned above (mail, calendar, to-do's, memos, addresses), all other programs & etc are fully restored.

__________________
"One of the most important things you learn from the internet is that there is no �them� out there. It�s just an awful lot of �us�." -- Douglas Adams

EricG

I have the same exact symptoms, although I get some PIM db's back and some not. It's weird and inconsistent, but I never get everything back usually 2 or 3 out of 4 PIM db's. I remember now that I also cannot do a succesful HotSync restore either from the backed up Lotus db's and I have to remove them & resync. So I guess this is a EasySync bug and not purely a Backup module bug. This concerns me and I emailed this thread to Visor support and Lotus support. Unfortunately, [email protected] returns an error that multiple people in the organization have this address so the mail will not be delivered! If you know of a contact at Lotus, send them this thread & see if we can get a response.

Regards,
Jake
PS I guess I'll try getting a memplug & backing up that way.

I've ordered a MEMPLUG and I am hoping that this fixes my problem.. Incase you didn't know, the memplug also has a backup module like backup function.. I asked about backing up of these "SyncDB" files and the memplug module developer seems pretty confidant that I shouldn't have any problems.

As far as who to blame with the Handspring backup module issue, I'd say Handspring.. they need to address the issue with the backup module's software. Their software is obviously missing files either during the backup or the restore process.

__________________
"One of the most important things you learn from the internet is that there is no �them� out there. It�s just an awful lot of �us�." -- Douglas Adams

Let me know if the memplug works...

EricG,

I would appreciate if you kept this thread posted on whether the memplug does the backup job for you.

Thanx,
Jake

Before you use the backup module....

I learned this the hard way, as did some others on this group.

Before you backup your data using the backup module, make sure that you have enough power in your batteries.

I was doing a routine backup one day, and suddenly my VDX crashed. I had never seen this problem before. When I tried to reset, it wouldn't work. I had to do the HARD reset that would erase all the memory from the Visor. When I checked the backup module, it was empty.

Handspring tech support confirmed this, so I was SOL. Empty visor and empty module.

This disaster could have been prevented by just checking the battery charge and making sure I had enough charge.

Trust me on this one....don't find out the hard way!

Mike

__________________
Million Dollar Bills, anyone?

<a href="http://www.millionbill.com">www.MillionBill.com</a>