For the developers:
First, thank you for continuing to improve the one program I rely on to protect my job by saving my bacon, er, data!
A couple of comments about the SP4 installation experience:
If you want the ability to clone a VHD/X to another VHD/X by simply mounting both virtual disks and using SSR's Disk Copy, pleae click this link to upvote the SSR Copy Virtual Disk to Virtual Disk idea!
https://www.veritas.com/community/ideas/ssr-copy-virtual-disk-virtual-disk
Enjoy!
Hello,
I have a MAC Dual Boot, with OS X 10.10 Yosemite and Windows 10 Education
I would like to know if SSR 2013 R2 SP4 is able to backup the whole PC, or if I should backup only the windows partition with it, and backup the OSX one with timemachine.
Error in EventLog
Error EC8F17B7: Cannot create recovery points for job: Drive Backup of Windows (C:\), DNA (D:\), Data (E:\).
Error E4F3000C: PostSnap failed. (UMI:V-281-3215-6071)
Ok so we are running Altiris CMS 7.5 SP1 HF5 and SSR 2013 R2
We do not even need these old packages so guess the question is how can I get these to not show up anymore as packages on our package server?
Thx
Ok so I downloaded SSR from my veritas page as my license entitles...
Typically the old way to get SSR-MS installed is to launch SIM and it will show as available. Is there a documented procedure now going forward on how to install the "Management Piece" into Altiris?
Is it possible to script an agent deployment from the SSR server. I see none of the switches available enable a remote PC to be specififed.?
We plan on using powershell to do this?
Thanks
Has anyone noticed this? Tried it on two machines, and both happened. The only way to fix it was to go to Windows hardware troubleshooter, and the drivers were restored. Device manager listed it as missing. Most people with panic and reinstall Windows.
Am using Windows 10 64 bit.
I cannot believe something like this was released.
Many Symantec System Recovery (SSR) customers, and potential customers, ask the same questions over and over again on the forums. Nothing wrong with this of course but I thought I would put this information together to help answer at least some of the most common questions that I see on a day-to-day basis.
Here goes...
Product Information Pages:
Symantec™ System Recovery 2013 R2 rapidly restores complete physical and virtual systems in minutes, not hours or days, even to dissimilar hardware, remote locations, or virtual environments.
Symantec System Recovery 2013 R2 is now available!
For more details, please refer to the following links:
https://www-secure.symantec.com/connect/blogs/new-symantec-system-recove...
http://www.symantec.com/docs/TECH225253
Feel free to ask any questions about this release on this forum thread.
By connecting with your LinkedIn profile and completing a 3 question survey, we'll get to know more about your unique interests to ensure we provide the solutions, technical knowledge, and product ideas most important to you.
Symantec System Recovery 2013 R2 SP4 is now available and includes support for Windows 10 and the Symantec Management Platform 7.6.
For more details and download links, see below:
Trialware: https://www.veritas.com/trial/en/us/system-recovery-2013-server-edition.html
I just upgraded to Windows 10 from Windows 7. I am using System Recovery 2013, Ver. 11.0.2.49853. The installation date is Monday, December 14, 2015. After the upgrade to Windows 10 it changed to a Trial Version with an Expired License. How do I correct this program so it runs in Windows 10 as it did in Windows 7.
SSR 2013 R2 11.1.2.51177 -- Win 7 Ultra 64.
Backup has worked OK for the past few months. Today I am getting the following errors. I am attempting to backup to my desktop computer with only two hard drives "C" and "U". I did a search, but could not find a solution.
I assume this has been answered somewhere already but cant find the solution. I cant seem to work out how to get the latest service packs for SSR 2013 R2 to appear in SIM. I seem to be running management platform 7.6 HF7 and SSR 2013 R2 11.1, but I get no updates available.
I'm running 2013 R2 SP4 11.1.4.55331. If I do a backup on both my Windows 10 machines and try to recover it tells me I need to repair the operating system. But it can not repair the problem. If I do a windows 10 backup there is no problem.
Restoring from an image is failing. I believe there is a bad line in the boot.ini file that is the cause.
I would like to edit the boot.ini file that is in the image, but I can figure out how to do that hand have the changes saved.
Is there a way?
