Sachesi has stopped working about sachesi HOT 13 CLOSED

The sizes not showing up is a Blackberry bug and very normal for large backups, which is why I recommend backing up 'blind' (not checking size).

There are other Blackberry bugs with backing up like the app-specific issue you discovered and the 4GB limit for each type.

I suppose I could show each app that is currently being backed up and that would resolve your issue?

from sachesi.

Ah, the problem is I do not know what the apps are without first checking size (which won't work and is probably why you are using Sachesi in the first place).

Sorry, seems to be a Blackberry bug I can't fix.

from sachesi.

Well, as I said in my original post, the sizes do show a few seconds after I click OK most of the time. So it might still be worth trying to display the app name while backing up.

Another tidbit of info, I tried it on another Win10 computer that had a newer ucrtbase.dll because I installed the Creators Update. On that computer the backup seems to complete, but not every time. The reason I say "seems" is because the one time I was there to watch the end, it was at 70% (settings 100%) and then the progress information simply disappeared. It didn't say the backup was complete or anything else.

I tried it again and the 2nd backup is exactly the same size (but I didn't see the end). Trying it a 3rd time and it failed (I didn't see) as the backup is half the size.

Any information you could add to the display would be helpful. If you display a percentage (as you are currently doing) then you must know how big it is going to be, right?

Thanks for your help.

from sachesi.

The device sends me a percentage only during backup AFAIR.
I only know size if i query it (which doesn't work for many people).
If querying size works, Blackberry Link should also work for you.

from sachesi.

I understand what you are saying. But Link is extremely buggy (more so on Win10, for which it has never been updated). At least Sachesi is still being updated, thanks to you. If I attempt a backup, it fails while computing backup data (after about a minute or so), saying "Backup did not complete. Verify that your device is turned on and connected to BlackBerry Link, and try again".

The message is so bogus it's not even funny. I wouldn't be able to start a backup if the device wasn't connected. And on top of that, I can do a Sync Calendar/Contacts so Link is obviously communicating with the device.

This got way worse when I upgraded my computer from Win7 to Win10. So I suspect a timing issue aggravated by Win10. I have to find a computer that still has Win7, just to check that theory. In the mean time Sachesi is my only savings grace, in the long run.

As I said, on Win10 Creators Update, Sachesi seems to have completed a backup. The size is a bit larger than the last successful backup with Link, which makes me think it's ok, but Sachesi was advertising a 7.6GB backup and the file is only 5.1GB.

Does Sachesi say something at the end when the backup is successful? Or does the percent display simply disappear?

Thanks for putting up with me on this.

from sachesi.

To be fair, the problem isn't Link itself but the devce and assumptions made by Link. When querying the size, the device attempts to create an actual zipped and encrypted backup of all your files and then report its size to you. When this times out (due to http timeout on your OS), it is reported as no reply and disconnection so the device can never report that size. The main failure is no progress updates.

If you are able to update the timeout somehow it would work better in Link but I have not investigated this too far. My attempts in Windows did not change the timeout. The device itself does not timeout.

I think if the backup is over 4GB, it will never succeed in Sachesi due to a limitation in my zipping third-party library (Quazip). It tries to write but writes to the wrong offsets. The backup would have been successfully read off the devoce, hence the success message.

Sachesi reports success when percent becomes 100 AFAIR.

from sachesi.

Oh oh, so you are saying that my backups cannot work with Sachesi, and never will, since they are over 4GB (currently 5GB)? That's too bad. If so, then would you consider switching to a newer library that supports file larger than 4GB?

I made a 5GB backup yesterday with Sachesi (still not sure whether it was complete). Are you saying that garbage is most likely garbage?

from sachesi.

If it told you it is 7GB, I would expect a 7GB file.
If it said success and gave you a 5GB file, in my mind, that would be the quazip bug.
I have tried to track down the >4GB bug before but couldn't find the issue. This was 2 years ago I think so QuaZip may be improved now (or not). It could certainly be worthwhile switching to something else.

from sachesi.

Did you check whether the backup is valid? Can Link see it?

from sachesi.

I just tried. As soon as I click on Restore, and therefore before I can even select which backup to restore, I get "BlackBerry Link has stopped working". Tried it 3 times. This is scary. I really need a Win7 computer. I am building a VMware image of Win7 right now to see if that will help (I don't have a free computer to wipe and install 7 on right now. They are all on Win10 already. So disappointing that BB never saw fit to upgrade BBLink for Win10.

from sachesi.

Hi Sacha,

As I write this, I am doing a backup of my Z10 using BBLink in a virtual machine running Win7. The same Z10 and BBLink that would fail in Win10. So it is obviously something in Win10 that broke Link.

The backup started with a temp file (.dtmp) of 7.3GB, size consistent with what Sachesi was announcing. The size of that file is continuously decreasing in size as the backup progresses. So there must be some compression going on. The reason I am saying this is that the 5.4GB backup that Sachesi created a couple of days ago might be fine. I will have to test if I can open it from Link in Win7.

Will keep you posted. It feels good to see a backup going :-)

from sachesi.

Ok. Thanks for the update.

from sachesi.

Update: The backup completed. Trying to restore anything still resulted in Link "has stopped working", even in the Win7 virtual machine. At first I thought it was because I was accessing the backups through a share. That was not it as copying them locally didn't help. So I renamed the extension of the two recent backups, the one done with Sachesi and the one just done with Link in the VM. Link no longer crashed. Renamed the Sachesi backup back and it crashed again. So that was the reason. Probably the >4GB restriction or something. So deleted the Sachesi backup. Back to using shares, I can read the latest backup (or even the older ones from 2 months ago) from the VM image, even when the backup files are on a share.

Back into Win10, Link no longer crashes when trying to restore (since the Sachesi backup is gone), but it still spins indefinitely while "Loading the restore content...".

So Win7 in a VM is the only reliable solution for me. It's apparently a timing thing since Link in Win7 is so fast at detecting and connecting to the device, whereas it's hit and miss in Win10, it can take 4-5 tries before being successful at connecting if at all. And it takes several minutes when successful (vs seconds in Win7).

Last, I tried running Link in Win7 compatibility mode under Win10. The restore is still spinning on "Loading the restore content ..." after 15 minutes. Not good.

So, looks like I can rest easy again knowing I can make backups of my Z10. But that solution (a virtual machine) is not for everyone. I hope someone can benefit from this exchange of the past couple of days. I think you should still look into updating the Sachesi library. Thanks.

from sachesi.