Skip down to the research record

Veeam backup lock: 3 expiry days after a 7-day setting

Quota Forecast Editorial Team · Published · 11 min read

A 7-day Veeam backup lock may keep files locked through day 10, 14, or 17, not exactly seven days. Many revenue teams keep a second copy of their forecast files in cloud storage. The copy exists for a bad day: a deleted workbook, a corrupted export, a ransomware incident, or a cleanup that removes the working folder by mistake. A backup only helps on that day if nobody can quietly delete or change it first. That is the job of a lock, which storage vendors often call immutability or object lock.

This post answers one practical question: if you set a backup lock to seven days, how long do the files actually stay locked? The honest answer is that the setting in your backup tool and the dates on your stored files can disagree. One source we checked describes three outcomes after a 7-day setting in Veeam, with files locked through day 10, day 14, or day 17. Below, we look at what those three days mean, why they matter for a forecast archive, and how to check your own setup.

Key takeaways

  • Confirm the lock period in both the backup tool and the storage bucket.
  • Measure lock expiration dates on several files written on different days.
  • Compare your measurements with the three outcomes the source describes: day 10, day 14, or day 17.
  • Budget storage for the data that cannot be deleted, not only the configured number of days.
  • Run restore tests on files from different write dates, and repeat the checks after any change.

This is general planning guidance, not legal or compliance advice. Your retention rules may come from company policy, auditors, or your industry, and those should drive the final choice.

What a lock actually does

A lock tells the storage service that a file cannot be deleted or modified for a set period. Backblaze states the basic rule this way: "A 14-day immutability period means files cannot be deleted or modified for 14 days after they're written." (Backblaze, "Object Lock Mistakes That Put Immutable Backups at Risk") The important words are "after they're written." The clock starts when the file lands in storage. It does not start when someone changed a setting, and it does not start when the planning meeting happened.

For revenue teams, that detail matters more than it first appears. A forecast file is often written at a different moment from the job that produced it. A weekly export might be generated on one day, copied to backup later, and revised before the next cycle. Each stored file can carry its own lock end date, so treat the lock as a rule for each file rather than one date for the whole folder.

A lock protects against deletion and overwriting. It does not decide whether a file is correct, complete, or easy to restore. A locked copy of a broken export is still a broken export. That is why the restore checks later in this post matter as much as the setting itself.

The three days to expect after a 7-day setting

Most people assume that a 7-day setting protects every file for exactly seven days after it is backed up. The source we checked says that assumption can fail. The passage reads: "If you configure a 7-day immutability period in Veeam and then check the actual lock expiration dates in your bucket, don't be surprised to see files locked through day 10, 14, or even 17." (Backblaze, "Object Lock Mistakes That Put Immutable Backups at Risk")

That gives three numbers to plan around:

  • Day 10: files stay locked three days longer than the setting suggests.
  • Day 14: files stay locked a full week longer.
  • Day 17: files stay locked ten days longer.

Read these as examples of what you may see, not as a promise about your system. Your own dates may have a different cause, so do not assume you already know the reason for them. The only reliable answer comes from measuring your own files, which the steps later in this post walk through.

Counting from the write date is the right starting point. It matches the vendor's own wording, which measures the lock from when each file is written.

A worked example with a weekly forecast

Consider a team that exports its forecast every Monday and writes a copy to the backup bucket the same day. The team sets a 7-day lock. If the pattern in the source holds for that file, the Monday copy could be locked through day 10, 14, or 17. Counting from Monday, that is a window ending on the 10th, 14th, or 17th day after the export. Put another way, the file might be protected for three, seven, or ten days beyond the number the team typed into the form.

Now add a Thursday revision. The team saves an updated version on Thursday and writes it to backup. That version has its own write date, so its lock end date is also its own. On a given Monday, the bucket might hold the older copy, which could still be locked, along with the newer Thursday copy. Neither date replaces the other. When the team counts what cannot be deleted, it has to count both.

This is why the budgeting warning in the next section matters. Locked data accumulates. A team that writes a copy every day and holds each one under a lock will always have several days of copies that cannot be deleted at once, and that number grows when the real lock window is longer than the setting.

The example is simple on purpose. Your real schedule may include month-end snapshots, scenario versions, and files that several people edit. Each one adds its own write date. Measure a sample from each group rather than assuming they all behave like the Monday file.

Why the extra days change your storage plan

Backblaze also makes a point about budgeting: "If you're budgeting for 7 days of immutable storage, you may actually need to account for closer to 14 days of data that can't be deleted at any given time." (Backblaze, "Object Lock Mistakes That Put Immutable Backups at Risk")

Revenue leaders often budget storage around the retention number they typed into a form. A 7-day lock that behaves more like a 14-day lock means more data is protected at any moment than the setting suggests. Put that larger figure in the budget, not the number on the settings page.

A simple way to plan is to work through three steps:

  1. Estimate how much forecast data you write each day or week, including versions and exports. For how often other teams back up, see backup frequency benchmarks.
  2. Estimate how many days files stay locked, using your measured dates rather than the setting alone. If you have not measured yet and your setting is 7 days, use the source's closer-to-14-days budgeting figure as a conservative starting point.
  3. Multiply the two numbers, then add margin for growth and for any copies you keep for other reasons.

