What is the highest version of Backup Exec System Restore for SBS2003?
Hello all, I have an SBS2003 with BESR v8.5. I like the software, but MS is telling me the drivers included in v8.5 can cause system instability. We are considering an upgrade if available. Thanks, -JohnSolved701Views1like2CommentsBackup cycle with external usb drives
I have been following the threads and asking some questions on this topic and I still don't havea clear answer. It seems others are also confused so let me try and ask again. Is SR ideal for creating a backup cycle (2 weeks/10 drives, in my case) which backs up the entire server each night to an externalusb drive?The idea is that the drive is replaced in the monrning with the drive for the next evening without any further user input. Is the program structured to do this with ease or (as it seems to me) must you resort to workarounds which don't always work? If it can be done is there a step-by-step guide how to do it? We now have an old version of Backup Exec which was designed to do the above with tapes and worked fine until we grew out of the tapes. I have the option of BE or SR. I prefer SR but I must be sure it can do what I want. The server is running ExchangeSBS 2003. Many thanksSolved612Views0likes3CommentsBESR 2010 Offsite confusion & jobs not running. (RDX included)
Hi Folks, I've got a lot of BESR's of various versions out there on a whole host of servers, most run with the following setup. 1tb+ USB HDD which is the backup target, and a RDX drive for the offsite target. For a long time I've thought the backups work perfectly, apart from the odd error in the middle of the night about consolodation which said it can't do it because some recovery points are missing, but they did exist. I found out what this was and will be explained shortly. What I have found is that the offsites are working, but the recovery points are being split over the multiple RDX drives and if you try and restore from one it complains that the recovery points are missing - which they are, they're on the other RDX drives! The software is quite happy though as it HAS copied it to the offsite. The USB drive for the backup target has everything on it and works perfectly, restores systems fully and everything.I hope I'm making sense so far. At the moment I do a new recovery base every week, so worst case I can restore using the offsite but depending on the cartridge the server may get restored back to a week or two ago - this is pretty bad! Is there any way to get around this? I've tried making two jobs, one for the permanent backup drive that runs a new base each week, incrementals during the week and a new one for the next week coming. Again, works perfectly. And a2nd job to run a nightly backup (independant recovery point) which on a few servers has run once, sometimes twice, and never again. (If this worked I'd be happy with it) I'm thoroughly confused! Ultimately I'd like the offsite RDX to contain a full recovery point + incrementals like I expected it to, if this is actually possible. Can anyone shed any light on what is going on, or what *I'm* doing wrong? Read the manual from cover to cover too and seems like I'm doing it right. Many thanks in advance! Ian422Views1like1CommentSSR 2011 - can not restore running system
We have a Hyper-V server HOSTA (Windows Server 2008 Std SP2 x64) with 2 guests SBSA (Windows SBS 2008 SP2 x64) and APPSA (Windows Server 2008 Std SP2 x64). Both SBSA and APPSA have Symantec System Recovery 2011 (Build 10.0.0.39952) installed, and backup to share on HOSTA and Offsite to a FTP location. The Offsite location has HOSTB (Windows Server 2008 R2 Std SP1 x64) with Symantec System Recovery 2011 (Build 10.0.0.39952) installed. When the Restoring SBSA or APPSA it fails every time in all ways we have tried: Convert sv2i to Hyper-V VHD fail: Converts ok, then on start of VM guest runs the mini setup, then updates, then randomly reboots. after that we receive the stop 7b error, But the data on the .vhd can be mounted and accessed. Create Hyper-V guest and use System Recovery Disk fails: Towards the end of the restore a "Recover My Computer Wizard" box pops up with the message: Error EBAB0013: A test that safeguards the integrity of the program failed unexpectedly. CHECK failed, Can::ReadFileFrameReal: .\Can.cpp(826): Read Failure. Error EBAB0013: A test that safeguards the integrity of the program failed unexpectedly. CHECK failed, Can::ReadFileFrameReal: .\Can.cpp(826): Read Failure. with an Ok button that takes you to the menu screen. Convert to VMware Server Disk fails: The convert stops at 99% with 3 seconds to go (With or without "Run Windows Mini-Setup") Convert s2vi using VMware Player 3.1 fails: Very slow reading the s2vi file and then I enter the password and straight away I get the error from VMware Player: Failed to open virtual machine: Failed to query source for information. We have tried a One off recovery point on-site and taken it to the off-site location and receive the same issues. A convert to vhd of APPSA on APPSA: converts ok, moved to HOSTA. on boot of the restored guest APPSA we receive: Windows Boot Manager Windows failed to start. A recent hardware or software change might be the cause. To fix the problem: 1. Insert your Windows installation disc and restart your computer. 2. choose your language settings, and then click “Next.” 3. click “Repair your computer.” If you do not have this disc, contact your system administrator or computer manufacturer for assistance. status: Oxc000000f Info: Windows failed to load because the NL5 data is missing, or corrupt. Please can someone suggest any ideas600Views0likes2CommentsSymantec Backup Exec System Recovery 2010 Granular Restore Option
Hi I am trialling the latest version of Symantec Backup Exec System Server (Edition) 2010. When browsing to a sv2i for a exchange mail folder the temp file that Symantec creates to mount the file is becoming to large for the size of my C:\Drive which is loacated - C:\Documents and Settings\james_chudley\Local Settings\Temp. I can mount sv2i files for regular non-exchange drives and am able to browse folders and files, I can do the same for the sv2i file above but am un-able to mount the exchange mail e-mail folders. Is there a way of changing where Symantec Backup Exec creates these temp files? I have pleanty of space on other drives on the same server which I can use for these files. Any ideas? J.Chudley321Views0likes1CommentKann keine Wiederherstellungspunkt-Sätze erstellen
Die Option "Wiederherstellungspunkte-Satz" ist immer ausgegraut und ich kann sie nicht auswählen! Es steht immer die Meldung darunter: Die Option Für Wiederherstellungspunkt-Sätze is deaktiviert, da einem vorhandenen Backup-Auftrag für einen Wiederherstellungspunkt-Satz bereits ein ausgewähltes LauFwerk zugewiesen wurde. Es kann nur jeweils ein Wiederherstellungspunkt-Satz Für jedes LauFwerk festgelegt werden. Habe schon alle Backups gelöscht damit ich diese Option anwählen kann aber egal was ich mache ich kann sie nicht aktivieren! Bitte um Hilfe! Anbei ein Screenshot1.3KViews0likes16CommentsBESR 2010 License
Hi All, We have one BESR 2010 License to backup our existing Exchange server 2007. I have setup a test server which I want to install BESR 2010 on and use that to convert the backup images to VHD file, it will not backup but will just do the conversion... Question is : Whether I can use that ONE License to activate the BESR 2010 trial I have on this test machine so that I can convert backup images to vhd almost every day, as I said - it won't backup, just do the conversion or granular recovery of exchange when required. Would that de-activate our existing BESR 2010 install on our Production Exchange Box or would it still carry on to work ? When I received the Symantec Disc folder, it also has something called BESR desktop one or three free licenses (would have to double check). Would be grateful for your input on this Kind Regards852Views2likes10CommentsBackup Exec 8.5 with Altiris
Hello, i´ve got a little problem with a server which is backedup with besr 8.0 (version 8.0.2.26324)and managedby an altiris server. The problem is that the altiris management console is reporteing me that the server never made backups. When i take a look at the backup destination, there is a backup of this server and its getting updated every day. So i think the altiris management console doesn´t get the right status from the altiris agentof this server(win2003 R2 x64 Standard). Thanks for your help.827Views0likes7CommentsBackup exec 12.5 & system restore 8.5 to the same NAS NOT WORKING
Help!! I a having a problem with a server it is win server 03 running exchange sql and I am backing to a single nas drive. The data up with backup exec 12.5 with the sql add in and Exchange add in and also using system restore to allow for quick recovery to a virtual pc for disaster recovery. there is no overlap in the time window of the to jobs but every week or so system restore just fails to run with this message Error EC8F17B7: Cannot create recovery points for job: Drive Backup of (C:\), Data (E:\). Error EBAB0013: A test that safeguards the integrity of the program failed unexpectedly. CHECK failed, Can::GetSafeFrameFileOffset: .\Can.cpp(321): offset != INVALID_FRAME_INDEX. Details: 0xEBAB0013 Source: Backup Exec System Recovery adnd there is plenty of drive space????? Graham992Views0likes6CommentsBESR 2010 GRO Exchange issues with monthly incrementals
Can anyone verify successfully using GRO in BESR 2010 on a Win7/2008 x64 machine, from a backup set with more restore points than available drive letters (22)? Okay so here is my issue. We have many clients we have been pushing out BESR 2010 to replace their current tape backup systems. Problem first noticed on a new 2008 r2 Server x64, running Exchange 2010 with BESR 2010 SP2. This Server is set to run Monthly Incremental Jobs to a hot swap sata disk, then gets copied to 2 offsite sata disks. All aspects of the backups have been running great along with mounting and restores with the exception of GRO. Here is what happens: Environment: We have a secondary 2008 r2 Server x64, with Outlook 2007 installed. 1. We attempt to run GRO, from the choice for mounting we choose "use recovery points from another computer" 2. Browse and locate the s2vi file (index) for the backup drive on the primary server attempting be to recovered. 3. When selected the name of the Server is displayed in the list, highlight and chose next. 4. Password is requested, input and passes. 5. at this point if we watch the computer (windows explorer) while the gro attempts to load the recovery points it assigns a drive letter for each recovery point. 6. Eventually GRO displays a warning that not all restore points will be available and the program screen for the GRO that would show mailboxes and also the drop down to choose the restore point to get data from is blank. 7. If you go to explorer you can see all drive letters are now filled with mounted restore points and they are able to be browsed. 8. GRO is locked and need to be closed, this leaves the drive letters mounted and requires manual dismount. ---------------------------------------------------------------------------------------------------------------------------- Okay so I thought maybe this is this server so we will try on a Win 7 x64 machine same exact results. Now if i have a backup set that has less than the available drive letters lets say 18, the GRO works fine from the Win 7/2008 box. So then I further tested on the Win 7 machine from a Client using 2003 sbs Server, (different backup source, OS, and bit) Same problem occurred with the drive letter limitation. If I do this on a Win XP machine with more than available drive letters (30 incrementals) from the 2003 SBS clients the problem does not exist and GRO works great. Problem is that if the exchange source on the backup was done on a 2007 or 2010 exchange then the version has to be 64 bit thus we need to use Win 7/2008 x64 to do the restore. So now we are S.O.L with this product on newer server implementations. I am hoping that someone has some incite other than don't do incrementals beyond the number of drive letters available because this is just absurd. Was this product ever tested properly in x64 incremental implementations beyond 22 days at Symantec...?Solved901Views3likes4Comments