As far as my experience goes:
1 : Backup the Exchange IS and all the SQL Databases in a seperate job (always FULL)
2 : Backup the DCs in a seperate job (System State, Shadow Copy Components and all the Drives---Full + Incremental)
3 : Backup the Drives of the serverother s in another job (Full + Inc.)
Depends:
1 : How many servers in total
2 : Approx. Data to be backed up
3 : Any application such as Exchange, SQL, Domain controllers...etc
4 : Media Rotation policies..
1. 7 Servers
2. On a Full Backup Approx. 500 GB which is run once a week and Incrementals which are 40 - 50 GB and run nightly.
3. 2 Domain Controllers, 1 Exchange Server, and a couple of servers running SQL
4. We have two HP Storageworks LTO3 400/800 Tape Drives, on the full backups we backup 300 GB to one drive and 200 to the other, we use 1 tape in each drive for the week.
As far as my experience goes:
1 : Backup the Exchange IS and all the SQL Databases in a seperate job (always FULL)
2 : Backup the DCs in a seperate job (System State, Shadow Copy Components and all the Drives---Full + Incremental)
3 : Backup the Drives of the serverother s in another job (Full + Inc.)
also depends on how your boss reacts to "failed" backups
if you have all your file/print servers in one job, and one has a problem on one share, then the whole job "fails", even if it is only one corrupt file.
if you have separate jobs, then only the one with the problem "fails"