UNSOLVED

pfrassino

updated

19 years ago

P

pfrassino

1 Rookie

•

77 Posts

0

772

November 13th, 2007 03:00

Restoring entire server on a different system disk path

Hi,
suppose to have a new system reinstalled, using disk E: as the system disk instead of C:.
Is the recovery supported relocating data from C: to E: ?? I've tried, but the networker server relocate files under E:\C\...
What about VSS SYSTEM BOOT, SYSTEM FILESET, SYSTEM SERVICES savesets?? I think that they have C:\ hardcoded, therefore the relocation is impossible...
The disaster recovery guide seems not to have any info about it.
Thanks for any suggestion

Pierpa
  • ble1

    6 Operator

    •

    14354 Posts

    •

    56186 Points

    383

    1

    Posted November 13th, 2007 04:00

    It won't work as disaster recovery asks for system to be installed first as it was before. Otherwise all system configuration would be restored as it was before pointing to wrong direction and causing BSOD (if you would even get to that point).
  • pfrassino

    1 Rookie

    •

    77 Posts

    383

    0

    Posted November 13th, 2007 08:00

    Yap!
    Don't try to make easy things too difficult ...
  • xe2sdc

    6 Operator

    •

    2831 Posts

    383

    0

    Posted November 14th, 2007 02:00

    Pierpa ben ritrovato !! Sono passati tanti anni da quando ci si vedeva ad Ivrea in Infostrada .. prima eravamo su fronti "opposti" mentre ora -mi dicono- siamo cugini ;-)

    But let's back to the topic .. From the little I know about NW I can only say that relocating a saveset works, as you noted, inside the same root .. I think it's a M$ specific issue since on every unix system the / (slash) is the single root of all filesystems .. In M$ you have many different roots ... C: is a different root then E: .. So your relocation will work WITHIN the same root. VSS savesets are a totally different story to be told since you aren't backing up real files but instead a copy of a very special object that have a very special meaning for the OS. I think they aren't hardcoded to C: .. they are simply bound to the boot disk of the running OS .. I suppose they will be recovered where the running OS keeps its registry and all other M$ specific informations. My 2 (poor) cents :-)
  • HabibG2

    455 Posts

    383

    0

    Posted November 14th, 2007 03:00

    A non NetWorker solution I have used in the past for situation like this, Why not use something like a disk image utility software ( i.e. Ghost, or paragon Disk manager.) Create an image of your existing disk and transfer it to your new partition.