connecting the disk to a local Mac (location 1) and do the first backup via ethernet? That would take forever compared to the USB 3 connection, but at least the backup would be "mac interpreted" both locally and remotely. case-sensitive Journaled) so that both the NAS and my mac can write to the disk properly? Or is there no way around biting the bullet, i.e. But what should I do about it? Is there a way to format the disk (e.g. In other words, they are not identical, only superficially displayed as such. Whereas sh-3.2# ls -l Ronja* | hexdump -C A simple “ls -l” gave me: drwxrwxrwx 2 _unknown _unknown 68 Ronja Rövardotterĭrwxrwxrwx 2 _unknown _unknown 68 Ronja Rövardotter What is going on and what can I do about it?ĮDIT 11 sept: The wise Tomáš Pospíšek (well acquainted with special characters, I presume ) advised me to go “under the hood”, and so I used his command (on Ronja instead of Pippi, since I had too many different Pippi folders). Folders are deleted indeed, but new ones are copies and in the end I am still sitting with duplicates and 82 GB in the subset instead of 64 GB as a result. When I try to get the system to keep only one of the special character folders/files with the -delete option, everything just happens all over. When the mac terminal displays the file and folder names, it evidently uses the same symbols, but it must still interpret them as different ‘underneath’, since otherwise the file system would not allow it. What has happened? To my untrained eye, it seems as if the rsync process initialised on the Mac cannot ‘see’ that the source files on the NAS are already present on the target disk, and put them there again. And they are not merely virtual, since the total size of the subset of the data went from 64 GB to 82 GB. If I use the Mac GUI, I can enter each of them and see that they contain the same (qualitatively identical) three tracks (I do not even know how to separate them using the command line, but with the GUI I can visually see that I ‘enter’ different folders). These two folders seem completely identical, yet they are listed alongside each other as two distinct folders. For example: drwxrwxrwx 5 _unknown _unknown 170 Pippi Långstrump-Pippi i Söderhavetĭrwxrwxrwx 5 _unknown _unknown 170 Pippi Långstrump-Pippi i Söderhavet Then it started to copy folders and files to the disk - even though they were already there! 70 GB later, from what I could tell, it had made a completely redundant copy of all folders which had special characters in their name (and a redundant copy of all files with special characters in their name in folders which did not have special characters in their name). Location 2: initialised a limited rsync pull job from the Mac, now with the new disk plugged in.įor some reason, step (4) did not finish in 2 seconds with no changes at all, but started to complain that “file has vanished: …” for a bunch-load of files. Travelled to the far away galaxy that we here call Location 2 Location 1: Pushed the data to the new disk with a rsync job on the NAS Location 1: Plugged the new disk into the NAS thanks to the wonders of USB. Since there is around 2TB of data to transfer, I did the following: I now plan to set up a new disk (also Mac OS Journaled) on Location 2. Task: rsync job on the Mac pulling folders to the external disk (location 2) from the NAS (location 1). Location 2 (in a galaxy far far away): Mac with external disk (Mac OS Journaled) Indeed, ever since I managed to solve an initial special character problem ( detailed here), after which I use the "-iconv=utf-8-mac,utf-8" option for the rsync on the mac. I have a setup that has been going on for ages. State of play: What follows below is rather long and includes two edits, but although the problem is further analysed, it is not yet solved. Question: Is there a way to use the same basic process (first backup locally via NAS, rest via Mac, using rsync) without the above problem? Problem: I get two copies of all data (files or folders) with special characters. Mac to the disk, now mounted on the Mac on a remote location. Future backups remote: rsync initialised on a.First backup local: rsync initialised on the Synology NAS to the disk.I use the following setup to backup data on a Synology NAS to a remote disk via rsync.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |