Recent Discussions
monthly report possible?
How do I define the filters if I want a monthly report on all successful orders? First I have 'Start time was accessed IN LAST 31 days' and linked it with AND with 'Order status = Completed (successful)'. But then I get a report in which the same order is listed again and again every second. No, I only want one line per order. My field definition: Start time, order name, total size of data, order duration, order status, error code, error category, error text. Please remember that a month sometimes has 30 days and sometimes 31 days.
Tape is not appendable despite having alot of free space available.
I am new to BackupExec but we are running into an issue with our tapes. We have a few servers doing a full backup to disk once a week, then the full backup gets duplicated to tape. When the Duplicate job comes up, it prompts to insert over writable media instead of just appending to the existing tape. So far only 2.4TB is used of 8TB available however, it will not append. The OPP is set to one year and the APP is set to Infinite allow append. So I don't know what would be blocking the append. Do the disk backups have to be in the same media set as the tape backups? Currently, backups on the disk are only protected for 1 week whereas they are protected for 1 year on tape. Let me know if there is more info needed.
Manual DR of Backup Exec Server - Backup files
Hello Team, Backup Exec Version: 16 OS: Windows Server 12 R2 Some reason my backup exec server got corrupted and lost. However, I have the access to the backup files B2D. I tried below but not working. Created new server with the OS 2012 r2 Installed Backup Exec 16 Created new B2D and copied the files from old B2D. Ran the Inventory job successfully but, catalog job failed with the above error message. V-79-57344-33994 - The data being read from the media is inconsistent. Appreciate for any recommendations or suggestions. I have a test lab, ready to perform any work around. Thanks, Durgarao
outdated powershell modules and little functionality
Already more than 10 years ago there were requests to control Backup Exec by Powershell. I get the impression that Veritas makes no effort to optimize BMECLI. Even simple functions are still not implemented, the module is from 2021. New functions are constantly being added to the application, but much remains the same. Bugs that were already included in 2022 are present in 2023 and 2024. Duplication of backup sets from a given time-range is not possible by GUI, powershell or other way. It seems to me that we are riding a dead horse but haven't realized it yet.Any plans to Filter Storage based Backup Sets
Is there any plan to make the Filter available in Disk Storage Detaiks / Backup Sets. I would like to filter for a time range, select all Backup Sets and duplicate them to tape. I tink this is a feature, that most database application, excel or other cheap solution could do in 2024. It would be awesome, if there would be an option for a duplicate job with all data within a time range... It looks like we will never have a usable application here, just more and more new features and functions. But something useful for once ... no, that's probably not going to happen."Duplicate Disk Based Backups from a given time range"
It been 3 year now, that i asked for simple feature ... Hi, i remember that Veritas promised in the past (i think it was around 2014), that in an upcoming Release, it would be able to ... "Take all Backup to Disc Data from a given time range (like once a day or week) and duplicate these data to a single cartrige in a single load/unload job? I still remeber the days, when we had a single job to backup all kind of servers and data in a single run and duplicate this data to tape. Then we needed to create a single Job for a single server and duplicate these data to a tape. So shoe shining begins again with the library, the library loads/unloads a cartridge for a single job and performance drops. Is it not possible for a database system, to get all backups2disc from a given time range and backup these in a single run? Any ideas for 2025 ? Jürgen
BE16 crashing after .NET 4.8 update but no access to entitlement information to download fix
Frustrating issue because we find ourselves between a rock and a hard place: We inherited our client from their previous IT provider who upped and disappeared overnight, without contact. We've managed via whatever written records they had on hand, with minimal issues so far. However a recent Exchange update required .NET Framework 4.8 be installed and as a result the Backup Exec console now crashes on startup whenever we attempt to load it. I did some quick digging online and found this is a known issue with a known hotfix. Unfortunately the hotfix cannot be downloaded without logging into our Veritas account with entitlements, and there's the rub: we don't have one. We located an account that had been setup, but it has no products attached to it. And we have no other records that we can locate. Our assumption is this may have been tied to the previous IT provider's own accounts instead. I called Veritas support, but they couldn't find record of the client's company name. They attempted to get information from the server, but to do so they have to open the Console, which is the entire reason we're in this mess. They have no solutions other than to come here and ask for advice. And so I do. Is there any way to pull our entitlement information from a file on the system so we can get the support we need to download this hotfix? Or any other workarounds we could consider? Thank you.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?keine 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? MfG
