Symantec System Recovery 2013 R2 is now available!

Chris,

RE: Should I upgrade to SSR 2013  R2?

       Testing image recovery.

Background.

I am at 11.0.249853 as of 2/2/15.

Win Pro 7 SP1 single PC. 

I am a CPA not an IT guy but for my small office I have to be both. SSR 2013 backups are going well and time to run an image recovery test. Testing image recovery from Dell 3600 (current system) precision workstation to Dell 3400 (old system not currently used so a perfect test machine),

The test recovery should be a valuable post for the forum. This would be a separate post but a follow up to  https://www-secure.symantec.com/connect/forums/ssr-2013-desktop-backup-jobs-win7-pro-64-and-partition-restore-order which I would cross ref to new post and lock thread.

I am using the term "recover" to restore an image from the 3600 volume C (operating sys) and D (Data)  to and older XP 3400. I am not worried about losing data on 3400. 

Questions

Should I upgrade to latest version? Do I have to rebuild backup jobs?  Current version is working fine so I would only update if absolutely needed. I have an active license so no cost to me except the cost of my time.

Anything I should know about problems with latest version? 

Any suggestions on my recover test?

Thanks very much.

Bob

Should you upgrade? If everything is working well, then there is no burning need to upgrade.

That said, I would always recommend people to upgrade to the latest version when they can. You should check your license entitlement though because you may need to pay for the upgrade..

If you do upgrade, your backup jobs will stay intact so there is no need to 'rebuild' them (unless I have misunderstood your question).

In terms of restore, please refer to the following which should help:

http://www.symantec.com/docs/TECH129112

Hope this helps.

Hi Chris,

FYI I updated to SSR 2013 R2 with some bumps.

Initial install failed. Hung on final installation step. Step was estimated to take 10 minutes and hung for one hour. I rebooted and had to restore PC from a Win 7 Pro restore point. Restore was successful. However, I also have Norton Internet Security that required using the Norton removal tool. Using a restore point apparently break NIS. I reinstalled NIS successfully.

Muzafar from tech support helped me install  SSR 2013 R2

Back up jobs from prior SSR 2013 were not saved in SSR 2013 R2 install. Maybe unsuccessful initial install was cause?

SSR 2013 R2 is performing one time backup.

I will rebuild backup jobs.

Thanks for the Tech 129112.

I will post my restore test in a separate post.

Bob

 

I just upgrade my SSR 2011 to 2013 R2. The binary file was downloaded from my symantec authorized account. Now it promps me for activation key where as in my symnatec profile it says no activation key required.

Can someone please help me out?

Ali

Please contact our customer care team:

http://customersupport.symantec.com/

I have installed this new verison on four different laptops and one PC.  I have yet to be able to create a recovery disc succussfully, whether setting for lights out or not.  It always fails to error code ECA3178D

I have also just trie to create an iso recovery disc image and that also fails to the same error code.

This product is useless if i can't completely recover a computer with it!  Guess i may need to go backwards to System Recovery 2013?  Why is it every time you release new products they don't work right?  Any fix for this?  All machines are using Windows 7 Pro x64 and Symantec Endpoint Protection 12.1.5

 

Is this the issue you are seeing?

http://www.symantec.com/docs/TECH227401

Yes, and No.  Yes if i try creating the a "lights out" recovery disc but even if i do not check that option i still have that same message shown here...

 

Yes, and No.  Yes if i try creating the a "lights out" recovery disc but even if i do not check that option i still have that same message shown here...

 

Sorry - Duplicate post

 

OK, can you please open a support case then?

As per the article I shared (what you are seeing looks the same), this is an issue that is currently under investigation.