Insufficient disk space - stop on command files execution
Hi, We are using command files option to delete backup's files in the folder on few servers We have few USB disks for each backup, switched every day, and we cannot use Veritas/Symantec to keep only 1 copy of backup because backup is covering about 90% disk space and Veritas require space for 2 backup to keep 1 backup. So we are using .bat file with command: But when backup startting, it stucks on not enought space info. I have to click on "cancel" and command file is ececuting and backup starting. My command file settings: What I'm doing wrong? Problem is on the old Symentec revovery, but the same problem is on new Veritas 21.3 on another server
symantec system recovery 2013 r2
We are in the process of migrating from vmware to windows server 2019 hyper-v for a windows server 2012 r2. We are trying to restore a backup of the windows server 2012 r2 using symantec system recovery 2013 r2 and we are able to restore the reserved partition and D drive. When we restore the C drive the process gets to 99% and just stops. We searched the internet for a solution with no success. thanks Frank
SSR 2013 R2 update SQL 2012 sp2 to SP3 or update SSR 2013 r2 to VSR 2016
Hi could you help me please its about ofSSR 2013 R2 update SQL 2012 sp2 to SP3 or update SSR 2013 r2 to VSR 2016 i have installed service pack 6 for SSR2013 R2 but SQL 2012 SP2 continue , i need sql 2012 sp3 because security IT is requested , now i this if not possible , could I update from ssr2013 r2 to VSR 2016 desktop edition ? i have a license too someone have some links about of this please my email is adolpoagustini@gmail.com Thanks in advance have a nice day
To upgrade System Recovery 2013 R2 to System Recovery 16 or 18. Which do I need?
I use Veritas System Recovery Desktop Edition 2013 R2 to backup a desktop & laptop. They are independent computers. There is no network or server. My license expired. Do I need to upgrade to VSR 16 or would VSR 18 be a better choice? Please help.How to change a backup destination showing against historic backups
I have been asked to removea SAN attached volume from the SSR MS server as the array is end of life and no longer supported. The problem is that there were a number of backup policies that used this volume as a destination. Consequently there are numerous backups that are recorded against this volume. I have physically copied the backups to an alternative volume on the server using Windows command line however the backups will still be showing in SSR MS against the original destination. Is there an easy way to point it at a different location? How would I go about restoring a PC if I needed to restore using any of these backups that have been moved? Apologies if I'm not making sense, many thanks for any help.
