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. David
Unable to eject Dell RD1000 cartridge
Greetings, Anyone had issues ejecting Dell RD1000 cartridges (40Gb through 200Gb hard-disk based removeable carts) when used as a backup target for BESR recovery points? The drive works great, but when it comes time to switch cartridges, the eject button does nothing. An attempt to eject the cartridge via My Computer gives "Error ejecting the media. It could be in use". When the BESR service is stopped, the cartridge can be immediately ejected on the first try. Once BESR is started again, the eject capability is once again lost. It strikes me that Symantec is "locking" the drive open, even when not in the middle of a recovery point creation--basically when it has no business touching the drive. This is a bad practice, as it is disallowing other system processes (like "eject" ) from using that drive, and makes this product virtually impossible to use as a viable backup product that allows for off-site backup strategies. I understand that BESR is primarily targeted at "non-removeable" media, but a good backup strategy necessitates that we also have off-site swaps of the target media. So this product is pretty well useless for single-server bare metal backups that can be taken off-site--at least in convenient form--without buying other backup products and drives to back up the target data (i.e. BESR creates the image file, then some second backup product backs up the image file to a removeable cartridge.) Geez, what a hassle. Any help? -Dan Message Edited by Dan Neuwirth on 06-28-200702:13 PM
BERS 6.5 Freezing
BESR v6.5 - running on Server 2003 R2 with SP1 Every couple of weeks this seems to hang and not run the scheduled job. The processes are running for the application but the console will not open. I have to kill the process and restart the service. This was doing the same thing - but more frequently on Livestate branded version - 6.02. anyone had the same issue Cheers ChrisLSR and NAS device
I am using LSR 3 advanced server suite. I can successfully create an LSR image on a NAS Server device I have (Buffalo technology 1GB terastation) using the NAS device name in a urn (\\bu-os3-01\backup\livestate). I cannot however, access the NAS device when booting from the LSR disk. I can ping the device, however I cannot see it either in network neighborhood, nor in the browser (no devices, including domain or workgroup server devices show up there). I can however ping the device, using either it's ip address or name. Any idea what I'm doing wrong? Is there an update to LSR 3 that fixes this issue? Thanks in advance, Lee Drake
The VSS Provider vetoed the operation
We are recieving the above error when attempting to back up one of our servers, after a reboot the backups will work for between 2 days and a week but then fail again. This is in the application log as event 100 and in the system log as event 20, source volsnap (The shadow copies of volume D: were aborted because of a failed free space computation.) We have upgraded too the latest version of BESR and the latest version of VSS from Microsoft in an attempt to fix this but it still occurs. Any ideas?
Error 800706be
I did a search on this error and only got 1 reference to Ghost. After upgrading from 6.5.4 to 7.0 one of my servers gives me the following: "The connection to the recovery agent was lost. The wizard will need to close." I clicked [OK[, then saw: "The remote procedure call failed." I clicked [OK] then saw: "Error 800706be running job: (job name)" The files are still on the network share. Any ideas? I will run the "fixinstall.bat" and reboot again to see if that helps.BESR 7.02
Just to give you a little history on my Backup Exec purchase first. I met a Symantec rep at a conference and he made me a lot of promises on what Backup Exec 7 would do for me. I was very impressed if it could do the things he suggested. For the initial purchase I ordered a license for two servers, the management software and 7 workstations. It has been at least 4 months now and I have installed it at least 5 different times, different ways trying to get the bugs ironed out. All I can say is that this product never should had been released. My server is a new install of Windows 2003 server standard edition, the workstation I am typing on is a Windows XP Pro new install with only Visual Studio and Symantec Antivirus 10, nothing else. Every backup seems to fail on all the workstations at least several times a week. Last night before I left I connected two machines to the Server Management software, both patched to 7.02. This morning both workstations had Visual C++ errors and out of memory errors, the Backup Exec agent had failed and the computers were so slow from being out of Virtual Memory they both had to be shut down manually. Now these are robust machines, one with 2 gig and the other with 4 gig of ram. The file server is a very nice Dell Poweredge, also very new with a dual core Xeon and 4gb of ram. The backup drive is a 500gb connected directly to the server and everyone has full rights. I am not an idiot and this software should just "work" out of the box. I have not fought this long to get something working since I started working with Linux, which requires just as much tinkering as this software. I could understand this amount of grief from Open Source software, but not something that cost me as much as it did. My question is why was this software released in it's present state and when is this 7.03 patch going to be ready ?
