rrJob queue database

If this option is disabled, then the rrServer saves the job database every 30 minutes.

Which means all changes and new submitted jobs are lost if the machine crashes/losses power.


If this option is enabled, then the rrServer saves jobs direclty after submission into a database file on the machine.
Job changes are saved more frequently as well.


Please see Hardware Requirements for the rrServer for more information if you enable this feature.




rrJob Data Files location

You may change the location of the rrJob Data Files.
This is NOT the job database/queue.
These are additional files.

The rrJob Data Files are:

  • Preview Images (can be encoded for confidential content)
  • rrViewer caches
  • Frames rendered table
  • Render log files
  • Framebar image



Delete Jobs

The server will automatically delete jobs based on these settings.

History Database


All jobs that are finished and then deleted will be exported into the History Database.

You can view render times, frame ranges and all other information about a job.

And you can also resubmit a job. 


Export deleted jobs into database 

If a job is removed from the queue, then it is exported into the History DB.
The History DB can be accessed by the rrHistoryDB application, by python or rrRealmReporter

Database name

The jobs are either saved into databases named after your company project or the user.

Delete after

Each database is split into a file per month. After x days this monthly file is deleted.

Zip render log files

Zip the render log files to keep them.

Note that you have to start all rrControl instances that are used to execute the "delete" command.
Otherwise rrControl clears the log folder before the rrServer gets the command to zip the log files.