Thanks, I will take a look in the log. I did find out one thing that is interesting. Last night at 9pm I was logged into my filers just to make sure that the dedup jobbed kicked off fine. I issued the sis status command a few times and noticed that the dedup job that I kicked off manually that took about 2 hours only took about 10 minutes when scheduled. In other words, issuing the command:
sis start -s <vol>
is different than having dedup start when it is scheduled. If I remember correctly, the sis start command scans all the data first and then goes back and does a search for blocks that can be deduped. It appears that if this process is started with a schedule, only the search step needs to be done and it is very fast.