Author: Skylar Thompson <skylar2 AT U.WASHINGTON DOT EDU>
Date: Wed, 5 Dec 2012 18:18:42 -0800
I think if you do a MOVE NODEDATA to migrate data from one primary pool to another, the data in the copy pool stays intact. I don't think there is a way to expire it other than through the normal nod
Author: "Ehresman,David E." <deehre01 AT LOUISVILLE DOT EDU>
Date: Thu, 6 Dec 2012 16:17:35 +0000
As the q occ shows, there are two storage pools. nr-pvl is the primary and nr-ofl is the secondary. David how many pri stg pools do you have and what is hierarchy (next stg) the other thing is check
Author: "Ehresman,David E." <deehre01 AT LOUISVILLE DOT EDU>
Date: Thu, 6 Dec 2012 16:19:17 +0000
No move data involved. In fact, the problem persists after deleting all the copy pool volumes for this node and doing a fresh backup stg. David I think if you do a MOVE NODEDATA to migrate data from
Author: "Sheridan, Peter T." <Peter.Sheridan AT CUNAMUTUAL DOT COM>
Date: Mon, 10 Dec 2012 15:08:47 +0000
What is retention set on copy pools versus primary pools ? If you're doing that level of evaluation, then I suggest you q contents for the node on the various volumes, and reconcile them. - Allen S.
Author: Maurice van 't Loo <maurice AT BACKITUP DOT NU>
Date: Tue, 11 Dec 2012 13:52:35 +0100
I saw this in multiple environments and as long it's not that copy has less objects than primary, I actually don't care ;-) Is it possible that if a file exists in multiple aggregates (i.e. big files