Symantec System Recovery 2013/2013 R2 Questions

Discussion in 'backup, imaging & disk mgmt' started by TheKid7, Aug 9, 2016.

  1. TheKid7

    TheKid7 Registered Member

    Joined:
    Jul 22, 2006
    Posts:
    3,469
    I have multiple Windows Server 2012 R2 Servers with Symantec System Recovery 2013 R2 installed on them (No physical boot media included. Make your own bootable ISO.). I also have two Windows Storage Server 2012 Servers with Symantec System Recovery 2013 installed on them.

    The Symantec System Recovery 2013 Licenses came with physical bootable restore media (one set each). I seem to have misplaced the restore media for one of these Servers. I think that the restore media will eventually show up. I installed Windows ADK on the Server for which I have the physical restore media. I noticed that to create a custom boot ISO, it required access to the physical restore media (or the files copied from it).

    All of the Symantec System Recovery 2013 R2 Servers ask if you want to make bootable media for a Server which has a License other than the one on which you are creating the Custom ISO. If yes, you enter the license key for that other Server.

    Will a custom boot ISO created with Symantec System Recovery 2013 R2 work for restoring images on a Server which has Symantec System Recovery 2013 installed (backwards compatible)?

    Thanks in Advance.
     
  2. TheRollbackFrog

    TheRollbackFrog Registered Member

    Joined:
    Mar 1, 2011
    Posts:
    3,045
    Location:
    The Pond - USA
    TheKid7, I believe it is as far as RESTORATIONS are concerned at a minimum (2013 vs 2012). But you're not describing "backwards compatibility"... you're asking about the same major versions at a different release level. Within major versions, compatibility is always supported, both at the imaging and restoration levels.
     
  3. TheKid7

    TheKid7 Registered Member

    Joined:
    Jul 22, 2006
    Posts:
    3,469
    I found the Restore Disk.

    I was able to make new boot media (containing the proper Network Drivers) for all of my Servers.

    Four of my Servers apparently were setup as UEFI rather than BIOS. I think I understand why UEFI was used for two of them (48 TB Each of Unformatted Storage Drive Size with the Operating System in RAID 1 using two ~300 GB hard drives). I am not sure why the other two were setup as UEFI.

    However, I have these Questions:

    1. On ALL of the Symantec Backup Task Configurations, I selected 'Show Hidden (Partitions?)'. Then I selected the C: partition plus any other previous hidden partitions that show up now. My goal is to backup whatever partitions which are necessary for restoring the Windows Server 2012 Operating Systems. Is it Correct to select (include) all of these hidden partitions with the 'C' partition when Imaging the Windows System Partition?

    2. If there other partition(s) other than the C partition, I typically Image the other partition(s) 'separately'. If I have to restore after a hard drive failure, I plan to first install C plus the hidden partitions, followed by restoring the other partition(s). Is this a good/correct practice?

    Thanks in Advance.
     
    Last edited: Aug 11, 2016
  4. oliverjia

    oliverjia Registered Member

    Joined:
    Jul 21, 2005
    Posts:
    1,517
    my 2 cents: keep OS and data on separate drives, and image the whole OS disk whenever possible, including all the system partitions for UEFI/GPT install: Recovery, MSR, EFI and C: partitions. This way whenever you restore the image to a new drive, you'll be up and running in no time.
     
  5. TheKid7

    TheKid7 Registered Member

    Joined:
    Jul 22, 2006
    Posts:
    3,469
    Symantec Additional Options.jpg Symantec System Recovery 2013/2013 R2 'Additional options' of the 'Drivers to Recover' section of the bootable Recovery Disk:

    Questions:

    1. Should ONLY 'Set drive active' be selected for the Restore of BIOS firmware Windows System Partitions?

    2. Should NOTHING be selected for the Restore of UEFI BIOS firmware Windows System Partitions?

    Thanks in Advance.
     
  6. Brian K

    Brian K Imaging Specialist

    Joined:
    Jan 28, 2005
    Posts:
    8,634
    Location:
    NSW, Australia
    TheKid7,

    I haven't used SSR for over a year and then only to test Entire Drive restores. The options in your screenshot above look like you are running a single partition restore. Is that correct?

    Regarding the "Set drive active" option. The C: partition may not be the Active partition. In a MBR system, the System Reserved Partition (if present) is the Active partition. In a UEFI system, the EFI System partition is the Active partition.
     
  7. TheKid7

    TheKid7 Registered Member

    Joined:
    Jul 22, 2006
    Posts:
    3,469
    Does anyone have any experience with Symantec Restore Anywhere?

    I am supposed to come up with a plan (written procedure) on what to do if there is a total Server failure and similar hardware is not available for restoring the Image.

    Thanks in Advance.
     
  8. richwood

    richwood Registered Member

    Joined:
    Oct 26, 2016
    Posts:
    1
    Location:
    Perth, Australia
    Yes, I've done it a few times and it worked fine. You need to include the chipset/hard disk controller drivers for the new hardware on your recovery USB stick. This is provided as an option when creating the recovery USB stick. When you fire up the recovery USB stick to begin the restoration and you get to the screen below, hold down SHIFT while clicking "Use Restore Anywhere to recover to different hardware" as this will bring up some more options which you will need to adjust depending on your individual circumstances

    NOTE: If restoring to different hardware, and the operating system being restored is Windows 2008 or above, ensure that the 'Run Windows Mini-Setup' option is disabled (Figure 6). To access this option, hold down the SHIFT key when enabling the Restore Anyware option.

    http://imgur.com/a/lMM0b

    To read the full guide, go here https://www.veritas.com/support/en_US/article.TECH129112

    http://imgur.com/a/lMM0b
     
Loading...