I just completed a revaulting. I wanted to make sure this did not execute during the day so I spaced out the revaulting into blocks. Overall it took a few weeks but there was a lot of unused time. In testing, we executed too much and the redo logs for the database filled up the storage volume. There are a lot of DB record changes. By looking at the contexts, I was able to create groups of products and libraries that when I changed the vaulting rules, would execute in 8 hour blocks. After each run, I would validate vaults and check progress.
I do not think there is a setting to tell it to start and stop revaulting. These are queue jobs so those could be started and stopped however I would be nervous monkeying with them. I can tell you that there was one test run that had 3M+ file moves which causes a DB issue. System was successfully able to do what it could and after a few tries, did manage to swallow that goat without errors. So short answer is yes, you can schedule the runs to start but they will run till completion.
