Fiery Secure Erase blocks reprint — job policy & disk space recovery
Joe B.
Reviewed for technical accuracy
Specialities: Fiery DFEs, Command WorkStation, Secure Erase policies, printed/hold queues, production print workflows
Fiery Secure Erase deletes jobs before reprint — printed queue, job policy, disk cleanup & job retention
Technician
Quick scan first:
• Which Fiery do you have (for example, FS200, FS350, FS500, FS600) and which engine (Ricoh, Konica Minolta, Canon, Xerox)?
• Are you using Command WorkStation on Windows or macOS?
• What exactly happens: Reprint icon greyed out, jobs disappear from the Printed queue, “disk full” or “low disk space on Fiery server” warning, or Secure Erase taking forever to run?
Technician
On Fiery, every job is written to the Fiery hard disk while it RIPs. When a job is deleted (for example, it falls out of the Printed queue, someone clears it, or you run Clear Server), Fiery Secure Erase overwrites the job data on disk with a multi-pass wipe, so the job can’t be recovered.
If:
• Enable Printed Queue / Save printed jobs is off or the limit is very low, and
• Secure Erase is set to erase immediately for all deleted jobs,
then jobs are securely wiped as soon as they leave the queue — which means no Reprint, and heavy disk churn when the disk is nearly full.
Plan: 1) Review your Printed queue & Reprint settings. 2) Tune Secure Erase operational mode so it still meets your security policy. 3) Do a controlled disk space recovery (Clear Server + job log retention) so reprint and performance stabilize.
Technician
On a workstation with admin rights:
1) Open Command WorkStation → right-click the Fiery → Device Center → Configure.
2) Go to Server > Jobs (or Job Management > Printed Queue on newer FS versions). Make sure Enable Printed Queue / Save printed jobs is turned On and set a reasonable limit, e.g., Jobs saved in Printed queue: 50–200 depending on volume.
3) In the same area, check whether Secure Erase is enabled. On newer Fiery FS systems it’s under Fiery Server > Security > Secure Erase. Note the Operational Mode: erase on job deletion, scheduled, or disabled.
4) Confirm that Reprint is allowed in your Job policy and that jobs are not forced to be deleted immediately after printing (some environments use “delete on print” for Direct queue jobs).
Once Printed queue is enabled and Secure Erase is not wiping jobs the moment they drop out, you should start seeing the Reprint option again for recent work.
Technician
When Secure Erase is on, Fiery overwrites job files on the HDD whenever a job is deleted by any Fiery function (users deleting jobs, Printed queue rolling over, Clear Server, etc.). That’s by design for compliance, but:
• If the Printed queue limit is high and you print large VDP/PDF jobs, the Fiery disk can fill with retained jobs.
• When the limit is reached, jobs “fall off” the Printed queue and are securely erased, which can be disk-intensive and slow, especially if many big jobs drop at once.
• Job metadata stays in the Job Log, but the image data is gone — so Reprint is not possible for those jobs.
Security-wise, that’s correct; operationally, we want a balance: enough jobs in the Printed or Hold queue to support reprint workflows, but not so many that the Fiery hard disk is constantly near full and Secure Erase is in overdrive. Next we’ll adjust how you store “master” jobs so you’re not relying only on Printed queue.
Technician
For heavy reprint environments, Fiery recommends a “master on Hold, copies from Printed” approach:
• Create a virtual printer or preset that sends important work to Hold, then operators release those jobs to Print when needed. The Held job stays on disk as your reprint “master”.
• Keep Printed queue for short-term reprints (same day / same shift). A limit of 50–150 jobs is usually enough.
• For jobs you must retain for weeks or months, use Fiery job archive (to network storage) instead of keeping everything on the Fiery HDD where Secure Erase and Clear Server will wipe them.
This way your job policy intentionally separates “must keep” jobs (Hold/Archive) from “nice to have” jobs (Printed), which reduces random data loss when Secure Erase or disk cleanup runs.
Technician
In Command WorkStation as admin:
1) Pause incoming jobs or notify users of a maintenance window.
2) Manually delete old jobs from the Hold and Printed queues that are no longer needed. With Secure Erase enabled, Fiery will overwrite those job files as they are deleted.
3) From the Server menu, use Clear Server, but choose the minimal options: for example, clear Completed/Printed jobs and unused VDP resources first, not the entire server configuration.
4) After Clear Server completes, give Secure Erase time to finish overwriting the freed space — avoid power cycling the Fiery mid-wipe.
5) Re-enable job submission and confirm that free disk space is back within a healthy range (typically 20–30% free).
This recovers disk space in a way that aligns with your data destruction policy without surprising operators who rely on active jobs in Hold.
Technician
• Each deleted job triggers a multi-pass overwrite of the job data on the Fiery disk (1-pass or 3-pass, depending on how the admin configured it for your FS level).
• If the disk is almost full and you delete a lot of large jobs at once (Clear Server, rollover in a big Printed queue), the secure wipe can contend with RIP and print traffic for I/O and CPU.
• On newer FS600 systems, Secure Erase follows NIST-style data sanitization and even more strictly guarantees that deleted jobs can’t be recovered, which is great for security but heavy when disk hygiene is poor.
Best practice: keep enough free disk space, schedule heavy Clear Server / Secure Erase windows during low usage, and avoid using the Fiery HDD as a long-term archive for thousands of jobs.
Technician
• Printed queue: Enabled, limit to ~50–150 jobs. Operators use Reprint here for same-day reruns.
• Hold queue: Used as the “live library” for recurring jobs. Saved presets or virtual printers send client work to Hold so it remains reprintable.
• Job archive: Long-term retention moved to network storage. You can Retrieve archived jobs back into Hold when needed.
• Secure Erase: Left On, but you coordinate with security on operational mode (for example, erase when jobs are deleted from queues, and schedule heavier cleanup out of hours).
• Disk maintenance: Monthly or quarterly review of Held/Archived jobs plus a controlled Clear Server for old Printed jobs.
With that, your Fiery stays compliant, the disk doesn’t fill, and operators can still rely on Hold, Printed, and Archive for everyday reprint workflows.
Technician
Quick answer: the accepted fix
Accepted fix when Fiery Secure Erase removes jobs you want to reprint: enable the Printed queue and save a limited number of printed jobs, keep “master” jobs in the Hold queue or Archive, and use Clear Server plus manual deletion to free disk space. Leave Secure Erase enabled for compliance, but schedule heavy cleanup so it doesn’t wipe everything operators still need.
Why Fiery Secure Erase hides Reprint (job deletion, queues & HDD)
On a Fiery DFE, every job passes through the Print, Hold or Printed queues and is written to the Fiery hard disk. When you delete a job manually, when it rolls out of the Printed queue, or when you run Clear Server, the Fiery treats it as “deleted”. With Secure Erase enabled, those deleted jobs are securely overwritten on the disk. After that, the job’s image data is gone, so Command WorkStation can only show a Job Log entry, not a reprintable file.
How to confirm Reprint & disk space are healthy
To verify your Fiery job policy is working, send a couple of test jobs: one to the Hold queue and one directly to Print. Confirm that the Held job remains available after printing and that the Printed job shows Reprint enabled in the Printed queue. Check the Fiery front panel or diagnostics to make sure available disk space is well above critical level. If Secure Erase is on, delete a non-critical job and watch that the Reprint option disappears only when you expect it to (after deletion or Clear Server), not immediately after printing.
Secure Erase & Fiery disk full — quick troubleshooting tips
Most “Reprint not available” cases come from Printed queue being disabled, low job retention, or aggressive Secure Erase combined with a nearly full disk.
Quick path: in Configure enable the Printed queue and set a safe “jobs saved” limit, move recurring customer work to the Hold queue or Archive, then run a controlled Clear Server to free space. Keep Fiery Secure Erase on to protect data, but treat it as part of your disk-hygiene plan, not a surprise — schedule heavy erasure when the press is idle so operators keep reliable reprint workflows.
Disclaimer: This information is AI-generated and intended for general guidance only. For advice specific to your environment, please consult a verified expert on Whizz-Tech before making decisions.
Getting Started Is Easy
Ask for help, 24/7
Members enjoy round-the-clock access to 12,000+ verified Experts, including tech support, mechanics, vets, and more.
Expert will respond in minutes
We match you with an Expert who specializes in your situation. Talk, text, or chat — whichever you prefer.
Save time & money
No scheduling hassles or expensive consults. Membership can save you significant time and money each month.
FAQ
Why are jobs missing from Fiery Reprint after Secure Erase is enabled?
If Printed queue is disabled or the “jobs saved” limit is low, jobs are deleted right after printing. With Secure Erase turned on, deleted jobs are overwritten on the Fiery disk, so only the Job Log remains and Reprint is no longer available for those jobs.
How do I keep Fiery Secure Erase on but still allow reprints?
Enable the Printed queue with a reasonable job limit, store important work in the Hold queue or job Archive, and use Clear Server during maintenance windows. Secure Erase can stay on to wipe deleted jobs, while active jobs in Hold/Printed remain reprintable.
What’s the safest way to free disk space on a Fiery server?
Delete old jobs from Hold/Printed, then run Clear Server from Command WorkStation to remove completed jobs, logs, and unused resources. With Secure Erase enabled, Fiery securely overwrites the freed space, so plan this as a scheduled disk cleanup and avoid powering off the Fiery during the process.
Does Clear Server permanently remove jobs when Secure Erase is on?
Yes. Clear Server deletes jobs and logs; with Fiery Secure Erase enabled, those deleted objects are also overwritten on the hard disk, so they cannot be recovered for Reprint. Archive any jobs you need before running Clear Server on a Secure Erase system.
Sources
- Fiery Help — Printed queue, Secure Erase & job options
- Fiery Security White Paper — Secure Erase & data sanitization
- Fiery Command WorkStation — Clear Server & freeing disk space
Filed under: Network security / VPN / office policies (advanced)
Related articles
- Android “Secure print only” — enterprise toggle: setup, policy, fixes
- Windows Hello for Business blocks driver installs — policy remediation
- Android Work Profile blocks printing — policy switches that fix it
- ChromeOS “Admin policy blocks printing” — allow printers in console
- Printer won’t print prescriptions or medical reports — it’s urgent and nothing comes out
- Chrome managed profile watermark prints wrong — policy override checks you can do safely
- Ricoh “Hold Print” enabled by AD — disable policy
- Ricoh SMB scan works but print fails — AES signing mismatch