Hi Michael, Could you elaborate on this :
..."In addition you should not set the default in set dbrecovery but use the nums= in the backup db command."... Regards, Stefan On Tue, Dec 20, 2011 at 7:34 AM, Michael malitz <michael.mal...@mm-it.at>wrote: > Hallo > > As I've seen during my tests for my new TSM 6.3 update workshop, the > database size did not change as such. > But you have to pay attention that the number of volumes you have to > allocate / use will be higher of course. > In addition you should not set the default in set dbrecovery but use the > nums= in the backup db command. > > Rgds mikel > Michael Malitz > > -----Ursprüngliche Nachricht----- > Von: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] Im Auftrag von > John Monahan > Gesendet: Dienstag, 20. Dezember 2011 00:02 > An: ADSM-L@VM.MARIST.EDU > Betreff: Node replication DB sizing > > I was wondering if anyone has any experience with the new node replication > and how it affects the TSM database size, both on the source and target > sides. I'm unable to find any type of sizing guidance for the DB side of > things. > > Thanks >