If your forecast files are small, the added cost may be modest. If you keep large exports, many versions, or both, the difference can grow quickly. Ask your storage provider for a pricing estimate that uses your measured numbers instead of the configured setting.

How to choose your lock period

The same source describes common practice: "The most common recommendation is 7 to 14 days, with 14 days being a reasonable default for most environments." (Backblaze, "Object Lock Mistakes That Put Immutable Backups at Risk") It also gives a second view: "Security teams that have tested their incident response workflows often find 7 days works fine." (Backblaze, "Object Lock Mistakes That Put Immutable Backups at Risk")

These two statements do not conflict. The first is a general default. The second describes what some teams find after they have tested their response. The practical lesson is that a shorter lock can work when you have tested how you recover and know you can act within the window. If you have not tested yet, the longer default gives you more room to find problems.

Think about detection time too. A forecast error may not surface until a monthly close or a quarterly review. If a lock expires before anyone notices a problem, the good copy may be gone. Compare how long errors usually take to surface in your organization with the lock window you measured.

Common mistakes to avoid

Teams that run into trouble with backup locks usually make one of a few mistakes:

  • Trusting the setting alone. The number on the settings page is what you asked for, not necessarily what the files show. Check the bucket.
  • Ignoring write dates. Files written on different days have different lock end dates. Checking one file tells you about only one file.
  • Budgeting for the setting, not the lock. Storage costs follow the data that cannot be deleted, which may be more than the configured number of days suggests.
  • Skipping restore tests. A lock keeps a file in place. It does not prove that you can open it, read it, and match it to your working version.
  • Giving too many people control. A lock is not a replacement for access control. Keep the list of people who can change backup settings short and written down.

How to check your real lock dates

You do not need special tools to start. The steps below work with most backup setups, though the exact screens will differ:

  1. Choose three to five forecast files written on different days. If your cycle is weekly, include one from early in the week and one from late in the week.
  2. For each file, record its write date and its lock expiration date. Use your storage console or whatever tool your team uses to report on the bucket.
  3. Subtract the write date from the expiration date and record the number of days.
  4. Compare each result with the setting you configured. If your numbers for a 7-day Veeam setting match one of the three values from the source, the pattern described above applies to your setting. Other tools may behave differently.
  5. Repeat the check after any change to the backup job, the bucket, or the retention rule. Check new files after a change, not only the old ones.

Write the results in a shared place. If only one person knows the numbers, the team loses them when that person changes roles.

Setting up a restore test

A locked copy is only useful if you can restore from it. Pick one forecast file from the locked copy, restore it to a separate folder, open it, and compare its totals with the working version. Do this before you need it, and write down how long the steps took. For more recovery steps, see backup recovery checks before quarter-end.

Run the test on a schedule, and vary the file. Test files from different write dates so you know the lock and the restore both work across the window. Record who ran the test, what they restored, and whether the totals matched.

If a restore fails, treat it as a finding. Check whether the file was still locked, whether the copy is complete, and whether your restore steps are current. Fix the gap, then test again.

What to write down

A short runbook saves time when someone new joins or when an incident happens. Keep it in the same place as your forecast process, not buried in a backup console. Include:

  • The configured lock period and the date it was last changed.
  • The sample of files you measured, with write dates and lock end dates.
  • The three possible outcomes from the source, so readers know what a 7-day setting may produce.
  • The restore steps, with the name of the person who last tested them.
  • The budget figure for locked data, and the assumption behind it.

A runbook that people actually read is worth more than a detailed one that sits in a folder nobody opens. Keep it to a page or two and review it each quarter, which lines up with the quarterly review many revenue teams already run.

Working with finance and IT

Revenue leaders rarely own backup settings, but they do own the risk. Start a short conversation with the people who do. Ask three questions: what is the configured lock period, what are the measured lock dates on recent forecast files, and what is the plan if a restore is needed?

Bring the measured numbers to that conversation, not just the setting. A sentence like "our 7-day setting produced locks through day [X] on the files we sampled" gives IT something concrete to check.

Also agree on who signs off on changes. A short written note with the owner, the date, and the reason is enough for most teams.

Final thoughts

A backup lock is a useful safety net, but only when you know what it actually does. For a forecast archive, the setting you choose is the start of the conversation, not the end. The dates on your files tell you what is protected, and the restore test tells you whether that protection works when you need it. Measure both, write down what you find, and revisit the numbers whenever the backup process changes.

Your next step today: open your backup console and check the lock expiration date on one forecast file written last week.

Related guides: Microsoft 365 backup: 3 backup and recovery checks.

Frequently asked questions

Does a 7-day lock always last seven days? No; one source we checked describes files locked through day 10, 14, or 17 after a 7-day Veeam setting.

When does the lock clock start? The clock starts when each file is written to storage, not when the setting changes.

How much storage should I budget for? Budget for the data that cannot be deleted at any given time, which may be closer to 14 days' worth when your setting is 7 days.

Sources