Need steps for adding 1.5TB space to Celerra .

Question

My envt has 2 celerra NS40G (5.6) , one at each site .. one Celerra is acting as production and other is acting as DR for production .. We have SRDF -S between the 2 celerra's .so failover can be executed on DR celerra once the production goes down .. DMX-4 is backend from where Celerra gets SAN , 2MDX-4 one at each site .

Now i have to add additional 1.5 TB SAN space on production , which means i will have to add same 1.5TB SAN on DR side as well .. Can someone provide the steps for doing this , allocation is not a problem .. how to get them into DG's on both sides and ensure they are getting replicated .. will this require any downtime.

pdubey2 · Answer

I would be able to do the pairing between devices on both the sites as we have dynamic binding between device which allows us to convert them to R1 or R2 devices on either sites..

I would like to know what needs to be done after i have added space of 1.5TB to each celerra , things like how do i scan on celerra, how to add to DG on celerra .. and so on ..

Rainer_EMC · Answer

Hi,I'm not that familiar with SRDF but I think you're looking at a bin file change anyway so its best to contact EMC support directly.regardsRainer

pdubey2 · Answer

Thanks Sandip and Peter ,do i need to run this na_rdf on source and destination celerra , against any dg name or just nas_rdf -init (with root priveleges) is fine ..

Rainer_EMC · Answer

I am not sure if Celerra supports Dynamic SRDF. You will want to check that out with your local EMC team.

support for dynamic SRDF was just added recently in 5.6.44

From the release notes:

Dynamic SRDF
Celerra® Network Server version 5.6.44.4 introduced and supports
the Dynamic SRDF® (Symmetrix® Remote Data Facility)
functionality. Dynamic SRDF enhances the disaster recovery (DR)
solutions that are currently available with Celerra Network Server.
When the DR site is activated, Dynamic SRDF synchronously mirrors
Celerra's volumes back to the original source site. This reversal of
remote mirror protection adds another level of redundancy in the
event that the DR site becomes unavailable. It also reduces the
downtime required to synchronize data during a restore because the
synchronize phase is no longer needed with Dynamic SRDF.

When the DR site is activated, Dynamic SRDF reverses the direction
of data mirroring. As a result, the data is synchronized from the DR
site to the original source site. The NFS or CIFS client that initiated
the I/O request receives the write-acknowledgement only after the
remote storage system validates the data in cache, thus ensuring data
consistency.

cosse · Answer

I am not sure if Celerra supports Dynamic SRDF. You will want to check that out with your local EMC team.

That being said, in order to discover the devices you need to run a server_devconfig command on all of the data movers that you present storage to.

server_devconfig server_x -probe -scsi -all
This will probe the bus for the new devices.

server_devconfig server_x -create -scsi -all
This will create the devices.

If you are using AVM, this will place the devices into to proper storage pool and they will be available for volume expansions.

Peter_EMC · Answer

No, it will not effect existing FS, VDM, etc ....but do not forget to run a nas_rdf -init on source and destination, because the devicegroup which needs to be failed over, nedds to be recreated

pdubey2 · Answer

Thanks for the steps ..Will scanning for new devices cause any issues to already esxisting filesystems ,and VDM's .. we have 7 vdm's and 7 CIFS ,filesystems running in production ..

nandas · Answer

Please ensure that you also run the server_devconfig commands (probe and create) on the Standby data mover as well - or else, the standby data mover will not work properly.

The scanning can be done ONLINE - no issues/impact on your existing data - file systems or VDM or CIFS access.

My 2 cents

Thanks,
Sandip

Peter_EMC · Answer

do i need to run this na_rdf on source and
destination celerra , against any dg name or just
nas_rdf -init (with root priveleges) is fine ..

You need to run it on both sides everytime you add Luns to the Celerra.

Celerra

Need steps for adding 1.5TB space to Celerra .

Was this post helpful?