plugout.net

Alright thank you for the follow up !

Hi

First test use an oldest Catalina version 10.15.5, and currently I succeeded to create a TM backup (it is still running, I hope not to get a kernel panic...)
Before testing on 10.15.7 I have to check first MacGTO issue's (Failed to reuse the first backup)

Thanks for the follow up !

I'm wondering if I will not have to factory reset my NAS :'(

Waiting for further instruction !

Thanks !

So first backup successful
and I can also update my TM backup (I repeated 3 backups)

On my side I have no issue with TM and MacOS X 10.15.5 :scratch

I go to upgrade to version 10.15.7 now...

Checking completed and I found nothing wrong. On version 10.15.7 I can reuse my TM share and run a new one without issue :scratch and on nas side backup history is right

Code: Select all

<dict>
   <key>Snapshots</key>
   <array>
      <dict>
         <key>com.apple.backupd.SnapshotCompletionDate</key>
         <date>2021-01-16T17:10:35Z</date>
         <key>com.apple.backupd.SnapshotName</key>
         <string>2021-01-16-181035</string>
         <key>com.apple.backupd.SnapshotTotalBytesCopied</key>
         <integer>1287198530</integer>
      </dict>
...
      <dict>
         <key>com.apple.backupd.SnapshotCompletionDate</key>
         <date>2021-01-16T22:08:10Z</date>
         <key>com.apple.backupd.SnapshotName</key>
         <string>2021-01-16-230810</string>
         <key>com.apple.backupd.SnapshotTotalBytesCopied</key>
         <integer>3021751866</integer>
      </dict>
   </array>

So should I factory reset my NAS ?

So it is only suggestions because I do not understand where is the issue...
All suggestions should be performed at the same time before settings a new TM service on your MAC

- on Mac side, remove the TM disk if it is still in-use (and check it is listed as TM disk on nasmame.local)
- on NAS side:
* delete the user account used by TM service to run its backup
* delete the TM share and check if there is no orphan files

Code: Select all

ls -l /share/1000/yoursharename
or
/share/1001/yoursharename
or
/share/1100/yoursharename

* upgrade again the fw even if the menu claims you have the latest (samba4 package will be reinstalled)
* patch again the fw to fix the TM size bug (viewtopic.php?f=27&t=3271#p32598)
* from the main setup menu (tab : AFP/Samba server) check if afp server is disabled and also the option "Stop samba when...". Avaihi daemon must be also running
* create again your TM share and its max size
* create again the user account and restore its permissions on the share

Now cross your fingers and try to set your TM service

well .. I did a full erase of my MAC and .. it fixed the issue (lol)

en français on dit : Utiliser un boulet de canon pour tuer une mouche.

Thanks !

Nice !

So your feedback is now in line with my tests. Tomorrow we go to release a patch with several fixes and it will include the safari fix

Great thanks ! :)