Hi PDM-Red,  Up to version 7

Hi PDM-Red,  Up to version 7 of Backup Exec System Recovery you could use drive letters as the destination, handy for daily full images to be removed off site, different disk every day etc. From version 8 this disappeared and has been that bain of our lives ever since, batch files here and there to overcome jobs failing because drive volume such and such isnt available. Bring BACK DRIVE LETTER designation for this otherwise nifty product ! PLEASE ! crying

Where can employees or

Where can employees or partners find an NFR license key for SSR 2013?


Can you provide a bit more

Can you provide a bit more detail on this please? A detailed example of what does not currently work would help..


The simplest way to get help

The simplest way to get help here would be to call Customer Care. They will guide you.

Grab the appropriate number here:


Or as a partner you can try to log into partner net and just search for "NFR". There will be a useful result.


Hi I am new to the forum but

Hi I am new to the forum but just wanted to let folk know of my experience of upgrading so far. I had SSR 2011 installed and working fine on our Windows Server 2003 R2 Standard Edition with SP2 installed. I performed an inplace upgrade to the SSR 2013 product and since then all my users have complained of very slow access times to our server but this is not my main issue. Once I completed the install and re-started the server the software took ages to connect to the agent and when it did connect it no longer had my previous back up jobs listed. I therefore went to re-create them, this is when I have come across a major issue. When starting the wizard for creating a new backup job and I ask it to backup the computer option there are no drives at all listed! If I can't see the drives then how am I to back them up? I then tried to create a folder backup which it can see them but gives errors when I try to move to the next part of the wizard after "Name & Destination". Error is

-Error E1AD78A5: Cannot save backup properties.

--Object reference not set to an instance of an object.


I am now sitting with a server that is not protected and I would seriously advise to re-consider doing an inplace upgrade.  Any help would be greatly appreciated


Form a support perspective,

Form a support perspective, the best way to deal with that is to have the system restored from backup to the state before upgrade. Troubleshooting upgrade issues should be the last options. The reason for that is to avoid "hidden issues", that don't show immediately after the upgrade but day/weeks/month later. Troubleshootin these is always a pain in the rear.


Hi Willie, Can you please

Hi Willie,

Can you please check if following 2 services exist  and are up in Services control panel?

1. Symantec System Recovery

2. SymtrackService





Thank you for the responses,

Thank you for the responses, I can confirm to PravinAmin that the first service appears is installed and started however the second service is not listed therefore I presume it is not running.




Hi Willie, Thanks for

Hi Willie,

Thanks for confirmation. Can you please try following and let me know if it resolves the issue?

1. Start command prompt with Administrative previliges.

2. Navigate to  C:\Program Files\Symantec\Symantec System Recovery\Shared\Drivers\Service folder

3. Locate Symtrackservice.exe (if OS is 32-bit) or Symtrackservicex64.exe (if OS is 64-bit) in the folder

4. Execute following command:

     a. 32-bit OS: "Symtrackservice.exe /service /start=Auto"

     b. 64-bit OS:  "SymTrackServicex64.exe /service /start=Auto"

5. Please make sure that the service gets registered and can be started.

6. Restart the server

Please let me know if this resolves the issue.






PravinAmin,   I can confirm



I can confirm that installing and startinig that service does resolve my issue and I can carry on and re-setup backup jobs as the previous jobs are missing but it does see all the drives and the previous backup images.


Many thanks




Hi Willie, Thanks for

Hi Willie, Thanks for confirmation. This could be some machine specific issue of windows missing to register the service. -Thanks, Pravin

Hey Bruce, I have just

Hey Bruce, I have just ordered my reseller NFR license. I logged into partner net, went to software benefits, order NFR. it then takes you off to the ordering portal at salesforce.com on the 4th page of products I am entitled to it showed:





I added it to my order and submitted, I got a confirmation email immediately stating the I should receive my key in 3-5 days.

Note: the salesforce ordering web portal is very "comprehensive"  if you have not already setup your NFR entitlement be advised it will take a bit of effort. Happy New Year to all.



SSR 2013 is now a live

SSR 2013 is now a live product and no longer considered 'beta'. If you have any questions or comments, please start a new thread. This will ensure your post receives full exposure to everyone monitoring this SSR\BESR forum. 

Thank you all for your questions and responses. We appreciate your comments and feedback.


They can put their SFTP

They can put their SFTP effort into a solution that is common for 2013, if you ask me...

Check out the idea: https://www-secure.symantec.com/connect/ideas/automatic-offsite-backup-replication

Hopefully Symantec picks up on this request...


thanks !

thanks !


Downloaded and installed SSR

Downloaded and installed SSR 2013 without any problem.

Windows 8 Pro, Intel i7, nVidia GTX670, backup ource 230GB SSD, backup target 3GB HD, all as used with Ghost 15 0n windows 7 with no problems.

Unable to back up. 

When attempting backup with SSR2013, program starts by calculating 'time remaining' as usual but then fails, stating there is not enough room on target disk (on a nearly empty 3GB HD!). blush

Error message:

-Error E4F3000E: Snapshot failure while using Volume Shadow Copy Service. Please check application event log for VSS errors. Error code: VSS_E_INSUFFICIENT_STORAGE (-2147212513).


Any ideas?


Hi, This error is of VSS,


This error is of VSS, occurs due to insufficient snapshot storage. Please refer to http://www.symantec.com/docs/TECH200588.

Mostly, there might be less space left on System Reserved partition with is 300 MB on Windows 8. You can relocate the snapshot area of this partition to C drive.





Pravin, thank you for fast

Pravin, thank you for fast response, appreciated.

Hum, perhaps I misunderstand, but reference tech. note states that problem occurs if source volume has less than 300GB of free disk space.

In my understanding source disk is that disk which is to be backed up - is this correct?

If so, SSR 2013 is unsuitable for backing up 95% of SSDs used for OS installation, most of which are 60-120GB; mine, at 240GB, is larger than most, and, currently, has 70GB free.

Hope that I simply misunderstand Tech. Note and reply.

Thanks and regards

Robert Challess




Hi Robert, This is slightly

Hi Robert,

This is slightly unrelated to size of disk drive or partition. The VSS shadowstorage size is set to 300 MB by default. VSS snapshoting is also used by other applications which captures snapshots. If such old snapshots are not deleted and new snapshot is tried, it may exceed the defined snapshot storage area causing the VSS error that you observed. The snapshot size in some cases itself bigger than shadowstorage limit resulting in the error.

Please run following command as Administrator to check the shadow storage details

vssadmin list shadowstorage

You can also resize the shadowstorage using

vssadmin Resize ShadowStorage command.

Please let me know if this resolves your query or please start a new thread in the forum for further discussion.





Hi Pravin Been there, done

Hi Pravin

Been there, done that.

ShadowStorage space increased to 18GB (!!!) and no change.  SSR 2013 continues to fail with refewrence to insufficient space, as described above.


Robert Challess