Windows 10? New software update for Symantec System Recovery 2013 Desktop Edition?
I am currently using Symantec System Recovery 2013 R2 with my Windows 8.1 based desktop PC. I am planning on upgrading to Windows 10 on July 29, 2015 when Windows 10 is released. I've been relying on Norton Ghost and SSR 2013 to do full system images for years. Is Symantec currently working on software for Symantec System Recovery 2013 so that it will be compatible with Windows 10? Will Symantec be offering a FREE update patch to Symantec System Recovery 2013 that will make it compatible with Windows 10? Will it be called Symantec System Recovery 2013 R3 or something else like Symantec System Recovery 2015? I would like to see SSR 2013 tested and certified as compatible with Windows 10 as soon as possible. I would prefer not to have switch to another vendor's system image backup software like Acronis. Their website is saying that you can get a free software update for Windows 10 compatibility for Acronis True Image 2015.34KViews12likes385Commentsveritas system recovery for windows 10
Has Symantec or Veritas released a Windows 10 version of SSR and I miss the notice? If not does anyone know a schedule date? I want to upgrade from Win 7 to Win 10 because some people say 10 is faster, but I will not until I have a good backup that I know will work without problems.551Views6likes2CommentsConverting 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.2.9KViews5likes19CommentsNorton Ghost users - Welcome to Symantec System Recovery!
As announced today (15 March 2013), Norton Ghost 15 is being discontinued, and will be replaced with Symantec System Recovery (SSR) 2013 Desktop edition. Click here for details. We'd like to welcome those customer who already have made the transition, or are thinking about it! Please use this thread to discuss any non-technical issues, such as functionality, upgrade information, etc. If you encounter a technical issue and require technical epertise, you are in good hands. This board is monitored by several SSR specialists, ready to assist. Simply start your own thread with your question. On the surface, Ghost 15 and SSR 2013 are very similar in the look and feel. The console hasn't changed much, so using the product itself should not be much of a learning curve. However, the engine itself has gone through several improvements. Here are a few of the changes in SSR 2013 from Ghost 15: Support for Windows Server 2012 and Windows 8 UEFI Support:Symantec System Recoverynow enables boot from UEFI (Unified Extensible Firmware Interface) in addition to BIOS. 64 bit Support: 32-bit and 64-bit recovery disks are now included. USB Recovery Disk: Create a custom Symantec SystemRecovery Disk on a USB device.Add 32- or 64-bit drivers. Advanced Monitoring and Reporting:Symantec SystemRecoveryMonitor is a new monitoring solution that's extremely simple to use andis FREE of charge to all Symantec System Recovery 2013 customers. It's a standalone andlightweightsolution for managing up to 100 nodes.It’s simplicity and no extra dependency eliminates the learning curve for users. Intuitive GUI along with essential action controls provide crisp status along with ability to take desired actions seamlessly through the same view. Improved support for virtual environments: Greater support for ESX, VMWare, HyperV, and Citrix. Smart Reconciliation:Now Backups and reconciliation are efficiently done by smartly tracking changed blocks.The reconcile time is drastically reduced to seconds by eliminating the need to do a complete reconcile in cases of crashes or abrupt shutdowns. In addition,incrementalbackups are now up to 750% faster. (Incremental Backup without reconcile at least 35%,Full Backup 15% faster,Incremental Backup with reconcile – At least 750% faster thanNorton Ghost 15) For more information on SSR 2013, visit http://www.symantecsystemrecovery.com. Again, welcome Norton Ghost users! Please let us help make the transition to SSR 2013 as seamless as possible.9.2KViews4likes97CommentsData recovery is not possible directly from a NAS (very very slow)
Hello, the three disks of our Windows Server SBS2011 be secured with Symantec System Recovery 2013 R2. At the beginning of the month, a basic backup and three times a day, an incremental backup. In C: \ is just the system on D: \ documents and H: \ is the operating program and the associated SQL database. I'm considering a contingency plan to restore the server in case of a hardware defect on the fly. At the moment I convert from the hard disk C: \ once a week the last recovery point in a VMDK. This automatically leads SSR. But only if the target path is empty. SSR can not overwrite the existing files. The creation of VMDK's takes currently about 110 minutes. The VMDK I can embed into the VMware Workstation, and it boots so without problems. After detection of the drivers, and a few simple steps, the machine runs to about one hour around. After that I want to move the data from the other disks in VMware disks. If at least one of the mirrored disks is still intact, copying files would be no problem. But if not, I have to resort to the backup. These are on a NAS. I open inside the server VM with Windows Explorer recent restore point on the NAS from D: \ or H: \, starts the "Symantec Recovery Point Browser". Then I copy the thousands of files that take a long time. Then I tried on the same way to map the last backup (providing). I enter the password of the backup, and after some time, a free drive letter suggested to me. After clicking OK nothing happens. There are no data is transmitted over the network. After 2 hours, still nothing has happened Update: After 2.5 hours, an Explorer window is open and the E:\ drive with the files is displayed. The sync or copy as with Total Commander takes an extremely long here. So this is not a solution. So. Then I copied to the server VM, the recent recovery points, including the last base backup from the NAS to an empty hard drive in the VM and repeats the steps with the mapping. This worked wonderfully without interruptions. I could synchronize or copy immediately. And that very quickly. Now the question arises: why does not directly from the QNAP NAS? Best wishes André ------------- Hallo, die drei Festplatten unseres Windows Servers SBS2011 werden mit Symantec System Recovery 2013 R2 gesichert. Am Anfang des Monats ein Basis-Backup und dreimal täglich ein inkrementelles Backup. Auf C:\ befindet sich nur das System, auf D:\ die Dokumente und auf H:\ das Betriebsprogramm und die dazugehörige SQL-Datenbank. Ich überlege mir einen Notfallplan, um den Server im Falle eines Hardwaredefektes auf die Schnelle wiederherzustellen. Im Moment konvertiere ich von der Festplatte C:\ einmal in der Woche den letzten Wiederherstellungspunkt in eine VMDK. Das führt SSR automatisch aus. Aber nur, wenn der Zielpfad leer ist. SSR kann die vorhandenen Dateien nicht überschreiben. Die Erstellung der VMDK's dauert momentan etwa 110 Minuten. Die VMDK kann ich in die VMware Workstation einbinden, und sie bootet damit ohne Probleme. Nach der Treibererkennung und wenigen Handgriffen läuft die Maschine nach etwa einer Stunde wieder rund. Im Anschluss möchte ich die Daten der anderen Festplatten auch in VMware-Festplatten umziehen. Falls wenigstens eine der gespiegelten Festplatten noch intakt ist, wäre das Kopieren der Dateien kein Problem. Aber wenn nicht, muss ich auf das Backup zurückgreifen. Diese liegen auf einer NAS. Öffne ich innerhalb der Server-VM mit dem Windows Explorer den letzten Wiederherstellungspunkt auf der NAS von D:\ oder H:\, startet der "Symantec Recovery Point Browser". Kopiere ich dann die vielen tausend Dateien, dauert das extrem lange. Dann habe ich versucht, auf dem selben Wege die letzte Sicherung zu mappen (Bereitstellen). Ich gebe dasPasswort der Sicherung einund nach einiger Zeit wird mir ein freier Laufwerksbuchstabe vorgeschlagen. Nach dem Klick auf OK passiert nichts mehr. Es werden auch keine Daten über das Netzwerk übertragen. Nach 2 Stunden ist noch nichts passiert Update: Nach 2,5 Stunden hat sich ein Explorer-Fenster geöffnet und das Laufwerk E:\ mit den Dateien wird angezeigt. Das synchronisieren oder das kopieren z.B. mit TotalCommander dauert auch hier extrem lange. Das ist also keine Lösung. So. Dann habe ich in der Server-VM die letzten Wiederherstellungspunkte einschließlich dem letzten Basisbackup von der NAS in eine leere Festplatte in der VM kopiert und die Schritte mit dem Mapping wiederholt. Das hat wunderbar ohne Unterbrechungen funktioniert. Ich konnte sofort kopieren bzw. synchronisieren. Und das sehr schnell. Nun stellt sich die Frage: warum funktioniert das nicht direkt vom QNAP-NAS? Viele Grüße André218Views3likes0Comments[Solved] Error E4F3000E. Error code: EndCreateSnapshotSet (-2147212540).
Hello everybody, i'm looking for a solutoin since yesterday. I saw that i'm not the one who had this error, but not with the same error code as me. So i checked (and tried) severals solutions found. including the following : http://technet.microsoft.com/en-us/library/cc734021%28v=ws.10%29.aspx http://www.symantec.com/business/support/index?page=content&id=TECH200584 i add the system writer according to thishttp://community.spiceworks.com/topic/203856-event-513-capi-2-cannot-fix-this-error-to-save-my-life but none of those sites are talking about the error code that finish with 540 like mine. I'll investigate further, but iff someone has any idea. It'll be helpful :)581Views3likes2Comments