How do you achive your Fiery jobs

[rcreveli]

We regularly archive our Fiery jobs on the Fiery server but, would like them to be backed up onto another device. We're currently trying to backup to a USB flash drive with limited success. When we archive large jobs 1GB+, the Fiery craps out. The flash drive is a 256gb USB 3.0 and the port is USB 3.0 so, I don't think that's the issue.

Before I started the Fiery had to be reloaded and we lost all 300 jobs in the archive Queue and don't want a repeat of that.

We do back up the original files in prepress but, reference the jobs in the Fiery for color settings, stock changes etc...

The machine is a Ricoh 7110 with a E-43A controller

Thanks
Ray

 

[DYP]

I would add another drive to the Fiery and set that as your archive drive. Either external USB or internal SATA. Then just back up that drive with a second drive on the Fiery or somewhere on the network.

 

[wonderings]

I never backup anything on the Fiery, I have the working files or imposed PDF's done on my computer so if I need to repeat I just drop the files back in. Seems easier to me and one less computer to worry about backing up.

 

[Possumgal]

I can see the need for archiving the settings on a complicated job or when critical color adjustments have been done. I believe when archiving, the Fiery asks where you want it archived. Maybe it just won't recognize a USB thumb drive, but would another kind.

 

[PricelineNegotiator]

I never backup anything on the Fiery, I have the working files or imposed PDF's done on my computer so if I need to repeat I just drop the files back in. Seems easier to me and one less computer to worry about backing up.

If you're a government office that has 1000's of forms and those are all that the machine ever runs, and those forms "never change", then it's totally legitimate.

 

[kslight]

Can't you tell the Fiery to archive to a network location? That would generally be my preference. Or, what happens if you archive to the internal hard drive then copy that to your flash drive? I've never had problems doing it this way, though I only do this for select jobs.

 

[msaeger]

You can archive to the internal drive, an external drive, or a network location. I would not really consider archiving to the internal drive a backup since when the Fiery crashes you will lose all the jobs anyway. On the archive tab settings you can manage the locations.
​​​​​​
You also can run the Fiery backup which will save different settings depending on what system software the Fiery is running.

 

[kslight]

You can archive to the internal drive, an external drive, or a network location. I would not really consider archiving to the internal drive a backup since when the Fiery crashes you will lose all the jobs anyway. On the archive tab settings you can manage the locations.
​​​​​​
You also can run the Fiery backup which will save different settings depending on what system software the Fiery is running.

If you are referring to my post...I said to archive to the internal drive THEN copy to the flash drive, instead of trying to archive to the flash drive directly..

 

[Shawnd]

Command Workstation 6.2

Archive Manager

Fiery Command WorkStation includes a new, simple, and safe storage solution for all Fiery jobs. To start using the Archive Manager, users are guided through a simple process to migrate all currently archived jobs on a Fiery server, for all connected Fiery servers, to a location that is independent from the Fiery server. Users with administrator rights have the freedom to set up archive folders on the network, cloud, or their own computer. Archive Manager offers a much more flexible solution for job storage: - Job archives can follow the same IT backup procedures as any other digital asset - Job archives can be easily shared across all connected Fiery servers - Users can find archived jobs faster using the basic search function, and find jobs even when the Fiery server is disconnected, or is being upgraded or reloaded - Users can list all archived jobs in one view where jobs can be previewed and searched If users have archived jobs on the Fiery server, the migration process moves those files to the chosen location through the Archive Manager.

This resolves previous issues such as:
- Losing archived jobs during Fiery software reload or upgrade processes
- Not being able to archive additional jobs after reaching 10,000 jobs per Fiery server in all queues
- Risk of locking up your Fiery server from lack of hard drive memory

Archive Manager is only available for cutsheet and high-speed inkjet engines

 

[DYP]

You seamed to overlook that you can now manage all job archives from all connected Fiery Clients. You do need to be networked to those archive folders from your client workstation. I find this is a great, maybe the greatest feature of the new Archive Manager.

 

[msaeger]

If you are referring to my post...I said to archive to the internal drive THEN copy to the flash drive, instead of trying to archive to the flash drive directly..

I guess I wasn't referring to any post just putting crap out there I get people archiving to the internal space and thinking their jobs are backed up.
​

 

[rcreveli]

Thanks for the replies. We were on CWS 5.8 because of bugs between the 7110 & 6.0. I just spoke to the Fiery specialist and he said 6.2 is a go. We're going to update to 6.2 and migrate the jobs through archive manager.