Watch the trailing / on your source. Even given the mismatch on creation date on some of the backup folders (contents were all date stamped correctly, but the folders had different creation dates). Even given the 200GB of new data, this should have been a quicker transfer. No instantaneous, but but not 400GB+ and counting time frame worth of data. Absent a trailing / on source, say ~/Documents, will copy the whole documents folder to the backup location, but a trailing / on the source, say ~/Documents/, will copy the contents of the folder to the backup location. Doh!

Let's be real, I know all that before starting, but copied an existing rsync script and tweaked a few things, but forgot to add the trailing / on the source destination anyway. Okay, PSA over now.



Edited 3 time(s). Last edit at 12/29/2015 01:16AM by silvarios.

Quote
silvarios
Let's be real, I know all that before starting, but copied an existing rsync script and tweaked a few things, but forgot to add the trailing / on the destination anyway. Okay, PSA over now.

Only the trailing slash for the source is important to designate the copy-mode.

---

Quote
Onamuji

Quote
silvarios
Let's be real, I know all that before starting, but copied an existing rsync script and tweaked a few things, but forgot to add the trailing / on the destination anyway. Okay, PSA over now.

Only the trailing slash for the source is important to designate the copy-mode.

Fixed. Sorry for the typo.

Remembering the trivial details is why just use Carbon Copy Cloner for large copies. (That and the fact that the Finder is slow and troublesome when copying lots of small files.)

---

Edited 1 time(s). Last edit at 12/29/2015 01:36AM by Onamuji.

Quote
Onamuji
Remembering the trivial details is why just use Carbon Copy Cloner for large copies. (That and the fact that the Finder is slow and troublesome when copying lots of small files.)

Love, love, love, love CCC. However, this is for my NUC running Linux, so rsync it is.

IINM, CCC uses rsync under the hood, but it still does avoid making these kinds of mistakes.

---

I am not Ryan Seacrest, and I do not approve this message.

CCC uses our own, highly customized version of rsync, fwiw. Not the vanilla build.

-s

Quote
Seacrest
IINM, CCC uses rsync under the hood, but it still does avoid making these kinds of mistakes.

Yeah, rysnc and some other stuff as far as I can tell. I have rysnc configured to largely do the same thing, even have the archive folder named similarly. I considered using hard links and having directories that appear more similar to a Time Machine backup, but went the usual CCC style backup route.

Quote
FormerlySaleenl
CCC uses our own, highly customized version of rsync, fwiw. Not the vanilla build.

-s

Well, there you go. Thanks for chiming in.

Again, I love, love, love Carbon Copy Cloner. I pay for upgrades even though it takes me years to get to the new version of OS X to even use that version of CCC. CCC was the hardest thing to let go when I left OS X as my day to day OS. It's just that good. No joke.

CCC is great. I've wanted to respond to this thread forever, but had lost my account... :-( Now I'm back.

Frustrating thing about rsync is I can never remember whether including or excluding the trailing slash copies the subfolders into the destination or the parent folder...
g=

Quote
gabester
CCC is great. I've wanted to respond to this thread forever, but had lost my account... :-( Now I'm back.

Frustrating thing about rsync is I can never remember whether including or excluding the trailing slash copies the subfolders into the destination or the parent folder...
g=

Glad to see you back! Yeah, I always forget too, which is why I keep some sample scripts built and saved to look at when building new ones. I'm too dense to remember such things apparently.