I also use this spool file backup strategy:
1) We dump spool files to a Roadrunner Virtual Backup (a.k.a. to disc) at night.
2) Then we print a SHOWOUT @[log in to unmask]@ to a 4-UP laser. *
3) Spool Files more than 9 days old are purged.
4) Next workday we copy the Virtual Backup to a DDS tape in RoadRunner append mode.
5) The 4-UP printout is filed away.

Uses:
a) If someone needs a report more than 9-days old we refer to the printout and do a RESTORE.
b) Per below, correct, COPY does not work, but RESTORE will.
c) Yes, you get a new spool file number, best to RESTORE with the SHOW option (or if using RoadRunner, REPORT), so you know what the new number is.  Saves you from having to look for it again.
d) The 9 day window usually covers a full work-week plus both sides of a weekend.
e) Since we do this daily we'll have a 9 day rolling window from which to restore from.
f) The 9 day purge also keeps the number of spool on the system down.

* (Actually #2 is a customized MPEX Sorted LISTF against @.OUT.HPSPOOL, to each his own.)

> -----Original Message-----
> Barry Lake wrote:
> >
> > At 6:58 PM +0000 9/22/99, [log in to unmask] wrote:
> > >   As I'm sure we all know, the HPIB interface is going away in a future
> > >release of MPE, although I can't remember when.  My problem is that currently we
> > >backup our spoolfiles to our 7978 tapedrive before lowering the fence to print our
> > >output from our nightly schedule.  We do this just in case a printer fails,
> > >ribbon jams/breaks, or...?  What I've attempted doing is copying the
> > >spoolfiles to another group before lowering the fence to print, which works fine, but I
> > >can't figure out how to copy them back to the spool to reprint if we do have a
> > >problem. Any help would be appreciated.
> >
> > You can't simply copy them back to the OUT.HPSPOOL group -- they won't be
> > tied into the spooler that way. What you need to do is use the ;PRINT
> > option of the SPOOLF command.