Quick guide on how to connect and use your Platform with Google Drive
1. Log into the server's Windows OS. **Not Platform from another workstation. This must be done on the server itself locally.
2. Go to drive.google.com and sign in/create a google/gmail account.
3. Install the desktop application
**Note that there are (2) different types of accounts. Personal there is a limited amount of space that can be used unless more space is purchased. Business account you must contact Google for pricing and information. For demonstration purposes, we will use the Personal account.
4. Log into the google account
5. Remove Desktop, Documents, and Pictures from the sync then click on *Choose Folder*.
6. Choose StorageGroup and the Platform Space in which you would like to sync with Google.
7. Allow the sync to proceed. *Speed is dependent on your internet speeds. Not the server.
8. Download Desktop Application for Workstation and sign in.
9. Do not sync Desktop, Documents nor Pictures but complete the backup application setup so the Application can be on the desktop. It should add a folder in your Finder/File Explorer that you can access your Google Drive from. This folder should contain the Platform Space that were synced. *Files may not appear immediately if they are still syncing to the Google Drive. Changes on the Google Drive folder that have synced Platform Spaces should reflect the changes that you make from the most updated side. If the workstation made changes more recently, then the Platform should go through a sync cycle to update the files on the Platform Server. Again, this is dependent on your internet connection.
Working with a Cloud Syncing Space
Connecting your Platform system to Google drive gives you a portal into your network storage from anywhere you can connect to the internet and is a valuable tool for offsite coordination. Below are a few best practices and tips to make the most of this ability.
- Do not work directly from a cloud syncing space, use it for staging and receiving file transfers from outside users. Once data is confirmed to be sent or received, move it to its own Platform Space or working folder on your local workstation.
- Editing directly from a cloud syncing space may result in your system attempting to upload hundreds of temporary and preview files. These will upload to Dropbox automatically and consume space and bandwidth, as well as cause organizational challenges.
- Do not use a sync space as long term storage. Anything you place in the space will be sync'd to cloud provider, and you may incur costs from the cloud provider or space limits based on how much is stored there.
- Be aware of your bandwidth. It's very easy to move 500GB of files into a Platform space from a local network source, but it may take a day or more to transfer to the cloud for anyone else to access. This will will depend on your bandwidth to the internet.
- Consider access and visibility. Anyone that has access to your cloud account will have access to things placed in this space, regardless of the permissions you set on the Platform Space that's syncing. If you need to keep something confidential, consider a different means of transfer.
- It is not recommended to enable the following features on a cloud sync space
- Avid Collaboration
- AE Render Space
- The best use of a cloud sync folder is sharing smaller files with users outside the local network. Compressed deliverables, dailies, smaller types of files like lower-third graphics, NLE/graphic project files, and documents among post production team members.
- In general, do not use it to transfer bulk raw media offsite editors. There are exceptions to this where the media is small and available bandwidth on both sides is high, however in most cases bulk raw media (a collection of camera cards from a shoot, for example) is far too large for reliable and timely transmission via cloud sync today. Consider sending bulk raw media to offsite users via shipped HDD as it will likely arrive faster than a cloud sync under normal circumstances.