One reason you may want to use an existing filesystem is if you don't want the target filesystem to be the same name (or mountpoint). This is not required unlike the other features that were already discussed (deduplication, thin, FLR, etc.).
Otherwise, if you tell it to create the filesystem for you, it will be created with the same name on the target.
dynamox
9 Legend
•
20.4K Posts
0
July 3rd, 2012 07:00
you specify one if you already have file system in place that you want to re-use. Source and target file systems have to be identical.
mjzraz
1 Rookie
•
93 Posts
0
July 3rd, 2012 08:00
That seems to have very little benefit. Could the target file system be thin provisioned?
Just looking to save on the free space that multiple file systems have. It adds up when you have 10-20 file systems all with 500gb+ free space.
dynamox
9 Legend
•
20.4K Posts
0
July 3rd, 2012 11:00
is the source thin file system as well ?
mjzraz
1 Rookie
•
93 Posts
0
July 8th, 2012 05:00
No the source file systems are not thin provisioned. Is thin provisioning reccomended in most cases?
I guess I feel like we have a lot of "committed" space tied up in free space that we need on all these file systems.
rupal1
433 Posts
0
November 9th, 2012 00:00
yes, if the Target is Thin proviosioned then you have to enable the same on the Source too to start the replication.
christopher_ime
4 Operator
•
2K Posts
0
November 17th, 2012 01:00
One reason you may want to use an existing filesystem is if you don't want the target filesystem to be the same name (or mountpoint). This is not required unlike the other features that were already discussed (deduplication, thin, FLR, etc.).
Otherwise, if you tell it to create the filesystem for you, it will be created with the same name on the target.