Recent Discussions
Hyper-V VMs get hosed after backup
"Hosed" being the technical term. It seems that after either/or of 2 VMs on the host machine, after a backup, cannot start. It also appears that Backup Exec creates snapshots that don't get re-absorbed into the parent virtual disk. So I'll end up with a series of .avhdx's, and if I try to start that VM, it'll tell me there's an ID mismatch in the chain of virtual disks. Pretty much every single time after a backup. The exact error is: 'VSERVER' failed to start. Synthetic SCSI controller (Instance ID XXXXX): Failed to Power on with Error 'The chain of virtual hard disks is corrupted. There is a mismatch in the identifiers of the parent virtual hard disk and differencing disk'. There is a fix, using the Set-VHD command, but I can't keep doing that over and over again. Additionally, I'll get this error from Backup Exec itself: V-79-40960-38691 - Backup Exec cannot create a recovery checkpoint for the 'VSERVER' virtual machine. (Note: "Use snapshot technology" is checked). Any ideas where I can start looking to fix this? Backup Exec version 21.4, 1200.2536, Windows Server 2019 Thanks!Cannot mount the windows PE image (SDR creation)
I'm trying to create a new simplified disaster recovery (SDR) disk (on 2 machines, actually). I get the error, "cannot mount the windows PE image. You may have insufficient privileges for the storage location C:\Users\<account>\AppData\Local\Temp\SDRStaging" I'm even running Backup Exec logged in as the service account we use for Backup Exec, and I'm running BE as an admin. Thoughts? Server 1: BE Version 16.0, 1142.1659, Windows Server 2016 Server 2: BE Version 20.6, 1188.2718, Windows Server 2016
Updating 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.
Duplicate existing backup set to tape automation.
Hello I have been playing around with duplicate to tape jobs lately and realized this issue: It is not possible to start multiple duplicate jobs and expect them to be queued awaiting a vacant tape drive with an appendable media loaded. I have only one LTO8 available in total, with no plans to aquire another due to budget. I have set up a backup job per server to run full backups to disks during the weekend. This gives me about 5 TB of backupfiles to be duplicated to tape during the week and fits nicely on one LTO8 tape cartridge. I currently have to run each duplication job with enough time between the jobs to have an available tapedrive ready when the next duplicate job starts. Othervise the job will fail with an error message like; No writable idle devices are available. Is there someone out there with similar setup? Any ideas are appreciated. Veritas can perhaps adjust the duplicate jobs feature to be "queued" to improve automation of the duplication sequence. Best regards from ArildCannot update Backup Exec (Error 1723 with installer package)
I'm trying to run Veritas Update for the latest hotfix available for my edition of Backup Exec (version 21.4, 1200.2536), and I get this: "Error 1723. There is a problem with this windows Installer package. A DLL required for this install to complete could not be run." Thanks!
Problem - Ready; Backup Exec server not available
Hello there, I am duplicating old L6 tapes to L8 tapes for a few weeks without any issues. Few days ago I've prepared new duplication job and it's holding on status "Ready; Backup Exec server not available". I don't know what happened. I tried to re inventory tape, re catalog tape, restarting server - nothing help. I can see that some backup sets can be duplicated and some (most) showing mentioned error. I' am also adding screenshot. I hope someone met this problem and could help. Greetings, DamianBE16 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.BE failed to register recently-restored VM
I tried to restore a Hyper-V VM early this morning; and though the files were apparently restored, Backup Exec threw this error: Final error: 0xe0009645 - Backup Exec failed to register the virtual machine. See the job log and the Windows Event Viewer for more details. The virtual machine will not be available in the Hyper-V or Virtual Server Administration Console. The Windows Event Log shows this: An account failed to log on. Subject: Security ID: SYSTEM Account Name: SERVER$ Account Domain: DOMAIN Logon ID: 0x3E7 Logon Type: 5 Account For Which Logon Failed: Security ID: NULL SID Account Name: FE02C21F-063E-4593-831F-C10A3C52D958 Account Domain: NT VIRTUAL MACHINE Failure Information: Failure Reason: The user has not been granted the requested logon type at this machine. Status: 0xC000015B Sub Status: 0x0 I should note I had to restore a virtual machine before this one with zero problems. This 2nd one didn't want to restore properly for some reason. Using BE "Silver Perpetual" Version 21.4 on Windows Server 2019 Thanks!
