Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Suggestion: Save multiple into just one folder #16

Open
ghost opened this issue May 18, 2016 · 2 comments
Open

Suggestion: Save multiple into just one folder #16

ghost opened this issue May 18, 2016 · 2 comments

Comments

@ghost
Copy link

ghost commented May 18, 2016

I'm trying to figure out if this is a bad thing.

I have about 5000 Google accounts I'd like to download their own Google drive files.

If I do one run of all of the accounts, one bad file will crash the backup of the remaining accounts. Plus it will take days.

Right now I have a BASH script that allows me to backup all of the accounts (one at a time) but 15 accounts simultaneously. (I can actually max out our company's internet pipe this way.) However I then wind up with 5000 backup folders, each having only one account. I then wrote another script the rsyncs all of the folders into one "combined" folder.

If I were to add a command line parm to make the destination folder NOT add the timestamped subfolder, would this create issues? Since I'm using a ZFS filesystem with snapshotting, I don't really need the timestamped folder names.

@ghost
Copy link
Author

ghost commented May 19, 2016

This is a really nasty hack, but it does seem to work.

# diff -u Brive/backend.py Brive-v2/backend.py
--- Brive/backend.py 2016-05-06 08:22:39.626896994 -0400
+++ Brive-v2/backend.py 2016-05-06 08:22:39.615771904 -0400
@@ -67,7 +67,8 @@
         return name

     # UTC ISO-8601 time
-    _UTC_TIME_PATTERN = r'%Y-%m-%dT%H%M%SZ'
+    # _UTC_TIME_PATTERN = r'%Y-%m-%dT%H%M%SZ'
+    _UTC_TIME_PATTERN = r'GD-BACKUPS'

     @staticmethod
     def _generate_session_name():

@BarnumD
Copy link

BarnumD commented Jan 12, 2018

PR: #19 Should will make this possible.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant