Advertisement
If you have a new account but are having problems posting or verifying your account, please email us on hello@boards.ie for help. Thanks :)
Hello all! Please ensure that you are posting a new thread or question in the appropriate forum. The Feedback forum is overwhelmed with questions that are having to be moved elsewhere. If you need help to verify your account contact hello@boards.ie
Hi all! We have been experiencing an issue on site where threads have been missing the latest postings. The platform host Vanilla are working on this issue. A workaround that has been used by some is to navigate back from 1 to 10+ pages to re-sync the thread and this will then show the latest posts. Thanks, Mike.
Hi there,
There is an issue with role permissions that is being worked on at the moment.
If you are having trouble with access or permissions on regional forums please post here to get access: https://www.boards.ie/discussion/2058365403/you-do-not-have-permission-for-that#latest

Window2003 server: Extending drive (san attached)

  • 13-07-2007 12:12pm
    #1
    schmills
    Closed Accounts Posts: 14 ✭


    Hi,

    on window2003 server which is SAN attached. There is currently an E: drive which is assigned 100gb of SAN disk space. I am getting another 100gb.

    1. My questions is about extending the E: drive (making it 200gb). Does this affect the raid set on the SAN or redundancy? or is there anything i should be concerned about later on, in terms of disaster recovery.

    2. Also the E: drive is NTFS, when you extend a drive does it automatically make the newly assigned space NTFS (is current data affected?)

    HAs anyone got expierence of this? or should i just create a new drive on the server and assign it the 100gb?

    Cheers,

    Schmills


Comments

  • #2
    zod
    Closed Accounts Posts: 2,025 ✭✭✭zod


    Easiest and safest way.

    1. Ask the SAN guy to assign you a new full 200GB block.

    2. Assign another drive letter to the new lun

    3. Stop everything using data on old 100GB drive, throw a deny on any shares, stop all data services

    4. Run robocopy to new drive - analyse log, check disk usage is as expected

    5. Swop the drive letters using disk manager

    6. Start services, test shares,

    7. After a week give the old lun back to the SAN engineer.


  • #3
    WizZard
    Registered Users, Registered Users 2 Posts: 6,762 ✭✭✭WizZard


    You can do the above if space on the SAN is not an issue. However, if space is an issue then you can extend the volume "live".

    This is possible and is non-destructive* to current data on the volume/partition.

    When the LUN has been extended you should see it in Disk Manager as having an extra 100GB empty/free space after the current partition.

    You then need to open a command prompt and type 
    diskpart

    Then select the disk and partition you need (use 
    list disk
    and 
    list partition
    to identify the correct disk/partition), using the commands 
    select disk <num>
    and 
    select partition <num>

    Since you want to use all the empty space for the partition you can issue the 
    expand
    command with no options.

    This will expand the partition to use the available disk space after the current partition. You should see the space available immediately.

    This procedure will not work on a system/boot drive

    Data redundancy/RAID sets on the SAN are not an issue, as they should not change.


    *Note: You have backups, right? :)


  • #4
    Mac daddy
    Registered Users, Registered Users 2 Posts: 2,942 ✭✭✭Mac daddy


    The guys looking after the SAN should be the ones worrying about the redundancy of the array.

    All they need to do is bang a extra drive in the disk cabinett, extend the physical array with the newly added disk.
    Once the array has been extended ( depends on the controller and disk types can take around 8mins per GB )

    The logical drive ( The one your OS sees ) needs to be extended use diskpart to extend the drive.

    Faster way of doing it is backup data blow the array away - recreate the array with the new disk in it and restore the data onto it.
    If you have a lto drive doesn't take that long.


Advertisement