CaryvaneHelp
/
EN

Customers & deployment

Everything in Caryvane belongs to a customer: agents, jobs, storage targets, connectors, users. An MSP sees its customers; a distributor sees its MSPs and their customers; nobody sees sideways. This page is the admin's tour — set up a customer, get machines enrolled, point them at storage, and know what you will be told when something goes wrong.

Customers and who can see what #

Customers shows the hierarchy: Distributor → MSP → Direct customer. Each row is a tenant with a type, a status, its agent count and its billing. New Customer creates one under you; ⋮ → Add customer under this nests one under an MSP. From the same menu: Edit, Users, Billing & Invoices, Add cloud credits, Suspend (their jobs stop and billing pauses; Reactivate reverses it), and Sync to Xero where accounting is connected. For personal drives there is Drive sign-in… in the same menu (whether and how people sign in at that customer's machines) and the Drive Users page of its own in the navigation (the people who may sign in for their own drives, imported from the customer's directory or added one by one) — see Personal drives. Suspended and cancelled customers stay on the platform but are hidden from the list unless Show suspended & cancelled is ticked; an active client under a suspended MSP keeps its MSP on screen.

Moving or removing a customer #

Both are Caryvane platform-admin actions, from the same ⋮ menu.

Move to another reseller… re-parents a customer — a direct customer under an MSP, a customer from one MSP to another, or back to Caryvane to bill direct. Pick a date and the old owner is invoiced for the part-period first, then the customer moves overnight; Move now switches immediately with no close-out invoice, which is only right for a customer put in the wrong place before they were ever billed. Only resellers that are allowed to hold that account type are offered, and a customer’s own sub-tree is never offered, so the move cannot fold the tree in on itself.

Delete… is for a customer created by mistake — a typo, a duplicate, a test account. It removes the customer, its console logins and any unused enrolment tokens. It refuses any customer that has agents, jobs, storage targets, a connector, an archive, an invoice or customers of its own, and tells you which of those is in the way. To stop billing a real customer, Suspend or cancel them instead — that keeps their history. Deletions are written to the Audit Trail.

Roles #

RoleSees and manages
Distributor adminTheir own tenant, the MSPs beneath it, and those MSPs' customers. Creates MSPs and customers, sets wholesale rates.
MSP adminTheir own tenant and their direct customers. Creates customers, enrols machines, edits customers' details — never other MSPs, never the distributor's rates.
ManagerFull control inside one tenant: jobs, agents, storage, users of that tenant.
UserDay-to-day operation inside one tenant: jobs, restores, drives.

Users (per customer, from the Customers menu, or the Users page for your own tenant) adds people with a username, email and initial password; under Roles, the Manager chip makes someone a manager (platform users also have Admin). Everyone who signs in with a password must use two-factor authentication: the console sets it up at their first sign-in with an authenticator app (standard TOTP), and an admin can Reset MFA from the user's row if they lose the device. The console also signs in with Microsoft or Google accounts, which skip Caryvane's own second factor because Microsoft and Google apply theirs. What every user and every AI key does is written to the Audit Trail.

Deployment tokens #

A deployment token is how a machine joins the right customer. Agents → Enroll Agent: choose the customer, an optional name for the token, and how long it lives (1 hour to 90 days; 24 hours by default). The dialog returns the token and a ready-to-paste msiexec command with it filled in.

Storage targets #

A storage target is somewhere data goes (or, for a cloud-to-cloud copy, comes from). It belongs to one customer, and the customer's credentials for it are stored encrypted and never shown again. Storage → Add Target, choose the provider, fill in the credentials, Test. The same target can serve as a backup destination, a cloud-drive source and an archive destination.

ProviderYou needNotes
Amazon S3Access key, secret key, region; default bucketBucket versioning is used for version history when enabled on the bucket. Realtime cloud-copy source via SNS.
WasabiAccess key, secret key, endpoint (e.g. s3.eu-west-1.wasabisys.com), regionSame behaviour as S3; the usual low-cost choice.
Backblaze B2, DigitalOcean Spaces, Cloudflare R2Key ID, key, endpoint, bucketS3-compatible.
Azure BlobConnection string, or account name + key; default containerOptional ARM app registration (Live change notifications — optional) lets Caryvane register Event Grid so a cloud copy can run continuously.
SharePoint / OneDriveSign in with a Microsoft account (OneDrive), or site URL with the picker (SharePoint)A storage target, distinct from the Microsoft 365 connector: this is one site or drive, browsable and mountable.
Google DriveWorkspace user to impersonate (uses the domain delegation), optional root folderWorkspace accounts only; consumer Google Drive is not offered.
Dropbox, EgnyteSign in (OAuth); Egnyte also needs the domainEgnyte tokens are refreshed automatically; a connection unused for 30 days needs signing in again.
SFTP, FTPHost, port, username, password or private key; base pathSFTP keeps versions with server-side copies.
SMB share, local folderServer, share, credentials / a path on the agent's machineOnly reachable from an agent on that network — not from the Cloud Agent, and the wizard says so. Browsed through an agent.

Browse on a target lists it live; from there folders can be marked for archiving. A target whose credentials fail shows the provider's message on its row until it is fixed — that is usually the first sign a key was rotated.

How much is stored #

Each target’s row shows how much is stored there and when that was measured. Caryvane measures every destination overnight rather than when you open the page, because measuring can mean paging through every object at the destination — so the figure always comes with its date, and you should read it as “as of then”. ⋮ → Measure usage now takes a fresh reading; on a very large destination it may report a partial figure and finish properly overnight.

