Michael,
In a job where you take image of E (SQL data) you should stop database before the job and then start database after the job. Here is more info:
How to start and stop Exchange or SQL services
Situation:
This document explains the benefit of stopping Exchange or SQL services before imaging a database server using Symantec LiveState Recovery or V2i Protector.
Solution:
Symantec LiveState Recovery and V2i Protector's ability to perform "hot imaging" (creating images of servers while they are still running Windows) is a great convenience, but you should be aware of some potential problems that this feature presents with regard to databases.
Databases, including Exchange and SQL, always have many files open, and these files are constantly changing. If you create an image while a database is up and running, then when you restore the image, the database may not be able to repair itself properly. Consequently, Symantec highly recommends that you temporarily stop services for your databases before creating an image. This is a good practice for ensuring a reliable backup of any database.
Databases such as Exchange or SQL need to be shut down only for the amount of time it takes to start and get through the first 5% of the imaging process. You can then restart the database.
The following Microsoft Knowledge Base articles describe how to start and stop the services associated with Exchange and SQL databases.
Exchange
XADM: Start and Stop Exchange Services from a Command Line (Article ID 160572)
XADM: How to Write a Batch File to Shut Down Exchange Server Quickly (Article ID 246287)
SQL
INFO: How to Schedule Backup & DBCC Commands Using AT Scheduler (Article ID 162294)