Pulse 2009 February 8-12 Las Vegas Nevada
Big improvements in DB capacity, recovery log, better reporting.. My advice is wait till announcement day, will be a great product Adrian Pardo Buenos Aires-Argentina -----Mensaje original----- De: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] En nombre de Richard Rhodes Enviado el: Viernes, 05 de Diciembre de 2008 18:25 Para: ADSM-L@VM.MARIST.EDU Asunto: Re: [ADSM-L] Database size, Split to multiple instances or wait for version 6.1 We recently had a meeting with IBM where they told us that v6.1 will be announced at some big IBM conference in March (I think). They told us that being at v5.5 is a requirement for upgrading to v6.1. Rick Timothy Hughes <[EMAIL PROTECTED] IT.STATE.NJ.US> To Sent by: "ADSM: ADSM-L@VM.MARIST.EDU Dist Stor cc Manager" <[EMAIL PROTECTED] Subject .EDU> Re: Database size, Split to multiple instances or wait for version 6.1 12/05/2008 01:24 PM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED] .EDU> Is this true in regards to TSM V6.1? Also Is it due out in Jan-Feb? The biggest single change will the conversion of the database to DB2, or UDB as it is often called these days. This will be a packaged DB2 version that will not need any maintenance by your DBAs. The DB2 database will permit the following Online reorgs - the ability to reorganise the database without needing to stop the TSM service Better database integrity checking with the ability to repair database problems online Bigger TSM databases, so fewer servers Bigger recovery logs, up to 256 GB with the ability to do roll-foward recovery The upgrade will be disruptive as the database will have to be rebuilt. It will also mean the end of several old database commands like extend log and extend DB, and we will need to learn some new commands instead Other potential features in TSM 6 are Data de-duplication The ability to interface with external security products Improved auditing and reporting facilities The ability to move data and metadata between TSM servers, so simplifying load balancing The EXPIRE INVENTORY command will be granular, so you can expire by node or node groups, policy domain or by data type The ability to concurrently copy data between storage pools while migrating to the next pool in the heirarchy, that is, concurrent migration and storage pool backup Regards Allen S. Rout wrote: >>>On Thu, 4 Dec 2008 18:50:23 -0500, Paul Zarnowski <[EMAIL PROTECTED]> said: >>> >>> > > > > >>We also have 15K rpm 36GB drives, in two mirrored RAID5,7 sets (TSM >>mirroring). >> >> > >Is that SSA? I thought you were still on that. > > >- Allen S. Rout > > ----------------------------------------- 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.