Recoverpoint journal on VNX - Thick or Thin ?

Using thick is considered best practice for journal LUNs. Due to the way the volumes will be effectively fully allocated during init.

Correct in the sense that the best practice is to use thick volumes as once the volumes are provisioned for journal usage they stay inflated as they are constantly written to on a new for old basis. The usage of the journal occurs by default after the full init.

Regards,

Rich

1) Since am using a SAS pool which is holding the journal LUNs, would it be a good idea dedicating / creating "Thick" LUNs for journal data? I understand the usage is high during initializations - how will it benefit when cost is the concern as you are dedicating capacity for non-frequent IOPs ?

2) Will this same Thick layout followed in the DR VNX as well, or can we go with Thin as this would be a col site?

Regards

Taz~

Use a separate pool for the journal requirement especially where the target is concerned.

Regards,

Rich Forshaw

Consultant Corporate Systems Engineer - RecoverPoint & VPLEX (EMEA)

Data Protection and Availability Solutions

EMC Europe Limited

Mobile: 44 (0) 7730 781169 44%20(0)%207730%20781169>

E-mail: richard.forshaw@emc.com

Twitter: @rw4shaw