What is Google Cloud Storage used for in cloudHQ?

A bucket can serve as the storage location for a backup of another cloud service, like Microsoft 365 OneDrive, Dropbox or Box. Keeping a bucket in sync with an Amazon S3 bucket works too. When you set up a backup, cloudHQ creates a one-way sync pair. Your files are copied into the bucket, and after that every change gets copied as well. A pair with Amazon S3 can be two-way. The steps for both setups are in these two notes: How to back up Microsoft 365 OneDrive to Google Cloud Storage and How to sync Amazon S3 with Google Cloud Storage.

How do I add my bucket to cloudHQ?

You do three things. They are listed on the Add Google Cloud Storage page, which you open from the Cloud Accounts tab. Step one: in the Google Cloud console, give the service account of cloudHQ the Storage Object User role on your bucket. Step two: download your verification file from cloudHQ and upload it to the bucket. Step three: type the name of the bucket into Bucket name and click the Add Google Cloud Storage button. For the details of each step, read How to prepare Google Cloud Storage for backup or sync.

Why does cloudHQ not ask me for a key or a password?

cloudHQ uses a Google service account that belongs to cloudHQ to sign in to Google. There is no service account key or HMAC key for you to create, and no secret leaves your Google Cloud project. What gives access is the role you grant on your bucket to that service account’s address. That’s the reason Google Cloud Storage gets added to cloudHQ in a different way than most cloud accounts.

What can cloudHQ do in my Google Cloud project?

cloudHQ can do only what the Storage Object User role allows, and only inside the bucket where you granted that role. In that bucket it is able to list, download, upload and delete files. What it can’t do is change bucket settings or change who has access to the bucket, and it can’t see any of your other buckets. When you remove the role on the bucket’s Permissions tab, cloudHQ no longer has access.

What is the verification file, and can I delete it?

The file is a small text file, and its name begins with cloudhq-verification. Every cloudHQ account gets its own name for this file. The file in your bucket proves that the bucket belongs to the person who added it to cloudHQ. Leave it in place for as long as cloudHQ uses the bucket. Each time cloudHQ starts working with the bucket, it checks for the file again. If the file is missing, the sync stops and you get an authorization error. A sync pair does not copy the file to the other side.

Can I use more than one bucket, and can cloudHQ create a bucket?

Each Google Cloud Storage account you add to cloudHQ is a single bucket. To use a second bucket, add it in the same way, as a second account. cloudHQ can’t create a bucket for you, so the sync wizard does not offer a new bucket. You create the bucket in the Google Cloud console first and then add it to cloudHQ.

Which buckets can cloudHQ not use?

Two kinds of bucket are refused when you add them. If Requester Pays is on for a bucket, cloudHQ can’t use it. The same goes for a bucket that has a retention policy, since a backup or a sync needs to replace and delete files. There’s another case too: some Google Cloud organizations block roles for accounts that come from outside the organization. If that happens, the organization’s administrator must first allow the service account of cloudHQ.

Google Cloud Storage has no folders. What does cloudHQ show?

Inside a bucket you’ll find objects, and an object’s name may include slashes. cloudHQ treats each slash as one folder level. Take the object reports/2026/summary.pdf: you see it as the file summary.pdf in the folder 2026, which is inside the folder reports. The Google Cloud console presents the bucket in the same way. A sync pair can start at the bucket or at any of these folders.

How does cloudHQ keep an empty folder?

A folder is only there in a bucket while some object name begins with it. So an empty folder would disappear. That’s why cloudHQ, for a new folder, writes an object with no content: its name is the folder name plus a slash at the end. When you make a folder in the Google Cloud console, the console writes that same object. cloudHQ shows it as the folder, and never as a file.

I changed a file directly in the bucket. When does cloudHQ see it?

