Exchange

33 Topics

exchange backup failed with status code 4200
Dear all , i have an backup enviroment contains solarois master server and windows media server i have alot of exchange databases distributed on 3 nodes "dag " recently i noticed that alot of database failed with status code 4200 " Operation failed: Unable to acquire snapshot lock (4200) on the same node and other policies complete successfully on the same node most of my backup policies start from 5pm till 4 am next day i have searched for the status code error , it indicate that the snapshot processis taken by another process but i can't point to the main problems i think that the problem due to current running jobs to same node , but every thing was running successfully with out making any changes to the enviroment , when i run the failed policies during the working hours , it complete successfully with out any errors another databases on other nodes of the cluster running successfully
sa2
8 years ago Place NetBackup
3.8KViews
0likes
7Comments
Exchange 2016 CU5 Support
Recently Microsoft released Cumulative Update 5 for Exchange 2016. This update made significant changes to the Mailbox Database structure. When CU5 is applied to Exchange 2016, Backup Exec is no longer able to restore individual items from a GRT-based backup of Exchange 2016. If restoring individual items is important to you, you may want to wait to apply CU5. If CU5 is applied, the current workaround should you need to restore individual items is to restore to a recovery database and then use the tools in Exchange 2016 to restore the individual items. For more information see technical Article 000126392. The Veritas Backup Exec team is currently working on a fix to address this issue and will release an On-Demand Patch (ODP) as quickly as possible. To stay up-to-date on this issue and be notified when the ODP is available, please subscribe to technical Article 000126392 BackupMikko
BackupMikko
8 years ago Place Backup Exec
3.4KViews
5likes
2Comments
status: 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 following
manol4ik
6 years ago Place NetBackup
2.8KViews
0likes
4Comments
Backup 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?
KevinTCCA
7 years ago Place Backup Exec
2.6KViews
0likes
6Comments
Backup 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?
Solved
AlexeyCherepov
6 years ago Place Backup Exec
2.2KViews
0likes
4Comments
Event 3479 Could not add all the mailboxes to the processing queue
we have EV 11.0.1. CHF2 since a few days if the exchange Mailbox archiving Task is starting we get following message in the event viewer: EVENT 3479 Could not add all the mailboxes to the processing queue. The mailboxes that could not be added to the queue will be processed on the next run of the archiving task. Mailboxes added to queue: 0 of 1154 MSMQ name: DIRECT=OS:SW-xxxxx-xxxxx\Private$\Enterprise Vault Exchange Mailbox Task for SW-xxxxxx-xxxxx 161109073116 A5 Run ID: Scheduled_20161109_074803 Exchange Server: SW-xxxxxx-xxxxxx Task name: Exchange Mailbox Archiving Task for SW-xxxxxx-xxxxxx so at the end NO Mailboxes are add the the queue. If i look in the Report i can see it is "running" but nothing happens. next day same Message same result. If i try to do a run now with a single Mailbox it will run successfull if i try to do a run now with more then one Mailboxes i can see every second a new report entry and come, ends and start again... in a neverending loop. Only clear the MSMQ queue solve this. If it try to do a run now with "All Mailboxes" i have the same result as with the normal scheduled run. I tried to delete the queues. same result as before I tried to delete the Mailbox Task and define a new one. Same result as before I have done no changes in EV, and the Exchange Guys told me they also have made no changes any ideas? Thanks Kai
Solved
Kai_8z
8 years ago Place Enterprise Vault
2KViews
0likes
2Comments
EV Exchange feature enquiry
EV Exchange can be customized to exclude the archive all subfolders under In box. Would like to ask whether EV 12.1 can perform the following : 1. Only achieve the first level of folders under IN box through GUI 2. If one know the names of all subfolders, KB 100016636 ( https://www.veritas.com/support/en_US/article.100016636 ) mention the way provided one know the subfolder names. My question is whether there is anysimplerway to achieve the same purpose ? One cannot know that for all users. Thanks
SL2018
7 years ago Place Enterprise Vault
1.9KViews
0likes
4Comments
Exchange Policy doesn't show Information Store
Hi, First we created an Exchange Policy and specified the Microsoft Information Store to be backed up, and everything went fine. After we opted to delete this policy and create a new one, this time when we tried to add the Microsoft Information Store it didn't show up ! So we checked the permisions and all prerequisites. After 2 days we tried again and it showed up and backed up succesfully , and then we wanted to change the destination storage and here the same issue appeared again. Thank you
Solved
lwalid
8 years ago Place NetBackup
1.8KViews
0likes
9Comments
Backing up Hyper-V exchange server
Hi. I have an Hyper V host on it I have my exchange server (virtual). I wont to backup it in that way that iw will be posible to restore the exchange vhd if needed and restor a specific mail from any of my exchange data bases. Is it posible? Wht is the best way to do this? thanks a lot.
Alex13
7 years ago Place Backup Exec
1.8KViews
0likes
9Comments
Journaling in Mixed Exchange 2010 / 2016 Environment
Running EV 12.0.3 in mixed Exchange 2010 / 2016 environment. Journaling is configured in Exchange 2010. EV Journaling and Archiving tasks running against Exchange 2010. New System Mailbox and EV Archiving task created and running against Exchange 2016. No mailboxes migrated from Exchange 2010 to Exchange 2016. What do I need to do with journaling before starting the migration of Exchange 2010 mailboxes to Exchange 2016?
Dan_A1
6 years ago Place Enterprise Vault
1.7KViews
0likes
4Comments