Re: Can I move specific SG but not all storage groups to their own LUN



Hi,

It is probably just a matter of time. Moving a 35 Gb file can take several
hours.

Leif

"extron" <extron@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:62A55120-8A63-4680-8C21-F3362DAF9E9B@xxxxxxxxxxxxxxxx
I have a question concerning whether I can separate specific Storage
group/message stores onto separate LUNS/spindles on our SAN?

Currently the LUN which holds all four of our Storage Groups is
approaching
6% of free disk space so to rectify the storage from running out I've
attached a new 300GB LUN. By the way the new LUNs also dependent on SA as
a
physical disk cluster resource so that in the event of a failure this new
LUN
will be failed-over to the passive node.

I have already attempted to move specific Storage Groups to the new LUN
but
when I attempt to move a 35GB .STM to the new LUN it seems to hang. Is
this
normal due to it's size because strangely it does copy on the new LUN the
the
same .STM and Windows does report it's 35GB.

Is it really of matter of me waiting for the move process to finish and/or
how long should I wait for it to finish processing?

The documentation I fumbled through is kind of vague and misleading on the
issue of how long the move takes so any one's feedback here is much
appreciated.


Exchange 2003 EE SP2
Windows 2003 EE SP1 W/latest updates/fixes, etc




.



Relevant Pages

  • Re: Moving Exchange2003 specific Storage Groups to separate LUNs or di
    ... Currently the LUN which holds all four of our Storage Groups is ... I have already attempted to move specific Storage Groups to the new LUN ... when I attempt to move a 35GB .STM to the new LUN it seems to hang. ... Windows 2003 EE SP1 W/latest updates/fixes, ...
    (microsoft.public.exchange2000.information.store)
  • Re: performance question
    ... and whatever else is the matter in terms of aggregates you really ... Each store should have its own LUN and ... that LUN should be in its own volume. ...
    (microsoft.public.exchange.admin)
  • Re: expand database volume
    ... disk perforance counters circa Windows NT and 2000. ... could create a new R5 with the larger drives and attach that to the lun. ... more disks to our SAN. ...
    (microsoft.public.exchange.admin)
  • Re: expand database volume
    ... disk perforance counters circa Windows NT and 2000. ... could create a new R5 with the larger drives and attach that to the lun. ... more disks to our SAN. ...
    (microsoft.public.exchange.admin)
  • Re: SAN to SAN migration
    ... So the methodology would be to run robocopy while the source LUN is in production and copy all of the data over. ... You wont be able to perform a real block level copy because the LUN is partitioned by the OS so you'll need to use a filesystem level tool. ... it's pretty much the standard for moving/migrating data cheaply and easily in the windows world. ... but takes a terribly long time b/c of the files on the LUNs are so ...
    (comp.arch.storage)