Can't append despite infinite append and free space
Hi, collecting logs to submit a ticket but figured I'd post here as well in case there's something easily/silly I'm missing. Backup servers to Tape media. Job A - fails because of shenanigans on our end. Some servers were done, others failed. Job B - Added the failed servers, trying to append to the same tape. Media Properties: Media set: Infinite overwrite and append (a set I created specifically for this purpose) Overwrite protected: Infinite - Do not overwrite Appendable until: Infinite - Allow append Media "Available capacity": 7.48 TB Job Details: Storage > Media Set > "When this job begins" - Append to media, overwrite if no appendable media is available." I tried the "append, cancel job if no appendable is available" but it would instantly cancel. Changed to the above and now instantly does "You cannot use the available media in the drive for this job because it is not overwritable" Anyone know why it's just refusing to append? A setting or something I'm missing maybe? Tried restarting the server, removing/pushing the tape back in, not really sure what else I can do.Solved65Views0likes7CommentsReimport journaling emails from M365 after incident
Hello, We had an issue with our EV Infrastructure for a few days, and now we have emails stuck in the "JRN_Errors" mailbox on M365. Is there a way to reimport those emails in EV Journaling ? Throught PST process or something else ? Thank you580Views0likes1Commentstatus: 26: client/server handshaking failed
I am trying to restore a single DB instance from Exchange in NBU 7.6.1 the problem is that I dont have support, So I have it difficult. Everytime I try to restore I keep getting the "handshake" error then 2810 error. The output: "06/08/2018 21:31:01 - begin Restore 06/08/2018 21:31:01 - Info bprd(pid=7064) Found (12.178) files in (1) images for Restore Job ID 23319.xxx 06/08/2018 21:31:01 - media 000613 required 06/08/2018 21:31:01 - restoring image dagpge_1532613051 06/08/2018 21:31:05 - Info bprd(pid=7064) Searched ( 6) files of (12.178) files for Restore Job ID 23319.xxx 06/08/2018 21:31:05 - Info bprd(pid=7064) Restoring from copy 1 of image created 07/26/18 08:50:51 from policy DAGPGE_correo 06/08/2018 21:31:06 - Info bpbrm(pid=7344) CORREONEW is the host to restore to 06/08/2018 21:31:06 - Info bpbrm(pid=7344) reading file list for client 06/08/2018 21:31:08 - connecting 06/08/2018 21:31:08 - Info bpbrm(pid=7344) starting bptm 06/08/2018 21:36:11 - Error bpbrm(pid=7344) handshake failure when starting tar on CORREONEW; read: 06/08/2018 21:36:11 - Info tar32(pid=0) done. status: 26: client/server handshaking failed 06/08/2018 21:36:11 - Error bpbrm(pid=7344) client restore EXIT STATUS 26: client/server handshaking failed 06/08/2018 21:36:11 - restored image dagpge_1532613051 - (client/server handshaking failed(26)); restore time 0:05:10 06/08/2018 21:36:11 - end Restore; elapsed time: 0:05:10 MS-Exchange-Server policy restore error (2810)" So now I am short of Ideas Attached to the mail you can see some screenshots of the steps I am following2.9KViews0likes4CommentsBackup Exec 16 - Temporary VMware folders are not cleaned from the Backup Exec data directory
HI All, So we started with Backup Exec 14 few years back and I've updated to BE 16 last week with latest patch due to following issue when Symantec could not resolve it. Issue: When backup up VM's, there are lot of Temporary folders been created in folder C:\Program Files\Symantec\Backup Exec\Data. (Folders name include VM's name and date ), and number of folders been created keep growing everyday. Troubleshoot done: I've logged a call with Symantec and for a week they did troubleshooting and today an Advanced tech called me and advised that this is a known issue and only work-around is to delete these folders manually ? Now I have had the same above issue while we were on BE 15, with all the patches installed, hence why I quickly upgraded to BE 16 to see if that resolve the issue. Symantec advance support tech directed me to this article ( https://www.veritas.com/support/en_US/article.000023219 ) which is according to the article was an issue on BE 2014. So I don't believe that Backup Exec 16 will have this now, will it ? And I can't accept an answer been deleting these folder manually every day as a solution. Does anyone experienced this kind of issue ? Cheers3.3KViews0likes3Comments