OUTLOOK: Can't open archived/stored emails
Hello, Since this week Microsoft updates, Outlook (2010/2016) can't open archived/stored items. Maybe, Outlook is blocking VBScript of custom forms. I'm using EV Client 10/11. To view an email, the users must "restore" to the mailbox and then open it. The message is: This item has been archived by Enterprise Vault. Click here to view the original item (this link doesn't work). Thank you.26KViews2likes27CommentsNDMP Backup with NETAPP v9
Hi, I trying to add a Netapp filer as NDMP data server into Backup Exec 16 (fully updated on 2016-02-21). I always get an error message "permission denied". See attachment of a print screen. The filer hosts several SVMs. ndmp node-scope-mode is disabeled. I have enabled debug mode on the filer. The error is: 00000010.00044551 023277ac Tue Feb 21 2017 10:36:54 +01:00 [kern_ndmpd:info:4145] A [src/rdb/SLM.cc 2511 (0x810404200)]: SLM 1000: current _sitelist is now: SLV <<1,1193>, 9b38433d-b29d-11e4-a313-00a0987d2136>. 00000010.00044552 023277ac Tue Feb 21 2017 10:36:54 +01:00 [kern_ndmpd:info:4145] [41423] ERROR: MD5 AUTH FAILED MD5 digest mismatch for 'backupexec' -- bad password I have tried with different password length without any success (8 and 16 chars). The NDMP backup is working fine with another backup solution (IBM TSM). Any idea is welcome on this topic. Thank you for your support. Regards, EricSolved7.1KViews0likes12CommentsError E000E020 on Backup Exec 2014.
Hello all, I would like to make a question regarding error E000E020, the error message I've been having in a remote site is: "e000e020 - The duration that this job is allowed to remain scheduled has passed. It will be rescheduled. Verify that storage is available and check the job's schedule settings. Ensure that there is enough time for it to begin running before it is considered missed." I've already checked the following article, and I think I can discard options A and C, as I don't think the options for option A is on Backup Exec 2014 (or maybe I am not finding them properly) and C we didn't have a time change here (therefor, there was no time change). So checking option B and normally we run the jobs as the following: Backup to Disk and then Duplicate to Tape. The disk we use for backup has a lot of free space left, as for the tape I wouldn't be surprised if it is not being change daily as it is a remote site where we don't have a lot of control (but then the error would only be on the duplicate job, not on the 1st backup). However the issue happens on the Backup job, where though I will attach some screenshots to see if it helps, I find odd the Job is set to start 9:00:00 PM, so it sometimes starts at 9:00:07 and it has end date of 9:00:04 (!?).Solved7KViews0likes3CommentsSearchFolderManager and error 8004011d
Hi, I am currently at a customer and he got a lot of processing errors. In cause, some mailboxe get folders with more than 40K items (some have 100K+). I then tried to run the searchfoldermanger on one mailbox to test but no can do. I get that error PS C:\Temp> SearchFolderManager.exe "/o=Tecteo/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=Porta bilite664" Managing search folders for mailbox: /o=ADInternal/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=Di Carmelo Luigi Error 8004011d Any idea why? I was thinking a MAPI error and started reviewed everything. Looks all correct. Let me know Cheers EDIT: I know I can change this max from 40K to higher in the registry but, would it not impact perfs?6.9KViews0likes11CommentsSnapshot / checkpoint a windows 2016 server with VSS (Error 4201)
Hi, Pre info: I have a good working snapshot policy with 10-15 clients that i take checkpoint everyday all of the working clients is windows 2012r2. Then i have one windows 2016 and that one gives me error (read more below). Netbackup 8.0 on Windowns Server 2012r2 (latest greatest patch). Client on host netbackup 8.0 (but shouldnt be neede due to checkpoint/snapshot). Client os Windows 2016 (latest greatest). HyperV cluster with Windows 2012r2 (almost latest greatest one patch behind). I added the host through browse as I did with the other, no worries there. then started manually task: gives me error: 2017-maj-10 12:52:05 - Info nbjm (pid=4932) starting backup job (jobid=514756) for client TBKONTEKWEB01, policy HYPV-SERVERS-DMZ, schedule Fullbackup_Daily 2017-maj-10 12:52:05 - Info nbjm (pid=4932) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=514756, request id:{8D546C81-5555-4E98-BB04-639EA9D9B67B}) 2017-maj-10 12:52:05 - requesting resource bkbackupmed01_dedup 2017-maj-10 12:52:05 - requesting resource bkbackupmaster.borlange.local.NBU_CLIENT.MAXJOBS.TBKONTEKWEB01 2017-maj-10 12:52:05 - requesting resource bkbackupmaster.borlange.local.NBU_POLICY.MAXJOBS.HYPV-SERVERS-DMZ 2017-maj-10 12:52:05 - granted resource bkbackupmaster.borlange.local.NBU_CLIENT.MAXJOBS.TBKONTEKWEB01 2017-maj-10 12:52:05 - granted resource bkbackupmaster.borlange.local.NBU_POLICY.MAXJOBS.HYPV-SERVERS-DMZ 2017-maj-10 12:52:05 - granted resource MediaID=@aaaab;DiskVolume=PureDiskVolume;DiskPool=bkbackupmed01_dedup;Path=PureDiskVolume;StorageServer=bkbackupmed01.borlange.local;MediaServer=bkbackupmed01.borlange.local 2017-maj-10 12:52:05 - granted resource bkbackupmed01_dedup 2017-maj-10 12:52:05 - estimated 0 kbytes needed 2017-maj-10 12:52:05 - begin Parent Job 2017-maj-10 12:52:05 - begin Hyper-V: Start Notify Script 2017-maj-10 12:52:05 - Info RUNCMD (pid=8816) started 2017-maj-10 12:52:05 - Info RUNCMD (pid=8816) exiting with status: 0 Operation Status: 0 2017-maj-10 12:52:05 - end Hyper-V: Start Notify Script; elapsed time 0:00:00 2017-maj-10 12:52:05 - begin Hyper-V: Step By Condition Operation Status: 0 2017-maj-10 12:52:05 - end Hyper-V: Step By Condition; elapsed time 0:00:00 Operation Status: 0 2017-maj-10 12:52:05 - end Parent Job; elapsed time 0:00:00 2017-maj-10 12:52:05 - begin Hyper-V: Create Snapshot 2017-maj-10 12:52:06 - started process bpbrm (pid=4272) 2017-maj-10 12:53:40 - Info bpbrm (pid=4272) TBKONTEKWEB01 is the host to backup data from 2017-maj-10 12:53:40 - Info bpbrm (pid=4272) reading file list for client 2017-maj-10 12:53:40 - Info bpbrm (pid=4272) start bpfis on client 2017-maj-10 12:53:40 - Info bpbrm (pid=4272) Starting create snapshot processing 2017-maj-10 12:53:41 - Info bpfis (pid=395212) Backup started 2017-maj-10 12:54:31 - Info bpfis (pid=395212) Backup type of VM is OFFLINE and configuration parameter [allowOfflineBackup] is not set. To backup this VM, set [allowOfflineBackup] configuration parameter. 2017-maj-10 12:54:31 - Critical bpbrm (pid=4272) from client TBKONTEKWEB01: FTL - vfm_freeze_commit: method: Hyper-V_v2, type: FIM, function: Hyper-V_v2_prepare 2017-maj-10 12:54:31 - Critical bpbrm (pid=4272) from client TBKONTEKWEB01: FTL - snapshot services: snapshot preparation failed: provider-private error. 2017-maj-10 12:54:31 - Critical bpbrm (pid=4272) from client TBKONTEKWEB01: FTL - vfm_freeze_commit: method: Hyper-V_v2, type: FIM, function: Hyper-V_v2_prepare 2017-maj-10 12:54:31 - Critical bpbrm (pid=4272) from client TBKONTEKWEB01: FTL - snapshot services: snapshot preparation failed: provider-private error. 2017-maj-10 12:54:31 - Critical bpbrm (pid=4272) from client TBKONTEKWEB01: FTL - snapshot processing failed, status 4201 2017-maj-10 12:54:31 - Critical bpbrm (pid=4272) from client TBKONTEKWEB01: FTL - snapshot creation failed, status 4201 2017-maj-10 12:54:31 - Warning bpbrm (pid=4272) from client TBKONTEKWEB01: WRN - ALL_LOCAL_DRIVES is not frozen 2017-maj-10 12:54:31 - Info bpfis (pid=395212) done. status: 4201 2017-maj-10 12:54:31 - end writing Operation Status: 4201 2017-maj-10 12:54:31 - end Hyper-V: Create Snapshot; elapsed time 0:02:26 2017-maj-10 12:54:31 - begin Hyper-V: Stop On Error Operation Status: 0 2017-maj-10 12:54:31 - end Hyper-V: Stop On Error; elapsed time 0:00:00 2017-maj-10 12:54:31 - begin Hyper-V: Delete Snapshot 2017-maj-10 12:54:31 - end Hyper-V: Delete Snapshot; elapsed time 0:00:00 2017-maj-10 12:54:31 - Info bpfis (pid=395212) done. status: 4201: Incorrect snapshot method configuration or snapshot method not compatible for protecting backup selection entries. 2017-maj-10 12:54:32 - started process bpbrm (pid=7280) 2017-maj-10 12:55:21 - Info bpbrm (pid=7280) Starting delete snapshot processing 2017-maj-10 12:55:23 - Info bpfis (pid=396560) Backup started 2017-maj-10 12:55:23 - Warning bpbrm (pid=7280) from client TBKONTEKWEB01: cannot open C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.TBKONTEKWEB01_1494413525.1.0 2017-maj-10 12:55:23 - Info bpfis (pid=396560) done. status: 4207 2017-maj-10 12:55:23 - Info bpfis (pid=396560) done. status: 4207: Could not fetch snapshot metadata or state files 2017-maj-10 12:55:23 - end writing Operation Status: 4207 2017-maj-10 12:55:23 - begin Hyper-V: End Notify Script 2017-maj-10 12:55:23 - Info RUNCMD (pid=11596) started 2017-maj-10 12:55:23 - Info RUNCMD (pid=11596) exiting with status: 0 Operation Status: 0 2017-maj-10 12:55:23 - end Hyper-V: End Notify Script; elapsed time 0:00:00 Operation Status: 4201 Incorrect snapshot method configuration or snapshot method not compatible for protecting backup selection entries (4201) Regards PoNutsSolved4KViews0likes6CommentsNetBackup status code: 6000 Message: The provided path is not whitelisted
I am able to successfully browse the file/folder structure of the VM backup from the NSS portal, select a file, and initiate the restore, although the restore attempts failed. NetBackup status code: 6000 Message: The provided path is not whitelistedSolved3.6KViews0likes1CommentBackup 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.3KViews0likes3Commentsprocess could not be started due to the following error: Unable to access proccess Manager
Hey After windows update 12.04 our Enteprise Vault 10.0.3.190 have been struggeling starting the indexing service. When it tries to start i see diffrent errors in eventlog and dtrace. the most common error is: The EVExchangeWebServicesProxy process could not be started due to the following error: Unable to access Process Manager The EVTaskGuardian process could not be started due to the following error: Unable to access Process Manager The EVStgOfflineOpns process could not be started due to the following error: Unable to access Process Manager The EVStorageQueueBroker process could not be started due to the following error: Unable to access Process Manager Tried uninstalling the Windows updates for Windows os, had no effect. Saw it was alot of Office updates aswell but i havent removed them yet. Is there anyone who have the same problem or can help me out?1.4KViews0likes2Comments