i don't use arcserve w/ exchange, but i have seen this behavior w/ arcserve in my backups. computer associates will tell you it is because the job script has become corrupt. simply create a new job script w/o using or importing and of the elements of the former job script and things will work...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.