Replication and overflow location at the target side

[flex]

Has anyone experienced this situation when using node replication with deduplication pools:
- ran out of space at the target side in that dedup pool
- and cannot allocate more space on the target server even if overflow location is set
- so the replication process always fails :-(

 

[delectro]

Isn't the overflow location only for volumes that you are planning to eject from library? Do you have nextstgpool assigned in the primary pool? Data should go there when first pool runs out of space

 

[flex]

dedup pool with tape next pool and no data goes into that pool and the replication stops due to lack of space