Reply
Highlighted
Posts: 5
Registered: ‎12-21-2011

E4200, Lion and Time Machine backup

[ Edited ]

Hi there!

 

Sorry if I'm double posting this, but I didn't find any posts of this thread.

 

Since lion is there for a while, it is still not possible to make a time machine backup on an USB hdd that's connected to the router. 

 

Is there a fix or workaround for this? Or is Cisco coming with an firmware update?

 

Thanks in advance!

 

- Michael 

Posts: 5
Registered: ‎12-21-2011

Re: E4200, Lion and Time Machine backup

Anyone?

Posts: 3,012
Registered: ‎09-07-2006

Re: E4200, Lion and Time Machine backup

What is the version of Cisco Connect Software that you are using. Older versions of Cisco Connect for Mac computers have compatibility issues with the latest release of Mac OS X (10.7 “Lion”). Only Cisco Connect versions 1.4.11222 and newer are compatible with the Lion operating system.

 

Check the link of the devices that have this update: http://www6.nohold.net/Cisco2/ukp.aspx?pid=80&vw=1&articleid=23897

 

So download the latest firmware and the Cisco Connect software to install.. Here is the link for setting for setting up the router - http://www6.nohold.net/Cisco2/ukp.aspx?pid=93&login=1&vw=1&app=search&articleid=21463&userrole=Links...

Posts: 5
Registered: ‎12-21-2011

Re: E4200, Lion and Time Machine backup

Hi,

 

First of all, thanks for your help!

 

But I've already installed the newest version of Cisco connect. And I can access the hdd. But every time I want to connect Time Machine with this hdd I'm getting an AFP Error. "The network backup disk does not support the required AFP features."

 

I read something about that Lion doesn't support "DHCAST128" anymore.

Posts: 3,012
Registered: ‎09-07-2006

Re: E4200, Lion and Time Machine backup

What is the file system that you have on your HDD connected to the USB port of E4200? I believe, to take the back through timemachine, the minimum requirement is to have a drive formatted in HFS+.

Posts: 5
Registered: ‎12-21-2011

Re: E4200, Lion and Time Machine backup

Yes. It needs to be HFS+ formatted. I tried it with 2 partitions on the hdd, HFS+ and NTFS. I didn't try it with the whole hdd partitioned in HFS+ though. Should that be it? I will give it a try in the next days! 

 

Thanks for your help Smiley Happy

Posts: 3,012
Registered: ‎09-07-2006

Re: E4200, Lion and Time Machine backup

The MBWE uses Netatalk to support AFP, and Apple has recently changed AFP, which caused it to stop working with this device and lots of others that also rely on Netatalk. Here is the link which will help you

http://community.wdc.com/t5/WD-ShareSpace/Mac-OS-X-Lion-and-AFP-compatibility/td-p/218420

Posts: 1
Registered: ‎03-08-2012

Re: E4200, Lion and Time Machine backup

I know, late to the party... But was wondering if anyone had any success in connecting an HFS+ formatted external HDD to the E-4200, and being able run Time Machine backups against it?

 

Now, off to continue my apparent endless search for answers to this mystery ;-)

Posts: 5
Registered: ‎12-21-2011

Re: E4200, Lion and Time Machine backup

Couldn't they just update the E4200, so that it works with tm on lion? Other companies did it, so why won't cisco do it?

Expert
Expert
Posts: 12,649
Registered: ‎07-16-2006

Re: E4200, Lion and Time Machine backup


@fernandoe wrote:

I know, late to the party... But was wondering if anyone had any success in connecting an HFS+ formatted external HDD to the E-4200, and being able run Time Machine backups against it?


The disk does not have to be HFS+ formatted. The disk must be formatted in whatever format the NAS, i.e. the E4200 can handle.

 

Time Machine saves backup in a sparsebundle on network drives. A sparsebundle can be written on any formatted drive. Doesn't have to be HFS+. I do time machine backups on a NAS with ext3 formatted drives...

 

As mentioned before: the problem is with AFP the protocol to access the network drive. AFP is required to access the network drive and if that doesn't work you can't do the backup. You'll have to wait until Linksys fixes this...