How it is measured depends on what the provider will tell us, and most of them will not simply answer “how big is this”.

ProviderHow the figure is obtained
SharePoint, OneDriveGraph keeps a running total on every folder and a quota on every drive — two calls, no enumeration.
Dropbox, Google DriveThe account’s quota comes back in one call; the folder figure needs a listing.
Amazon S3S3 has no bucket-size call. Where the access key can also read CloudWatch, the daily BucketSizeBytes metric answers in one request — the same number the S3 console’s Metrics tab shows, so it can be up to 48 hours old and, on a versioned bucket, includes old versions. Otherwise the bucket is listed.
Wasabi, B2, R2, MinIO and other S3-compatibleListed. These have no CloudWatch, so there is no cheaper route.
Azure BlobThe container is listed. If you added the optional ARM app registration (the same one used for Event Grid), Azure Monitor also reports what the whole storage account holds — shown separately, because that is the account, not your container.
SFTPWalked, with the volume’s real free space from the server’s statvfs where it supports it.
FTPWalked, a folder at a time.
SMB share, local folderNot measured. This is your own disk — nobody bills you by the gigabyte for it, so there is no figure to track and Caryvane does not go looking. The row says “Your own storage” rather than showing a gap.
EgnyteNot measured. Egnyte has no size API — its Folder Size Report is an admin screen — so the only way to work it out is to walk every folder, one API call each, against an allowance of 1,000 calls a day shared with your backups. Spending that to duplicate a number Egnyte already shows you is a bad trade, so Caryvane does not. Use Settings → Reports → Folder Size Report in Egnyte.

Two things the row will never do. It will not show 0 for a destination it could not measure — that reads as “your backups are gone”, so it says “Not measured yet”, or keeps the last good figure with its date and the reason the latest attempt failed. And where the provider reports a limit, the tooltip says what that limit covers: a local folder’s limit is the whole volume, and a Google quota is the whole account including Gmail — neither is a limit on your backup.

Caryvane measures the destinations you are billed by the gigabyte for. An SMB share or a local folder is your own disk, so it is deliberately left alone — the server cannot reach a customer’s file server in any case, and a local path means something different on every machine.

Agents #

Agents lists every machine under the customers you can see, with online state (checked in within the last 90 seconds), version, platform and last-seen time. Offline is not a fault: laptops close and old machines are retired. Per machine, ⋮:

Agents update themselves within minutes of a release (running jobs are allowed to finish first); the version column shows who has and has not. A machine stuck on an old version is nearly always offline or unable to reach the console — see Troubleshooting.

Maintenance notices #

Settings → Notices: a title, optional notes, a window and a tone. While the window is live the notice is shown as a banner above every page of the console, to everyone, so the person who lives on Jobs sees it too; dismissing it hides it for that session only. Dates are entered in your own time zone. Taking a notice down early marks it withdrawn and keeps the record, for the night somebody asks why their backups were late.

Notifications #

Notifications (per customer): email addresses and an optional webhook (URL plus an HMAC signing secret so the receiver can verify it is Caryvane) for these events — Job completed successfully, Job failed, Job completed with warnings, Agent goes offline, Boot check failed. Caryvane sends the email; nothing to set up on your side. Send test proves the route. Overrides sit on the job (Mute notifications for this job, on the Done step when you edit it) and on the agent, for the one noisy job or the laptop that is off every weekend.

Cloud Agent jobs and credits #

Storage-to-storage copies, connector backups and archiving jobs can run on the Caryvane-hosted Cloud Agent instead of a customer's machine, so the data never passes through hardware you manage. Each is a cloud job drawn from the customer's allowance: on a paid plan it is metered; a prepay customer buys cloud credits, which you add from Customers → ⋮ → Add cloud credits. The wizard refuses to create a cloud job for a customer with no allowance, with the reason. Cloud Fleet (platform admins) shows the workers and what each is running.

Archiving Policy #

Archiving moves files that nobody has touched for a set time out of a customer's live storage into cheap storage, and records where they went. It is deliberately two separate acts, both explicit:

  1. Mark the folders. Storage → the target → ⋮ → Archiving… to switch archiving on for that connection. Then Browse it; each folder gains an Archiving rule action: Archive — move files older than N days, months or years (judged by Last modified, or Last opened where the source reports it) — or Never archive. Rules inherit down the tree — mark Finance for 3 years and every subfolder follows, except one you mark Never. Badges on the folders show the rule in force, faded where it is inherited, with the ancestor it comes from on hover.
  2. Create the Archiving job. Jobs → New Job → Archive old files to cheaper storage: the marked connection, the archive destination and prefix, weekly by default. The one destructive switch — Remove archived files from the source — is off until you turn it on, so the first run is a copy you can inspect. Each run judges every file under a marked folder, copies the ones old enough, verifies the copy (hash where both sides report one, else size), records it in the catalogue, and only then — only with the switch on, only with hash or size proof — deletes the original.
What customers ask for

A typical firm marks Projects for 3 years, Correspondence for 1 year, and Contracts as Never. Archived files are retrieved by download from the catalogue, not from the original folder, so tell the customer where their old files went before the first removal run.

Billing #

Direct customers are billed in advance; MSPs and distributors in arrears on the agents actually enrolled, at the rates set on their tenant (Customers → ⋮ → Edit; a distributor sets wholesale rates its MSPs cannot see). Billing & Invoices per customer lists invoices; with Xero connected they are pushed and reconciled automatically. A new direct customer starts on a free trial without a card; connectors and cloud jobs wait for the paid plan.

Go deeper #