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.
Why is my backup-to-disk-folder offline?
We are using a backup-to-disk-storage on a NAS-share which has been working since a long time A couple of days ago this storage went offline and is still offline. Whenever I try to online it, it takes a couple of minutes, then an error message comes which is not helping me. - I can access the CIFS-share with the account BackupExec is using - I can read files and make new files. The error message says the typical reason is that the B2D-folder was deleted, o r the share is no more available. I think I tested this and there is no problem. Alos, my attempts to import this share in a new storage fail. The error message says there is no B2D-folder which can be imported. Can some one help?
Backupexec always does 'verify' step even when disabled...
I have disabled 'verify' for the job defaults of every type. When starting a job I also double-check that the 'verify' step is disabled. We are writing to an AWS Tape Gateway appliance, so Backupexec sees it as any other tape drive, but we do not need this step. What am I missing?
Inaccurate disk storage
Hi All, Anyone can help me figure out or resolve the issue? We have network storage (10TB free/50TB) after deleting the old backup with that we can at least have the space available. but in the BE console shows (46.5TB used/50TB). and that is not accurate to our original capacity which is (10TB free/50TB). It might also cause a failed backup and it turns out to offline status because it is already full. Is there any resolution that might help us to resolve this? Thank you in advance.Veritas Backup Exec Job Failures (network unstable)
Hi, Is there any way to improve reliability of backups on slow/unstable/wide networks? I have a Veritas BE in the cloud that pulls backups from multiple sites around the world and saves them to S3 bucket. Some of these backups could be up to 200-300 GB and take several hours (up to 24) to complete. Quite often they end up failing after several hours with error codes like E00084F8, E000848C,E00084EC. Most likely there could be some occasional network issues, which is not unexpected if the backup runs for such a long time. The question is: are there any settings or configs in Veritas BE that I can use to improve reliability? Maybe some better buffering, etc.?Veritas Backup Exec and Hyper-V VM's
Hi all, I hope someone can help me clarify this. I have a Hyper-V hosts with several VM's on it. I am backing them all up using Veritas Backup Exec v22. What I am unsure of is the correct way to sele/deselect vhdx files to a) ensure a proper backup that can be used to restore the VM; b) avoid duplicating very large amount of data. My VM <xxxx03> has 2 HDD's definined (hence 2 hhdx files). Within the VM I have disks C: and D: defined using their separate vhdx files. When I select my VM to be backed up under Microsoft Hyper-V -> Virtual Machines, it shows me both vhdx files. LEt's say I want top backup the entire VM and both disks. I suspect I check all the boxes here. So far, all clear. But then I realise that both these vhdx files (and some extra) are also shown under my Hyper-V host itself (drive E:). So, do I also need to check all everything in here? Or will it double the size of the backup?
Full server Restore Fails
I have a Production server (HP ProLiant DL360 G9, RAID 50, 2.1TB SAS, Windows Server 2016 Standard, Sql Server 2017 Standard) and I try to use SDR to restore this to another Backup Server (HP ProLiant DL360 G9, RAID 50, 3.9TB SAS), My backup medium is a Quantum LTO-4 tape drive attached to the production server. I have ensured that my backup has the Simplified Disaster Recovery status and downloaded the SDR disc from the "Configuration and Settings > Create Disaster Recovery Disc" menu, When I use the disc, it connects to my network, finds the backup exec server, identifies the SDR backup and then begins the restore smoothly without issue, When the restore finishes and I go to reboot the Restored server, it gets through the UEFI BIOS stage and then shows "No bootable device found", I have tried the restore twice, once allowing the software to configure the storage leaving roughly 1.8TB unconfigured and once reconfiguring the storage manually to make use of the whole disk. On further inspection using the SDR disc and DiskPart I find that the drives are not set as bootable and the boot and system sectors do not show as boot or system as they do in diskpart on the production server. When booting with a Windows Server 2016 disc and attempting BOOTREC /FixMBR, /FixBoot and /RebuildBCD nothing happens and /RebuildBCD shows "Operating systems found:0" I have attached the SDR logs from the restore of the server and some images of the not bootable and diskpart. I've updated the ADK to the right version, Updated backup exec to version 22.2 and made a backup and sdr disc from 22.2, tried with a different USB and nothing seems to work, I have been on case with Veritas support since 29th February 2024 and they just keep asking me if the SDR disc boots and consistently trying to downgrade the case severity (I now realise after 12 years that backup exec wont restore my servers quite scary for me). I once had similar issues with the support and found someone who could help in the forums, so hoping that lightning strikes twiceNewb's question first time restoring in Backup Exec 20.4
When I select the backup set that I want to restore and then hover my mouse over the 'Restore' function, it reads 'Browse the backup set and then restore the data.'. If I then click on 'Restore', is there a subsequent window where I get to select the specific folder(s) I want to restore or does it automatically restore the entire backup set? I'm hoping it's the former as I don't want to overwrite all my current data. Thanks.
