Backup For
Trade Publishers & Small Media Companies

The records that make up a publisher's archive

A trade publisher or small media company generates records across two different functions inside the same office, or the same pair of computers: the editorial and production side that makes each issue, and the business side that keeps the publication running. Most of it is a mix of layout application files, spreadsheets, PDFs, and folders organized by issue date or client name.

• Print ready layout and press files, the packaged, output ready files sent to a printer or press for each issue
• Photo and image libraries used across issues, including licensed images and staff or contributor photography
• Editorial drafts and in progress copy for stories not yet finished or not yet run
• Back issue archives covering every issue the publication has ever produced
• Advertiser insertion orders and ad contracts documenting what was sold, to whom, and for which issue
• Ad artwork supplied by clients for each ad placement
• Subscriber and circulation lists
• Mailing and distribution files
• Rate cards
• Contributor and freelance agreements
• QuickBooks company files covering the business side of the operation

All of this sits on the Windows computers in your office as ordinary files, not as a regulatory record, and Everyday Backups makes no compliance or recordkeeping claim about any of it. It backs up files saved locally to your Windows computer. If your circulation system or your website's content management system is cloud hosted, its database lives on that vendor's servers, not on your office computer, and is not something a local backup service reaches. What is covered is anything your team saves or exports onto your own machines, which for most publishers is the majority of the files that actually matter day to day.

Your archive is the product, and the press date does not move

A publisher loses two different things at once when a hard drive fails or a file goes missing, and both are worth naming plainly, because neither is really about convenience.

The archive is cumulative and irreplaceable. Every issue your publication has ever produced is an asset that can still be resold, reprinted, licensed, referenced, or used to prove what ran and when. A back issue is not a discarded draft once the next issue ships, it stays valuable for as long as someone might want to see what your publication covered, quoted, or advertised in a given month or year. Recreating a run that spans years, or decades, is not a matter of re-downloading a file from somewhere else. It is a re-manufacture, and for most publishers it is simply not possible, because the contributors who wrote the pieces have moved on, the source photos were never kept anywhere but that one folder, and the advertiser artwork supplied for that issue was never sent to you a second time.

The deadline is set by other people, not by you. A press date, a mail date, and a bindery slot are booked with a printer, a mailing house, and a bindery days or weeks in advance, on their schedule, not yours. Losing the layout files for an issue three days before press does not simply push the issue back three days while you rebuild the work. It can mean losing the press slot entirely, missing the mail date that was coordinated with a distribution schedule, and losing the ad revenue that issue was built to carry, since an ad placed for an issue that does not run on time is an ad that did not deliver what the advertiser paid for.

Both of these are reasons a lost file matters more to a publisher than it might to a business that is simply reordering the same product every month. The archive cannot be re-bought, and the calendar cannot be renegotiated after the fact.

What this covers, and what it does not

Everyday Backups backs up files saved locally on your Windows computer. It does not back up a cloud-hosted content management system running your website, a hosted circulation database run by a vendor, or a web server anywhere outside your own office.

If your publication's website runs on a content management system hosted by a vendor, or your circulation and subscriber management runs through a hosted platform, the data behind those systems lives on that vendor's own servers, not on your office computer. A local backup service has no way to reach a database it was never given access to, and Everyday Backups makes no claim that it does. What it protects is the layout files, image libraries, editorial drafts, back issue archive, contracts, artwork, lists, and QuickBooks file that your team saves onto your own Windows machines, which for most independent publishers is still the bulk of what would be genuinely painful to lose.

It is also worth saying plainly that a backup is a data recovery tool, not a security product. Backing up your files does not prevent someone from viewing them, stealing them, or gaining unauthorized access to your systems, and it does not stop ransomware from encrypting your machines in the first place. What it does is give you a copy to recover from after something has already gone wrong, whether that is a failed hard drive, an accidental deletion, or an attack that has already happened.

Why this is not the print shop page, and not the marketing agency page

This page is not the print shop page, and it is not the marketing agency page, even though a publisher's office can look similar to both from a distance.

A print shop and a marketing agency both produce to order. A job comes in, it moves through production, it is delivered to the client, and in most cases its value to the business that produced it mostly ends there. See our backup for print shops and backup for marketing agencies pages for how that shapes their own backup priorities.

A trade publisher works differently. You own and resell a growing archive. Every issue you manufacture becomes inventory that you keep, indefinitely, and that inventory can still generate value years after it was made, through reprint requests, licensing, research references, or simply proving what ran in a given issue. That inventory accumulates on a calendar you do not control, since a press date is fixed by your printer's schedule and a mail date is fixed by your distribution plan, not by how ready your files happen to be. A print shop or an agency that loses a finished job can, in the worst case, produce a similar job again for a similar client. A publisher that loses its back issue archive has lost inventory it can never make again in the same form, produced against a calendar that already moved on. That is a different risk shape, and it is why this page exists separately from those two.

Where backup gaps hide in a publisher's office

