Ver 6.4.2 RC1 - changelog items relating to Time Machin backup?

[janpeter1]

Hi

I struggle with backup from Time Machine to ReadyNAS 314 with firmware 6.4.1.

Just wonder if here is something in 6.4.2 RC1 that may help. 

I read the changelog and try to interprete itiem: 3, 4 and 15 and would be happe

if some could say that these changes have a positive effect on stability of performance

of Time Machine backup.

For long time (both with 6.2.x and 6.4.0 and 6.4.1) the backup

get corrupt after 4-6 weeks. Right now it does not work at all for one Mac (but does with 

work with another newer Mac - still same OS X 10.10.5). 

I discuss something of this issue on other thread, and here I just want to know if an

upgrade to 6.4.2 RC1 likely would help.

[mdgm-ntgr]

Can you send me your logs (see the Sending Logs link in my sig)?

How are your Macs connected to your network? Are they connected via ethernet or Wi-Fi?

[janpeter1]

I just sent the system loggs to you together with some explaining text

and screenshoots of the Mac.

The problem occurs with Mac mini connected with LAN-cable.

Sometimes I do connect over wifi (or both). 

I have also tried now to connect the NAS direclty with ethernet cable direcdtly 

the Mac mini but get the same error message.

I have no problem to continue doing backup to a seperate external USB-HD
just coonected to Mac mini. For me this indicates that the problem is by the NAS.

Somehow I think the TM sparsebundle has been corrupted. 

Other times during the fall with ReadyNAS314 I have gotten a message that

the backup is corrupted and that I should do a new backup from scratch.

That message I do not get this timem though. As reported earlier in the forum

I have gotten this message about every 4-6 weeks and then I restart the backup.

Thus the external HD stands for the longer backup history, while the NAS takes

the shorter history.

Thanks

[mdgm-ntgr]

Please translate (roughly) the error message from the screenshot that you sent in the email.

[alexejCederholm]

I do have quite a similar problem with my time machine backup, I usually do the initial backup via ethernet as it is usally 130gb large. Then the incremental backups are performed via WiFi. It usually takes between 1-8 weeks before I receive the message that time machine could not verify the backup and that I have to start a from scratch.

At the moment I run 6.4.2 RC1, but I have had the same issue from many firmwares back.

Thank you in advance

[janpeter1]

Hi,

Mdgm - I sent you translation of screenshots I sent to you the other day.

Alexej - good to know that I am not alone with this issue!

Have you had 6.4.2 RC1 long enough to see the same tendency that TM backup becomes corrupt?

I just re-interpreted the error message from Time Machine about checking that the HD is ok.

I always thought it meant I should check the source HD, i.e. Mac mini in this case, and there everything ok.

But it couls alsoe mean to check the destination HD - and when I check the ReadyNAS HD with the specific TM backup

Mac OS X Disk Utility report that there is an error (in the destination sparse bundel) and the file system check has error code 8.

According to Apple this means some partitioning cannto be read - there is also a warning about index key is not ok that came just before

when running the Disk Utility. Finally the recomendation from Time Machine is to "Repair" the HD using the Disk Utility.

I really hesitate to press the button for reparing the TM backup on the NAS since it is another filesystem there (BTRFS) and

also I suspect that the repair may do something on a lower level than the files. I talked with Apple support about this case

and managed to get someone on "the second level" and he confirmed that "repair" work on both file level and lower level

when it repairs and could not say what would happen if we use this funcdtion on an BTRFS-file system.

He also meant that EXT3-system is much, much more similar to Apples HFS+ system and easier to deal with.

The support person talked with colleagues and perhaps looked in som data base but could not quickly find

any similar report as mine. The person new about Linux and various distros somewhat but did not know BTRFS at all,

but could relate to EXT3.

Just also to check I also run Disk Utility on another TM backup for another Mac where I have no problem

and yes Disk Utility finds that sparse-bundle ok - and I get a final green line saying as usual that the disk is probably ok.

So my question to Netgear and this fourm is - what will happen if I do "Repair" with Mac OS X Disk Utility on the 

Time Machine sparse-bundle on the ReadyNAS (running 6.4.1 at the moment)?

Also sorry that this thread becomes so far from talking about 6.4.2 RC1 and some moderator may move this

thread to a more appropriate place - at least after we have finsihed this topic.

Regards

[mdgm-ntgr]

I have replied to your PM.

[grumbledog]

I have the same issue. I used to "regularly", that is every few months or so, have corrupted backups. However for the last several months I haven't been able to complete a backup at all. Any data that I can share to help diagnose and/or solve the issue I will gladly do so. For me the backup starts, it just never finishes, and then after a few hours it seems to get bored or something, and just stops doing the backup. The next time it tries again, and the process just repeats. Till now, it has not managed to complete. In case it matters, I am using a shared time machine, and not a private time machine. Maybe I will try setting up a private time machine and see if that helps at all?

[janpeter1]

I have actually not faced your kind of problems with TM backup not getting finished in a defined way.

And with defined way I mean either succesful backup or a clear error message from Time Machine software.

A couple of questions to you:

1) The Mac HD that you try to do backup on might have some trouble.

Good to check with Mac OS Disk Utility and do verify (and after that perhaps also do repair permissions).

2) Do you also do backup directly to an external USB-HD? If so, does that one work and the NAS does not, or?

Good also to know your Mac OS version and ReadyNAS model and firmware version 

[janpeter1]

I have actually not faced your kind of problems with TM backup not getting finished in a defined way.

And with defined way I mean either succesful backup or a clear error message from Time Machine software.

A couple of questions to you:

1) The Mac HD that you try to do backup on might have some trouble.

Good to check with Mac OS Disk Utility and do verify (and after that perhaps also do repair permissions).

2) Do you also do backup directly to an external USB-HD? If so, does that one work and the NAS does not, or?

Good also to know your Mac OS version and ReadyNAS model and firmware version