Restore GRT backup of Exchange Information Stores to TAPE fails with error V-79-57344-759
Hi! Restore GRT backup of Exchange Information Stores to TAPE fails with error V-79-57344-759. Backup Exec copy backup form type to local disk processing files and failed when try connect it on exchange server. Finded: GRT backup of Exchange Information Stores to TAPE fails with error: "VFF Open Failure. This can be caused by low memory or disk resources." https://www.veritas.com/support/en_US/article.100001258 But I can't create: Key : HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VirtFile Value: VFF Extended Timeout Type: DWORD The Maximum value is (Decimal) 600 seconds. Start out at 240 seconds at first. If error still occurs then 480, before going to 600. Restart all the Backup Exec Services for the changes to take effect. Error - Canoot create value: Error writting to the registry. Try stop all Backup Exec service.1.5KViews0likes2CommentsRestore serial appointment
We tried to restore a Outlook serial appointment which one was edit on element level every time when the meeting occur. After the successful restore we have the only unknown Items in the Series. Is this normal? I'm grateful for any help! Thanks in advance!628Views0likes0CommentsBE15 Restore Wizard Doesn't Display Exchange Mailboxes Using GRT
I am running BE15 on Windows Server 2016 backing up an Exchange 2016 CU17 mailbox server. When attempting to perform a restore (Microsoft Exchange mailbox items), when I expand the backup instance and database, no mailboxes are shown. Anyone help/ideas would be appreciated!861Views0likes1CommentDo I need to backup Exchange Server flat files?
We have on-premise Exchange servers in a DAG, and presently have three backup jobs related to Exchange and Active Directory. Backup #1 gets the Microsoft Information Store on one of the Exchange servers. This job gets all the Databases and Logs. Backup #2 is a Simplified Disaster Recovery backup of the Domain Controller, which includes drives, System State and Active Directory. Backup #3 is a Simplified Disaster Recovery backup of the Exchange Server, which includes the Drives and System State, but not the Microsoft Information Store. Do I need the third backup job? Would I ever need to restore something from the flat files or System State of the Exchange Server?641Views0likes1CommentConfiguration Backup Exec 2014 V-Ray for Exchange 2013 & SQL Server 2012
Hi, We have Backup Exec 2014 V-Ray and two hyper-v virtual machine with Windows Server 2012 R2. On first machine is installed Exchange 2013 with 3 virtual disk: 1 - System, 2 - Database, 3 - Logs. On second machine is installed SQL Server 2012 with 3 virtual disk: 1 - System, 2 - Database, 3 - Logs. This is my configuration for backup job for this two virtual machine: Is the above configuration is correct for these applications? Is BackupExec 2014 correct backup SQL Server i Exchange with multiple virtual disk ? Will the integrity of the data be retained after the virtual machine has been restored? THX1.4KViews0likes3CommentsBackup Exec 15 restore to Exchange 2016 mailbox fails as EWS error/credentials error
Hello, I currently have the following problem: If I want to restore a mailobject from a full backup of our Exchange 2016 databases it fails with the following error: Final error: 0xe0000388 - Cannot log on to EWS with the specified credentials. Review the resource credentials for the job, and then run the job again. Final error category: Resource Errors So after this I checked the credentials and the DAG host says "Test failed, Test recommended", which is weird because backups work without a problem, which shouldn't be, right? I then found this article and checked all the steps, which seem to be OK (I even put the account I have configured for the backup in the administrators group on our CAS servers), the only difference being that it is not our default account, but I have tested it with the default too and the result is the same (i.e. the test fails). I have also checked the EWS login with https://mail.domain.com/EWS/Exchange.asmx and I get the service page, so the login does work. Does anyone have any idea how to fix this problem?2.6KViews0likes6CommentsBackup Exec 16 and GRT restore MS Exchange 2007
Hello guys. I have new-installed Veritas Backup 16 (on Windows Server 2012R2) I have MS Exchange 2007 on Windows Server 2003 R2 x64bit I configure everyday B2D-job with full backup of MS Exchange bases with GRT (only Exchange-bases no any other files) And I have two problems with it 1. Every job is finished with error V-79-57344-65193 for some of Information store (not for all, only for two from three). I check this article in KB and do all reccomendations but no result 2. When i try to restore any item from GRT-backup (for example one email) i get BROWSE FAILURE. The volume that is used for the staging location must be a writable NTFS volume that is local to the Backup Exec server. Also, the volume must have the same sector size as the volume from which the Exchange log files were backet up. or for some cases the next Unable to complete the operation. The following error was returned when opening the Exchange Database file: '-546 The log file sector size does not match the sector size of the current volumn. " I check sector size for Exchange Server and for Backup Exec server(special folder on local disk, which i point GRT-restore path in Global Settings Backup Exec. Exchange: Bytes Per Sector : 512 Bytes Per Cluster : 4096 Bytes Per FileRecord Segment : 1024 Backup Exec: Bytes Per Sector : 512 Bytes Per Physical Sector : 4096 Bytes Per Cluster : 4096 Bytes Per FileRecord Segment : 1024 So it looks like the same. Anyone can helps me to understand what i'm doing wrong?Solved2.2KViews0likes4Commentsstatus: 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.9KViews0likes4Comments