Many thanks Del That is exactly what I needed to know
Regards Steve Steven Harris TSM Admin Canberra Australia On 30/06/2014 9:16 PM, Del Hoobler wrote:
Hi Steve, Domino and Exchange are different, so don't try to manage their backups in exactly the same way. You can certainly have different management classes for your FULL (database and logs) backups vs. your INCREMENTAL (logs only) backups. INCREMENTAL backups will inactivate when a new FULL backup completes successfully. Once inactivated, their life is dependant on the RETONLY setting of the management class. If you want to keep your FULL backups for 18 months and your INCREMENTAL backups for 100 days, that can be done as well via the VSSPOLICY statements in the TDPEXC.CFG file. Something like this: VSSPOLICY * * FULL TSM MC18MONTHS VSSPOLICY * * INCR TSM MC100DAYS ...where 'MC18MONTHS' and 'MC100DAYS' are management classes with the desired settings.) More details in the management class binding can be found here: http://www-01.ibm.com/support/knowledgecenter/SSTG2D_7.1.0/com.ibm.itsm.mail.exc.doc/c_exc_policy_overview.html Thank you, Del ---------------------------------------------------- "ADSM: Dist Stor Manager" <[email protected]> wrote on 06/27/2014 01:30:51 AM:From: Steven Harris <[email protected]> To: [email protected] Date: 06/27/2014 01:31 AM Subject: Exchange Incremental Expiry Sent by: "ADSM: Dist Stor Manager" <[email protected]> Hi Again Further to my last, the customer for which I am designing exchange backups has until now been a Domino shop. Previously we have taken a Weekly selective/daily incremental for the databases (remembering that an incremental on Domino only backs up new databases and those that aren't logged) plus daily or more frequent log backups. The database management class keeps for 18 months. The logs are kept for 100 days. I'm now supposed to implement this in Exchange. I can do a weekly full/daily incremental with no problem and put them to different management classes as I do for Domino, however the TDP for Exchange manual states Incremental object names are always unique. These names contain qualifiers whose values make them unique. Incremental object names are generated at the time of the backup and therefore are not predictable and cannot be specified. So the question becomes "When is the incremental backup marked inactive?" Does it even make sense for an incremental to have a different retention to a full? IIRC the same applies with MSSQL and the client deletes the logs when the full on which they depend is no longer on the server. If that is the case for exchange then there is no point in a different retention for incrementals. Please chime in if you know Thanks Steve. Steven Harris TSM Admin Canberra Australia.
