Hi, I've some strange (in my opinion) behaviour on the allocated space on snapmirrored volume on secondary storage.
I've some volume replicated from a primary to a secondary storage and I was expecting that the allocated space on the snapmirrored volume (with guarantee=none) was about the same as the source used space.
The source volume have guarantee=file, I've changed one to guarantee=none (to have the same setting on source/destination) and I've done a Snapmirror update but nothing changed.
This is the situation:
Source:
| Volume | Allocated | Used | Guarantee |
| DPI_Data | 210GB | 209GB | none |
| DPI_Exe | 52GB | 51GB | file |
| DPI_Log | 1017MB | 968MB | file |
| DPI_Temp | 65MB | 4248KB | file |
Destination:
| Volume | Allocated | Used | Guarantee |
| DPI_Data_BK | 277GB | 209GB | none |
| DPI_Exe_BK | 119GB | 51GB | none |
| DPI_Log_BK | 69GB | 912MB | none |
| DPI_Temp_BK | 68GB | 4740KB | none |
As you can see the first 2 are 210/52 GB allocated on the source and 277/119 allocated on the destination. It seems a bit strange ...
There's anything I can check?
The Data Ontap version is 7.3.6P2.
