Actually you will need a fourth node to provide scheduling. The TDP for mail cannot be schedule, only the backup archive client could be schedule. You would schedule the BAC to issue a command to start the TDP. Actually I update my exchange nodes once a week to a different domain to force it to use a different storage pool, but the retention is the same for both policy domain. This is to force the creation of an offsite copy of the exchange data once a week. This is adequate for my office, so your mileage may vary. We also only have weekly Iron Mountain pickups.
-----Original Message----- Hi , Became a little bit confusing ..... So What the purpose of many management class per node utility If can't use for this purpose describe ????? Domain Nodename Mgm Include Schedule Opt File Domain_Exchange Exchange EXCH_daily INCLUDE "*\...\full" EXCH_daily Sched_Exch_daily dsm.opt (Default) Domain_Exchange Exchange EXCH_monthly INCLUDE "*\...\full" EXCH_monthly Sched_Exch_montly dsm_monthly.opt Domain_Exchange Exchange EXCH_yearly INCLUDE "*\...\full" EXCH_yearly Sched_Exch_yearly dsm_yearly.opt If I understand correctly with this configuration every backup the files will be rebinding to the MGM in action !!!!!!!!!!!!!! And the only way to achieve it , is to create also 3 different nodenames ..... Correct So wasteful !!!!!!!!!!!! Regards Robert Ouzen