UNSOLVED

StorageAdmin2

updated

17 years ago

0

1348

August 24th, 2009 00:00

Write_Disabling the devices on DMX

Hi Guys,
Here is my requirement .
I got a DMX-3 replicating devices to DMX-2K in my current setup and I am migrationg all the DMX-3 devices to DMX-4. Now i wana split the relationship b/w DMX-3 & DMX-2K and after the split , i wana make sure the devices on the DMX-2K( R2 ) remain write_disabled because i don't want anyone access those devices after they are turned into STD after the split. I am gone use the same devices on DMX-2K as destination for DMX-4, How can i write disable the std device on DMX-2K , ofcourse not using device file , may be a bin load ? and another question is when i will again re-establish the relationship b/w DMX-4 &DMX-2K , will i have any issues since the device on DMX-2K are write_disabled ?

Also I don't want all the devices on DMX-2K write_disabled, only the R2 ones which will be changed to STD devices.
Please let me know a way out ?
  • xe2sdc

    6 Operator

    2831 Posts

    880

    0

    Posted August 24th, 2009 02:00

    Bhat instead of using "symrdf split" command you can use "symrdf susp" command that will simply stop RDF without changing R2 devices to RW enabled.

    Can you please explain better the following steps ?? You are going to use some of your R2 devices in DMX2K as R2 devices for your brand new DMX4. But also want to change some devices to STD. Can you please provide better details on this ??
  • xe2sdc

    6 Operator

    2831 Posts

    880

    0

    Posted August 24th, 2009 03:00

    1) the relation is static. But you can convert the relation to dynamic if you prefer
    2) you can unmask devices (if you are using masking).
    3) you can still control (via symrdf) the replica and issue a symrdf susp instead of a symrdf split and leave to EMC the task to remove the pairs (via a binfile) if you don't convert devices to dynamic
  • 880

    0

    Posted August 24th, 2009 03:00

    The relationship b/w DMX3 &DMX2K is static and that would be broken via bin file. and then we will have relationship b/w DMX3 with DMX4 and also DMX2K with DMX4. Now since it is via bin load by EMC , it will not be suspended, we will be removing the rdf leg b/s dmx3 and dmx2k. So all devices on dmx2 will turn in std devices, i just don't want those devices on DMX2K to be accessed mistakely since they wud be write_enabled , so after the rdf leg is broken b/w dmx3 and dmx2k, i want all the std devices which were R2 previously to be write_diabled.
    Hope this explains things :)
  • 880

    0

    Posted August 24th, 2009 04:00

    Stefano

    If i wana make the std devices which were R2 previously write_diabled and not with symdev command, is there any option to do that under bin file load ?
  • xe2sdc

    6 Operator

    2831 Posts

    880

    1

    Posted August 24th, 2009 05:00

    EMC personnel can issue symwin commands and set your devices WD.
    You don't need a binfile. Your local friendly CE will use symwin and disable writes on your devices.
  • 880

    0

    Posted August 25th, 2009 03:00

    Well seems like the EMC CE, is not happy to run the symwin commnads and thinks that might be potentially dangerous ???
    I will be using the symdev -f option to write_disable the devices.
    Thanks for your help.
  • KD8EWE

    2 Intern

    155 Posts

    880

    0

    Posted September 1st, 2009 12:00

    You can use the following for write dsiable a device

    symdev ¿sid xxxx write_disable [SymDevName]

    and to write enable a deivce as follows

    symdev ¿sid xxxx rw_enable [SymDevName]
  • 880

    0

    Posted September 1st, 2009 17:00

    There too many devices for me to use this option, anyways i have used the file options and wd the devices, thanks for your inputs.