Frequently asked questions

Whatever you back up to it: documents, photos, server snapshots, databases, code repositories. Each item sits in a bucket, like a folder, and you decide what goes in.

A cloud drive is a sync app you have to remember to use. disk.ie is a target for backup software that runs on a schedule, keeps history, and verifies yesterday's files are still readable today.

The wire protocol and the tools are identical; the difference is the operator. disk.ie is operated by Netquirk on infrastructure independent of the public-hyperscaler region you might otherwise use, and pricing is set on this site instead of a tier table elsewhere.

No disk.ie app to install. You use a backup tool you already trust — rclone, restic, the AWS CLI, Cyberduck — and point it at https://s3.disk.ie. The quick start has the commands.

Sign in once at my.netquirk.com. The disk.ie service appears as a tile on the dashboard once your account is enabled; enable it and the access-key section becomes available.

Sign in, open the disk.ie tile on the dashboard, click Access keys, then Create access key. The secret is shown once at creation — copy it then or lose it forever. The access-key id stays visible in the list; the secret never appears again.

Yes. Each access key has its own scope. A restore-only key is a key whose policy allows only GetObject on the buckets and prefixes you choose. Create one in Access keys → Create access key → Read only.

On disk.ie infrastructure, on storage that is independent of any home or office network you use. The data-centre city is published to existing customers on the plan page in the dashboard.

Yes. Files travel over HTTPS to disk.ie and are encrypted again before they are written to disk. Only the access keys you create can read them back.

Your data is unaffected — it lives in a different physical location. Sign in from a new device, create a fresh access key, and run your backup tool against the same https://s3.disk.ie endpoint.

Deleted files are kept for a grace window after deletion, listed with their key in Recovery on the dashboard. After the grace window they are removed and the storage is reused.

The S3-compatible endpoint supports standard PUT/GET/DELETE. Versioned buckets keep every prior copy; non-versioned buckets overwrite in place. Pick a mode per bucket from the dashboard.

The status page reflects the state of the S3 endpoint, the account portal and the off-site replica drill. Outages are listed by component, with the time the issue started and the time it was resolved. Your data stays in place; writes queue until the service is back.

Yes. Encrypted replicas are produced on a schedule; replica drills re-read them and compare the byte digests against what was last written. The result of the most recent drill is shown on the status page.

On the status page, in the row labelled Last off-site replica drill. A green row means every byte of every object came back identical. Anything else is surfaced to the operations team first and then to customers.

Storage is measured daily, averaged across the month, and billed the day after. Restores and downloads do not count as usage.

Writes are paused before they would push you past the cap. You will not receive a surprise bill. Move up a plan or free up space from the dashboard.

Yes. Plan changes take effect at the start of the next billing cycle and the difference is prorated against what you have already paid.

Your files stay readable for a short grace window. We email you before any data is removed and you can download everything with the AWS CLI before then.

There is no standing free tier today. Sign in at my.netquirk.com to see whether a trial is available for your situation.

The AWS CLI's s3 sync is the simplest way: aws --endpoint-url https://s3.disk.ie s3 sync s3://<bucket> ./backup/ repeat for each bucket, and you have every byte, byte-identical to what you uploaded. rclone sync works the same way against the disk-ie: remote.

Yes. There is no proprietary format on the disk.ie side — bytes, keys, buckets, and metadata are all standard S3. Point another S3-compatible host at the same buckets and the same files there.

From the dashboard, revoke every access key, then request account deletion from the support form on the support page. The account record is removed at the end of the billing cycle.