May 19th, 2010 04:00

I guess the interface must not be in use. Do I also have to remove CIFS servers, VDM's, replication...?

4 Operator

 • 

8.6K Posts

May 19th, 2010 04:00

No

4 Operator

 • 

8.6K Posts

May 19th, 2010 05:00

Probably

You can try stop the CIFS service

If you have downtime for à Data mover reboot and à good relationship

to your local EMC technical contact you can try asking for à RPQ for

à direct way.

PLEASE take the time file à product enhancement request for this on

Powerlink

Rainer

May 21st, 2010 04:00

PER filed.

can you confirm that:

* modify the "virtualdevs" file

* `server_standby server_2 -activate mover`

* `server_standby server_2 -restore mover`

works and has no side effects?

2 Intern

 • 

366 Posts

May 21st, 2010 05:00

Hi,

I wouldn't recommend you to do it.

It can have unpredictable side effects. Only a senior tech support or field specialist should do this.

Gustavo Barreto.

4 Operator

 • 

8.6K Posts

May 21st, 2010 07:00

Hi,

as Gustavo said - please do NOT modify config files or NASDB files yourself - there is a reason that we dont only do that through commands.

There are often dependencies there to other config files or databases and you can quite some problems - up to the data mover failing to boot.

If you have a need there talk to support if they can get an approved procedure from engineering specifically for your config.

Even then they would only do it after having tested it in the lab.

regards

Rainer

No Events found!

Top