Veritas System Recovery Management Solution
Hi! Why I don't see my job (backup policy and independent) in Veritas System Recovery Management Solution? There are exist and everything works from computer. I have administrators account and should see every task. In old server (ssr2013) there was no problem.Solved1.5KViews0likes4CommentsEmail notifications in VSR 16 are very cryptic
Hi - I just upgraded from SSR 2013 R2 to 16. I feel right at home except that the email notifications are a pain. They've gone from simple, readable messages like this: Date: 11/17/2017 1:29:23 AM Notification Type: Info Priority: High Description: Info 6C8F1F7E: A scheduled incremental recovery point of drive F:\ was created successfully. to this: Date: 11/17/2017 4:02:24 AM Notification Type: Info Priority: High Description: Result (0x6c8f1ff2 34 VPRO_INFO_SCHEDULED_BACKUP_INC_JOB Args [1] Arg (0xbab000d 24 Full Backup - All Drives);)<9 1.0-*-*-* > Can they be changed back, or failing that, can I get a glossary somewhere so I can at least figure what the heck it means?Solved2.3KViews0likes9CommentsVSR 16 Backup Destination Unavailable! - I'm stumped.
We recently upgraded to VSR 16 and since the upgrade, backups have been failing with the following errors: -Cannot create the recovery point. --Error E7D10041: Unable to establish a network connection to \\"servername"\symantec_system_recovery ---Error EBAB03F1: Following Operating System error occurred while performing requested operation: 'The specified network password is not correct.' (UMI:V-281-3215-1005) Keep in mind that there were no changes made to the policies, the packup destination, username or password for the destination. These clients were backing up without an issue on 2013 R2. Furthermore, in testing, I have setup a new system with VSR 16 and assigned to the same policy. The new system is able to backup just fine. This really isn't making much sense and is rather frustrating. I've even created a new policy and applied the policy to two systems with the same results. New system continues to backup while the other continues to have issues. One workaround is to manually enter the backup destination on systems that are having an issue, however this does not resolve the problem and it is not a suitable solution for the number of systems that are having this problem and it also does not address the cause in the first place. Any help would be much appreciated.2.1KViews0likes6Comments