Re: Dev Class type FILE with multiple directories
Ian, The Technote says, "When predefining volumes, the Tivoli Storage Manager server will use all of the volumes in one directory before using the volumes in another directory." Here is the example: 7) Sort list of empty volumes alphabetically: List appears as c:\.BFS c:\0002.BFS c:\0004.BFS d:\0001.BFS d:\0003.BFS d:\0005.BFS 8) Begin filling volumes in the order of the list from step 7. To the contrary, my experience is that predefined volumes are used in this order: c:\.BFS d:\0001.BFS c:\0002.BFS d:\0003.BFS c:\0004.BFS d:\0005.BFS My filesystems are not on NFS, although I didn't see anything in the Technote stating it applies to NFS only. Best wishes, Keith
Re: Dev Class type FILE with multiple directories
Keith, the difference is that you are using pre-defined volumes - which the doc says will be used in alphabetical order - see the worked example at the bottom of the technote (steps 1 - 8 ). The true round-robin across directories only works when using scratch volumes (that are auto-created on demand). Ian Smith Oxford University. On 12/11/11 15:33, Arbogast, Warren K wrote: Rick, I am just getting started with FILE deviceclass storage pools, so take the following with ample grains of salt. However, my experience contradicts swg21497567. Or, I might misunderstand that Technote. This is a TSM 6.2 RHEL5 server. The file deviceclass has fourteen 2 TB filesystems on raid10 ldevs. Volumes were predefined to the storage pool with 'wait=yes', so they were created one at a time in round-robin order across the filesystems. A small amount of client backups are being written to the file pool at this time, so it is clear how volumes are being used. Client backup files are written to the storage pool in volume name order, not in filesystem name sort order. Today I see one full volume in each directory, and many empty volumes. If the Technote applied, all full volumes would be in the first directory. Ås far as I know, Keith
Re: Dev Class type FILE with multiple directories
Rick, I am just getting started with FILE deviceclass storage pools, so take the following with ample grains of salt. However, my experience contradicts swg21497567. Or, I might misunderstand that Technote. This is a TSM 6.2 RHEL5 server. The file deviceclass has fourteen 2 TB filesystems on raid10 ldevs. Volumes were predefined to the storage pool with 'wait=yes', so they were created one at a time in round-robin order across the filesystems. A small amount of client backups are being written to the file pool at this time, so it is clear how volumes are being used. Client backup files are written to the storage pool in volume name order, not in filesystem name sort order. Today I see one full volume in each directory, and many empty volumes. If the Technote applied, all full volumes would be in the first directory. Ås far as I know, Keith
Re: Dev Class type FILE with multiple directories
A colleague just sent me this link: See DCF 1497567: Allocation and use of scratch and predefined FILE storage pool volumes http://www-01.ibm.com/support/docview.wss?uid=swg21497567 By the way, keep in mind that at least on some appliances, the NFS-mounted filespace "used/remaining space" attributes apply to the entire appliance filesystem, no matter which directory you query. As the platforms improve, some sort of quota system will probably be provided. Although whether it apply to pre-compressed/deduped or post-compressed/deduped numbers is a good question. How to allocate directories among devclasses is becoming a more interesting topic as NFS-mounted dedup appliances become more prevalent. Some resources are tied to devclasses, such as mountpoints, that would require some consideration. Richard -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Richard Rhodes Sent: Friday, November 11, 2011 3:00 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Dev Class type FILE with multiple directories If you have a dev class of type FILE with multiple directories, how does TSM determine which dir to create a new volumes in? I've checked everywhere I can think of and the most I can find is comments that TSM is free to pick any dir to create a new scratch vol in. Assuming lots of free space in multiple directories specified for one dev class type file, how does TSM pick which dir to create a file dev in? What I'm interested in is one of those "what if" questions. If you have a file dev class (NFS) on a dedup box and its getting full. So you purchase a new box, set it up, and add it to the devclass as an extra directory. You now have two directories. If one is full TSM will use the other, but if both have freespace I'm curious how TSM decides which to use. Just curious . . . Rick - The information contained in this message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately, and delete the original message.
Re: Dev Class type FILE with multiple directories
Here is an excerpt from a TSM-Data Domain best practiced doc from EMC. "? ?directory=/tsm/ddr/tsm_dir1,/tsm/ddr/tsm_dir2, /tsm/ddr/tsm_dir3? This will allow the TSM server to round robin incoming data streams over each network link. There is no configuration control over path preferences, and in the event the link of a given path is not available, TSM will skip that path and open the next data stream on the next available path." The context for this was to mount different directories over different network links to balance the link utilization. It indicates it is round robin, but I don't know how authoritative this is. I couldn't find any information about it in the TSM manuals although my link utilization is even, which would confirm that it is round-robin. You could remove the full directories from the device class definition. This won't prevent reading volumes already created, it will only prevent new scratch volumes from being created there. Then you can add it back in later as the data expires and space clears up. Regards, Shawn Shawn Drew Internet rrho...@firstenergycorp.com Sent by: ADSM-L@VM.MARIST.EDU 11/11/2011 03:00 PM Please respond to ADSM-L@VM.MARIST.EDU To ADSM-L cc Subject [ADSM-L] Dev Class type FILE with multiple directories If you have a dev class of type FILE with multiple directories, how does TSM determine which dir to create a new volumes in? I've checked everywhere I can think of and the most I can find is comments that TSM is free to pick any dir to create a new scratch vol in. Assuming lots of free space in multiple directories specified for one dev class type file, how does TSM pick which dir to create a file dev in? What I'm interested in is one of those "what if" questions. If you have a file dev class (NFS) on a dedup box and its getting full. So you purchase a new box, set it up, and add it to the devclass as an extra directory. You now have two directories. If one is full TSM will use the other, but if both have freespace I'm curious how TSM decides which to use. Just curious . . . Rick - The information contained in this message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately, and delete the original message. This message and any attachments (the "message") is intended solely for the addressees and is confidential. If you receive this message in error, please delete it and immediately notify the sender. Any use not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval. The internet can not guarantee the integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will) not therefore be liable for the message if modified. Please note that certain functions and services for BNP Paribas may be performed by BNP Paribas RCC, Inc.
Dev Class type FILE with multiple directories
If you have a dev class of type FILE with multiple directories, how does TSM determine which dir to create a new volumes in? I've checked everywhere I can think of and the most I can find is comments that TSM is free to pick any dir to create a new scratch vol in. Assuming lots of free space in multiple directories specified for one dev class type file, how does TSM pick which dir to create a file dev in? What I'm interested in is one of those "what if" questions. If you have a file dev class (NFS) on a dedup box and its getting full. So you purchase a new box, set it up, and add it to the devclass as an extra directory. You now have two directories. If one is full TSM will use the other, but if both have freespace I'm curious how TSM decides which to use. Just curious . . . Rick - The information contained in this message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately, and delete the original message.
