Re: [ADSM-L] Proctect Stgpool

David,

I'm using 'protect stgpool' exactly like I used 'backup stgpool' previously. Every day, after the backup window is completed, I run a protect stgpool, then a repl node. This ensures that the storage pool is protected from corruption and that all node metadata is synced across my two TSM servers. Using protect stgpool is also much more consistent over fast high-latency networks like our link between the primary datacenter and our recovery center across the country. Because protect stgpool runs on an extent level, running a multi-session protect command will always fill the pipe until process completion. Then I cut a db backup to a local disk and the server maintenance window is complete.

I don't use the forcerec command unless I see a replication error or failed replication process.

Hope that helps,
__________________________

Matthew McGeary
Senior Technical Specialist - Infrastructure
PotashCorp
T: (306) 933-8921
www.potashcorp.com

From: David Ehresman <david.ehresman AT LOUISVILLE DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
Date: 06/07/2016 08:33 AM
Subject: [ADSM-L] Proctect Stgpool
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

If you are using container stgpools, how are you using the "protect stgpool" command? Are you running it throughout the backup window or after backups have completed? When and how often do you run the "replicate node" command? Are you using the forcereconcile option? Why or why not? I'm getting ready to set up container replication and trying to understand the implications of the various options. David