Recent Discussions
All I want to do is buy a licence (PART TWO!)
I previously posted here about the difficulties of buying a licence in the UK, especially for individual users. https://vox.veritas.com/t5/System-Recovery/All-I-want-to-do-is-buy-a-licence/td-p/903155 I've was told back in January that Veritas is working on a solution and I was sent a temporary slf licence file until things can be sorted out and I can actually buy one. Well VSR 23 is now warning me that my licence will expire in 57 days from now and I'm STILL waiting for an answer from Veritas. CAN SOMEONE PLEASE HELP AND TELL ME THE SITUATION. WHEN WILL I BE ABLE TO BUY A LICENCE? Thanks
Problems Installa Testversion System Recovery
Hello, i will test the Veritas System Recory n on Windows Server 2022 and it wont work. I download the Instalaltion Files of the Version 23. Then i try to start the Installation. In the Explorer i chosse start the Installation the Installation start with files will copy.. then the window got closed by itself and the installation is aborted. Then i try the installation with this Manual https://www.veritas.com/support/en_US/article.100060200The instalaltion was working now. But itdisplay me some error message during the installtion. After the Installation i cant run Veritas System Recovery. A lot of Error Messages. VQA tells me its not working on Windows Server 2022 and i see the Version 21 and not 23. I cant understand, its weird. i am a little bit shoked, it just to try a Testversion and a lot happend wrong. Thank you and Greetings RaphaelIssue with Veritas System Recovery 22 and Windows Server, see my Description
Hi, I have a Windows Server 2022 and install Veritas System Recovery 22 on it. We have some users that can connect per Remote Desktop to that Windows Server. Every Time if the user log in on it, getting the following message: "The current user 'DOMAINNAME\USERNAME' has read-only privileges and cannot make administrative changes. Would you like to add privileges for full control? Click No to continue in read-only mode." Is there any way to disable it or hide it for all the users? RegardsVeritas System Recovery Manager 22 issue
Hi, I have installed Veritas System Recovery Manager 22 and add some Computer to monitor these. Some machine does not join domain. It means I have to add Computer wiht local administrator. I have created on the machine which has not joined the domain a local user named "backup" add it to Administrator right. But with that user "backup" cannot connect to the Agent If I add the Computer with Default Administrator, I can connect to the Agent. Where and how can I add the user "backup" to be able to connect to the agent? Regards
SSR 2011 won't boot after Upgrade to Win 10 from Win 7,
I was happily running Win 7, with the normal upgrades, since 2012 when I got my Dell Precision Tower. But, I was now looking for a software upgrade for my new printer and foolishly believed MS who wrote that all my software and hardware would work under Win 10. The online upgrade to Win 10 from the MS website was smooth, except I lost all use of more than $5,000 of music hardware and software - checked discussions boards and found that no upgrades to Win 10 existed for these things.I went in to reverse back to my Win 7 just 3 days after the Win upgrade, which Win 10 promised to keep available for 10 days. Gone. Program stated that needed files had been erased. Fortunately, I thought, I had backed up my Win 7 C: drive with SSR 2011 before the so-called upgrade. I have SSR 2011 backups going as far back as 2012, and many in between. I have reinstalled from one or more of these quite a number of times with no issues. Now my SSR 2011 recovery disk won't boot. I downloaded from Dell my original (apparently not) Win 7 ISO and created a bootable USB. This did boot and did install a clean version of Win 7. But, my SSR 2011 disk still won't boot. I've run all the upgrades on this but still won't boot. I spoke with a friend who manages IT for a medium size corp, and he said the problem was, first, that the Dell ISO was not my original, that it was fully brought up-to-date., and, second, that my BIOS had been rewritten. If so, then I'd like to reinstall what I had before this disaster struck. My objective is get to something installed such that I can boot the SSR 2011 recovery disk and reinstall as everything was working just fine before I descended into the Win 10 flames. Any suggestions? Would a new retail Win 7 package with a product key take me back? Any suggestions about a BIOS flash program that would take it back? Thanks.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 twice.
Unable to select target disk in VSR23 bootable usb
I am having trouble selecting a target disk for recovery in VSR23 bootable usb. The disk is visible in the Veritas interface (a) and I can browse its contents, but the X drive(target disk) does not appear in the list of available targets when I try to create a recovery job (b).How can I resolve this issue? Environment: Veritas System Recovery 23 Windows 10 Target disk: Dell M.2 PCIe NVME Class 40 Solid State Drive - 512GB Thank you for your help.
