|
 Node replication DB sizing
Hallo Stefan,
if you set with the command "set dbrecovery" the number of streams
(NUMStreams=), as a result, automatically triggered DB Backups potentially
will use more than one drive during time periods where you "may be" do not
want it (on the other hand, if you specify e.g. 4 streams and do not have
enough drives, the streams are revised down to the available number (see msg
ANR4320W). What I did not test so far is the influence of database process
"preemption" on that behavior.
So, in fact both should work, but I would prefer to specify the number of
streams when I actually am executing the backup db command during my daily
maintenance cycle in order to have "more control".
Rgds mikel
Michael Malitz
PS: My next TSM 6.3 update workshop will take place 12/13. January (affirmed
date)
-----Ursprüngliche Nachricht-----
Von: ADSM: Dist Stor Manager [mailto:ADSM-L < at > VM.MARIST.EDU] Im Auftrag von
Stefan Folkerts
Gesendet: Dienstag, 20. Dezember 2011 13:09
An: ADSM-L < at > VM.MARIST.EDU
Betreff: Re: AW: Node replication DB sizing
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.malitz < at > 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 < at > VM.MARIST.EDU] Im Auftrag
von John Monahan
Gesendet: Dienstag, 20. Dezember 2011 00:02
An: ADSM-L < at > 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
|