A publisher's office does not usually lose files all at once. The gaps tend to hide in a handful of specific habits.

• Layout software treated as the only copy. Your page layout application, named here only as a software category and not as an endorsement of or a compatibility claim about any specific product, opens and edits your files. It does not by itself guarantee that an independent backup exists somewhere other than the machine it runs on.
• Back issue archives kept on one machine, organized by folder and never confirmed to be part of any backup routine. A folder structure that goes back years is easy to assume is safe simply because it has survived this long.
• Ad artwork supplied by clients saved once and never copied elsewhere. Artwork sent by an advertiser for a specific placement is often not something you can quickly request again, and sometimes not something you can request again at all if the advertiser's own campaign has ended or the contact has moved on.
• Editorial drafts and in progress copy stored only on a writer's or editor's laptop. A piece that is still being worked often has no copy on a shared or backed up location until it is finished.
• Subscriber and circulation lists exported once for a mailing and then left on a single computer. The list itself often represents work that took months or years to build, with no second copy anywhere.
• Cloud storage sync mistaken for backup. A synced folder mirrors whatever is currently on your device. If a layout file is deleted, corrupted, or encrypted by ransomware, that change can propagate to the synced copy too, often within seconds. See cloud sync versus backup for the distinction.
• QuickBooks file stored only on the office computer that also holds every layout file and image library. A single failure on that machine can threaten the editorial archive and the accounting records at the same time.
• Backup media kept in the same building it is meant to protect. An external drive sitting next to the computer it backs up offers no protection against fire, flood, or theft affecting the whole office at once.
• Whoever set up the folder structure has since moved on. A small publishing operation is often run by a lean staff, and when the person who knows where the back issue archive actually lives leaves, that knowledge is not written down anywhere else.

Understanding the 3-2-1 backup rule for a trade publisher

The 3-2-1 rule is a straightforward framework promoted by CISA and widely used in small-business backup guidance. Applied to a publisher's office, here is what it looks like against the records that actually matter.

A backup standard for publisher offices

The checklist below reflects CISA small-business backup guidance and FTC small-business cybersecurity material, applied to the file environment of a publisher's office. It is a starting framework for backup decisions, not a legal, compliance, or recordkeeping standard.

• Map every machine in the office. List every Windows computer used for layout, editorial work, ad sales, and accounting, including any laptop a writer or editor works from off-site. For each one, ask what data lives there that is not copied anywhere else.
• Include your back issue archive explicitly. This is often stored in a folder structure outside your layout application entirely, organized by issue date. That folder needs to be explicitly included in your backup configuration rather than assumed to be covered automatically.
• Retain enough version history to reach back through a full production cycle. CISA guidance notes that ransomware and accidental deletions are often not discovered for days or weeks, so a short backup window may not reach a clean, pre-incident copy of a file that was quietly damaged earlier.
• Encrypt backup data in transit and at rest. Advertiser contracts, insertion orders, contributor agreements, and QuickBooks files include financial and contact detail for advertisers, contributors, and subscribers.
• Monitor backup jobs and receive failure alerts. A backup job that fails silently leaves you with no current coverage and no warning, particularly in the days before a press deadline.
• Test restores on a regular schedule. A practical cadence is a quarterly spot restore: pick a layout file, a back issue, an insertion order, and a QuickBooks file from different dates, and confirm you can retrieve and open them. CISA's guidance is direct on this point, an untested backup is not a reliable backup.
• Document who handles recovery. Someone in the office should be able to answer three questions without searching: what is backed up, where does it go, and how do you start a restore.

For a broader self-assessment of your current backup posture, see the small-business backup checklist. For general QuickBooks backup practices referencing Intuit's own documentation, see backup for QuickBooks.

Your layout software, editorial system, and QuickBooks: what backup actually covers

Ransomware and the publisher's office

The FTC and CISA both publish guidance specifically noting that small businesses, including operations holding years of accumulated records, are targets of ransomware campaigns, in part because they typically have less dedicated IT support than larger organizations.

For a trade publisher, the factors that make a ransomware event particularly consequential are straightforward: a back issue archive, layout files, and advertiser contracts concentrated on one or two Windows machines, a subscriber and circulation list built over years and stored locally, no backed up copy of the folders that hold current production files, and typically no dedicated IT staff checking backup health day to day. Everyday Backups is a data recovery tool, not a security product, and it does not prevent ransomware from occurring in the first place, nor does it promise that your office can keep working uninterrupted while systems are down.

CISA's #StopRansomware guidance identifies offline and encrypted backup copies as the primary technical recovery path once ransomware has already encrypted production files. A backup connected to the same network as the infected machines, or a sync folder that mirrors changes in real time, can itself be encrypted before the attack is even noticed. A backup that is not continuously mounted on your local network is the copy most likely to come through a ransomware event with your layout files, back issue archive, and subscriber list still usable. For more on what readiness looks like after an attack, see ransomware restore readiness.