The requested FRS entry is unused
Hello all, I have been stuck on this for a while now with now solution and this problem, so far, has occurred only on one machine. When attempting to recover, in the last few seconds of the recovery I receive an error message: -Cannot copy data from the recovery point to the destination. --The requested FRS entry is unused (free, 0). (UMI:V-281-3215-1010) I was not able to find much help on the web either. Any help would be much appreciated. Symantec System Recovery 2011 Scenario: System A has a recover point created on our central storage. Hard drive of System A needs to be replaced I have the hard drive connected to my system and properly partitioned and attempting to recover using the SSR console note: I have successfully completed this exact same process a few times. This is the first failure.Solved1.5KViews0likes7CommentsSSR 2011 Symantec System Recovery Disk ISO download
I have SSR 2011 installed and would like to create a System Recovery disk, but i don't have the ISO. I know there's a download for that and I've seen a location for a 2013 version, but I assume I need a 2011 version. Where can I download one? Thanks, Rob13KViews1like15CommentsRestore fails with Error EA390013, copy drive fails also
I'm trying to replace my 160GB drive with a larger 250GB drive. I'm running version SSR 2011 Desktop 10.0.3.45857 on Win 7 x86 OS. I have only 2 Recovery points and bothe fail when I install the new drive and boot with the recovery disk of the same version mentioned above.It appears to be at the very end and "Error EA390013: At end of Something" comes up. When I scan the disk through anaylize it doesn't have any data restored mainly the Windows default folders, like Windows, Users - but only default and Public.Both rescovery points fail the same way. There never appeared to be anything wrong with the 160GB drive it is just getting close to full. So next I reinstalled the original 160GB drive and booted to it with the larger drive also installed. I rancopy drive but it too fails at 96% with -- "High Priority Error: Error EC8F17B3: Cannot complete copying of (C:\) drive. Error EC8F0409: Cannot copy source drive to destination location. Error EA390013: At end of something. 0xEA390013 (Symantec System Recovery) (UMI:V-281-3215-6067)" What do any of these errors mean?Too vague. I just ran Windows error checking on the 160GB drive, it found nothing. Is this error due to my 160GB source drive or is there something wrong with the new 250GB drive? Any help is appreciated.3.5KViews1like15CommentsSystem Recovery vs. Backup Exec
We have been using / recommending Backup Exec to our clients and are considering System Recovery instead. I found this in another post about this topic. Is everthing correct? Any other comments? Backupexec 2010 a. File based b. Can backup to tape c. Can restore individual email d. Can do bare metal restore to SAME/SIMILAR hardware e. easy to take tapes offsite BE System Recovery (BESR) a. image based b. cannot backup to tape c. cannot restore individual email (restore whole information store from image file) d. can do Hardware Independent Restore e. can be set to backup incremental every 15 mins with almost no impact on performance f. easily import image to VM in case of total failure (i.e. server room fire)4.1KViews3likes3CommentsSSR2011 sometimes delayed offsite - no error
Hi all, I have a strange problem. The situation is as followes: The fysical server runs a hyperV version of w2k8r2. The client is a SBS2011 standard There is always an USB drive connected to the fysycal server(in fact 2, that are being exchanged every week) Each drive has its own driveletter (R and S so that the devices keeps that drive letter) They are shared as \\hypervserver\R$ and \\hypervserver\S$ and are used as offsite copy! On the SBS2001 runs SSR 2011 (latest with all updates) and it runs a backup of the SBS machine on an internal drive K:\ (that drive is an virtual drive on the hyperv server). and to offsite network share mentioned before. I get an email when the backup startsand whenpartsare finnished For many years it ran smoothly until sometimes the offsitecopy was not made. When the backup ran at 0.15 at night it normally also created offsite copy directly after it. Every month when updates ran the server SBS 2011 needs to reboot. The last 3 month the backup runs on the local K:\ drive but no offsite copy after a reboot of one of the machines (hyperv or SBS). Very strange is that when I exchange the external drive, it does run offsite copyafter the backup is created. Last thursday I updated the servers and that night the same thing happened. I did NOT exchange the external drive and it took until saturday untill the offsite copy was triggered. Very strange. The server is not very busy so I do not think that is the cause. I already reset the backup three times. That is no solution! Problem keeps coming back. I do not see any errors.. Can somebody help me? I know that The VProSvc.exe (Backup Exec System Recovery Service) initiates the ftp Offsite Copy process. And that seems to run fine. ButI am not sure if that process also is used for SMB backup to a network share. Help is appriciated Thank you in advance R Stokhof765Views0likes0CommentsCareless Support for Installation of our System Recovery 2011- Bad Support
Dear All, Two months ago, we have opened a case with Veritas for upgrade of symantec management console from 7.1 V2 to 7.6 Version. Till date they have called us 100 times and every time they will tell that we are collecting the logs and escalating the case to the higher level. When SSR was under Symantec they were solveing any issue within hours not even days. I request the responsible manager or whoever he is to contact us immediatly to take correction action to solve our issue becasue we have a 3 years license agreement with Symantec and it seems there is no use of the renewal we made. hope speaking in public we give us a positive & quick response. please contact my netwrok engineer Faraz to solve this issue now. Faraz: 00966533618553 Hamza Sheikh Head of IT NAFCEL - Jeddah +966553232844679Views0likes3CommentsRecovery Points Not Available
I have had SSR 2011 running for well over a year, backing up to a drobo which is on line all the time, as well as several Buffalo NAS drives which are rotateded daily. This has been working fine until yesterday, when i received a notice that the drobo did not have enough space. When i came in and checked, drobo had about 4TB of free space, which was plenty of space to backup. Checking SSR, it is indicating that all Recovery Points are Unavailable. However, if i go to the Manage Backup destination, i can delete one, even though it indicates that it is unavailable. Can anyone assist. Thanks564Views0likes2CommentsSSR 2011 - VProConsole Error
Hi Community, wir versuchen es mal hier im Forum. Wir bekommen bei einem Kunden seit kurzer Zeit immer diese Fehlermeldung, wenn wir die Console starten wollen. Hier die Fehlermeldung: __________ Details Daten System.Collections.ListDictionaryInternal Innere Ausnahme Unbekannter Konfigurationsabschnitt "runtime". (C:\Program Files (x86)\Symantec\Symantec System Recovery\Console\VProConsole.exe.Config line 3) Meldung Das Konfigurationssystem konnte nicht initialisiert werden. Quelle System.Configuration Stapelverfolgung bei System.Configuration.ClientConfigurationSystem.EnsureInit(String configKey) bei System.Configuration.ClientConfigurationSystem.PrepareClientConfigSystem(String sectionName) bei System.Configuration.ClientConfigurationSystem.System.Configuration.Internal.IInternalConfigSystem.GetSection(String sectionName) bei System.Configuration.ConfigurationManager.GetSection(String sectionName) bei System.Configuration.PrivilegedConfigurationManager.GetSection(String sectionName) bei System.Diagnostics.DiagnosticsConfiguration.GetConfigSection() bei System.Diagnostics.DiagnosticsConfiguration.Initialize() bei System.Diagnostics.DiagnosticsConfiguration.get_IndentSize() bei System.Diagnostics.TraceInternal.InitializeSettings() bei System.Diagnostics.TraceInternal.get_Listeners() bei System.Diagnostics.Trace.get_Listeners() bei dotNetBase.TextLogger.StartListening() bei dotNetBase.TextLogger..ctor(TraceSwitch Switch, String AbsoluteLogFileName, Int32 MaximumLogFileSize) bei dotNetBase.TextLogger.InitInstance(TraceSwitch Switch, String AbsoluteLogFileName, Int32 MaximumLogFileSize) bei Symantec.VPro.VProUI.ProtectorUtils.InitDebugging(String sDebugFilename) bei Symantec.VPro.VProConsole.Program.Main(String[] args) Ziel-Site EnsureInit __________________ Reparatur des Programms hat keinen Erfolg gebracht. Windows- und Symantecupdates sind alle installiert. Hat vllt. noch jmd. ein paar Lösungsansätze oder gar Lösung parat? Danke im Voraus. :) Gruß Maaß IT1.2KViews0likes7Comments