Tip-How to

3259 Topics

0xe000feb9 - The NDMP subsystem reports (Any real fixes or work arounds)
OK I have seen and read quite a few posts on this matter, with very few solutions. Here is my issue. Here is what I am having for an issue. Iam using the BackupExec 11D (7071) and backing up Windows Systems. The majority of my jobs run fine. There are a few jobs that error out because of the *** Completed status: Failed Final error: 0xe000feb9 - The NDMP subsystem reports that a request cannot be processed because it is in the wrong state to service the request. Final error category: Resource Errors For additional information regarding this error refer to link V-79-57344-65209 **** I have checked out the port 10000 on the affected servers. The port on the affected system is used by Client system I have uninstalled rebooted reinstalled on the affect system with no change. Changing the port on all the servers is not a good option as the amount of systems that is affected is not large, and change it on good systems I fear may cause more harm then good. So anyone have a good solution for htis or a wokr around for the affect systems to be able to back them up? Thanks for any suggetions.
MacLEOD
16 years ago Place Backup Exec
24KViews
0likes
12Comments
A failure occurred querying the Writer status.
Dear all, Since some weeks I have been experiencing this horrible error. I have consulted the Symantec Support pages, but I can find no 'permanent' solution for the environment I am using. Rebooting the server every day is not an option, this is the fileserver that people access remotely almost nearly 24/7. It also doesn't seem to work, the first one or two backups after a reboot work but then it just goes back into the error listen in this threads topic. There is also a suggestion about freeing more space on C:\, I think there is enough (see below). My backup server is Windows Server 2008 R2 Standard. It's fully up to date up with the most recent Windows Updates. This is a physical server. The server I am having trouble with is Windows Server 2012 Standard. It's fully up to date up with the most recent Windows Updates. This is also a physical server. It has a C:\ drive with 125GB free of 150GB It has a D:\ drive with 1.6TB free of 1.6TB It has an E:\ drive with 2.2TB free of 5.5TB I have attached a screenshot showing the amount of times this server won't backup properly because of the above error. The worst thing about it is because I am backup up such an immense amoutn of data it takes about 25-30 hours to do a full backup. But it doesn't go into error until it's completely done! How can it POSSIBLY give a Writer error status at the very end of the backup process!! How is that even possible? The writer error is about failing to make a snapshot, why does it not INSTANTLY see that theres a problem and goes into error, why do I have to wait for 30 hours in anticipation to see if the backup software does why I purchased it. I have 53 servers to backup which takes me over four days, if my fileserver goes into error my entire backup schedule for that week goes out the window. This is becoming increasingly annoying.I don't want to have to come in on weekends because the backup software andomly decides it doesn't want to work. I'd like to add that my Exchange server also experiences this problem, except not that often. It's just as annoying though as you can understand that if my fileserver gets used 24/7 the Exchange server can't exactly get a daily reboot either. It's even more of a pita to reboot. All my other servers never have any problems, physical or virtual. Hyper-V or V-Sphere. It just works. Please advise. Thanks
Solved
Notlupus
11 years ago Place Backup Exec
17KViews
1like
7Comments
Physical volume library drive or Robot paused, offline or disabled
Hi all, I had opened up the magzine of the autoloader and replace the tape manually. After that, I encountered the error whenever I tried to bring the robotic library online and which I swop back to the original tape. Now, how do I resolved this and what would be the correct procedures to replace the tape from the autoloader using BE2012? Regards, Qingyan
Solved
Qingyan_Lim
11 years ago Place Backup Exec
15KViews
3likes
8Comments
Backup Exec log files 38GB
We've had an issue with our server due to lack of free space. We've examined the contents of the drive and "C:\Program Files\Symantec\Backup Exec\Logs\" is taking up 38GB of space. Can you tell me why it would take up this much space please? More importantly how do i cap it at say 10GB? We are using Backup Exec 2010 R3 on a windows 2007 sbs server. All our backups are backup to disk folders on removable drives and we backup also backup exchange and SQL. Thanks, your help is appreciated Thanks
Solved
resolver101
13 years ago Place Backup Exec
12KViews
1like
4Comments
Connection not established
I am constantly getting the above message. I Have checked all the services are running using the same account name with no issue. I have created a default logon account using the same credentials as the services are using That account is both local admin and in the backup accounts group
Solved
GEA_Paul
11 years ago Place Backup Exec
11KViews
2likes
11Comments
Backup jobs Hängen "In der Warteschlange"
Hallo, habe ein mittelschweres Problem... Egal ob Inventarisierung oder Auswerfen eines Bandes die Jobs bleiben immer mit Auftragsstatus "In der Warteschlange" hängen... habe schon die DB reorganisiert bla... ALLES was das BEutility halt machen kann... jobs gelöscht die noch geplant waren und nochmal versucht... anmeldekonto nochmal das Passwort eingetragen dienste neugestartet, Server neugestartet... Habe auch den Medienserver schon angehalten neugestartet... da bekomme ich ne Meldung: Der server kann icht angehalten werden und beim Starten dass er nicht wiederaufgenommen werden konnte... Habe dann auch das Bandlaufwerk aus BE entfernt und nochmal neu erkennen lassen und treiber nachinstalliert von SYM erst wenn ich die Dienste neustarte kassiere ich ne Fehlermeldung: E0008821 Ansonsten kann ich sagen: Windows 2003 Server 32bit Full Patched Backup Exec 12.5 for Windows Full Patched... Im Oktober bzw. November lief alles absolut einwandfrei... Ich wäre sehr dankbar für tipps!
Solved
Matthias_Hiller
14 years ago Place Backup Exec
10KViews
1like
8Comments
Backups failing - "Ready; No idle devices are available"
All of a sudden, Backup Exec 2012 is not running most of my jobs. The job status stays at"Ready; No idle devices are available" It ran 2 of the backups but I'm not sure why it didn't run the others. I have 2 drives, but it would only use one at a time. Both initially have a status of 'Online.' When I was able to get one of my backup jobs running, it would load into one drive, that status would change to 'Active.' Then, if I try to run another job, the other drive will change to 'Active' for a moment, then go back to 'Online' and the job status goes to"Ready; No idle devices are available" These are the things I've tried: Shutting down and restarting the server and the backup device Restarting the Backup Exec services Pausing and unpausing the backup drives What else can I try?
grahwong
11 years ago Place Backup Exec
8.6KViews
1like
6Comments
Differences in Catalog and Inventory
I am new to using Backup Exec and I'm trying to understand the differences in catalog and inventory. I inserted new tapes into a tape library and ran an inventory job. This showed all my media and under media description it shows "blank media". When would you run a catalog job? What are they used for? Is it necessary to run when new media is inserted? Thanks in advance,
Solved
Crazy_Excalibur
13 years ago Place Backup Exec
7.7KViews
1like
4Comments
Backup Exec 2010 R3 download
Where do i get the latest download for BackupExec 2010 R3? Thanks
Solved
ThaveshinP
14 years ago Place Backup Exec
7.6KViews
1like
2Comments
How to Format or Erase a tape (Backup Exec 10d)
How can I wipe a tape? If I try to use the the Long Erase, Quick Erase or Format option via Device and Media Operations the options are always greyed out.
Skinjob
16 years ago Place Backup Exec
7.3KViews
1like
6Comments