Hi, Version A will only have 4 versions. Daily changed, so over the last 4 back-up runs. Nothing to do with the 30 days. Version B will have only its first back-up version. Because it hasn't changed, there are no extra version to expire. Nothing to do with the 30 days either.
Version C has been changed on day 2 5 10 and 29. Initial back-up version will be expired due to backing up the changed versions. Version of day 2, 5 and 10 will expire after 30 days (Retain extra version = 30 days) or by backing up any new versions (Version = 4). Version D has been deleted (and this is registered by a backup run). All version will expire within 30 days after back-up (Retain extra version = 30 days) and the last version will be deleted 30 days after after it has been expired (marked as deleted by the backup runs which marked is deleted). Regards, Karel -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Vats.Ashok Sent: dinsdag 2 mei 2006 17:34 To: [email protected] Subject: Re: Retention policy question : We are running TSM 5.3.0.0 on aix 5.3 and the implementation was done by a consultant with the following retention policy in place : Version = 4 Retain only version = 30 days Retain extra version = 30 days If we have two files A and File B file A changes every day but file B never changes after the initial creation day ...what happens to the backup copies in the TSM serv on day 30th, 32nd and 33rd.... Appreciate any input Thanks, Ashok >q co Policy Policy Mgmt Copy Versions Versions Retain Retain Domain Set Name Class Group Data Data Extra Only Name Name Name Exists Deleted Versions Version --------- --------- --------- --------- -------- -------- -------- ------- SQL_DOMA- ACTIVE MDEFAULT STANDARD No Limit No Limit 30 30 IN SQL_DOMA- ACTIVE SQLTRANS- STANDARD No Limit No Limit 30 30 IN DISK SQL_DOMA- SQL_POLI- MDEFAULT STANDARD No Limit No Limit 30 30 IN CY SQL_DOMA- SQL_POLI- SQLTRANS- STANDARD No Limit No Limit 30 30 IN CY DISK STANDARD ACTIVE STANDARD STANDARD 2 1 30 60 STANDARD STANDARD STANDARD STANDARD 2 1 30 60 WIN_DISK- ACTIVE MDEFAULT STANDARD 4 1 30 30 _DOMAIN WIN_DISK- WIN_DISK- MDEFAULT STANDARD 4 1 30 30 _DOMAIN _POLICY WIN_TAPE- ACTIVE MDEFAULT STANDARD 4 1 30 30 _DOMAIN WIN_TAPE- WIN_TAPE- MDEFAULT STANDARD 4 1 30 30 _DOMAIN _POLICY -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Loon, E.J. van - SPLXM Sent: Tuesday, May 02, 2006 1:20 AM To: [email protected] Subject: [ADSM-L] TDP for SQL tracing Hi *SM-ers! I added the trace parameters to the dsm.opt on a client running the DP for SQL Server client. I added the following lines: Tracefile d:\tdptrace\tdptrace.txt Traceflags stats, options, compress Tracemax 100 The tracefile confirmed this: 05/01/2006 21:30:47.745 : Current trace classes enabled: CONFIG, COMPRESS, TIMESTAMP, PREFIX, STATS But it only contains the CONFIG output. No statistics, no compression info, nothing... What am I doing wrong??? Kindest regards, Eric van Loon KLM Royal Dutch Airlines ********************************************************************** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. **********************************************************************
Dit bericht is vertrouwelijk en kan geheime informatie bevatten enkel bestemd voor de geadresseerde. Indien dit bericht niet voor u is bestemd, verzoeken wij u dit onmiddellijk aan ons te melden en het bericht te vernietigen. Aangezien de integriteit van het bericht niet veilig gesteld is middels verzending via internet, kan Atos Origin niet aansprakelijk worden gehouden voor de inhoud daarvan. Hoewel wij ons inspannen een virusvrij netwerk te hanteren, geven wij geen enkele garantie dat dit bericht virusvrij is, noch aanvaarden wij enige aansprakelijkheid voor de mogelijke aanwezigheid van een virus in dit bericht. Op al onze rechtsverhoudingen, aanbiedingen en overeenkomsten waaronder Atos Origin goederen en/of diensten levert zijn met uitsluiting van alle andere voorwaarden de Leveringsvoorwaarden van Atos Origin van toepassing. Deze worden u op aanvraag direct kosteloos toegezonden. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos Origin group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. On all offers and agreements under which Atos Origin supplies goods and/or services of whatever nature, the Terms of Delivery from Atos Origin exclusively apply. The Terms of Delivery shall be promptly submitted to you on your request.
