Before a forecast file backup starts running, verify three things: destination space, access to the equipment, and the credential that unlocks the stored copy.
- You must be able to reach the computer, target device, and connection when a restore is needed
- The repository password or key must be on hand and producible without hunting
- Fix the three in order: without space the job doesn't write a complete copy; without access you can't reach it; without the credential it won't open
- Re-run the checks whenever something changes: a Mac swap, drive replacement, cloud account change, or key rotation
Quarter end is when a lost forecast file hurts most. A rep's spreadsheet holds the pipeline math you're about to present. It lives on a Mac or a backup drive. If the backup job isn't set up right, the file you need may not be recoverable. Three checks catch the common failures before the job ever runs: destination space, access to the equipment, and the credential that unlocks the stored copy.
This is a practical pre-flight, not a theory piece. Each check below is a specific thing you verify today, before the scheduled job starts, so that when you go looking for last quarter's forecast at 11 p.m. on the last day of the quarter, the file is there.
Check one: Is there enough room on the destination?
Every backup job writes a copy somewhere. Before it can run, that somewhere needs room for the copy you're making. The destination can be an external USB drive, a network attached storage device, or a cloud backup service. Acronis states the requirement plainly: "You must have sufficient space on the destination storage (an external USB drive, a NAS device, or Acronis Cloud) to perform a backup." The rule comes from Acronis initial setup.
Sufficient is not a vague word here. Your Mac has a total capacity, and the backup needs room to hold what you copy, plus what it accumulates over time. Apple's guidance on Time Machine sizing: "Use a storage device with at least twice the storage capacity of your Mac." See Back up your Mac with Time Machine. If your Mac holds 1TB of storage, Apple recommends the backup disk hold at least 2TB.
Why twice? Because a backup drive is not a mirror you overwrite each night. Time Machine keeps a history. Apple's schedule: hourly backups for the past 24 hours, daily backups for the past month, and weekly backups for all previous months. That history is what lets you roll back to a version of a forecast file from three weeks ago, before the numbers got restated. None of that history fits if the drive is sized like a photo stick.
What to do today: Open your backup tool, look at the destination, and confirm free space comfortably exceeds what the job needs. If you sized the drive once and your Mac has since grown, recheck. A job that runs out of room mid-cycle can leave you with an older copy than you think.
Check two: Can you reach the machine, the drive, and the connection?
A backup job does not run itself into a healthy state. You need physical or remote reach to three things: the computer holding the forecast files, the device you're writing to, and, for cloud or off-site setups, a working connection that can carry the data out and bring a restore back.
Read it from the restore side, which is the moment that actually matters. Quarter end arrives. You're in a hotel. The forecast file is on your office Mac and the copy is on a USB drive in a desk drawer. If you can't reach the computer or the drive from where you are, you have a backup but not a recoverable file. The distinction between "backed up" and "recoverable" is the whole point of this post.
Recoverability is about access, not just copies
A file you cannot reach at the moment you need it is not backed up in any way that helps you. Access breaks in ordinary ways. The external drive stays on a desk at the office while you work from home for two days. The cloud account requires a code sent to a phone you left behind. The backup tool needs a login you set up under an old company email that no longer resolves.
For a revenue leader, the practical test is simple. Walk the restore path in your head, from where you expect to be at quarter end, and confirm every hop is reachable from there. If any hop depends on a device, account, or connection you might not have, fix it before the job starts.
Check three: Do you hold the credential that opens the stored copy?
The stored backup is a repository. To reach into it and pull a file out, you need a password, also called a key. restic's documentation states: "To access the repository, a password (also called a key) must be specified." That comes from Preparing a new repository in the restic documentation.
A backup written with a key you've lost is, functionally, not a backup. The bytes are there. The forecast file sits inside them. Nobody can read it. This failure is quiet. The job runs green for months. Then the day you need the file, the key isn't where you thought it was.
Check whether the key is the same as, or separate from, your Mac login password, because the answer depends on how the backup tool was configured. Check it against your cloud backup account password for the same reason. In restic, the key is a password specified to access the repository. If several people on the team touch backups, it's worth knowing exactly who holds it, and whether that person is reachable when quarter end lands.
restic also notes that it supports both master and non-master application keys as of version 0.9.2, which matters if your setup hands out keys to more than one person or system. The detail comes from the same restic page.
What to do today: Locate the credential, confirm you can produce it without hunting, and store a copy somewhere you'll reach at quarter end without needing your office machine. If you can't produce it now, you won't produce it under deadline.
The three checks in one place
Here is the pre-flight as a single pass, built from the requirements above.
| Check | What you verify | Why it matters at quarter end |
|---|---|---|
| Space | Destination holds at least twice the Mac's storage | Room for the copy plus retained history |
| Access | Computer, target device, and connection reachable | You can start a restore from where you are |
| Credential | Repository password or key on hand | The stored copy actually opens |
Why these three, in this order
The order matters because each check gates the next. Without space, the job doesn't write a complete copy. Without access, a complete copy sits somewhere you can't reach it. Without the credential, a copy you can reach won't open. Fix them in sequence and you remove the three gaps that can leave a backup unusable at the moment of need.
A revenue leader keeping forecast files doesn't need to become a backup engineer. These three checks take an afternoon to walk through once, then a few minutes each time something changes: a new Mac, a new drive, a cloud account renewal, a key rotation. The cost of skipping them is a quarter-end scramble with a file that turns out not to be there.
Running the checks against a real forecast folder
Take a rep's forecast folder. Four spreadsheets, a couple of exports, a few hundred megabytes. It sits on a Mac at the office, and a USB drive is plugged into the same machine most days.
The first check asks about the destination. The Mac holds more than the drive's capacity, and the drive hasn't been rechecked since a storage upgrade two years ago. Sizing it at twice the Mac's storage gives the room needed for the copy plus the retained history that lets you go back to an older version of a file.
The second check asks about access. The rep travels for the last two weeks of the quarter. If the only copy reachable from the hotel is on a drive that stays plugged into a machine in the office, the restore path breaks exactly when it's needed. Moving the drive, or using a destination reachable remotely, closes the gap.
The third check asks about the credential. The repository key was created when the backup tool was first configured. It lives in a password manager under an entry nobody has opened in a year. Confirming that entry exists, that the password manager works from any device, and that the rep can produce the key on demand, closes the last gap.
Three checks, one folder, an afternoon. After that, the job runs and the files stay recoverable.
What "recoverable at quarter end" actually looks like
Recoverable means you can pull a specific file, from a specific point in time, into a working copy you can open, without depending on a single device, desk, or person. Time Machine's history — hourly for the past 24 hours, daily for the past month, weekly for all prior months — supports that, provided the destination was sized to hold it. A tool writing to a cloud or NAS destination supports it too, provided you can reach the destination and hold the key.
The test isn't that a job shows "completed." The test is that you can name a file, pick a date, and end up with that file open on screen. If any part of that chain depends on something you can't reach at quarter end, the chain is broken before it's tested.
Related guides: 2 CISA ransomware guide sections for a forecast file · Forecast file versions: 3 retention layers to check · AI call scorecard checks: 5 rules before the forecast.
Common questions
Do I need a separate backup for each rep's machine? Size the destination to at least twice the storage of each Mac holding forecast files. Apple's guidance gives the sizing rule for each machine individually. We recommend one destination for several Macs only if it holds the combined total.
What if the drive is already full and the job is scheduled to run this week? Stop the job until the space check passes. A job running against a full destination either fails or writes an incomplete copy.
Who should hold the backup key? Whoever will be reachable at quarter end with access to the password manager where it's stored. For a single rep and a single folder, that's the rep. For a team folder, that's whoever you'd call at 11 p.m. on the last day of the quarter. The source materials here don't prescribe a policy for team key custody, so set one that matches how your team actually works and confirm it with whoever administers your backup tool.
Is a USB drive enough, or do I need cloud storage? Either can satisfy the checks, provided the drive is sized appropriately and reachable when you need it, or the cloud destination is reachable from where you'll be and your credential opens it. The checks don't prefer a destination type. They ask whether that specific destination holds the room, the reach, and the key.
How often should I re-run these three checks? Re-run them whenever the underlying facts change: a Mac swap, a drive replacement, a cloud account change, a key rotation. Also re-run them once a quarter before the forecast gets heavy use. Each pass is quick when nothing has changed.
What if my forecast files live in a shared folder others write to? The same three checks apply to whatever the shared folder sits on. Whoever administers that storage system owns the space and access questions for it. Your part is confirming you can reach it and open the stored content when needed.
Closing
Three checks. Enough room on the destination. Reach to the machine, the drive, and the connection. The credential that opens the stored copy. Walk them before the job starts, walk them again when something changes, and the forecast file you need at quarter end will be there when you reach for it.