cloudHQ sees it at the next scan. Google doesn’t notify cloudHQ when something changes in your bucket, so cloudHQ reads the object list on a schedule and compares it with the previous list. A pair that takes changes from the bucket has this hint on its Synchronization Options page: Synchronization of changes from Google Cloud Storage is not real-time. Please select schedule. You choose the time between two scans under Full scan frequency. A backup into the bucket works differently: a change made in OneDrive or Dropbox, for example, is not delayed by the scan schedule.

Why is the name of a file in cloudHQ not the same as the object name?

Some characters are allowed in object names but not in file names on other cloud services. When that happens, cloudHQ displays the object with a title that the other side accepts. A backslash or a vertical bar appears as an underscore, spaces at the start and end get removed, runs of two or more spaces turn into a single one, and a title never goes past 255 characters. Nothing in your bucket is renamed. The object keeps its own name.

Does upper and lower case matter in names?

It does. Google treats Invoice.pdf and invoice.pdf as two separate objects. cloudHQ shows both in the list and syncs each one.

What does cloudHQ do when a file and a folder have one name?

In a bucket, an object named data can be in the same place as objects like data/january.csv. With other storage, that means a file and a folder share the same name in one place. cloudHQ shows the folder as data and the file as data – file, and it syncs both. cloudHQ never creates such a pair itself. If a sync would have to place a file beside a folder with the same name, cloudHQ leaves that file out and tells you why: cloudHQ does not put a file beside a folder of the same name in Google Cloud Storage: please rename one of them.

Why can cloudHQ not replace or delete some objects?

When a retention policy or a hold covers an object, Google keeps it protected. cloudHQ does not touch that object. It reports Google Cloud Storage does not allow this object to be replaced or deleted: a retention policy or a hold protects it. This does not stop the pair: its other files are synced as usual.

Which objects does cloudHQ add to my bucket?

cloudHQ adds the files of your sync pairs, under the names and in the folders they have on the other side. On each object it uploads, cloudHQ sets one metadata entry, cloudhq-check. Later it uses this entry to find out whether the file has changed. A new folder gets the empty object from the question about empty folders. If Archive files before they are changed or deleted by sync is on, a “cloudHQ_archive” folder with the earlier versions is added too: What is the cloudHQ_archive folder? When you create a sync pair, cloudHQ also saves a test file named cloudHQ_test_file with a random ending and deletes it right away.

A file was renamed on the other side. What happens in the bucket?

In that case cloudHQ asks Google to rename the object inside the bucket. The file’s content isn’t downloaded and uploaded again. Inside a bucket a folder doesn’t have a name of its own, so cloudHQ renames the objects in that folder one at a time. When a folder holds a very large number of files, this takes time.

What happens if the role is removed or the verification file is deleted?

cloudHQ makes a few more attempts. If those don’t work, the sync pairs on that bucket stop and you get an authorization error. cloudHQ also sends you an email about it. To fix it, grant the role again or upload the verification file again, then open the Cloud Accounts tab and click the Authorize button of the bucket. After that the pairs continue on their own. Full steps are in How to prepare Google Cloud Storage for backup or sync.

How do I restore a file from the backup?

A backup in a bucket consists of normal objects. Open the bucket in the Google Cloud console, or use any other tool for Google Cloud Storage, and download the file you need. If Archive files before they are changed or deleted by sync is turned on for the pair, you will find earlier versions and deleted files in the “cloudHQ_archive” folder of the backup.

What does it cost?

You’ll find the current plans and prices for cloudHQ sync and backup, along with any free trial, on the pricing page: https://www.cloudhq.net/g_suite/pricing. How the plans work is described in the note about the subscription plans of Sync and Backup. Storage in your bucket is billed by Google to your Google Cloud project, and cloudHQ has nothing to do with that charge.

Where can I check what a sync pair has copied?

Each pair on the Sync & Backup tab has a View Sync Events button. Click it for the pair you want to check. For a full explanation of that page, see How to monitor sync, backup or migration.

—