Natalie,

If you want to be able to "Delete" old Exchange backups,
(and have them REALLY go away, i.e. release storage pool space)
you MUST follow the Policy guidelines documented in the
Exchange Agent Installation and User's Guide.

"Roger Hohmann" is correct in stating that each backup
will create a NEW ADSM object, which means that it will
NEVER be replaced by another backup.  So, as Roger stated,
you must initiate "deletes" from the Exchange Agent,
which essentially does "expiration" on the backup object.

If you don't set up a policy as described and you don't
"delete" the backups on a regular basis, you will soon
find that your storage pools will be filled with
Exchange backups that don't go away.

We are looking at ways to add automatic expiration
for Exchange backups, but it is not there today.
Many of our customers have set up scripts that do
the deletions on a scheduled basis.  Search through
the ADSM-L archives to see examples of how some
customers are doing this.

Del Hoobler
ADSM Agent Development

>> Hello All,
>> I have recently downloaded the newest release of the Exchange Server 5.5
>> ADSM Agent. The ADSM Policy Requirements and Recommendations state that
>> the VERDELETED parameter of the Backup Copy Group (on the ADSM Server)
>> should be set to 0 (zero). However, I have tested that it can also work
>> with the parameter 1. If this is the case, could I assume that any
>> parameter will work O.K., thus another ADSM domain will need not to be
>> created for Exchange alone.
>> Has anyone else come accross this ?
>> Please let me know!
>> Regards,
>> Natalie Jenkins
>> Abbey Life.