Anyone know of a bug id, or does DRS scheduler automatically bump the
start date out a few months if a backup attempt fails to connect to
backup server after so many times? I've had this happen at a few
clients (various 5.1.x versions) and TAC is not able to find anything causing DRS scheduler start date to get set in future.
Why is there a start date for the scheduler anyway? Why not just