Stop a Time Machine Backup That Is Competing With the VPN

A backup that starts in the middle of a VPN session competes for the same uplink and makes both jobs slower. The fix is a deliberate stop followed by a schedule change, rather than pulling the network out from under the backup. Apple's own controls cover both halves of that. Doing them in the other order is how a temporary bandwidth decision becomes a long backup gap.

Stop the Backup You Are In

The Time Machine menu in the menu bar carries the controls you need: current progress, the time of the last backup, Back Up Now, and an entry to stop or skip the running operation.

Use that entry before you disconnect a network destination. Cutting the connection instead leaves the backup interrupted and teaches you nothing about why it was slow. A deliberate stop records an intention, and the next backup starts from a known point. It also avoids leaving a sparse bundle in a state the next attempt has to repair.

The same menu is where you confirm the last completed backup, which matters more than the stop itself.

Where the Menu Hides

If no Time Machine item appears in the menu bar, the status display is switched off rather than the feature. Turn it on through the Time Machine settings for the installed macOS release. The wording of that control has moved between releases, so look for the option about showing Time Machine in the menu bar. The toggle lives in the Time Machine pane rather than in Control Center.

Then confirm the destination is still configured before blaming the schedule. A destination that was forgotten or is offline makes the menu report a state that looks like a scheduling failure. The command tmutil destinationinfo answers that question directly.

Change the Window, Not Just This Backup

A recurring conflict needs a schedule change, and the path is System Settings, then General, then Time Machine, then Options. The frequency control offers manual backup or an automatic interval, depending on the release.

Manual mode is the right tool when you want to finish a VPN session before the next network backup begins. Understand what it does: it changes automatic scheduling for the whole Mac, not for one connection. It also obliges you to arrange the next backup yourself. A temporary bandwidth decision becomes a permanent gap the moment that obligation is forgotten.

tmutil status
tmutil destinationinfo
tmutil latestbackup

Those three commands describe the state you are about to change: whether a backup is running, where it would go, and when the last one finished. Capture them before editing settings so the comparison afterwards means something.

Two Settings That Look Alike

Two options sit close together and solve unrelated problems. One selects source files to omit from backups, and the other removes a configured destination entirely.

Excluding a folder does not stop Time Machine from using a VPN connection, and forgetting a destination is not a way to postpone today's backup. Both mistakes are common because the labels sound like policy. A network-enforced prohibition on backup traffic over a particular tunnel is a separate design, and a schedule choice says nothing about the path a later backup takes. Guessing at a process exclusion can affect far more than one backup.

Read the middle column against the problem you actually have before clicking either of the first two.

Prove a Backup Completed, Then Restore the Schedule

When the intended network and destination are available again, run a backup and wait for it to finish. Disconnect nothing until the menu reports that the operation has stopped.

tmutil startbackup --block
tmutil latestbackup
tmutil listbackups | tail -3

A completed backup is the only proof that the gap is closed, and the timestamp from the second command is the evidence to keep. If manual scheduling was temporary, restore the previous automatic frequency in the same session. Leaving it manual is a decision rather than a default. Write the new window and the reason for it beside the destination details.