ANR0984I Process ### for Move Container (Automatic) started

[ILCattivo]

So I have a system where a couple of SP 8.1.4 servers protect each others Container Storage Pools and subsequently replicate certain nodes afterwards as part of a daily maintenance script.

Today I started to see act log messages of the likes below for the very first time on one of the 8.1.4 servers/

Feb 9, 2018, 10:09:52 AM ANR0984I Process 671 for Move Container (Automatic) started in the BACKGROUND at 10:09:52. (PROCESS: 671)
Feb 9, 2018, 10:09:52 AM ANR0984I Process 670 for Move Container (Automatic) started in the BACKGROUND at 10:09:52. (PROCESS: 670)
Feb 9, 2018, 10:09:52 AM ANR0984I Process 669 for Move Container (Automatic) started in the BACKGROUND at 10:09:52. (PROCESS: 669)
Feb 9, 2018, 10:09:52 AM ANR0984I Process 668 for Move Container (Automatic) started in the BACKGROUND at 10:09:52. (PROCESS: 668)
Feb 9, 2018, 10:09:52 AM ANR0984I Process 667 for Move Container (Automatic) started in the BACKGROUND at 10:09:52. (PROCESS: 667)
Feb 9, 2018, 10:09:52 AM ANR0986I Process 664 for Move Container (Automatic) running in the BACKGROUND processed 124,192 items for a total of 10,708,840,448 bytes with a completion state of SUCCESS at 10:09:52. (PROCESS: 664)
Feb 9, 2018, 10:09:52 AM ANR0204I The container state for O:\proinst1\LOCAL-INLINE\04\0000000000000426.dcf is updated from AVAILABLE to PENDING. (PROCESS: 664)

Now, I'm not familiar with this automatic process, certainly don't initiate it by any script or other admin schedule.

Does anyone within the community know what the system is doing during these processes in relation to the container storage pool.? I've read that manual Move Container commands are often used for moving data between containers on one server or where there are disk errors present, but what about the automatic ones?
Could this be some kind of background self defragmentation of the container pool going on here, similar to reclamation and I need not be concerned? Looking at the actlog history it's not something that occurs every day on this particular windows server sometimes every 5 to 7 days maybe, and I can't see it logged at all within the last 30 days on the other (Linux) server?

Thanks

 

[blankgap]

Hi,

has anyone experience with this?
My Servers started to do these automatic container moves as soon as they were upgraded to v8.1.4

Yesterday i had 1153 (!) moved containers, leading to no space available on the Storagepool because these containers change to state=PENDING after moving. (6TB out of 18TB (!!) Stgpoolcapacity was on PENDING)

Reusedelay is set to 2 on the pool.

Thank you

 

[RecoveryOne]

I was just reviewing this post the other day, I went from 7.1.1 to 8.1.1 and then 8.1.5 and all of a sudden a lot of move container processes kicked off.
I seem to recall that there were some improvements with how container fragmentation is evaluated by the server and that is partly responsible for the number of these processes. I do not believe there is any config options as its all done in the background to us.

Not sure if it will be useful to anyone, but over the past 10 days Move Container (Automatic) has shuffled about 23.59TB.
Will say, right before the move container process kicks off, TSM reports "Containers are only using 99.54% of 68027.62 GB due to fragmentation". Thats from ANR4392I. The worst I seen is 97.15% of 69340.05 GB. Would be handy to know at what percentage TSM feels that it needs to defrag.