G Suite for Education is free. We plan to keep the core offering of G Suite for Education free. This offering includes user accounts for future incoming students. As you may know, Google was founded by a research project at Stanford University, and this is just one way we can give back to the educational community.
Google Drive does have a feature to transfer ownership from one user to another within the same domain. This is mainly for the case that a user leave a company, and his/her account is terminated.
However, Google does not allow to transfer ownership across the domain. People keep asking for this feature for many years, and there are workarounds – use drive sync, or use 3rd -party apps.
But, there is a by-product workaround (or solution) for this — Team Drives.
Just create a Team Drive (e.g., “transfer”), add a source account and a destination account as members, then you can move files and folders between the two accounts using the team drive.
Technically, when you move files/folders from My Drive to a Team Drive, Ownership of those files/folders will be changed from the source to the Team Drive. And, when you move files/folders from a Team Drive to My Drive, Google will change ownership from the Team Drive to the destination account.
For files, you can move from/to a Team Drive freely. But, for folders, you need your GSuite admin to set “Move any files and folder to Team Drive” privilege for you.
Note: the moving process from/to a Team Drive is NOT instantaneous – it takes time. So, if you move a large number of files and folders to/from a Team Drive at once, you should WAIT.
Well, my installation is based on the official deb package. However, you cannot automatically upgrade from 2.2 to 2.3. I think this is because graylog might change things overtime and they don’t want to break things without administrator’s supervision.
So you need to download and dpkg -i to install it manually.
Some Linux users user Deja-Dup / Duplicity to backup their files. The tools work pretty well and very reliable.
However, in very rare occasions, Deja-Dup will keep asking you a password even you put the right one. To debug this, you can do
DEJA_DUP_DEBUG=1 deja-dup --backup
to see what’s going on, and grabbing those error messages to find the right solution.
Interestingly, one of those occasions is that you have files with size = 0 byte in your backup set. These zero-byte files cause GPG fails when it tries to test your backup set even with the right password.
To solve this, simple, delete those zero-byte files from the backup set. It is safe to do so anyway. :P