While testing Autonomy Connected, I'm able to back up. I have not been able to restore email to a different machine. Are there limitations?

Hi Lenny,

Is there an email archiving solution in place? If so, the MUD folder may not need to be backed up.

Don

@donmontalvo, interesting post. We're also a Connected shop for Windows (since before HP and even Iron Mountain). We've been backing up Macs for a couple of years. We rolled out v8.6.4.2 a while back without issues
HOWEVER...
I just found out from my techs that we've never done a restore to another machine. I'd been backing up for a year and my SSD went belly up last week (flashing folder w/ "?" at boot). I rebuilt but have to figure out how to reinstall CNB and restore with my old account number, which I do have. Do you have any words of wisdom or command line options to share? Thanks.

@evarona wrote:

I just found out from my techs that we've never done a restore to another machine.

Part of designing/implementing a backup solution is ensuring backups actually work. I'd get a paper trail going on this, to ensure the team responsible for the solution have a true backup (and restore) system in place. ;)

"Because it's the Restore That Matters." - Tim Jones (TolisGroup CTO)

Don

Thanks Don. Unfortunately, I have no say over design of this system but agree with you. Fortunately for me, my CNB admin came back from holiday today and pointed me to the "Reinstall Agent" option of the service center. Worked like a charm except that the app is not "Apple or identified developer" signed so I had to bypass GateKeeper. I've asked if the vendor can provide a signed version that is compatible. Let's see what comes back.

Thanks.

Emil, As long as Autonomy build the .pkg on a windows server I don't think they can sign the installer. We have to manually download the .pkg and script the install for our techs.

C

Hello everyone, i hope y'all had a great weekend. I wanted to post this here even thou it is not a JAMF related issue but it has to do with Connected Backup, and seems most of you have used it.
The application works great for the first few months, after a while there's something in the system that is triggering the connected backup to fail within the first 5 to 9 seconds. When i check the logs the only thing i get is:
-Failed to detect separator in CFilePath Constructor for path 99
-CProtocolSessionQueue::Run() caught an unexpected C_CEexception.
I have a case opened with Autonomy already but they haven't been able to figure out either were the point of failure is.
Up to right now the only solution is to re-image the device, but i would like to get to the root cause of it. Not everyone is very happy with a re-image.

Any advice would be greatly appreciated

Resurrecting an old thread, but would some you mind detailing how you were deploying this? It reminds me of Mozy were you had to have codes, etc..

@jhbush1973][/url In one large multimedia environment ("Why so serious"), we deployed the PKG as-is, and users had to launch and enter their credentials for the server to set up backups for that Mac and for that user to "own" the backups.

In one large retailer ("Giant Sinking Ship") we set deployed with a bit of scripting and launchd stuff, to capture the username and automagically configure the agent for that user, transparent to the user. The challenge we had was the Mac enviroment appeared to never have been fully migrated from forest to domain, so user accounts varied from CORPjdoe to CORP jdoe to ACMEjdoe to ACME jdoe...to the desired jdoe. So we had to move their Macs over to domain first (we scripted that too), so everyone was logging in with jdoe short name, then allow the configuration to happen.

I need to sanitize the info before posting, the usual proprietary info concerns, but happy to chat offline if you need this now.

We are starting to have problems with mac client verison 8.6.2 ever since our users installed the Mavericks update of 10.9.2. Our windows clients backup fine so i am going to have to open a ticket with support and find out what is going on. I personally don't like the product at all. It fails constantly on windows and osx . They always have network issues and i don't its a great product just forced to support it. Anyone have a clue all of sudden its failing, could it be the ssl fix they included in the update? Apple could've patched that security hole.

@jcavallino][/url I haven't seen issues here with 10.9.2 outside the usual errors when backing up. Autonomy fails if you have certain files open or apps. We use the hosted version of the solution. We aren't LDAP integrated, but I'm working on that at the moment. The code and extra accounts that need setup just to backup is crazy. I would love to switch to Crash Plan PROe, but that may have to wait until next year.

@jhbush1973- I hear that. But we are a AD and just client side macs and i have casper running for the mac side but on a windows server. So connected serves 90% of the windows side but the mac side is probbally at 10% right now.I just need to know if there is a newer verison for connected than i can deploy that. Do you know which apps are mainly affected when connected is open and trying to backup? That would be awesome

@jcavallino we are running client version 8.8.0.2 of Connected Backup for Mac. I see the backup errors with Outlook the most.

This discussion seems to be the most relevant place to link the post my colleague made regarding Connected Backup and Java and then some. I'll link it here with hopes that it's helpful to others using this same software.

Connected Backup, java, and some lousy version checking code

@makingtortillas thanks for posting the link to your husband's thread, interesting information.

@jhbush1973 not sure if you guys updated to 8.8.4, but if you did, do you still get backup errors when Outlook 2011/2016 is open?

@jarednichols had a valid point, why bother to backup Outlook 2011/2016 data. Unfortunately not all companies have an email retention policy forbidding local archiving in Outlook 2011/2016. And Microsoft haven't provided a management option to dis-allow. So for legal reasons, some companies have a mandate to backup the local archives. Which, unfortunately, is all flat files, inter-mingled with local cache of Exchange email.

Don

@donmontalvo we are using 8.8.3 and I believe the issue is resolved, but a new client is expected shortly from what my HP TAM told me.

8.8.4 is out and includes embedded Java. Not that it makes it any less sucky. CrashPlan is still a much better solution.

Anyone know what is the proper method to kill the Connected Backup process?

The usual loop script doesn't seem to work, complains that Connected Backup process is not running when it is.

We found that killing /Applications/Autonomy/Connected Backup/Connected Backup.app/Contents/MacOS/JavaAppLauncher kills the Connected Backup process.

But I seem to remember that could cause problems if any other Java application is running that users JavaAppLauncher.

Thoughts?

Circling back, it is indeed the JavaAppLauncher process we need to kill, as per the vendor.