Solved

Backing up Windows 2012 system state using BackupExec 2010 R2 issue

Posted on 2014-02-26
4
1,882 Views
Last Modified: 2016-11-23
We have a Windows Storage Server 2012 (WS5400D0804) that we use for our company data. Our media server has Windows Server 2008 R2 as the OS and are using Backup Exec 2010 R2. There were some errors occurring in the Backup Exec for our full weekly backup which led me to a fix on Symantec's website. After I applied the registry fix, I wanted to test backing up the system state for our Windows Storage Server 2012. Upon trying to back it up, it was taking forever. I let it sit for 1.5 hours 2 times and it never succeeded. I looked at the log from the week before to see how long the system state was generally taking on our full weekly Friday backup and it turns out it is taking 5 hours to complete which is ridiculous!!! I looked at our Windows Server 2008 R2 system state backup from the week before to see how long it takes that one to backup and it only takes 2 minutes and it is twice the size. We do have the Backup Exec Windows Server agent on the  2012 server, too. Why is this taking 5 hours to try and backup the system state for our 2012 server? Any information would be greatly appreciated. I will attach screenshots of the settings that are used for the backups in BackupExec also.

(The error that was coming up at first that led me to look at this in the first place, was "VSS Snapshot warning. File %BeBootDrive%\bootmgr is not present on the snapshot.")

(Tape Drive = Dell Powervault LTO3-080)

Thanks,

Allison
BE.png
BE3.png
BE4.png
BE.png
BE2.png
0
Comment
Question by:f4ichick02
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
4 Comments
 
LVL 58

Accepted Solution

by:
Cliff Galiher earned 500 total points
ID: 39890529
Backup Exec 2010 R2 does not support Server 2012 at all and yes, in this instance, support means it doesn't work right.  Server 2012 was added only to 2010 R3, and only with service pack 3.

Additionally, storage server 2012 is technically not even supported with 2010 R3, but core, standard, datacenter, essentials, and foundation are. Chances are it *would* work, but if there were ever a DR issue and support were required from Symantec, you'd be in untested and murky waters.
0
 

Author Comment

by:f4ichick02
ID: 39904521
Thank you for the information. We are going to upgrade to Backup Exec 2010 R3 next week to see if it makes this error go away and I figured that it did not "officially" support Windows 2012 storage server but I just figured I would ask anyways in case someone else was experiencing this issue or came across this before. Thank you for your input though.
0
 

Author Closing Comment

by:f4ichick02
ID: 39904538
It was basic information I already knew but it did however convince my boss to let us try and upgrade to Backup Exec 2010 R3 next week.
0
 

Author Comment

by:f4ichick02
ID: 40028031
I just wanted to add another comment to my post about what happened after updating to Backup Exec 2010 R3. I upgraded to 2010 R3 and on our next full backup where the Windows Storage Server 2012's system state gets backed up, it only took roughly an hour compared to the 5 hours it was taking before. Our Windows 2008 R2 server only takes minutes so I really think that 1 hour is still to long but it is way better than 5 hours like before! I hope this helps anyone out that is in the same boat.
0

Featured Post

Transaction Monitoring Vs. Real User Monitoring

Synthetic Transaction Monitoring Vs. Real User Monitoring: When To Use Each Approach? In this article, we will discuss two major monitoring approaches: Synthetic Transaction and Real User Monitoring.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

The article will include the best Data Recovery Tools along with their Features, Capabilities, and their Download Links. Hope you’ll enjoy it and will choose the one as required by you.
Resolve DNS query failed errors for Exchange
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles from a Windows Server 2008 domain controller to a Windows Server 2012 domain controlle…
This tutorial will walk an individual through the process of installing the necessary services and then configuring a Windows Server 2012 system as an iSCSI target. To install the necessary roles, go to Server Manager, and select Add Roles and Featu…

691 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question