FAST VP on VMAX 10k/20k/40k doesn't differentiate between FC RAID1 and FC RAID5, but since you're creating separate policies for your two FC pools/tiers (rather than trying to put both the FC R1 and R5 tiers into the same policy), this is fine.
That's correct -- a thin pool can only belong to a single VP tier.
The new FC RAID1 pool should consist of a new/unique disk group, pool, and tier, and should be in a new policy. You can share the existing EFD and SATA tiers in the new policy that contains the new FC RAID1 tier.
seancummins
2 Intern
•
226 Posts
0
February 10th, 2015 11:00
Hi Jim,
Yes, this is supported.
FAST VP on VMAX 10k/20k/40k doesn't differentiate between FC RAID1 and FC RAID5, but since you're creating separate policies for your two FC pools/tiers (rather than trying to put both the FC R1 and R5 tiers into the same policy), this is fine.
Thanks,
- Sean
seancummins
2 Intern
•
226 Posts
1
February 10th, 2015 11:00
Jim,
That's correct -- a thin pool can only belong to a single VP tier.
The new FC RAID1 pool should consist of a new/unique disk group, pool, and tier, and should be in a new policy. You can share the existing EFD and SATA tiers in the new policy that contains the new FC RAID1 tier.
Thanks,
- Sean
JimK513
1 Rookie
•
89 Posts
0
February 10th, 2015 11:00
all I read is that a thin pool can ONLY belong to a single VP tier. I found that limitation in a 2012 and 2014 release of P/N 300-012-014.
We would be using the efd and sata pools in two different tier configurations.
JimK513
1 Rookie
•
89 Posts
0
February 10th, 2015 11:00
awesome. thanks.
Jim