Re: Group collocation
Only data from nodes in collocationgroup will be collocated, data from other nodes in same stgpool will not be collocated. Best regards, Kolbeinn Zoltan Forray/AC/VCU [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 13.10.2005 20:27 Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject Group collocation I am starting to roll out Group Collocation and have a question that I did not find an absolute/clear answer to. If I take a storage pool and change it to GROUP from NO collocation, what about the data for nodes that ARE NOT in collocation groups ? Does their data get collocated or not ? Will I all of a sudden go from 1-2 daily LTO2 mounts to 30 ?
Re: Group collocation
My apologizes, Mark you are correct! The best practise should be to use at least two seperate storagepools, the first with collocation=no (where all non-collocated nodes belongs to) and the second with collocation=group (where nodes in collocaton groups belongs), you can then chose if you use the second pool also for collocation by node (non grouped nodes) or if you add the third stgpool with collocation=node (and perhaps the fourth stgpool with collocation=filespace if your environment is large enough). Best regards, Kolbeinn Stapleton, Mark [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 14.10.2005 01:39 Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject Re: Group collocation Zoltan Forray/AC/VCU [EMAIL PROTECTED] If I take a storage pool and change it to GROUP from NO collocation, what about the data for nodes that ARE NOT in collocation groups ? Does their data get collocated or not ? Will I all of a hsudden go from 1-2 daily LTO2 mounts to 30 ? From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Kolbeinn Jósepsson Only data from nodes in collocationgroup will be collocated, data from other nodes in same stgpool will not be collocated. This is incorrect. My experience has been that, when setting a pool to collocation by group, that any node not belonging to a collocation group will get its data to that pool collocated. (from page 312 of the TSM 5.3 for Windows Administrators' Reference) GRoup Specifies that collocation is enabled at the group level for client nodes. The server attempts to put data for nodes that belong to the same collocation group on as few volumes as possible. If the nodes in the collocation group have multiple file spaces, the server does not attempt to collocate those file spaces. If you specify COLLOCATE=GROUP but do not define any groups, data is collocated by node. Similarly, if you specify COLLOCATE=GROUP and you define a group but do not add nodes to the group, data is collocated by node. === The workaround I found is to create collocation groups and populate them, then create one more collocation group that contains all other nodes that write to that storage pool that are *not* already in a group. -- Mark Stapleton ([EMAIL PROTECTED]) IBM Certified Advanced Deployment Professional Tivoli Storage Management Solutions 2005 IBM Certified Advanced Technical Expert (CATE) AIX Berbee Information Networks Office 262.521.5627
Re: Tivoli Continuous Data Protection for Files
My experience for Journal Based Backup is that it does not fix problems you can run in when single filesystem has millions of files/dir's in a single filespace and you get the ran out of memory symptom, the reason is that you must complete one non-journal based incremental backup before the JBB can start journaling, and on default, every first time after Windows reboots Also I have the feeling that the MEMORYEFFICIENTBACKUP YES does often not help. Split up filesystems or throw in extra memory are perhaps, in some cases, not an alternative. Others experience and solutions very welcome :) Best regards, Kolbeinn Jósepsson - Systems Engineer Tivoli Certified Consultant - IBM Tivoli Storage Manager V5.1 IBM Certified Deployment Professional - Tivoli Storage Resource Manager V1.2 www.nyherji.is Maurice van 't Loo [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 05.10.2005 08:46 Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject Re: Tivoli Continuous Data Protection for Files Hi Richard, I use CDP right now as a test for backing up local files on workstations. As fas as i seen, i don't know if you want to use it on fileserver with that many files Try it on your workstation first, than you see the product for yourself. Did you also tried: MEMORYEFFICIENTBACKUP YES ? An other thing you can do besides putting more memory in your server is to split the filesystems Regards, Maurice van 't Loo - Original Message - From: Dearman, Richard [EMAIL PROTECTED] To: ADSM-L@VM.MARIST.EDU Sent: Tuesday, October 04, 2005 6:31 PM Subject: [ADSM-L] Tivoli Continuous Data Protection for Files Has anyone used Tivoli Continuous Data Protection for Files product on a file server with a very large amount of files and directories. I have a server with millions of files and directories that I can not get backed because the TSM client either runs out of memory and shuts down trying to do an incremental, I tried journaling but it keeps failing as well. This product seems to be journaling continuously which would be good so the journal would not fill up and fail but can it complete the initial filesytem backup. Thanks **EMAIL DISCLAIMER*** This email and any files transmitted with it may be confidential and are intended solely for the use of the individual or entity to whom they are addressed. If you are not the intended recipient or the individual responsible for delivering the e-mail to the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is strictly prohibited. If you have received this e-mail in error, please delete it and notify the sender or contact Health Information Management 312.413.4947.
