Adrian, Are you sure that you are getting what you want? By assigning several nodes to various retention levels, are you backing up each node every day?
If your EXCHANGE_MONTHLY node only backs up once a month, all of the changes that have happened during the month will NOT be captured and you will simply have a snapshot in time that will be preserved for a year. If you backup with this node on the 1st of each month, you will not be able to restore to October 15th - Only to Oct 1st (the day of backup). Similarly, the EXCHANGE_YEARLY node - if run once a year will miss all of the activity during the year and only represent a one day slice that is kept for many years. If you backup with this node on January 1st, you will not be able to restore May 17th mail using this EXCHANGE_YEARLY node. If you want the granularity of being able to restore a specific day's data, from 3 years in the past, you must have backed up that day's data on that day. If a file is created and deleted in the same day, and was not backed up while it existed, it cannot be restored. If a file is created on Monday and deleted on Friday and your backups run on Saturday, that file cannot be restored because it was never backed up while it existed. Cheers, Neil Strand Storage Engineer - Legg Mason Baltimore, MD. (410) 580-7491 Whatever you can do or believe you can, begin it. Boldness has genius, power and magic. -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Schaub, Steve Sent: Monday, November 19, 2007 8:11 AM To: [email protected] Subject: Re: [ADSM-L] TDP for Exchange If you truly do only have one node, you have effectively shot yourself in the proverbial foot - every time you run the tdp to a different mgmt class it is going to rebind EVERYTHING for that node. So whatever monthly/yearly backups you had were rebound to the daily class and expired. You need to define multiple nodenames if you want to maintain 3 different retentions. You could get by with a single nodename by using the COPY instead of full if you could settle for 2 different retentions. Steve Schaub Systems Engineer, Windows Blue Cross Blue Shield of Tennessee 423-535-6574 (desk) 423-785-7347 (mobile) -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Adrian Compton Sent: Monday, November 19, 2007 8:00 AM To: [email protected] Subject: [ADSM-L] TDP for Exchange Hi all I have an EXCHANGE SERVER backing up via TDP for Exchange I have 3 Management classes with different Retention periods i.e EXCHANGE - 30 Days, EXCHANGE_MONTHLY - 365 DAYS and EXCHANGE_YEARLY - 2555 Days I have 1 node and 4 schedules associated, i.e Daily Incremental, Weekly Full, Monthly Full, Yearly Full Each schedule points to a CMD file in the TDPEXCH directory that includes its own version of the OPT file. The Daily Incr and Weekly Full opt files point to EXCHANGE mgmt class, Monthly opt file points to EXCHANGE_MONTHLY mgmt class etc. During a restore that I have recently had to do, I can only see 30 days worth of backups. Any ideas what could be wrong. I am using TSM 5.3.5 and TDP for Exchange 5.3.4 Adrian Compton Group IBM Tivoli Admin Pharmacare Limited trading as Aspen Pharmacare P O Box 4002 Korsten Port Elizabeth 6014 Switchboard Tel No: +27 (0) 41 407 2111 Tel No: +27 (0) 41 407 2855 Fax: +27 (0) 41 453 7452 Cell: +27 (0) 82 320 4495 Email : [EMAIL PROTECTED] This email is solely for the named addressee. Any unauthorised use or interception of this email, or the review, retransmission, dissemination or other use of, or taking of any action in reliance upon the contents of this email, by persons or entities other than the intended recipient, is prohibited. If you are not the named addressee please notify us immediately by way of a reply e-mail, and also delete this email and any attached files. Disclaimer: You must scan this email and any attached files for viruses and/or any other defects. Pharmacare Limited accepts no liability for any loss, damages or consequence, whether direct, indirect, consequential or economic, however caused, and whether by negligence or otherwise, which may result directly or indirectly from this communication or of any attached files. Please see the following link for the BlueCross BlueShield of Tennessee E-mail disclaimer: http://www.bcbst.com/email_disclaimer.shtm IMPORTANT: E-mail sent through the Internet is not secure. Legg Mason therefore recommends that you do not send any confidential or sensitive information to us via electronic mail, including social security numbers, account numbers, or personal identification numbers. Delivery, and or timely delivery of Internet mail is not guaranteed. Legg Mason therefore recommends that you do not send time sensitive or action-oriented messages to us via electronic mail. This message is intended for the addressee only and may contain privileged or confidential information. Unless you are the intended recipient, you may not use, copy or disclose to anyone any information contained in this message. If you have received this message in error, please notify the author by replying to this message and then kindly delete the message. Thank you.
