Restore Jobs start but stall, don't complete, or complete with lower job rate than previous restores
Most of the times recent attempted restores will start but will stall and require me to cancel them. I did one test restore last night that took about 29 minutes for one file at a rate of 1.00 MB/min. Currently I have one job that went to 99% complete and is just sitting there for almost two hours. Job Rate continues to decline the longer it sits. Previous restore about 30 days ago was with speed of 264.00 MB/min What could have caused this sudden slow down and how to I fix this? Any help is super appreciated.Restore from Tape when you don't have access to the source server
I am trying to restore from a completed tape backup from a server that is currently dead. I have made the selection from the media, but it points to Resource Credential from the dead server. Is there a way to restore some of the data from that tapes and remove that Resource Credential requirement?
Windows Registry Keys for Publishing Remote Agent for Windows following upgrade
I recently upgraded from 2014 to 20.6 and most everything went well. I found out that the CAS setup couldn't be migrated (SQL issue) so we had to manually add servers and recreate the jobs. The only real issue that I have encountered is that I have one Windows 7 Pro 32-bit client that following the update to the Remote Agent for Windows pops a "Cannot obtain settings for the Agent for Windows publishing from the registry." I was able to find the registry key that had the old server settings HKEY_LOCAL_MACHINE\Software\Symantec\Backup Exec For Windows\Backup Exec\Engine\Agents\Agent Directory List and modified this to include the new servers. It still popped the publishing error. I uninstalled the agent, reinstalled it both via push and manually, but I cannot get the publishing to pull from the registry. I compared the registry to a successful 64-bit upgrade and found several missing keys. I input the keys that I could (Remote machine ID for %computername% I figure is from the server once trust is established). The server installs on the BE server but does not connect nor does it establish trust. This is my only 32-bit Windows 7 Pro system, so I'm wondering if this is a 32-bit issue only. Does anyone have any advice or input?My computer caught fire…
I was advised to repost this topic here by Symantec... All I have got left is the external drive, (USB, 1000 GB), containing the backups. I wasn't unduly worried – after all this is why you have backups isn't it? The computer was fairly old and had two IDE drives with Windows 7 and a matching motherboard with an older type of RAM. The backup was made with Ghost 12 – I had no idea that it had become obsolete. I bought a new computer with two SATA drives. Apparently IDE drives and matching motherboards boards are no longer made. I booted from the SRD but the machine couldn't see the USB drive. I installed Windows 7 and then it could see the USB drive when I booted from the SRD. I told to restore the C drive after which it wouldn't boot from the drive. I subsequently chatted with Symantec support who told me that if I installed the appropriate Ghost application on the new machine it would be possible to restore from my USB drive. The agent insisted that in the whole of Symantec there was not a single remaining copy of any version of ghost… I managed to find a "Try and buy" copy of Ghost 15. Will this work? If not what can I do? The chatline agent did not know the answer to these questions and referred me to this forum. DavidUnable to open a disk of the virtual machine.
Hi, I have installed backupexec on a physical server I have added my esxi host and installed VMware Now i have a strange problem when i want to restore backups that given from other vm on this esxi host appear this error: The job failed with the following error: Unable to open a disk of the virtual machine. I have realy confused what do i have to do ? All of the best porn in one place https://collectionofbestporn.pro
DLO Agent Uninstall
We had an older version of Backup Exec (12.5 I believe) that we no longer use. Some of the clients that were using the DLO agent to be backed up still have it installed. We decommissioned the server running the main BE software some time ago. Without the server the install point for the DLO agent is no longer there. How can we uninstall the agent from the clients without having to reinstall BE on a server and setup our enviroment again? When I try to uninstall from a client it is asking for the DLO agent .msi file. Can that file be downloaded or can I get it off one of the 12.5 DVDs?
26 hours remaining
Hello all. I've been using SSR 2013 for years to do a nightly image of my Win 7 machine to a secondary internal hard drive. It usually takes a little over an hour for a full image. The other day I woke up in the morning, and the backup was still running, with an estimate of 23-26 hours. After rebooting and trying again with the same results, I uninstalled SSR and installed VSR 21, and started a backup to a new destination folder. Same thing, 26 hours remaining. The primary drive is a Samsung EVO 1 TB SSD. Backup is a Seagate 6 TB HDD (3 months old). No performance problems otherwise. I recently installed OneDrive which I haven't used before, so I thought that might be related, but I've since removed it. Has anyone seen anything like this?Veritas System Recovery Installation
Hi. When i tried to install Veritas System Recovery Version 18 in my historian Server. I encounter some error. After certain part, the Veritas installation dialog box hang and the installation just stuck at one point. When i tried to click on Cancel to cancel the installation, the installation dialog box cannot be cancelled. The x button on the top right of the dialog box also cannot be clicked. I will attach photos and videos of which the installation process get stuck and hang. Thank you so much.