Since you have ssh access you might consider setting up a 'unirepo' (universalrepo) using file system (you're already using file system repo with your courses ... the alias problem when restoring to other server).
Setting up a unirepo would enable you to do command backup of a course in production server ... which would save the backup to the unirepo. Those backups, run from the command line, take apache out of the loop ... will be faster and can backup larger courses.
Then, in the dev instance, set up a file system repo pointed to the unirepo. Set up the file system repo in only one course that you won't be deleting in the dev instance, and you can backup/restore on that server in less time ... no download only to have to turn around and upload (the backup .mbz files).
I've done exactly as briefly described above for 3 sites (different entities) who 'share' courses amongst themselves - one unirepo - 3 production sites ... no issues with time outs uploading/downloading, no increase file size uploads, etc.
Can share a how to if interested.
'spirit of sharing', Ken