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
File dev based stgpool access=unavailable
Here's another NFS based dedup box question . . . Taking a NFS based dedup box down would require taking the NFS share offline (unmounting it). What would you do in TSM to stop it from accessing the FILE dev based stgpool? The only thing I can see is a update stgpool x access=unavailable. For tape we take the drives and/or paths offline when we take a lib down. Just wondering what the equivalent is for a FILE based stgpool. Thanks Rick From: Ian Smith ian.sm...@oucs.ox.ac.uk To: ADSM-L@VM.MARIST.EDU Date: 11/14/2011 06:47 AM Subject:Re: Dev Class type FILE with multiple directories Sent by:ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 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 - 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
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
Error ANS0106E
Hi to all I have some clients after upgrading to Client version 6.3.0 showing this message: tsm i -su=yes Incremental backup of volume '\\websrv02\c$' Incremental backup of volume '\\websrv02\d$' Incremental backup of volume '\\websrv02\e$' Incremental backup of volume '\\websrv02\f$' Incremental backup of volume 'SYSTEMSTATE' ANS0106E Message index not found for message 1793. ANS0106E Message index not found for message 1793. The backup still works but how can I fix this message , any clue ? My TSM server version is: 6.2.3.0 Regards Robert
Re: Error ANS0106E
Hi Robert, I assume that your clients are Windows. It's generally an upgrade problem. It can happen when the TSM services (scheduler)are not shut down. It's'probably due to a corrupted dscenu.txt There is a simple fix : copy the dscenu.txt file from a machime without the problem. the other way is to uninstall and then reinstall the client. Note that this does not apply specifically to 6.3, so your problem may be different. --Message d'origine-- De: Robert Ouzen Expéditeur : ADSM: Dist Stor Manager À: ADSM-L@VM.MARIST.EDU Répondre à: ADSM: Dist Stor Manager Objet: [ADSM-L] Error ANS0106E Envoyé: 15 nov. 2011 07:13 Hi to all I have some clients after upgrading to Client version 6.3.0 showing this message: tsm i -su=yes Incremental backup of volume '\\websrv02\c$' Incremental backup of volume '\\websrv02\d$' Incremental backup of volume '\\websrv02\e$' Incremental backup of volume '\\websrv02\f$' Incremental backup of volume 'SYSTEMSTATE' ANS0106E Message index not found for message 1793. ANS0106E Message index not found for message 1793. The backup still works but how can I fix this message , any clue ? My TSM server version is: 6.2.3.0 Regards Robert -- Best regards / Cordialement / مع تحياتي Erwann SIMON
External Disk Unit and TSM Deduplication
Hello, We have IBM 3583 LTO2 Tape library. This library hasn't got enough capabilities for our daily backups. But we beleive it can handle backup copies for offsite media. So, we need to a new backup device. We thought about EMC datadomain and IBM Protectier dedup device but they were expensive. We have two option. We have to choice one of them. 1. We can buy a new LTO5 library for primary and offsite backups instead of LTO2 library. 2. We can buy a new simple external disk unit which has enough capacity. We can use TSM 6.2/3 deduplication for primary backups. We will use old LTO2 library for offsite media. Disk unit will have RAID6 disk system. Which option do you prefer. Why? Do you use TSM's deduplication? Is there any known problem? Thanks Alper Dikkat: Bu elektronik posta mesaji kisisel ve ozeldir. Eger size gonderilmediyse lutfen gondericiyi bilgilendirip mesaji siliniz.Firmamiza gelen ve giden mesajlar virus taramasindan gecirilmektedir. Mesajdaki gorusler gondericiye ait olup HAVELSAN A.S. resmi gorusu olmak zorunda degildir. Attention: This e-mail message is private and privileged.If you are not the recipient for whom this e-mail message is intended, please notify the sender immediately and delete this e-mail message from your system.All sent and received e-mail messages go through a virus scan. Any opinions presented in this e-mail message are solely those of the author and do not necessarily represent HAVELSAN A.S.`s formal and authorized views.
