• These scripts are for those of us who don't have the hardware to run update_releases in a separate process while backfilling, or don't want to risk a huge postprocessing backlog.

• The scripts will incrementally backfill one day at a time, ensuring that all releases are processed for each day of backfill.

• update_binaries will be run every 'x' runs of update_releases in order to keep your current releases up to date while backfilling. This value is set in BINARIES_KEEPUP.

• It will also run update_parsing, removespecial, update_cleanup, and optimise_db after each day of backfill is completed.

• safebackfill.sh will backfill all active groups
• safebackfillgroup.sh will backfill a single group

• First edit the paths for PHP and Newznab, set the number of days to backfill, enter your MySQL information, and number of update_releases loops to allow before running update_binaries again.

• For safebackfill.sh simply run the script.

• For safebackfillgroup.sh run the script with the full group name as a parameter: ./safebackfillgroup.sh alt.binaries.teevee for example.

This script is intended to be run instead of your usual screen script until you've reached the desired level of backfill

• Do I need to set my backfill days for groups in the site admin? No, the script will do it for you, and you may overload the backfilling process if you set it manually.

• Should I run this at the same time as my screen script? No, as mentioned above, this is meant to temporarily replace your screen script until you're done backfilling.

• Does the script stop when it's done backfilling? Nope, it will keep running so you don't fall behind on current releases until you notice your backfilling is finished and switch back to your regular screen script.

• How do I know when the script is done? You'll need to keep an eye on your active groups in Admin/View Groups to see what the "Backfill Days" value is. Once they're at the number of days you set in BACKFILL_DAYS, you're done!

• The import script is a slightly updated/modified version of the standard screen script for importing.
• Because the new nzb-import.php allows the importing of any desired number of NZB's, you are able to set that number and the script will ensure all imported releases are processed fully before importing more.

• First edit the paths for PHP and Newznab, set your nzb path, number of nzb's to import per run, and all the other variables.
• Simply run the script in your screen/tmux session and let it do its thing.