Re: Creating a second options file
I don't know the REAL answer to this but in past classes we were told that /.../ indicated from 0 to any number of subdirectories so in your example, /path/* is unnecessary. Warren, Matthew (Retail) wrote: To be honest, it one of those things I've always intended to follow up, but never have. My reasoning at the moment goes; /path/* means all files in the dir at that point, so it would match /path/fish but not /path/chips/fish /path/.../* means any files in dir's after PATH to any level of depth. So, a FILE /path/fish would NOT match because fish is not a dir, but /path/chips/fish would match. So to match the 'root' portion of a path (if you get my meaning) AND all files in dir's from that path, you need both. ...I could very well be inaccurate on this. As it goes, I did start to test it when I wrote your reply, but instead came across what appeared to be strange behaviour when using '*''s to specify a path branch, and that led to me posting here about that, and digressing from my original aim... Matt. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Smith, Rachel Sent: Thursday, February 24, 2005 1:00 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Creating a second options file Thanks Matthew, that worked a treat, One question, do you need both includes in the file or would one suffice? Include /.../* 30days Include /* 30days Thanks, Rachel ___ Disclaimer Notice __ This message and any attachments are confidential and should only be read by those to whom they are addressed. If you are not the intended recipient, please contact us, delete the message from your computer and destroy any copies. Any distribution or copying without our prior permission is prohibited. Internet communications are not always secure and therefore Powergen Retail Limited does not accept legal responsibility for this message. The recipient is responsible for verifying its authenticity before acting on the contents. Any views or opinions presented are solely those of the author and do not necessarily represent those of Powergen Retail Limited. Registered addresses: Powergen Retail Limited, Westwood Way, Westwood Business Park, Coventry, CV4 8LG. Registered in England and Wales No: 3407430 Telephone +44 (0) 2476 42 4000 Fax +44 (0) 2476 42 5432 -- Steve Bennett, (907) 465-5783 State of Alaska, Enterprise Technology Services, Technical Services Section
Re: Creating a second options file
To be honest, it one of those things I've always intended to follow up, but never have. My reasoning at the moment goes; /path/* means all files in the dir at that point, so it would match /path/fish but not /path/chips/fish /path/.../* means any files in dir's after PATH to any level of depth. So, a FILE /path/fish would NOT match because fish is not a dir, but /path/chips/fish would match. So to match the 'root' portion of a path (if you get my meaning) AND all files in dir's from that path, you need both. ...I could very well be inaccurate on this. As it goes, I did start to test it when I wrote your reply, but instead came across what appeared to be strange behaviour when using '*''s to specify a path branch, and that led to me posting here about that, and digressing from my original aim... Matt. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Smith, Rachel Sent: Thursday, February 24, 2005 1:00 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Creating a second options file Thanks Matthew, that worked a treat, One question, do you need both includes in the file or would one suffice? Include /.../* 30days Include /* 30days Thanks, Rachel ___ Disclaimer Notice __ This message and any attachments are confidential and should only be read by those to whom they are addressed. If you are not the intended recipient, please contact us, delete the message from your computer and destroy any copies. Any distribution or copying without our prior permission is prohibited. Internet communications are not always secure and therefore Powergen Retail Limited does not accept legal responsibility for this message. The recipient is responsible for verifying its authenticity before acting on the contents. Any views or opinions presented are solely those of the author and do not necessarily represent those of Powergen Retail Limited. Registered addresses: Powergen Retail Limited, Westwood Way, Westwood Business Park, Coventry, CV4 8LG. Registered in England and Wales No: 3407430 Telephone +44 (0) 2476 42 4000 Fax +44 (0) 2476 42 5432
Re: Creating a second options file
Thanks Matthew, that worked a treat, One question, do you need both includes in the file or would one suffice? Include /.../* 30days Include /* 30days Thanks, Rachel -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Warren, Matthew (Retail) Sent: 23 February 2005 11:51 To: ADSM-L@VM.MARIST.EDU Subject: Re: Creating a second options file It sounds like you may be slightly misunderstanding the policy-domain-management class structure to policy domains in TSM. You can use 2 management classes and one include/exclude list with 'include (filespec) (classname)' statements to achieve what you describe. To do what you need, I would; Have a single policy domain, for simplicity I'll call it DOMAIN1 with active policy set POLICY Define 2 management classes DOMAIN1 POLICY 30days DOMAIN1 POLICY 5days Set the copygroup retentions as you require for 30 and 5 day retention. Register the node to the DOMAIN1 domain. Edit the include/Exclude list for the node, the following lines are a bare minimum to get the behaviour you describe (I am assuming you are using UNIX) Include /.../* 30days Include /* 30days Include /.../*.fle 5days Include /*.fle 5days This will include all the .fle files in the 5days management class, and other files in the 30day management class. Remember in general the include list is scanned from bottom to top when finding a match. Certain statements (like include.dir etc..) are processed before the list is scanned. Matthew. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Smith, Rachel Sent: Wednesday, February 23, 2005 11:11 AM To: ADSM-L@VM.MARIST.EDU Subject: Creating a second options file Hi, I have a standard policy domain setup to retain backups for 30-60 days. I will be setting up a new policy domain to retain backups for 5 days. At present a client is using the 30 day retention policy to retain backups but I want files with the extension: *.fle to be excluded from the 30 day policy (add exclude *.fle to dsm.inclexcl). Then the *.fle files are then to be backed up using a NEW policy which would be retaining the data for 5 days. My question is: How do I setup a second option file on the same client to point to the 5 day retention policy? Would I need to create a second client/node name to add to the NEW policy? Please advise Thank you, Rachel ___ Disclaimer Notice __ This message and any attachments are confidential and should only be read by those to whom they are addressed. If you are not the intended recipient, please contact us, delete the message from your computer and destroy any copies. Any distribution or copying without our prior permission is prohibited. Internet communications are not always secure and therefore Powergen Retail Limited does not accept legal responsibility for this message. The recipient is responsible for verifying its authenticity before acting on the contents. Any views or opinions presented are solely those of the author and do not necessarily represent those of Powergen Retail Limited. Registered addresses: Powergen Retail Limited, Westwood Way, Westwood Business Park, Coventry, CV4 8LG. Registered in England and Wales No: 3407430 Telephone +44 (0) 2476 42 4000 Fax +44 (0) 2476 42 5432
Re: Creating a second options file
It sounds like you may be slightly misunderstanding the policy-domain-management class structure to policy domains in TSM. You can use 2 management classes and one include/exclude list with 'include (filespec) (classname)' statements to achieve what you describe. To do what you need, I would; Have a single policy domain, for simplicity I'll call it DOMAIN1 with active policy set POLICY Define 2 management classes DOMAIN1 POLICY 30days DOMAIN1 POLICY 5days Set the copygroup retentions as you require for 30 and 5 day retention. Register the node to the DOMAIN1 domain. Edit the include/Exclude list for the node, the following lines are a bare minimum to get the behaviour you describe (I am assuming you are using UNIX) Include /.../* 30days Include /* 30days Include /.../*.fle 5days Include /*.fle 5days This will include all the .fle files in the 5days management class, and other files in the 30day management class. Remember in general the include list is scanned from bottom to top when finding a match. Certain statements (like include.dir etc..) are processed before the list is scanned. Matthew. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Smith, Rachel Sent: Wednesday, February 23, 2005 11:11 AM To: ADSM-L@VM.MARIST.EDU Subject: Creating a second options file Hi, I have a standard policy domain setup to retain backups for 30-60 days. I will be setting up a new policy domain to retain backups for 5 days. At present a client is using the 30 day retention policy to retain backups but I want files with the extension: *.fle to be excluded from the 30 day policy (add exclude *.fle to dsm.inclexcl). Then the *.fle files are then to be backed up using a NEW policy which would be retaining the data for 5 days. My question is: How do I setup a second option file on the same client to point to the 5 day retention policy? Would I need to create a second client/node name to add to the NEW policy? Please advise Thank you, Rachel ___ Disclaimer Notice __ This message and any attachments are confidential and should only be read by those to whom they are addressed. If you are not the intended recipient, please contact us, delete the message from your computer and destroy any copies. Any distribution or copying without our prior permission is prohibited. Internet communications are not always secure and therefore Powergen Retail Limited does not accept legal responsibility for this message. The recipient is responsible for verifying its authenticity before acting on the contents. Any views or opinions presented are solely those of the author and do not necessarily represent those of Powergen Retail Limited. Registered addresses: Powergen Retail Limited, Westwood Way, Westwood Business Park, Coventry, CV4 8LG. Registered in England and Wales No: 3407430 Telephone +44 (0) 2476 42 4000 Fax +44 (0) 2476 42 5432
