Hot 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?
Symantec 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.
Best way to replace current backup disk with new disk
(1) I currently have disk M: where I backup my files to. (2) I have a new larger disk (currently I: and different label than M:) which I now want to use for my backup files. I have no problem moving existing backup files to the new disk with SSR, but the caveat is that when done I want to change M: to say Z: and then change I: to M: The reason is, of course, that I want my backup drive to continue to be drive letter M: with my new backup drive. What would be the best way to do this without causing the backup files to be orphaned. Thanks for the help -- David
Manage backup destinations>Delete recovery point does not delete files?
I have a simple maintenance question. I wanted to properly delete a very old backup/restore point/image, whatever it is called. It was an independent image of a PC drive with the image stored on a NAS. I used SSR to go into advanced, right clicked the drive letter and found the restore point I wanted. It matched the name, date, etc. of the one I wanted to delete. I right clicked and chose delete, then chose yes. It disappeared from the SSR lists but the backup files are still there on the NAS. So I deleted manually....but I would have thought SSR have deleted the files but perhaps this is a safety feature. Thanks, BJB
Symantec LiveState 2013 R2 & ESXI Free -> VM-Based and/or Cold Image Possible?
Hello, We have inherited a Server running ESXI Free and a single VM with Server 2012R2 -Recognizing the limitations inherent in the Free Edition in terms of protecting the ESXI, is at least possible to install 2013R2 w/in the Virtual Machine and successfully back it up to external storage for DR Consideration? -Model would be if total server failure at least 2012 Server can be saved and restored to different machine via V2P -Apparently VM does have standard Backup Exec on it currently that running - did not know if this would extend to 2013 R2 -Additionally to get an entire image of the machine can the entire Drive be imaged via Cold Boot with new version of SRD Thank you very muchOff-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 1TBof 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.
Help make SSR Smarter - Manage Backup Destination & Limit Number of Recovery Points Saved
Is anyone else struggling to coerce SSR 2013 R2 on Windows Server 2012 R2 to properly manage available backup disk space? SSR 2013 R2 offerstwo features: Manage Backup Destination, Settings, Monitor disk space usage for backup storage,and Define Backup Wizard, Options, Limit the number of recovery points saved, but neither of them appear to work. Monitor disk space usage is unavailable (it's greyed out) for backup drives used with backup jobs configured forUSB Disk Rotation. Limit the number of recovery points saved is messy when used with USB Disk Rotation backup drives because the Limit is the total number of recovery points spread among all the backup drives, which is overly constrictive like a snake. For example, SSR requires us tomanuallyanticipate and continually verify that all the recover points will fit on every backup drive. Additionally,the backup size better not increase, otherwise we have to manually decrease the Limit. And, watch out if some other space hungry files are written to the backup drive (who hasn't used their backup drive to write a quick file!). All this oversight and intervention is necessary when using the Limit function becasueSSR will NOT automatically delete the oldest backup, instead it will pop-up aninsufficient space message and sit there waiting for response. Meanwhile, days and weeks can pass with NO backup! All of this simple disk space checking activity can be more easily and efficiently handled by SSR instead of requiring the attention of an administrator. Thoughts?
