General discussion

Locked

BackupExec 10d woes!

By adamberger82 ·
I am quite frustrated with backup exec!!! I am running version 10d in a windows 2000 domain. For the most part it runs fine, but i am having continual problems backing up the "wmi repository data directory" on multiple machines. This directory is located in \WINNT\system32\wbem.(windows 2000) its not even every night, randomly a few computers will not backup that directory and i get a failed job. Sometimes a job will stop in that directory on the file regevent.mof file and will freeze the job and not be cancelable until i reboot my backup server. Ive checked into the symantec forums and i am finding that this is a huge problem for alot of people, and the troubleshooting process for the problem is extravagant and does not fix the problem in the long run. A lot of people seem to think its a bug in veritas software. I am at the point where im ready to exclude the directory, but im not sure what the **** it is, or if its important. It has something to do with driver integration from what i can tell from the long winded Microsoft site. I was just interested if anyone else has these problems at all and if so, what actions you took. For now I'm going to exclude this directory on every computer, but the last thing i want to find out is that my restores will all fail if i skip this directory. The annoying part is that ntbackup has no problem with this at all (no surprise). Please do not post any solutions involving corrupted directories or ways to fix it from the symantec website. Ive been on the syamntec site and have also had them on the phone and there solutions DO NOT work. I have tried them, they work for a couple days and the problem comes back. I am more interested in skipping this directory at this point, because i am told that it may be backed up by system state anyways.(ive also heard skipping the directory may not solve the problem because of this) Anyone have the same problem?

This conversation is currently closed to new comments.

9 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

by russellrl2 In reply to BackupExec 10d woes!

I'm not sure why you are backing system32 files in the first place. I use BackupExec 10d also but I create a folder on the C drive called User and that is what I backup. Everything in the users profile (Microsoft Office to include Outlook personal folders) is pointed to that folder so it is backed up. I don't have any problem accessing this folder. If the user doesn't want something backed up (personal items) they keep it on their desktop or in their My Documents folder. I hate wasting tape on .MP3s.

Collapse -

by adamberger82 In reply to

Russell, I forgot to mention these are Windows 2000 servers in my company. I am doing full backups of these servers. c drive, system state every single night. That is why im worried about my backups not being complete.

Collapse -

by adamberger82 In reply to BackupExec 10d woes!

Russell, I forgot to mention these are Windows 2000 servers in my company. I am doing full backups of these servers. c drive, system state every single night. That is why im worried about my backups not being complete.

Collapse -

by HAL 9000 Moderator In reply to BackupExec 10d woes!

I don't know that Backup is the correct solution in this particular case as you are doing a complete backup and including Critical Windows Files to be included. These can and quite often do cause problems.

I find it easier to create an Image to CD/DVD with a tool like Ghost and overwrite the images on rewritable media when required. It's faster and safer as well as having the advantage of having the ability to make a Bootable Drive/Partition when you restore from the Image. You could always use a Removable HDD to do this to as well and instead of creating an Image of the complete Drive you could just Clone it.

I do this quite a lot so if something goes wrong I can have the servers up & running in a very short time and then clone to the drive that was removed after everything is working correctly.

Col

Collapse -

by adamberger82 In reply to

Thanks for the reply Col. As far as imaging, i have toyed with the idea however it does not provide me with the insurance id like to maintain for job security reasons. What happens if the image you made fails? You have no other backup besides your one image to fall back on. In addition to this i have a alot of SQL based apps that have changes made all day. I cant reimage all my servers nightly, thats the type of overmanagement im looking to avoid by having my backups fully automated via backup exec.
Does ghost give you options to exclude SQL and exchange databases from its imaging? So lets say, if it does, i exclude the SQL and exchange databases on the servers i need imaged. Can I be sure that i can restore my database from backup, when the system state was imaged 2 weeks ago? In addition to this, id have to reimage anytime a new app or update is applied, the time needed to keep images up to date is too costly, and not neccesary if you are using an automated backup plan.
My point being, yes you are right, backing up the windows files does cause problems, but its the only way i can ensure that the system is returned to its exact state RIGHT BEFORE failure, not from an image i made 2 weeks ago. An image made 2 weeks ago, may or may not bring me back to the exact state i had the night before.

I have a full backup of all servers in my company running nightly. So at all times i have 5 copies of all my servers stored and ready to rip. I am simply trying to weed out the odds and ends of the backupexec suite, so i can ensure my backup integrity. I may decide to image the non critical servers to cut down on my backup lengths and sizes, but for now i will stick with backup exec.

I was really directing this question towards people who are using this backupexec suite and have or are experiencing this problem. However, you all may continue to take pot shots at my backup plan!! hehe, j/k. :) thanks again Col

Collapse -

by HAL 9000 Moderator In reply to BackupExec 10d woes!

Well have you considered instead of doing a complete Backup every day. To do a Major Backup or Image and then do incremental backups daily, hourly or whatever you need to do?

That would give you greater flexibility and only slow down the time required to do a complete rebuild slightly.

Of course I would recommend that you do an Image Regularly and them just proceed with the Incremental Backup's till the next complete Image is done.

That will get you around the problem of attempting to back up the entire Windows Directory and having the backup fail because some Windows components will not allow you to back them up.

Col

Collapse -

by mstillwagon In reply to BackupExec 10d woes!

Yeah, I feel your pain with this one. We've been having the exact same issue, plus multiple other ones with BE 10. In regards to your issue, we have a workaround that actually works quite nicely. I hope this works for you.

The WINNT\system32\wbem folder is actually part of the system state. For some reason, BE has trouble backing up with WIM repository (which I'm still not sure why). What I've done is exclude the folder from the selection list, which allows the backup to process successfully. Since I'm still not 100% sure how necessary that folder is, I've created a seperate folder on the C drive called "Backup." In this folder, I've stored a local backup of the system state, which is run everyday about an hour before the regular backup job starts. This backup of the system state honestly only take a few minutes, so you should have to worry about it screwing up your regular backup.

Here's the only problem with this: if everything crashes and you need to do a restore, you're going to have to remember that your system state was backed up to the C:\Backup folder and must also be restored. It's an additional step that you'd have to remember and might cause you a lot of frustration if you forget.

Since I did this, the error has stopped completely, but I'm still searching for a better method, as too many exceptions could prove to not be that great of a thing. Best of luck to you.

Collapse -

by mstillwagon In reply to

Sorry, but I forgot to mention this part, although it may be self-explanitory. The C:\Backup folder that I created is backed up by the main backup. This folder contains the local backup of the system state, so you're still (in essence) backing up the WINNT\system32\wbem folder.

Collapse -

System State

by BBPellet In reply to

If your backing up the system state...then your whole system32 is backed up. You do not need to have the \%system%\system32\* in your selection list, just select the system state. Then all your registry files and the entire system32 folder are backup, they are also backed up in the "hot state" in otherwords as the system is active and current.

You will get this error if you have both the system state and the actual system32 folder in your selections. You basically backing it up twice...once when BE does a flat file backup and again when it backs up the system state. You actually only need one...and that is the system state as it is the most current and safest to restore...especially in an Active Directory Controller.

Back to Windows Forum
9 total posts (Page 1 of 1)  

Related Discussions

Related Forums