Now that Crashplan forces you to bass a UUID from the server to the client things are a bit more complicated.
One complicating factor is that even though I got everything working with the latest everything a few weeks ago I tried to fire up my machine and do a new backup and hit a snag.
After some digging I found out that if I simply restart the crashplan service within the jail the .ui_info file gets overwritten and the UUID changes.
(How to reproduce)
service crashplan restart
cat /var/lib/crashplan/.ui_info
service crashplan restart
cat /var/lib/crashplan/.ui_info
I assume that my problem is that my client no longer has this UUID.
My question:
How do I keep that UUID (and preceding port) from changing?!
One complicating factor is that even though I got everything working with the latest everything a few weeks ago I tried to fire up my machine and do a new backup and hit a snag.
After some digging I found out that if I simply restart the crashplan service within the jail the .ui_info file gets overwritten and the UUID changes.
(How to reproduce)
service crashplan restart
cat /var/lib/crashplan/.ui_info
service crashplan restart
cat /var/lib/crashplan/.ui_info
I assume that my problem is that my client no longer has this UUID.
My question:
How do I keep that UUID (and preceding port) from changing?!