Re: AW: TDP for Exchange - Management Class
This information is not correct. You can schedule a Data Protection for Exchange node. Use the ACTION=COMMAND type schedule. There is an appendix in the Data Protection for Exchange User's Guide that shows you exactly how to do it. Thanks, Del ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 05/20/2006 10:16:04 AM: 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 ? DomainNodename MgmInclude 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_montlydsm_monthly.opt Domain_Exchange Exchange EXCH_yearlyINCLUDE *\...\full EXCH_yearly Sched_Exch_yearlydsm_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
Re: AW: TDP for Exchange - Management Class
I can understand how it can be a little confusing, but if the management classes were used how you suggest, it would contradict the whole basis of management classes in the backup copy groups. This is backup, not archive. That means each backup object on the TSM server, with the same name, gets the same management class. This is a strict rule, that has no exceptions. This is the same as the BA client backing up a file. That is why I recommend using a COPY-type backup for your Exchange archival purposes. You can bind the COPY-type backups to a management class that meets your longer term needs. And, all of this can be automated, with no manual intervention. Thanks, Del ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 05/20/2006 04:56:43 AM: 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 ? DomainNodename MgmInclude 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_montlydsm_monthly.opt Domain_Exchange Exchange EXCH_yearlyINCLUDE *\...\full EXCH_yearly Sched_Exch_yearlydsm_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 -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Volker Maibaum Sent: Friday, May 19, 2006 11:57 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: AW: TDP for Exchange - Management Class Hi, thanks to all for the very helpful feedback! I didn't think of using the copy backup for monthly and yearly backups. That will make it a lot easier I guess that I will use the monthly policy for copy backups INCLUDE *\...\copy MONTHLY And use a seperate dsm.opt file (dsm.yearly.opt) to bind the yearly copy backups to the proper management class. C:\Programme\Tivoli\TSM\TDPExchange\start_full_yearly_backup.cmd pointing to dsm.yearly.opt regards, Volker Am Freitag, den 19.05.2006, 11:34 +0200 schrieb Salak Juraj: Hi Del! I might be wrong because I do not use TDP 4 Mails by myself, I am only RTFM, but I´d think about simplified solution 2 by Del: Background: I think the only reason for having different requirements for monthly an yearly backups is TSM storage space, if this were not a problem keeping monthly backups for as long as yearly backups should be kept would be preferrable. a) create only 1 NODENAME b) define INCLUDE *\...\full EXCH_STANDARD and maybe INCLUDE *\...\incr EXCH_STANDARD and maybe INCLUDE *\...\diff EXCH_STANDARD appropriately to your regular (daily) backup requirements c) define INCLUDE *\...\copy EXCH_MONTHLY_AND_YEARLY appropriate to maximal combined requirements of your monthly AND yearly requirements AND have EXCH_MONTHLY point to separate TSM storage pool (EXCH_VERYOLD) d) on regular basis (maybe yearly) check out all full tapes from EXCH_VERYOLD storage pool from library. Disadvantage: reclamation of backup storage pool issues because of offsite tapes in primary storage pool, but this can be solved as well. You will end with a bit less automated restore (only) for very old data but with very clear and simple concept for everyda/everymonth backup operations and with more granularity (monthly) even for data older than a year. I am interested in your thoughts and doubts about this configuration! regards Juraj -Ursprüngliche Nachricht- Von: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Im Auftrag von Del Hoobler Gesendet: Freitag, 12. Mai 2006 15:14 An: ADSM-L@VM.MARIST.EDU Betreff: Re: TDP for Exchange - Management Class Hi Volker, Are you using separate NODENAMEs for each of the different DSM.OPT files? If not, your solution won't do what you think. Data Protection for Exchange stores objects in the backup pool, not the archive pool. That means, each full backup gets the same TSM Server name (similar to backing the same file name up with the BA Client.) It follows normal TSM Server policy rules. That means, if you are performing FULL backups using the same NODENAME, each time you back up with a different management class, all previous backups will get rebound to that new management class... just like BA Client file backups. Remember, this is standard behavior for BACKUP. You are trying to get ARCHIVE type
Re: AW: TDP for Exchange - Management Class
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 ? DomainNodename MgmInclude 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_montlydsm_monthly.opt Domain_Exchange Exchange EXCH_yearlyINCLUDE *\...\full EXCH_yearly Sched_Exch_yearlydsm_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 -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Volker Maibaum Sent: Friday, May 19, 2006 11:57 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: AW: TDP for Exchange - Management Class Hi, thanks to all for the very helpful feedback! I didn't think of using the copy backup for monthly and yearly backups. That will make it a lot easier I guess that I will use the monthly policy for copy backups INCLUDE *\...\copy MONTHLY And use a seperate dsm.opt file (dsm.yearly.opt) to bind the yearly copy backups to the proper management class. C:\Programme\Tivoli\TSM\TDPExchange\start_full_yearly_backup.cmd pointing to dsm.yearly.opt regards, Volker Am Freitag, den 19.05.2006, 11:34 +0200 schrieb Salak Juraj: Hi Del! I might be wrong because I do not use TDP 4 Mails by myself, I am only RTFM, but I´d think about simplified solution 2 by Del: Background: I think the only reason for having different requirements for monthly an yearly backups is TSM storage space, if this were not a problem keeping monthly backups for as long as yearly backups should be kept would be preferrable. a) create only 1 NODENAME b) define INCLUDE *\...\full EXCH_STANDARD and maybe INCLUDE *\...\incr EXCH_STANDARD and maybe INCLUDE *\...\diff EXCH_STANDARD appropriately to your regular (daily) backup requirements c) define INCLUDE *\...\copy EXCH_MONTHLY_AND_YEARLY appropriate to maximal combined requirements of your monthly AND yearly requirements AND have EXCH_MONTHLY point to separate TSM storage pool (EXCH_VERYOLD) d) on regular basis (maybe yearly) check out all full tapes from EXCH_VERYOLD storage pool from library. Disadvantage: reclamation of backup storage pool issues because of offsite tapes in primary storage pool, but this can be solved as well. You will end with a bit less automated restore (only) for very old data but with very clear and simple concept for everyda/everymonth backup operations and with more granularity (monthly) even for data older than a year. I am interested in your thoughts and doubts about this configuration! regards Juraj -Ursprüngliche Nachricht- Von: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Im Auftrag von Del Hoobler Gesendet: Freitag, 12. Mai 2006 15:14 An: ADSM-L@VM.MARIST.EDU Betreff: Re: TDP for Exchange - Management Class Hi Volker, Are you using separate NODENAMEs for each of the different DSM.OPT files? If not, your solution won't do what you think. Data Protection for Exchange stores objects in the backup pool, not the archive pool. That means, each full backup gets the same TSM Server name (similar to backing the same file name up with the BA Client.) It follows normal TSM Server policy rules. That means, if you are performing FULL backups using the same NODENAME, each time you back up with a different management class, all previous backups will get rebound to that new management class... just like BA Client file backups. Remember, this is standard behavior for BACKUP. You are trying to get ARCHIVE type function, which won't work. Good news... there is a way to do exactly what you want... ... I have two ways to do it. Solution 1: Create a separate NODENAME for your 3 types of backups. For example: EXCHSRV1, EXCHSRV1_MONTHLY, EXCHSRV1_YEARLY Have a separate DSM.OPT for each NODENAME, with the proper management class bindings. Set up your three schedules for your three separate nodenames. Solution 2: Create 2 separate NODENAMEs. Use one for the STANDARD and MONTHLY backups (perform COPY type backups for your MONTHLY backups). Use the other nodename for the YEARLY backups. For example: EXCHSRV1, EXCHSRV1_YEARLY Have one DSM.OPT for your STANDARD and MONTHLY backups and a different DSM.OPT for your YEARLY backups. In the DSM.OPT file for your STANDARD and MONTHLY backups, set up different policy bindings
Re: AW: TDP for Exchange - Management Class
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 ? DomainNodename MgmInclude 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_montlydsm_monthly.opt Domain_Exchange Exchange EXCH_yearlyINCLUDE *\...\full EXCH_yearly Sched_Exch_yearlydsm_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
Re: AW: TDP for Exchange - Management Class
Hi, thanks to all for the very helpful feedback! I didn't think of using the copy backup for monthly and yearly backups. That will make it a lot easier I guess that I will use the monthly policy for copy backups INCLUDE *\...\copy MONTHLY And use a seperate dsm.opt file (dsm.yearly.opt) to bind the yearly copy backups to the proper management class. C:\Programme\Tivoli\TSM\TDPExchange\start_full_yearly_backup.cmd pointing to dsm.yearly.opt regards, Volker Am Freitag, den 19.05.2006, 11:34 +0200 schrieb Salak Juraj: Hi Del! I might be wrong because I do not use TDP 4 Mails by myself, I am only RTFM, but I´d think about simplified solution 2 by Del: Background: I think the only reason for having different requirements for monthly an yearly backups is TSM storage space, if this were not a problem keeping monthly backups for as long as yearly backups should be kept would be preferrable. a) create only 1 NODENAME b) define INCLUDE *\...\full EXCH_STANDARD and maybe INCLUDE *\...\incr EXCH_STANDARD and maybe INCLUDE *\...\diff EXCH_STANDARD appropriately to your regular (daily) backup requirements c) define INCLUDE *\...\copy EXCH_MONTHLY_AND_YEARLY appropriate to maximal combined requirements of your monthly AND yearly requirements AND have EXCH_MONTHLY point to separate TSM storage pool (EXCH_VERYOLD) d) on regular basis (maybe yearly) check out all full tapes from EXCH_VERYOLD storage pool from library. Disadvantage: reclamation of backup storage pool issues because of offsite tapes in primary storage pool, but this can be solved as well. You will end with a bit less automated restore (only) for very old data but with very clear and simple concept for everyda/everymonth backup operations and with more granularity (monthly) even for data older than a year. I am interested in your thoughts and doubts about this configuration! regards Juraj -Ursprüngliche Nachricht- Von: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Im Auftrag von Del Hoobler Gesendet: Freitag, 12. Mai 2006 15:14 An: ADSM-L@VM.MARIST.EDU Betreff: Re: TDP for Exchange - Management Class Hi Volker, Are you using separate NODENAMEs for each of the different DSM.OPT files? If not, your solution won't do what you think. Data Protection for Exchange stores objects in the backup pool, not the archive pool. That means, each full backup gets the same TSM Server name (similar to backing the same file name up with the BA Client.) It follows normal TSM Server policy rules. That means, if you are performing FULL backups using the same NODENAME, each time you back up with a different management class, all previous backups will get rebound to that new management class... just like BA Client file backups. Remember, this is standard behavior for BACKUP. You are trying to get ARCHIVE type function, which won't work. Good news... there is a way to do exactly what you want... ... I have two ways to do it. Solution 1: Create a separate NODENAME for your 3 types of backups. For example: EXCHSRV1, EXCHSRV1_MONTHLY, EXCHSRV1_YEARLY Have a separate DSM.OPT for each NODENAME, with the proper management class bindings. Set up your three schedules for your three separate nodenames. Solution 2: Create 2 separate NODENAMEs. Use one for the STANDARD and MONTHLY backups (perform COPY type backups for your MONTHLY backups). Use the other nodename for the YEARLY backups. For example: EXCHSRV1, EXCHSRV1_YEARLY Have one DSM.OPT for your STANDARD and MONTHLY backups and a different DSM.OPT for your YEARLY backups. In the DSM.OPT file for your STANDARD and MONTHLY backups, set up different policy bindings for FULL backups vs. COPY backups (since FULL and COPY get named differently on the TSM Server, they will also get their own policy.) Example DSM.OPT INCLUDE statements are like this: *---* The following example binds all FULL objects *---* to management class EXCH_STANDARD: INCLUDE *\...\full EXCH_STANDARD *---* The following example binds all COPY objects *---* to management class EXCH_MONTHLY: INCLUDE *\...\copy EXCH_MONTHLY As far as your original question... you can check the management class bindings by bringing up the Data Protection for Exchange GUI... go to the restore tab, click on the storage group you want to look at. It will show the management class bindings. (Make sure to view active and inactive, to see the previous backup bindings as well.) You can also use the SHOW VERSION TSM Server command: SHOW VERSION EXCHSRV1 * SHOW VERSION EXCHSRV1_MONTHLY * SHOW VERSION EXCHSRV1_YEARLY * This will show you the management class bindings. I hope this helps. Let me know if any of this isn't clear. Thanks, Del
