Daniel

I found some java exceptions in service.log.0 and entries saying “corrupt FMF entry” which sounded like corrupt cache.

So I’ve deleted the cache, restarted CrashPlan and this time in synced much quicker. Now it’s backing up 200GB, which means it found other other 800GB.

Ticket opened with CrashPlan support, but so far they have been far less…[Read more]

That’s the problem, on CrashPlan site it shows my NAS as 0MB and 100% complete. So it looks like CrashPlan deleted all my files on the site, and I’m afraid it might do the same on the NAS.

I’ve stopped the package for now as I’m not sure what it’s doing. I could just remove the backup and let it upload 1TB of data, but seeing this has shaken my…[Read more]

Um guys, I’m starting to worry at this point about the safety of my data.

I got CrashPlan working finally, and thanks for all your help. But now it’s stuck at synchronising and it shows 1 file and 0MB of data. I had 1TB of documents and photos that are irreplaceable.

Is it possible that CrashPlan is deleting all my data now?

I logged into…[Read more]

Wow! Nasty move on part of CrashPlan.

I’m glad I spent the few extra bucks on the “+” version of Synology with Intel CPU.

Well, I found out the cause why my Crashplan was just endlessly scanning and never backing anything up, and it had nothing to do with DSM or Crashplan updates. I even opened a support ticket with Crashplan and did they help? No, for sure not, how could they possibly know what is wrong 🙂

My license has expired! I only found that out after…[Read more]

Ok, after CrashPlan throwing a spanner in the works by pushing an upgrade that broke everything, I’m back on track. Still no backup, back to compacting.

No errors in the service log, scanning works, but crashplan will not back up anything. I hope this time compacting will complete before they release another upgrade 🙂

Hi,

I can confirm the fix #1 worked for me. I didn’t have syno_package.vars anymore, so I created a new file with just the USR_MAX_HEAP setting. I don’t remember if there was anything else in this file.

It seems to be scanning and synchronising, so I guess it’s ok. The upgrade happened in the middle of compacting the backup, and I didn’t have a…[Read more]

Is there any way to block the upgrade? Reinstalling the package seems to bring a working version, but then when you stop and start the package it gets the upgrade which destroys the installation.

I’m on DS412+ which is Intel Atom D2700, so x64. It doesn’t help.

Also, the jar file is deleted during the upgrade, so I can’t even manually do it.

The whole /volume1/@appstore/CrashPlan/lib/ directory is missing!

It seems that the upgrade script downloads a new version of java (1.8) and then messes up the install.

I’d post the log, but I get error 403 forbidden, so the site must be really unhappy about some characters in the log file.

Anyways, it cannot find the backup engine. I tried uninstalling CrashPlan and Java7, then installing Java8, and then…[Read more]

It seems that the upgrade script downloads a new version of java (1.8) and then messes up the install.

Increased Java heap size from 1GB to 1.5GB (never had any problems) and did the compacting yesterday.

Still not working. I think all compacting did was remove the version history, so I won’t be able to restore previous versions of my files in case I need to. 🙁

Next step is to delete the cache tonight, and then I’m out of options.

I’m using the…[Read more]