Recent Discussions
Simple Licensing Model - very early License Warnings
Hi all, there is one thing about the simple licensing model for Backup Exec, that annoys me more and more with each day passing :-) Imagine the following: A customer has licenses to backup 6 Instances. On the Backup Exec dashboard he has this kind of meter that shows him: You are backing up 5 of 6 licensed Instance at the moment. Starting at using 3 or 4 instances of the 6 instances that he has licensed, he is getting a warning (!) in Backup Exec every day that he is nearing the lincensed limit. A warning in yellow and with the little house symbol on the dahboard page in red if not acknowledged. And this warning is not even able to be caknowledged automatically ( I had a support call open for this and the support engineer was puzzled about this himself). I understand that with the simple licensing model the topic of underlicensing becomes a problem very quickly and mercylessly (because after 30 days underlicensing it just stops backing up any instance that is not licensed) ...but people: a warning every day while the customer ist still safely within his licensed limits. Veritas got to be kidding me :-) I saw yesterday, that this is still the case with BE 24.... I cannot be the only person that is extremely annoyed by this?Tim_Frodermann5 days agoLevel 318Views0likes0Commentskeine Koplettsicherung eines Servers möglich
Dieser Server läuft als virtuelleMaschine auf Proxmox, wie die meisten anderen auch. Per Agent soll eine Gesamtsicherung er:stellt werden. Erfolglos Im Auftragsprotokoll finde ich dann das: Auftrag beendet am Samstag, 19. Oktober 2024 um 03:25:43 Abschlussstatus: Fehlgeschlagen Endgültiger Fehler: 0xe000848f - Nicht genügend Speicherplatz. Endgültige Fehlerkategorie: Ressourcenfehler Zusätzliche Informationen zu diesem Fehler finden Sie unter der Verknüpfung V-79-57344-33935 Unter dieser Nummer finde ich keinen Eintrag: Und im Abschnitt 'Überprüfen / Fehler' finde ich das: Überprüfen- \\seth.em-da.lokal\System?State Daten für \\seth.em-da.lokal\System?State\System Files\System Files sind beschädigt. Daten für \\seth.em-da.lokal\System?State\SYSVOL\SYSVOL\SYSVOL Share sind beschädigt. Daten für \\seth.em-da.lokal\System?State\_SharedHardlinkData_\dc206d76.10000.5980 sind beschädigt. Daten für \\seth.em-da.lokal\System?State\_SharedHardlinkData_\dc206d76.10000.5a27 sind beschädigt. Daten für \\seth.em-da.lokal\System?State\_SharedHardlinkData_\dc206d76.10000.5a79 sind beschädigt. Daten für \\seth.em-da.lokal\System?State\_SharedHardlinkData_\dc206d76.10000.5a8d sind beschädigt. Daten für \\seth.em-da.lokal\System?State\_SharedHardlinkData_\dc206d76.10000.5b34 sind beschädigt. Daten für \\seth.em-da.lokal\System?State\_SharedHardlinkData_\dc206d76.10000.5f24 sind beschädigt. Daten für \\seth.em-da.lokal\System?State\_SharedHardlinkData_\dc206d76.10000.5f58 sind beschädigt. Daten für \\seth.em-da.lokal\System?State\_SharedHardlinkData_\dc206d76.10000.6026 sind beschädigt. . . . In den Settings sind Speicher eingetragen, die wirklich ausreichend freien Speicher haben. Der Registryeintrag HKLM\SOFTWARE\Veritas\Backup Exec For Windows\Backup Exec\Engine\Misc\ 'BescLargeDiscBlock' ist auf 110 gesetzt. Was / wo ist ..\System?State\_SharedHardlinkData_\.. ? Was sind Shared Hardlinks? Vor allen Dingen liest sich das so, als ob er die Sicherung schon gemacht hat, aber bei der Überpüfung Probleme hat. Wie kann ich das lösen? MfGFred105 days agoLevel 325Views0likes5CommentsCannot establish connection to local host
Hello, I have a BE instance that only backs up drives on the localhost that it is running on. It is a Windows Server 2016. I noticed that the one backup job was failing and when I tried to look at the details of the job, the server information would never load. I was unable to test credentials or even see what drives were configured to be backed up because nothing would load. I started troubleshooting and got to the point where I decided to uninstall and try a fresh install. I was able to complete the new install, but the software again cannot connect to the localhost, This time, int he Backup and Restore section, I see the server, but it shows a status of "Connection not established". When I try to establish the connection, I get error "Communication with the server times out on the call 'RetryResourceContainerConnection'. I have tried everything I can think of to solve this issue. Any ideas would be appreciated!sjc675 days agoLevel 215Views0likes2CommentsUpdating BE to ver 24-Firewall white list
Our internal network has blocked all internet except through a whitelist. I need a listing of what sites to open up so the internal BE server can "reach" the update server at Veritas and update itself. Support has been less than useful. (that's very kind) They keep giving me ports to open for backup jobs but that's LOL not what I"m doing. I just need the internel BE server to get to the BE Cloud device/server so I can update the program. Does anyone have any idea what I whitelist. Firewall traces are rather cumbersome and I've found no KB articles of any use. The product works fine I just NEED to update it.jstrowe7 days agoLevel 317Views0likes1CommentSlow File Transfer Speeds in Veritas Backup Exec Job Rate
Hello everyone, I’ve been experiencing a noticeable slowdown in the job rate when using Veritas Backup Exec version 24 to back up data to disk. Initially, the backup job starts with a good transfer speed, but over time, it gradually slows down to around 10 MB/s. Has anyone else encountered this issue, or does anyone have suggestions on what could be causing this? I’ve checked the basics like disk space, network performance, and hardware, but I’m not sure why the speed deteriorates so much as the job progresses. Any insights or troubleshooting tips would be greatly appreciated! Thanks in advance!17Views0likes1Comment- 8Views0likes1Comment
Report Configuration
Unable to get daily, weekly report as per our requirement. The details is already populated in Alerts & Job History. If its possible, please help if not take the same as a future enhancements. Required Details in Report. Job Started, Job Ended, Job Name, Job Backup Method, Drive Name, Media Label, Byte Count, Job Rate. Awaiting for some positive feedback. Regards, Shiju ChackoShiju_Chacko9 days agoLevel 47Views0likes1CommentMSSQL 2008 server suddenly stopped backing up
MSSQL 2008 server suddenly stopped backing up.There are two database, they back up in the same (14:00) time, backup first database was successful, second no. After that moment both database have not backed up, in bpcd I didn't fount anything useful. where to find the problem?aleks_rov9 days agoLevel 21.1KViews0likes4CommentsHandbuch
Ich suche folgendes: deutsches Handbuch auf Seite 40 Auf der Registerkarte "Startseite" werden Statistiken für Ihre gesamte Backup Exec-Umgebung angezeigt. Mithilfe der Ansicht "Server" können Sie den Backup-Status aller Computer in Ihrem Netzwerk überwachen. Ich sehe hier nicht, das ich da eine Ansicht "Server" wählen könnte. Wo ist das? MfGFred1014 days agoLevel 37Views0likes0Comments