rsync permissions update every run.

---

Radjin wrote:

 

---

StephenB wrote:

Try:

rsync -aPvuin --delete-during --delete-excluded --ignore-errors --exclude={'*.Trashes*','*.fsev*','*.DS_*','*.Spotlight*','*Automatically Add*','*Downloads*'} /Volumes/Media\ Drive/ rsync://admin@10.0.1.20:/data/NAS1_Media_Server/Backup/media

---

rsync://admin@10.0.1.20:/NAS1_Media_Server/Backup/media

Changing to this seems to work:

 

I am going to let it run and move some date to see what happens.

 

Thank you.

---

Using the above worked perfectly with the small change I made just below that.  I'm amazed at the speed difference. I can only guess it's due to actually connecting to the rsync server rather having one machine scanning through a SMB connection.  

Thanks for all your help.

I'm glad I was able to help.

FWIW, the rsync: bit was needed because rsync defaults to running rsync-over-ssh when you have a remote source or destination.  That ensures the network connection is encrypted/secure, but isn't necessary when you are running on a home network.  Normally I use rsync backup jobs in the NAS to back up over the network, and had forgotten that.

Have you ever accessed the terminal through ssh and ran rsync that way?  Looking at posts here it looks like the GUI does not always use the most efficient options.

---

Radjin wrote:

Have you ever accessed the terminal through ssh and ran rsync that way?  Looking at posts here it looks like the GUI does not always use the most efficient options.

---

 

---

Not recently.  I use rsync backup jobs to for my NAS to NAS backups. They run on a schedule, which is more convenient (and consistent) then running them manually.

My PC backup jobs use Acronis TrueImage (I use Windows, not MacOS).  Desktops are scheduled (by Acronis); I do back up the laptops manually.

Radjin wrote:

Looking at posts here it looks like the GUI does not always use the most efficient options.

---

---

What specific options you are thinking of?