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 Chris
LSR 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 DrakeThe 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?
