SSR 2011 fails to cleanup .v2i recovery points after a backup
We have Symantedc System Recovery 2010/2011 across several sights, and we have noticed a common problem occurs where previous recovery points do not get cleaned up post backup as per the rules in the backup job. Is there anything else we can do to make this more robust without resorting to post backup scripts deleteing files as this will mess up SSR's recovery point history and run the risk of deleting the last good backup if the current backup fails. Currently we are aware of only 2 places we can automate this process, in the backup job you can set the amount of recovery points to keep, and in the manage backup destination/settings you can set a threshhold based on capacity. So for example if I am creating a backup files that is 350 gb (final compressed .v2i files), and I have set "Limit the number of recovery points for this backup" to 1, and set the "manage destination settings" to "monitor disk space usage for the backup storage" and set the threshold to 360 gb, also set to "auto matically optomise storage" Have I missed something here or is there a better way we should be doing this? From what I can see in the logs, at the point the process should be purging the previous days .v2i files SSR seems to think the backup device is unavailable (when it fails), however the backup device in this specific example is an Iomega NAS drive on a 1GB lan... ThanksSolved3.5KViews1like42CommentsSymantec System Recovery 2013 r2 sp4 & Server 2008 r2 BSOD
I am backing up a Server 2008 R2 with Symantec System Recovery 2013 r2 sp4. The image backups fine. When we do a restore we get one of the following errors BSOD stop 7b, No operating system found, etc I have found this article on Microsoft and Veritas which talks about the C:\Boot files being located inside the image file. https://www.veritas.com/support/en_US/article.TECH125582 Within this article it talks about how it is backed up with the image of course, but when it is restored it is written twice: once by ASR Writer and then again by the image file with the end result of the GUID not matching. Here is Microsoft's explanation: https://support.microsoft.com/en-us/kb/2261423 So then if the C:\Boot is located in the image file to exclude it when you do a restore of the image. Unfortunately I have no luck in trying to find out how to exclude this on a restore or even during a disk-based backup. Has anyone been able to resolve this issue? I have and currently working with Veritas but do not have a resolution. Please let me know. Thank you.2.9KViews0likes14Commentschanging backup settings to allow new hard drives
Our current setup: Windows Small Business Server 2011 (which is actually Server 2008 R2) Symantec System Recovery 2013 Logical drives are C:, D: and E:. We back these up on a weeknightly basis (Monday, Tuesday, Wednesday, Thursday, and Friday). It also backs up the System Reserved drive. It is a recovery point set that run a complete backup each night to an external USB drive. Before the backup runs, we delete out the previous recovery backups from the week before. Ex: on a Tuesday night, we plug in the USB drive labeled "Tuesday". In Windows explorer, we delete out the backup files that are there from last Tuesday's backup. This leaves the hard drive blank, allowing that night's backup to run, which completely copies over the C:, D: and E: drives to the Tuesday USB hard drive (in the case of someone accidently leaving the previous week's backup files on the USB drive, the job creates a differential backup of the logical drives to the USB drive). -We are using a recovery point set job description. Every day, the job shows up as scheduled with the destination drive labeled according to the day of the week: [Monday]\, [Tuesday]\, etc. -Each hard drive has a recovery point set limit of 1. -All the USB hard drives are identical. The problem is that one of the hard drives has failed and we are replacing it with a different, higher capacity USB hard drive. Now the scheduled jobs do not run on that drive. When we run the scheduled backup job manually, it backups successfully to the new USB hard drive. I do not have any error messages right now, unfortunately. What changes do I need to make to my scheduled backup job to allow it to backup to different models of hard drive? We are not using offsite backup features.Solved2.8KViews0likes13CommentsBackups Failing - Cannot create recovery points for job
Hi, 1st post. We have recently installed Backup Exec System Recovery 2010 Management Console. We have deployed the Altiris Agent and the Backup Exec 2010 Plug in. We have a mixture of Server 2000/2003/2008R2 servers running BESR 8/8.5 and 2010. There are a group of servers that will not back up, the message they receive is as below (taken from Event Log) Error EC8F17B7: Cannot create recovery points for job: Fraserburgh Macrae. Error E7D1001F: Unable to write to file. Error EBAB03F1: The specified network name is no longer available. Error E7D10046: Unable to set file size. Error EBAB03F1: The specified network name is no longer available. (UMI:V-281-3215-6071) Details: Source: Backup Exec System Recovery We are backing up across the LAN to a brand new NAS box. Permissions are correct and I can copy backup files between the server and NAS and the other way too. I have also amended the \\server\share to \\ipaddress\share to no avail. I have tried the articles listed via Google but am still at a loss as to what to do. If you are able to help that would be excellent as I have been struggling with Symantec Support for about 6 weeks for various issues with regards this installation. Cheers.Solved2.7KViews2likes7CommentsOff-Site drives are always over filling
I have SSR 2013 Version 11.0.2.49853. I have been to the forums here before with the same problem the following posts: https://www-secure.symantec.com/connect/forums/ssr-2013-site-site-different-file-sizes https://www-secure.symantec.com/connect/forums/system-recovery-2013-site-drives-cant-delete-old-points I'm still having problems with the off-site drives always filling up. The on-site drive has 1TB of space left while the off-site only has 7GB of space left. This is getting ridiculos and I would love some insight on how to prevent this from happening. I currently have to delete all the data in the off-site drives and rerun the backup. I shouldn't have to do this especially when I'm told the on-site and off-site should have the same data and delete the same data.2.6KViews0likes20CommentsFormer Ghost 15 user - Getting trapped in the SSR 2013 Trial
A few days ago I had an issue with doing a system restore using Ghost 15. I went to that forum for help and learned that Symantec was going to discontinue Ghost and recommended users "check out" SSR 2013 with its free trial. I downloaded the free trial and eventually learned it would not install unless I first remove Ghost. That wasn't from anything that I saw when the SSR installation failed; that happened without any additional information. However, I did eventually find my way to this forum and a helpful Guru pointed out the issue and also that I could always re-install Ghost if I wasn't happy with SSR. I uninstalled Ghost, installed SSR, and started backing stuff up. Now, if one of the things you want to do is a full system restore (my primary interest) then you need a recovery disk. SSR will make a recovery disk for you and all you need to do is provide an activation key which you don't get with the trial version. No problem, as all I need to do is install Ghost. But I can't install Ghost until I uninstall SSR. And SSR WILL NOT UNINSTALL. Whenever I try to uninstall it there's an Error 2738 and something about a VBasic error. So now I have a trial verision of a program that I can't use and a paid for program I can no longer load. I guess it can all be fixed if I pay Symantec for an activation key for a program that I'm not sure I want in the hopes it will maybe allow me to upgrade to a latter version that can uninstall so I can install the program I uninstalled so I could evaluate the Free Trial. To put it another way, I may have to pay Symantec to I can remove their free software and load back the software I paid them for as well. And, even it it turns out there's a simple, and hopefully less expensive, way out of this I've still wasted a lot of time on what should be a free trial of a comercial product which appears to be more of an alpha test. (If I sound upset, it's because I really am)2.4KViews3likes12CommentsHow to migrate from Ghost 15 HW to new hardware with Recover Anywhere
I am replacing my current Win7 PC running Ghost 15 with a new PC (different hw, of course). Right now the new pc is bare metal with no sw installed on it. I want to migrate to my new PC with Recover Anywhere. I am trying to figure out what I need to do to accomplish this. Do the recovery points (system reserve & C) have to be created with SSR (I am assuming that the correct product would be SSR 2013 Desktop) or can they be created by Ghost 15? Do they have to be hot or cold, cold being created from the SRD. If the recovery points have to be created by SSR that means I will have to install SSR on my current machine. Symantec tells me I cannot upgrade SSR over Ghost 15, that I have to first uninstall Ghost and then install SSR (I find that pretty ugly and amazing that it would even be developed that way). If I can use Ghost 15 recovery points, how to I create an SSR SRD to boot from my new PC in order to do the do the RA? Sure sounding like I'm going to have to install SSR on my current machine. Is it possible to boot the new machine from my Ghost 15 SRD and recover anyhere? I don't think that's even an option because I don't know that Ghost 15 supports RA. What things do I need to look out for with an RA recovery? I know any sw that is hw dependent will require reinstalling or reactivating (like Windows and Office). Any caveats? This is my 1st RA so, so I would appreciate some help here. I have had no luck with Symantec tech spt. DavidSolved2KViews1like5CommentsHot Swap - Lost disk format?
In my desktop PC I have an hot swap adapter. This allow me to have two or more hard drives with the same drive letter say "E:" Most of the time I use the hot swap for different groups of files (Movies on one drive, Books on a different) and the drive letter is "E:" which is the default letter that is assigned by the PC since it is the need letter not use by my internal hard drives. I back up my OS and Data with SSR to my 3 Tb internal hard drive that is assigned the letter "V:". Over the last few days, my V drive has been showing signs of getting "sick". So I purchased a second 3Tb drive. I removed the V drive from inside the computer. I placed my new 3Tb drive in the hot swap adapter and change the label to "Second BackUP- V2" and assigned it the drive letter "V:". It was my intention to rotate the two V drive as one does external USB drives. Since drives in the hot swap adapter are not on the USB port, the USB option is grayed out when I creat a new backup job. The SSR backup appeared to be running OK until at the very end, I receive an error. When I looked at the new V2 drive with Windows Disk Manager it was (1) unlable and (2) looked as if it was un-formated. I then put the original V drive in the hot swap adapter to make a backup before I attempted to find out what was wrong. SSR could not find the original V drive. When I looked at the original V drive it also appears to have "lost its format". Before, I attempt to take any other action, I am asking for your help. It appears that SSR does not like two disk with the same name. I did notice that SSR "identify" each backup location. Could this be the problem? Any quick solution to restore my backup copies without using a file recover software?2KViews0likes3Comments