Veritas Backup Exec version upgrade & migrate to another new Server
Hello, We need to upgrade our Veritas Backup Exec version from 16 to latest compitable version as per hardware support in existing Server having OS is Windows Server 2008 R2 Standard, then need to migrate the same to new Server hardware with Windows Server 2022 Standard. Please help us to do the same. Thanks & Regards, Soumabrata Bhaumik
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?
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.
Cannot obtain settings for the Agent For Windows publishing from the registry
Hello. Our Backup Exec version 16 is running on a Windows Server 2016. We are unable to upgrade it because we run a software on one server that can only be supported on Windows Server 2003. The Windows 2003 server was suddenly not backing up properly. Restart did not work and I reinstalled the agent. Now when I try to install it, it does not show up in my backup exec because you need to enable publishing in the Agent on the 2003 server. However, when I try to do that by going to the publishing tab, I get an error message "Cannot obtain settings for the Agent For Windows publishing from the registry". It then goes to the tab but the checkmark is greyed out. I also noticed the Backup Exec Agent for Windows service is stopped. It automatically closes if you try to start it saying it closes it if the service is not in use. I have tried both installing the agent manually and pushing from the backup exec server. It installs fine but you cannot enable the publishing. I also tried deleting every backup exec file, folder, and registry key I could find to fully reset it before reinstalling. Other servers work fine. How can i fix this? Please let me know. Thank you.
Auto Generated Document Backup Get .PST
Hello! Backup Exec user here. Loooooooong time user from back in the Ghost days! :)) I'm using it pretty outdated version, 16! However, the software is so solidly made I still haven't gone ahead and got a new one. Mostly that's just as I'm trying to save money. And, really, it's just so reliable. It does everything you need. That's a testimony to how well made it is. I've just started doing a document backup using the pre-programmed settings. Here to four I'd always just done a full backup, only because I thought that was easier? But now, to try to economize even further On service base, i've decided to go with the pre-programmed setting where it allows us to back up the whole computer twice a week, and the documents every day. There was one setting in that pre-programmed documents menu that confused me a bit. It's about email files. Please take a look at this image: Among the choices it shows for email files are .dbx, .eml, .msg, .nws, .ost... After that OST there's just an ellipsis. That ellipsis is making me a little scared! You see, I still have a lot of very important email files that are .PST And, I believe that even my outlook is still using .PST? So, put another way, if the checkbox for email files does not include .PST .Files, that won't be much help for me. Please can anyone confirm with a bit of documentation? Sorry about the age of the software, but I'm just an academic and I'm trying to save every penny I can. :D Veritas 16. Sincerely, Cal
Failed Status - V-79-57344-4611
We are experiencing an issue with our VMWare backups writing to the deduplication storage. Other file level backups complete to the same deduplication storage without issue. Some files and folders were copied from another drive to the deduplication drive when the other drive was full. Those files and folders have since been moved but the VM backups continue to fail. I have ensured that the virus software is not scanning the deduplication drive and that indexing is turned off. Any other ideals on how to resolve this issue while maintaining the current backups on the deduplication drive? Job Completed Status Completed status: Failed Final error: 0xe0001203 - An error occurred while creating or accessing the directory specified for this operation. Check to make sure that the B2D folder and/or the temporary path specified for this operation are valid. Final error category: Resource Errors For additional information regarding this error refer to link V-79-57344-4611 Errors V-79-57344-4611 - An error occurred creating or accessing the directory \\.pdvfs\SERVER\2\BEData\STHVMDK specified for this operation. Ensure that the directory is accessible and can be written to.Veritas Backup Exec 16 Unintall Removes the SQL DB and kills other software that share SQL.
Hello, Is there any way to uninstall Backup Exec 16 without uninstalling the DB? This server has multiple programs that have SQL database. When uninstalling Backup Exec, it Uninstalls the SQL and kills other programs. Is there a special uninstaller or some work around that i can use to ONLY remove backup exec?
Remove VM from old version
Hi Guys; I would like to know, how I can proceed to remove the Virtual Machine from the old Backup exec version. We don’t need more backups from this VM, and then we decided to remove it, but we are not sure if the procedure attached is correct. Could help to clarify the issue? Thank you in advance for your collaboration Regards RC
