Per Synology, wireless Time Machine backup not supported!

[gd11_be]

And this time also the MacBook Air has shown the problem

1. (gd11_be - Belgium) - DS211 - iMac - Mid 2010 - Wired network
2. (gd11_be - Belgium) - DS211 - iMac - Late 2010 - Wired network - felt like happened after putting mac to sleep during TM backup
3. (gd11_be - Belgium) - DS211 - MacBook Pro - Late 2010 - Wifi -felt like happened after putting mac to sleep during TM backup
4. (Date: April 11th 2012) (gd11_be - Belgium) - DS211 - iMac - Wired network
5. (Date: July 20th 2012) (gd11_be - Belgium) - DS211 - iMac - Wired network - upgraded to DSM 4.1 Beta just before
6. (Date: July 29th 2012) (gd11_be - Belgium) - DS211 - MacBook Pro - Wifi - upgraded to DSM 4.1 Beta, felt like after putting mac to sleep during TM
7. (Date: August 18th 2012) (gd11_be - Belgium) - DS211 MacBook Air - Wifi

But then their might be light at the tunnle as I received the following message from Support ..

The only limitation is to setup one user account for one sparse bundle.
For example:
1. Single account for all PCs which is to setup an account (TM) for time machine backup and all PCs use this account for time machine service.
PC1 -> TM
PC2 -> TM
PC3 -> TM
2. Multiple account for multiple PCs which is to setup different accounts in DS for different PC.
PC1 -> TM1
PC2 -> TM2
PC3 -> TM3
However, if you mix up the two ways, some errors may occur.

?? I will reply to support with all my information, and ask them for guidance on how to set this up properly then.

[mackworth]

The only limitation is to setup one user account for one sparse bundle.
For example:
1. Single account for all PCs which is to setup an account (TM) for time machine backup and all PCs use this account for time machine service.
PC1 -> TM
PC2 -> TM
PC3 -> TM
2. Multiple account for multiple PCs which is to setup different accounts in DS for different PC.
PC1 -> TM1
PC2 -> TM2
PC3 -> TM3
However, if you mix up the two ways, some errors may occur.

?? I will reply to support with all my information, and ask them for guidance on how to set this up properly then.

How does scenario 2 work? As far as I know, you can only create one "Time Machine" on the network. So the scenario would be:

Mac1 (user1) -> <TMVolume>
Mac2 (user2) -> <TMVolume>

This is the scenario that I was using, and I still had it fail... (Latest gen macbook air, mountain lion, 5ghz wireless backup)

I am very close to just buying a Time Machine device from Apple.

[gd11_be]

Indeed, exactly ! I am also confused about their feedback. You can only create one Time Machine share, so I think the only possible solution is the way I have setup my system

One Directory
3 seperate Users, one per PC/Laptop, with its quota, and that create automatically the sparse bundles per PC/Laptop.

[mackworth]

Indeed, exactly ! I am also confused about their feedback. You can only create one Time Machine share, so I think the only possible solution is the way I have setup my system

One Directory
3 seperate Users, one per PC/Laptop, with its quota, and that create automatically the sparse bundles per PC/Laptop.

Yeah, I tried that, and it still causing the same problem. I honestly don't think its ever going to work. This isn't just a synology problem. If you do a google search, this happens with other brands that use netatalk...

[gd11_be]

OK, but does that mean that a Time Capsule from Apple does NOT use Netatalk? How can Apple then make it work? Just curious for the links to the places on the web where you can find back that also other brands have the same issue

[mackworth]

OK, but does that mean that a Time Capsule from Apple does NOT use Netatalk? How can Apple then make it work? Just curious for the links to the places on the web where you can find back that also other brands have the same issue

Apple invented AFP (Apple File Protocol) so they have a closed source solution that they use in their products. Netatalk has no relation to Apple, and had to reverse engineer AFP which is why there are issues like this.

Anyway,

https://discussions.apple.com/thread/36 ... 0&tstart=0 QNAP
http://forum.qnap.com/viewtopic.php?p=263661 QNAP
https://discussions.apple.com/thread/37 ... 0&tstart=0 ReadyNas

If just do a search for '"Time Machine must create a new backup for you" NAS' on google, you will see it all over the place for different companies.

[brickere]

