Backup Exec duplicate backup jobs malfunctioning
Hi, as per instructions from Symantec a while back I decided to use the Duplicate Backup Jobs in Backup Exec to make a copy of the last full when it ran to external storage. When it ran, instead of creating the individual files, it created BKF files which isn't what Symantec told me it would do. Also it gave a generic hardware error after it placed 26.1GB of data and the drive is a 2TB hard drive formatted with NTFS. The drive volume is still there. It is mounted on a USB 2.0 port on a Synology NAS. I'm wondering if anyone knows how to restore the files after the full runs. Do I attach a duplicate backup job or is there a way to attach a full restore? Thanks
missing some bfk files - restore with some missing still?
i need to restore a full back up (we got hit with crypto) and its missing a bunch of the bkf files, it somehow got switched to delete after 4 weeks and my fault for not catching it. is there anyway to extract whatever bfk files i have somehow? i know there will be lost data, but some data is better than no data. windows sbs2008 backupexec 2010 r3.4 Thanks brianConverting Norton Ghost 15.0 to SSR 2013
We have recently received notification that Norton Ghost has been discontinued and consequently a free 60-day trial of SSR 2013 is being offered. It clearly states that Ghost must first be uninstalled, but nowhere is there any up front statement of "backward compatibility". The 309 page SSR 2013 User's Guide does not have the word "ghost" in the text. The absence, in your message to Norton Ghost users, of any reference to backward compatibility suggests that the two products are completely different. After all, if there was a simple conversion path, I am sure your marketing people would have made a clear, bold statement about this in trying to retain Norton Ghost users. Our assumption, therefore, is that SSR is not 100% backward compatible; and therefore we should be advising clients NOT to uninstall Norton Ghost, NOT to install the new SSR 2013, BUT to switch to Acronis True Image instead. Is our assumption a reasonable one? If not, where is the documentation about transition and conversion from Ghost to SSR? Obviously we are not going to risk our reputation or damage to clients based on casual and possibly ambiguous comments in a forum. At the very least, we would expect to see an officially documented Symantec technical statement about backward compatibility, transition, conversion tools, etc.