I had no idea Time Machine was such a problematic (and hot) topic on here until now. I have some friends running a DS411 and they just got this same TM backup error message (and apparently it's happened a couple of times this week).

For my part, I've never had this issue. We're now using a Time Capsule for backup, but for about a year we were using a dedicated 2TB Caviar Green drive in a DS1511+ for TM backups. We have a 27" late 2009 iMac running Snow Leopard with a hardwire connection and never had an issue.

We are also currently running a DS211j at home which is handling backup for my wife's MacBook Pro (running Lion) and my MacBook Air (running Mountain Lion) and still I've never experienced this issue. At home we have an AirPort Extreme router, and the DS is running a JBOD config (3TB total I think, only about 250GB allocated for backups because we have small SSDs in our laptops).

I'm sorry to hear this is such an issue for you guys. I hope it gets sorted out soon.

EDIT: Actually I think I take it back. I may have gotten the TM message once on one of our laptops at home. I saw a screen shot of one and suddenly it seemed familiar, so disregard what I said before. But I'll keep an eye on it now and let you know if it occurs.

[Hansel]

Bought my first Mac (book pro) the other day, and have just run into this issue (Time Machine has been turned on for about 4 days all up, so it's happened almost straight away).

I'm using a 1512+ if that makes any difference (but clearly it doesn't).

Running wireless (which also doesn't make a difference as seen in this thread) and the backup is under the Admin account (not a unique account for TM).

Very, very annoying. I really don't want to have to spend another $400 or whatever on a Time Capsule just to have this work, especially when it's an advertised feature for my NAS.

[747driver]

Glad I found this thread!
Was about to buy a 412+ or a 1512+ to be used for Time Machine backups + other things.
Will reconsider my options...

[Hansel]

Well I've had to give up on it, it just keeps happening. Back to Crashplan I guess.

[747driver]

Did the OS X Lion 10.7.5 Supplemental Update fix the issue?

[Hansel]

I'm on Mountain Lion, but you'd assume the same fix would be present already for that.

[doug316]

How to fix your corrupted TimeMachine image:

http://www.garth.org/archives/2011,08,2 ... rrors.html

[anschmid]

Had the same problems on my Synology NAS but have solved it and I am now running backups since August last year and had not a single failure, even from a Macbook backing up over Wifi.

If anybody wants to try here are the steps:

1) Create a new share called "Backups" and make the owner "admin" (Apple TM server also use "Backups")
2) Do NOT select "Backups" as your Time Machine share (under Contorl Panel - Win/Mac/NFS - Mac File Server) - just leave it as "Not selected yet"
3) Go to the Mac you want to backup and via Finder mount the "Backups" share manually as "admin"
4) Go into TimeMachine preferences and selected the mounted "Backups" share as destination
5) You can now disconnect the manually mounted "Backups" share
6) When Time Machine wants to do it's first backup it will ask for user and password, enter "admin" and password - only needed one time it will remeber the credentials

That's worked for me and I don't have anymore issues.

Last hint is don't try to use an old TM sparsebundle. Just let TM create a new one the first time the backup runs.

[gd11_be]

Hi All,

Here is an update on my TimeMachine issues

1. (gd11_be - Belgium) - DS211 - iMac - Mid 2010 - Wired network
2. (gd11_be - Belgium) - DS211 - iMac - Late 2010 - Wired network - felt like happened after putting mac to sleep during TM backup
3. (gd11_be - Belgium) - DS211 - MacBook Pro - Late 2010 - Wifi -felt like happened after putting mac to sleep during TM backup
4. (Date: April 11th 2012) (gd11_be - Belgium) - DS211 - iMac - Wired network
5. (Date: July 20th 2012) (gd11_be - Belgium) - DS211 - iMac - Wired network - upgraded to DSM 4.1 Beta just before
6. (Date: July 29th 2012) (gd11_be - Belgium) - DS211 - MacBook Pro - Wifi - upgraded to DSM 4.1 Beta, felt like after putting mac to sleep during TM
7. (Date: August 18th 2012) (gd11_be - Belgium) - DS211 MacBook Air - Wifi
8. (Date: January 16 th 2013 ) (gd11_be - Belgium) - DS211 MacBook Air - Wifi - Related to DSM 4.2 Beta. Failed twice, clearly something broken in DSM 4.2 BETA in this area. Rolled back to DSM 4.1
9. (Date: January 17th 2013) (gd11_be - Belgium) - DS211 - iMac - Wired network - back on DSM 4.1 after DSM 4.2 Beta Fail