Our environment is as below
EV Server 10.0.1
File Server on Windows 2008 R2
Users are sometimes unable to view the placeholders when they open the shared drives from their PC's. However they are able to see unarchived files. This is intermittent. If the same folder is checked by the admin directly from File Server, all files including placeholders and non archived files are visible.
If anyone has an idea on this or a solution please inform.
Thanks!
VJ
Hello,
after I upgrade enterprise vault 10 sp1 to sp2 , when the archiving task run we get a lot of errors:
and all of the queue from msmq automatically purge.
Event id:
Log Name: Symantec Enterprise Vault
Source: Enterprise Vault
Date: 17/10/2012 16:32:11
Event ID: 8390
Task Category: Storage Online
Level: Error
Keywords: Classic
User: N/A
Computer: xxxxx
Description:
The EnterpriseVault.DirectoryConnection object reported an error.
The specified archive folder already exists
Log Name: Symantec Enterprise Vault
Source: Enterprise Vault
Date: 17/10/2012 16:32:11
Event ID: 6469
Task Category: Storage Online
Level: Error
Keywords: Classic
User: N/A
Computer: xxxxxx
Description:
An exception has occurred.
[Internal reference CArchiveAssister/RF/ce]
Log Name: Symantec Enterprise Vault
Source: Enterprise Vault
Date: 17/10/2012 16:32:12
Event ID: 13360
Task Category: Directory Service
Level: Error
Keywords: Classic
User: N/A
Computer: xxxxx
Description:
An error was detected while accessing the Vault Database 'EnterpriseVaultDirectory' (Internal reference: {CADODataAccess::ExecuteSQLCommand} [.\ADODataAccess.cpp, lines {1316,1318,1333,1351}, built Sep 12 21:03:54 2012]):
Description:
An attempt was made to create a resource lock name with invalid values for ParentFolderVEID[1F063BF399B0AD24DB5E3BF207FE02C4A1110000vltsrv01] and ContainerArchiveVEID[Not Supplied]
SQL Command:
CreateArchiveFolder
Additional Microsoft supplied information:
Source: Microsoft OLE DB Provider for SQL Server
Number: 0x80040e14
SQL State: 42000
Native Error: 00050000
HRESULT 0x80040e14
Log Name: Symantec Enterprise Vault
Source: Enterprise Vault
Date: 17/10/2012 16:32:12
Event ID: 8453
Task Category: Directory Service
Level: Error
Keywords: Classic
User: N/A
Computer: xxxxx
Description:
The EnterpriseVault.DirectoryService object reported an error.
The error code was 0x80040e14
Log Name: Symantec Enterprise Vault
Source: Enterprise Vault
Date: 17/10/2012 16:32:12
Event ID: 8390
Task Category: Storage Online
Level: Error
Keywords: Classic
User: N/A
Computer: xxxxxx
Description:
The EnterpriseVault.DirectoryConnection object reported an error.
0x80040e14
Internal references:
Error [0x80040e14]
{CDirectoryConnectionObject::CreateArchiveFolder} [.\DirectoryConnectionObject.cpp, lines {2874,2891,2893}, built Sep 12 21:03:57 2012]
Log Name: Symantec Enterprise Vault
Source: Enterprise Vault
Date: 17/10/2012 16:32:12
Event ID: 6469
Task Category: Storage Online
Level: Error
Keywords: Classic
User: N/A
Computer: xxxxxx
Description:
An exception has occurred.
[Internal reference CArchiveAssister/CF/ce] [
Details:
ContainerArchiveVEID: null
ParentFolderVEID: 1F063BF399B0AD24DB5E3BF207FE02C4A1110000vltsrv01
FolderName: Top of Information Store
FolderPath:
]
Log Name: Symantec Enterprise Vault
Source: Enterprise Vault
Date: 17/10/2012 16:32:12
Event ID: 13360
Task Category: Directory Service
Level: Error
Keywords: Classic
User: N/A
Computer: xxxxx
Description:
An error was detected while accessing the Vault Database 'EnterpriseVaultDirectory' (Internal reference: {CADODataAccess::ExecuteSQLCommand} [.\ADODataAccess.cpp, lines {1316,1318,1333,1351}, built Sep 12 21:03:54 2012]):
Description:
An attempt was made to create a resource lock name with invalid values for ParentFolderVEID[1F063BF399B0AD24DB5E3BF207FE02C4A1110000vltsrv01] and ContainerArchiveVEID[Not Supplied]
SQL Command:
CreateArchiveFolder
please advice me
Thanks Ronen
Hi everybody,
if users are working in groups and with ressource or shared mailboxes, sometime other users are trying to open Placeholders from colleagues. They do not have access to open this placeholder, because the user, which moved the placeholder to the ressource mailbox has archived the item in his own mailbox and moved the placeholder to the ressource or shared mailbox afterwards. So if the user still open the item, he gets the following message on the top of the content:
This item was archived by Enterprise Vault on ...... There was an error loading this item -- some functionality may not be available
In my opinion, it could be helpful, if the user knows, where´s the original location of this item. So the user can ask the owner to fix the problem, because this based to handling error by user. A possible
This item was archived by Enterprise Vault on ...... Archive ID: <ArchiveID><Alias.FQDN> Archive Name: <Archive Name> Folder Path: (eg.) \Mailbox\inbox\project1\test123 There was an error loading this item -- some functionality may not be available
The data can only be found in the client log and with assitance of the central IT in the VAC.
This would also be a good information for support.
regards
Thorsten
Hi all,
Right ive just done the EV course, No previous experience with EV and now my first EV fault!
All my users are working fine except one, who's emails have not archived since Aug. Now she was on client 7.5 and i upgraded her to 9.04 (server version is 8). I thought with 9.0.4 having logs it maybe able to shed some light but no luck. Can anyone point me in the right direction to start troubleshooting this. Shes in all the right groups and everyone else is working fine.
Thanks in advance guys!
Hi,
Apologies for the test entry, but I was continuously getting a symantec error when I was trying to upload for the last two days. My issue is as follows -
Hi,
User accesses a shared mailbox called Claims Admin GHO. She can see all the folder structure in the MyArchive under the inbox, which should have mirrored on the MyArchive under her vault. However, she does not have any folders under the Vault.
I checked the Archive explorer view in Enterprise Vault and it displays all the folders. However, she cant see it in the Outlook client.
We have added EV as an addin on Outlook ( 2003 ) client and we are using the Enterprise Vault Version 9.0.3.1221 and our Vault server is also of the same mode.
Could you please tell me what the issue is. For better clarity, I have pasted the screenshots of the client and the archive explorer view and the ev log files. Please advise.
For my part - the workarounds I have done so far -
(1) recreated the registry keys and downloaded the cache again
(2) reset the ev client
(3) removed and readded the Vault for personal and shared mailbox
Thanks in advance,
Rakesh S.
Hi
Running EV9.0.2
Our current 2 replicated Centeras are low on space so we're working with EMC to put in new, larger Centeras.
I have 5 separate vault stores, each containing a single partition. There are 5 Centera pools.
I've reviewed the procedure on pg 115 of "h6790-symantec-enterprise-vault-centera-wp.pdf" and have some questions:
EMC Centera migrations
In EV 6.0 or later multiple EMC Centera partitions can exist in a single Vault Store, which can be useful during EMC Centera hardware migrations
In this case, using the Vault Administration Console (VAC). all existing partitions pointing to the old EMC Centera will be closed, and new partitions will be created to archive against the new EMC Centera for all on-going data With this configuration, archiving activities mill not be impacted and users will be able to read from both closed and open vaults
BEST PRACTICE: How to migrate EV data from older to newer Centera hardware is as follows:
1. "Close" all current vaults, so that they are in read-only mode Consequently, no extra data is added to the old cluster, making this environment stable. - do they mean setting all vault stores into Backup mode? CONFUSING
2. Create as many vaults as currently exist, but pointing to the new cluster. All new writes/reads go there: the user should implement the virtual pools. and all other security configurations at this time (pools/profiles/PEA files, and so on). - do they mean creating new vault stores? If so, what about the existing archives on the old vault stores? CONFUSING
3. Now that the new environment is up and running. it is possible to start the migration process. one vault at a time This allows the company more control over the process, prioritizing the vaults to migate first. For each Vault:
Obtain the list of clips (savesets) to migrate (by vault). There are two ways for doing this:
4. The customer provides a clip list to EMC Centera (Support or Professional Services) to perform the migration
5. Once migrated and a reconciliation has been completed, the old vault, which was closed, is reconfigured to point to the new EMC Centera (connection string) - I assume this means the partiiton in the vault store is pointed at the new Centera IPs, and new PEA file.
6. Repeat steps 3 - 5 as needed
7. Once all vaults are migrated, the old cluster can be disposed.
we are currently running Enterprise Vault for Exchange Server version 8.0.5.1048 on our EV servers, but have upgraded our clients to version 9.0 (9.0.2.1061.0.dcom). Our client systems are XPSP3, and running Microsoft Office Outlook 2007 (12.0.6607.1000) SP3 MSO (12.0.6662.5000).
We now have a need to install the Administration Console on a number of client systems, but are having problems that appear to be related to the differences in versions.
When I tried to install the console, a message indicated that we cannot install an older version over a newer one. De-installing the client got us past this issue, and the install went OK, with the console functioning perfectly.
Of course, without the EV client installed, users of these systems are unable to view archived messages from Outlook. I was able to re-install the EV client and get Outlook working properly with it. But this caused the administration console to fail.
I tried installing the admin console to a different folder, but the EV client recognized where EV was located and installed to that location instead of its usual default folder.
Does anyone have any suggestions as to how we could get these two things coexisting on our XP systems without doing any version upgrades?
We will not be able to upgrade the servers to version 9 or 10 as originally planned, which I expect would resolve this issue. I suspect that installing version 9.0 on these XP clients would likely resolve the client-side issue, but would that be a problem if the EV servers were still at version 8? Note that these installs are for individuals that have been authorized only to export archives to PST files, so that is basically all they will see in the console.
Thanks in advance for any suggestions...
/ Al Dunbar
Hi,
I'm using Ev 8.0 SP4 and so far I cannot retrieve back old file which has been archived in my file server into my desktop,
instead of getting the file I want, I got this duplicated .tmp file which I cannot delete now ?
see the following:
any help would be greatly appreciated.
Thanks,
Hi, I'm using EV10 SP1, Exch2010. On both EV servers (mailbox and journal) I am getting a few of the below warnings.
Log Name: Symantec Enterprise Vault
Source: Enterprise Vault
Date: 10/19/2012 9:27:51 AM
Event ID: 7110
Task Category: Storage File Watch
Level: Warning
Keywords: Classic
User: N/A
Computer: server.domain
Description:
An invalid SIS part was encountered while doing watch file scan. Following further information is available.
Partition Name = Journal Vault Store 01 Ptn01
VaultStoreEntryId = 13E47CC3616170F46A80FAB9A914FD1991210000SVR01
ParentTransactionID = E09F7A90495C0F383D6C19C77EE10561
Invalid Reason = Verification failed for sis part when post processing Saveset with TID = [E0F727A7B3E8178299B5F849323CDA71].
Following sis part details are available:
FPDistinctionByte = [35]
FPHashPart1 = [-984110173]
UniqueId = [0].
Ran a dtrace of storagefilewatch, storagemanagement which couldnt capture all the info as it was running over the buffer (ran for 3 mins captured 100MB), but it did get:
StorageFileWatch) <4208> EV:H {CSisPartVerifierExistence::VerifySISPart:#358} _com_error exception: [SIS part validation failed. The stored SIS part size is different to the size expected. (0x80041bc2)]
Anyone seen this before?
Thanks,
Hello,
I am hoping for some suggestions on the kind of WORM hardware that is compatible with EV, for an Office < 100 employees and with email volume < 75-100GB/year. I have experience with NetApp SnapLock but it seems to be an overkill for the above requirements and I am hoping to hear what other shops do.
Thanks in advance,
TheEmptyMind!
Hello All.
When the EV server removed the network cable, I didn't stop the Enterprise Vualt Indexing Service.
My EV version is 10.0.2.
I check that the EVIndexVolumesProcessor, EVIndexQueryServer process not stop in task manager
Please help me.
This is the dtrace log.###########################################
Running in Terminal Services session...
Monitoring debug output from processes running in the console session
Monitoring debug output from processes running in the current Terminal Services session
1 23:15:24.172 [11820] (EVIndexAdminService) <5876> EV-M {VelocityProcessHealthMonitor.CheckProcessPriority} VelocityProcessPriorityMonitor is performing it's periodic check of process priorities
36 23:15:34.187 [11820] (EVIndexAdminService) <9252> EV-M {VelocityProcessHealthMonitor.CheckProcessPriority} VelocityProcessPriorityMonitor is performing it's periodic check of process priorities
40 23:15:34.920 [12988] EV: CProcessState::SetStopping
41 23:15:34.920 [12988] EV: CProcessState::SetStopping
42 23:15:34.920 [12988] EV: CProcessState::SetStopping
43 23:15:34.920 [12988] EV: CProcessState::SetStopping
44 23:15:34.920 [12988] EV: CProcessState::SetStopping
45 23:15:34.920 [12988] EV: CProcessState::SetStopping
46 23:15:34.920 [12988] EV: CProcessState::SetStopping
49 23:15:34.967 [8220] EV: CProcessState::SetStopping
50 23:15:34.967 [8220] EV: CProcessState::SetStopping
51 23:15:34.983 [1572] EV: CProcessState::SetStopping
52 23:15:34.983 [10108] EV: CProcessState::SetStopping
53 23:15:34.983 [7272] EV: CProcessState::SetStopping
54 23:15:34.983 [9104] EV: CProcessState::SetStopping
55 23:15:34.983 [2396] EV: CProcessState::SetStopping
56 23:15:34.983 [1572] EV: CProcessState::SetStopping
57 23:15:34.983 [7272] EV: CProcessState::SetStopping
58 23:15:34.983 [9956] EV: CProcessState::SetStopping
59 23:15:34.983 [9104] EV: CProcessState::SetStopping
60 23:15:34.983 [12880] EV: CProcessState::SetStopping
63 23:15:34.983 [9104] EV: CProcessState::SetStopping
68 23:15:34.998 [12880] EV: CProcessState::SetStopping
69 23:15:34.998 [8012] EV: CProcessState::SetStopping
78 23:15:34.998 [9956] EV: CProcessState::SetStopping
79 23:15:34.998 [12880] EV: CProcessState::SetStopping
82 23:15:34.998 [8012] EV: CProcessState::SetStopping
86 23:15:34.998 [4712] EV: CProcessState::SetStopping
88 23:15:34.998 [9956] EV: CProcessState::SetStopping
89 23:15:35.014 [8012] EV: CProcessState::SetStopping
102 23:15:35.014 [4712] EV: CProcessState::SetStopping
112 23:15:35.014 [4712] EV: CProcessState::SetStopping
122 23:15:35.029 [11820] (EVIndexAdminService) <12836> EV-L {ServiceBaseEx.OnStop} Stopping Indexing Service ...
123 23:15:35.029 [11820] (EVIndexAdminService) <11920> EV-L {ServiceBaseEx.Run} Starting Indexing Service shutdown routines.
124 23:15:35.029 [11820] (EVIndexAdminService) <11920> EV-L {ServiceBaseEx.Run} Executing OnPerformShutdown()
125 23:15:35.029 [11820] (EVIndexAdminService) <12836> EV-L {ServiceBaseEx.OnStop} Maximum allowed shutdown time [2100000 ms]
126 23:15:35.029 [11820] (EVIndexAdminService) <12836> EV-H {ServiceBaseEx.OnStop} Requesting additional time for Indexing Service to stop. Start time[오후 11:15:35], Log Time[오후 11:15:35], Elapsed Time[00:00:00 ms]
127 23:15:35.029 [11820] (EVIndexAdminService) <11920> EV-L {IndexAdminService.OnPerformShutdown} Starting Index Admin Service shutdown routines in a background thread
128 23:15:35.029 [11820] (EVIndexAdminService) <11920> EV-L {IndexAdminService.OnPerformShutdown} Miscellaneous indexing service shutdown tasks started
129 23:15:35.029 [11820] (EVIndexAdminService) <11920> EV-H {EVIndexAdminUtils.InvokeHelper} Calling Void <OnPerformShutdown>b__16(). Reference: Stopping StorageRevisionDiscovery
130 23:15:35.029 [11820] (EVIndexAdminService) <11920> EV-H {StoragePendingWorkDiscovery.Stop} StoragePendingWorkDiscovery stopping
131 23:15:35.029 [11820] (EVIndexAdminService) <11920> EV-L {IndexAdminService.OnPerformShutdown} Miscellaneous indexing service shutdown tasks completed (0 ms)
132 23:15:35.029 [11820] (EVIndexAdminService) <11920> EV-L {IndexAdminService.OnPerformShutdown} Stop child processes and unregister indexing service endpoints started
133 23:15:35.029 [11820] (EVIndexAdminService) <11920> EV-L {StateManager.UnregisterForDCOMClient} Inside UnregisterForDCOMClient
134 23:15:35.029 [11820] (EVIndexAdminService) <11920> EV-L {StateManager.UnregisterForDCOMClient} Unregistered IndexAminCOM with COM SCM with cookie 16
135 23:15:35.029 [11820] (EVIndexAdminService) <11920> EV-H {StateManager.StopServiceEndpoints} Stopping background thread for managing index service host.
136 23:15:35.029 [11820] (EVIndexAdminService) <6876> EV-L {StateManager.CloseServiceEndpoints} Inside CloseServiceEndpoints.
137 23:15:36.075 [11820] (EVIndexAdminService) <11920> EV-H {StateManager.StopServiceEndpoints} Stopped background thread for managing index service host.
138 23:15:36.075 [11820] (EVIndexAdminService) <11920> EV-L {StateManager.StopChildProcesses} Stopping child processes of Index Admin Service.
139 23:15:36.075 [11820] (EVIndexAdminService) <11920> EV-L {StateManager.StopChildProcesses} Stopping child processes: {EVIndexVolumesProcessor,EVIndexQueryServer}
140 23:15:36.075 [11820] (EVIndexAdminService) <11920> EV-L {ChildProcessManager.StopChildProcesses} Stopping child processes of Indexing Service [Max shutdown time: 900000 ms].
141 23:15:36.075 [11820] (EVIndexAdminService) <11920> EV-L {ChildProcessManager.StopChildProcesses} Stopping child process 'EVIndexVolumesProcessor'
142 23:15:36.075 [11820] (EVIndexAdminService) <11920> EV-L {ChildProcessManager.StopChildProcesses} Stopping child process 'EVIndexQueryServer'
143 23:15:36.075 [11820] (EVIndexAdminService) <11920> EV-L {ChildProcessManager.StopChildProcesses} Waiting for all child process '{EVIndexVolumesProcessor,EVIndexQueryServer}' to stop.
144 23:15:36.090 [11820] (EVIndexAdminService) <11100> EV-L {ChildProcessManager.AsyncStopChildProcess} Inside AsyncStopChildProcess to stop child process EVIndexVolumesProcessor of Indexing Service [Max shutdown time: 900000 ms].
145 23:15:36.090 [11820] (EVIndexAdminService) <11160> EV-L {ChildProcessManager.AsyncStopChildProcess} Inside AsyncStopChildProcess to stop child process EVIndexQueryServer of Indexing Service [Max shutdown time: 900000 ms].
146 23:15:36.090 [11820] (EVIndexAdminService) <11100> EV-L {ChildProcessManager.StopChildProcess} Stopping child process EVIndexVolumesProcessor of Indexing Service [Max shutdown time: 900000 ms].
147 23:15:36.090 [11820] (EVIndexAdminService) <11160> EV-L {ChildProcessManager.StopChildProcess} Stopping child process EVIndexQueryServer of Indexing Service [Max shutdown time: 900000 ms].
148 23:15:36.121 [11820] (EVIndexAdminService) <11100> EV~E |Event ID: 40966 A program fault has raised an exception.|Exception: 연결할 수 없는 네트워크에서 소켓 작업을 시도했습니다 203.235.217.29:6364|Diagnostic: Error Code is 10051|Type: System.Net.Sockets.SocketException|Reference: |Command Line: "C:\Program Files (x86)\Enterprise Vault\EVIndexAdminService.exe" -EntryID:1E8F05D6DE9A7F14FA1B9B41C49107E4D1710000VARCEV|Application Domain: EVIndexAdminService.exe|Process Id: 11820|Thread Id: 11100|Stack Trace: |Server stack trace: | 위치: System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)| 위치: System.Net.Sockets.Socket.Connect(EndPoint remoteEP)| 위치: System.Runtime.Remoting.Channels.RemoteConnection.CreateNewSocket(EndPoint ipEndPoint)| 위치: System.Runtime.Remoting.Channels.RemoteConnection.CreateNewSocket()| 위치: System.Runtime.Remoting.Channels.SocketCache.GetSocket(String machinePortAndSid, Boolean openNew)| 위치: System.Runtime.Remoting.Channels.Tcp.TcpClientTransportSink.SendRequestWithRetry(IMessage msg, ITransportHeaders requestHeaders, Stream requestStream)| 위치: System.Runtime.Remoting.Channels.Tcp.TcpClientTransportSink.ProcessMessage(IMessage msg, ITransportHeaders requestHeaders, Stream requestStream, ITransportHeaders& responseHeaders, Stream& responseStream)| 위치: System.Runtime.Remoting.Channels.BinaryClientFormatterSink.SyncProcessMessage(IMessage msg)|Exception rethrown at [0]: | 위치: System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)| 위치: System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)| 위치: KVS.EnterpriseVault.ProcessManagement.IAdminControl.Stop()| 위치: KVS.EnterpriseVault.ProcessManagement.ProcessManager.KVS.EnterpriseVault.ProcessManagement.IAdminControl.Stop()
149 23:15:36.121 [11820] (EVIndexAdminService) <11100> EV-L {ChildProcessManager.WaitForProcessState} Waiting for child process EV Index Volumes Processor to reach target state Stopped [Max wait time: 900000 ms].
150 23:15:36.121 [11820] (EVIndexAdminService) <11160> EV~E |Event ID: 40966 A program fault has raised an exception.|Exception: 연결할 수 없는 네트워크에서 소켓 작업을 시도했습니다 203.235.217.29:6366|Diagnostic: Error Code is 10051|Type: System.Net.Sockets.SocketException|Reference: |Command Line: "C:\Program Files (x86)\Enterprise Vault\EVIndexAdminService.exe" -EntryID:1E8F05D6DE9A7F14FA1B9B41C49107E4D1710000VARCEV|Application Domain: EVIndexAdminService.exe|Process Id: 11820|Thread Id: 11160|Stack Trace: |Server stack trace: | 위치: System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)| 위치: System.Net.Sockets.Socket.Connect(EndPoint remoteEP)| 위치: System.Runtime.Remoting.Channels.RemoteConnection.CreateNewSocket(EndPoint ipEndPoint)| 위치: System.Runtime.Remoting.Channels.RemoteConnection.CreateNewSocket()| 위치: System.Runtime.Remoting.Channels.SocketCache.GetSocket(String machinePortAndSid, Boolean openNew)| 위치: System.Runtime.Remoting.Channels.Tcp.TcpClientTransportSink.SendRequestWithRetry(IMessage msg, ITransportHeaders requestHeaders, Stream requestStream)| 위치: System.Runtime.Remoting.Channels.Tcp.TcpClientTransportSink.ProcessMessage(IMessage msg, ITransportHeaders requestHeaders, Stream requestStream, ITransportHeaders& responseHeaders, Stream& responseStream)| 위치: System.Runtime.Remoting.Channels.BinaryClientFormatterSink.SyncProcessMessage(IMessage msg)|Exception rethrown at [0]: | 위치: System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)| 위치: System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)| 위치: KVS.EnterpriseVault.ProcessManagement.IAdminControl.Stop()| 위치: KVS.EnterpriseVault.ProcessManagement.ProcessManager.KVS.EnterpriseVault.ProcessManagement.IAdminControl.Stop()
151 23:15:36.121 [11820] (EVIndexAdminService) <11160> EV-L {ChildProcessManager.WaitForProcessState} Waiting for child process EV Index Query Server to reach target state Stopped [Max wait time: 900000 ms].
158 23:15:37.042 [11820] (EVIndexAdminService) <12836> EV-H {ServiceBaseEx.OnStop} Requesting additional time for Indexing Service to stop. Start time[오후 11:15:35], Log Time[오후 11:15:35], Elapsed Time[00:00:02.0124258 ms]
161 23:15:39.054 [11820] (EVIndexAdminService) <12836> EV-H {ServiceBaseEx.OnStop} Requesting additional time for Indexing Service to stop. Start time[오후 11:15:35], Log Time[오후 11:15:35], Elapsed Time[00:00:04.0248516 ms]
174 23:15:41.067 [11820] (EVIndexAdminService) <12836> EV-H {ServiceBaseEx.OnStop} Requesting additional time for Indexing Service to stop. Start time[오후 11:15:35], Log Time[오후 11:15:35], Elapsed Time[00:00:06.0372774 ms]
175 23:15:43.079 [11820] (EVIndexAdminService) <12836> EV-H {ServiceBaseEx.OnStop} Requesting additional time for Indexing Service to stop. Start time[오후 11:15:35], Log Time[오후 11:15:35], Elapsed Time[00:00:08.0497032 ms]
176 23:15:44.187 [11820] (EVIndexAdminService) <9252> EV-M {VelocityProcessHealthMonitor.CheckProcessPriority} VelocityProcessPriorityMonitor is performing it's periodic check of process priorities
177 23:15:45.092 [11820] (EVIndexAdminService) <12836> EV-H {ServiceBaseEx.OnStop} Requesting additional time for Indexing Service to stop. Start time[오후 11:15:35], Log Time[오후 11:15:35], Elapsed Time[00:00:10.0621290 ms]
178 23:15:47.104 [11820] (EVIndexAdminService) <12836> EV-H {ServiceBaseEx.OnStop} Requesting additional time for Indexing Service to stop. Start time[오후 11:15:35], Log Time[오후 11:15:35], Elapsed Time[00:00:12.0745548 ms]
179 23:15:49.116 [11820] (EVIndexAdminService) <12836> EV-H {ServiceBaseEx.OnStop} Requesting additional time for Indexing Service to stop. Start time[오후 11:15:35], Log Time[오후 11:15:35], Elapsed Time[00:00:14.0869806 ms]
180 23:15:51.113 [11820] (EVIndexAdminService) <5876> EV-L {ProcessManager.LeaseRenewal} Renewing the lease of the object EV Index Volumes Processor. Current state of lease: Active
181 23:15:51.113 [11820] (EVIndexAdminService) <9252> EV-L {ProcessManager.LeaseRenewal} Renewing the lease of the object EV Index Query Server. Current state of lease: Active
182 23:15:51.129 [11820] (EVIndexAdminService) <12836> EV-H {ServiceBaseEx.OnStop} Requesting additional time for Indexing Service to stop. Start time[오후 11:15:35], Log Time[오후 11:15:35], Elapsed Time[00:00:16.0994064 ms]
183 23:15:52.018 [12988] (TaskController) <11408> EV~E |Event ID: 40966 A program fault has raised an exception.|Exception: 연결할 수 없는 네트워크에서 소켓 작업을 시도했습니다 203.235.217.29:5603|Diagnostic: Error Code is 10051|Type: System.Net.Sockets.SocketException|Reference: |Command Line: "C:\Program Files (x86)\Enterprise Vault\TaskController.exe" -EntryID:1C922E6D530E0A94FA138D015455BEE181011v00VARCEV|Application Domain: DefaultDomain|Process Id: 12988|Thread Id: 11408|Stack Trace: |Server stack trace: | 위치: System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)| 위치: System.Net.Sockets.Socket.Connect(EndPoint remoteEP)| 위치: System.Runtime.Remoting.Channels.RemoteConnection.CreateNewSocket(EndPoint ipEndPoint)| 위치: System.Runtime.Remoting.Channels.RemoteConnection.CreateNewSocket()| 위치: System.Runtime.Remoting.Channels.RemoteConnection.GetSocket()| 위치: System.Runtime.Remoting.Channels.SocketCache.GetSocket(String machinePortAndSid, Boolean openNew)| 위치: System.Runtime.Remoting.Channels.Tcp.TcpClientTransportSink.SendRequestWithRetry(IMessage msg, ITransportHeaders requestHeaders, Stream requestStream)| 위치: System.Runtime.Remoting.Channels.Tcp.TcpClientTransportSink.ProcessMessage(IMessage msg, ITransportHeaders requestHeaders, Stream requestStream, ITransportHeaders& responseHeaders, Stream& responseStream)| 위치: System.Runtime.Remoting.Channels.BinaryClientFormatterSink.SyncProcessMessage(IMessage msg)|Exception rethrown at [0]: | 위치: System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)| 위치: System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)| 위치: KVS.EnterpriseVault.ProcessManagement.IAdminControl.Stop()| 위치: KVS.EnterpriseVault.ProcessManagement.ProcessManager.KVS.EnterpriseVault.ProcessManagement.IAdminControl.Stop()
184 23:15:52.876 [6456] (EVIndexQueryServer) <10792> EV-L {SearchTaskGarbageCollector} [7ms] GC Collect and WaitForPendingFinalizers
185 23:15:53.141 [11820] (EVIndexAdminService) <12836> EV-H {ServiceBaseEx.OnStop} Requesting additional time for Indexing Service to stop. Start time[오후 11:15:35], Log Time[오후 11:15:35], Elapsed Time[00:00:18.1118322 ms]
186 23:15:54.202 [11820] (EVIndexAdminService) <5876> EV-M {VelocityProcessHealthMonitor.CheckProcessPriority} VelocityProcessPriorityMonitor is performing it's periodic check of process priorities
187 23:15:55.154 [11820] (EVIndexAdminService) <12836> EV~I |Event ID: 41300 The Indexing Service is pending shutdown.|Requesting additional time for shutdown routines....
188 23:15:55.154 [11820] (EVIndexAdminService) <12836> EV-H {ServiceBaseEx.OnStop} Requesting additional time for Indexing Service to stop. Start time[오후 11:15:35], Log Time[오후 11:15:55], Elapsed Time[00:00:20.1242580 ms]
189 23:15:57.166 [11820] (EVIndexAdminService) <12836> EV-H {ServiceBaseEx.OnStop} Requesting additional time for Indexing Service to stop. Start time[오후 11:15:35], Log Time[오후 11:15:55], Elapsed Time[00:00:22.1366838 ms]
190 23:15:59.179 [11820] (EVIndexAdminService) <12836> EV-H {ServiceBaseEx.OnStop} Requesting additional time for Indexing Service to stop. Start time[오후 11:15:35], Log Time[오후 11:15:55], Elapsed Time[00:00:24.1491096 ms]
191 23:16:01.191 [11820] (EVIndexAdminService) <12836> EV-H {ServiceBaseEx.OnStop} Requesting additional time for Indexing Service to stop. Start time[오후 11:15:35], Log Time[오후 11:15:55], Elapsed Time[00:00:26.1615354 ms]
200 23:16:03.203 [11820] (EVIndexAdminService) <12836> EV-H {ServiceBaseEx.OnStop} Requesting additional time for Indexing Service to stop. Start time[오후 11:15:35], Log Time[오후 11:15:55], Elapsed Time[00:00:28.1739612 ms]
201 23:16:04.217 [11820] (EVIndexAdminService) <9252> EV-M {VelocityProcessHealthMonitor.CheckProcessPriority} VelocityProcessPriorityMonitor is performing it's periodic check of process priorities
202 23:16:05.216 [11820] (EVIndexAdminService) <12836> EV-H {ServiceBaseEx.OnStop} Requesting additional time for Indexing Service to stop. Start time[오후 11:15:35], Log Time[오후 11:15:55], Elapsed Time[00:00:30.1863870 ms]
203 23:16:07.228 [11820] (EVIndexAdminService) <12836> EV-H {ServiceBaseEx.OnStop} Requesting additional time for Indexing Service to stop. Start time[오후 11:15:35], Log Time[오후 11:15:55], Elapsed Time[00:00:32.1988128 ms]
204 23:16:09.241 [11820] (EVIndexAdminService) <12836> EV-H {ServiceBaseEx.OnStop} Requesting additional time for Indexing Service to stop. Start time[오후 11:15:35], Log Time[오후 11:15:55], Elapsed Time[00:00:34.2112386 ms]
205 23:16:11.253 [11820] (EVIndexAdminService) <12836> EV-H {ServiceBaseEx.OnStop} Requesting additional time for Indexing Service to stop. Start time[오후 11:15:35], Log Time[오후 11:15:55], Elapsed Time[00:00:36.2236644 ms]
206 23:16:13.266 [11820] (EVIndexAdminService) <12836> EV-H {ServiceBaseEx.OnStop} Requesting additional time for Indexing Service to stop. Start time[오후 11:15:35], Log Time[오후 11:15:55], Elapsed Time[00:00:38.2360902 ms]
207 23:16:14.217 [11820] (EVIndexAdminService) <9252> EV-M {VelocityProcessHealthMonitor.CheckProcessPriority} VelocityProcessPriorityMonitor is performing it's periodic check of process priorities
208 23:16:15.278 [11820] (EVIndexAdminService) <12836> EV~I |Event ID: 41300 The Indexing Service is pending shutdown.|Requesting additional time for shutdown routines....
209 23:16:15.278 [11820] (EVIndexAdminService) <12836> EV-H {ServiceBaseEx.OnStop} Requesting additional time for Indexing Service to stop. Start time[오후 11:15:35], Log Time[오후 11:16:15], Elapsed Time[00:00:40.2485160 ms]
210 23:16:17.290 [11820] (EVIndexAdminService) <12836> EV-H {ServiceBaseEx.OnStop} Requesting additional time for Indexing Service to stop. Start time[오후 11:15:35], Log Time[오후 11:16:15], Elapsed Time[00:00:42.2609418 ms]
211 23:16:19.303 [11820] (EVIndexAdminService) <12836> EV-H {ServiceBaseEx.OnStop} Requesting additional time for Indexing Service to stop. Start time[오후 11:15:35], Log Time[오후 11:16:15], Elapsed Time[00:00:44.2733676 ms]
212 23:16:21.315 [11820] (EVIndexAdminService) <12836> EV-H {ServiceBaseEx.OnStop} Requesting additional time for Indexing Service to stop. Start time[오후 11:15:35], Log Time[오후 11:16:15], Elapsed Time[00:00:46.2857934 ms]
215 23:16:23.328 [11820] (EVIndexAdminService) <12836> EV-H {ServiceBaseEx.OnStop} Requesting additional time for Indexing Service to stop. Start time[오후 11:15:35], Log Time[오후 11:16:15], Elapsed Time[00:00:48.2982192 ms]
222 23:16:24.232 [11820] (EVIndexAdminService) <5876> EV-M {VelocityProcessHealthMonitor.CheckProcessPriority} VelocityProcessPriorityMonitor is performing it's periodic check of process priorities
223 23:16:25.340 [11820] (EVIndexAdminService) <12836> EV-H {ServiceBaseEx.OnStop} Requesting additional time for Indexing Service to stop. Start time[오후 11:15:35], Log Time[오후 11:16:15], Elapsed Time[00:00:50.3106450 ms]
224 23:16:27.352 [11820] (EVIndexAdminService) <12836> EV-H {ServiceBaseEx.OnStop} Requesting additional time for Indexing Service to stop. Start time[오후 11:15:35], Log Time[오후 11:16:15], Elapsed Time[00:00:52.3230708 ms]
225 23:16:29.365 [11820] (EVIndexAdminService) <12836> EV-H {ServiceBaseEx.OnStop} Requesting additional time for Indexing Service to stop. Start time[오후 11:15:35], Log Time[오후 11:16:15], Elapsed Time[00:00:54.3354966 ms]
226 23:16:31.377 [11820] (EVIndexAdminService) <12836> EV-H {ServiceBaseEx.OnStop} Requesting additional time for Indexing Service to stop. Start time[오후 11:15:35], Log Time[오후 11:16:15], Elapsed Time[00:00:56.3479224 ms]
237 23:16:33.390 [11820] (EVIndexAdminService) <12836> EV-H {ServiceBaseEx.OnStop} Requesting additional time for Indexing Service to stop. Start time[오후 11:15:35], Log Time[오후 11:16:15], Elapsed Time[00:00:58.3603482 ms]
238 23:16:34.248 [11820] (EVIndexAdminService) <5876> EV-M {VelocityProcessHealthMonitor.CheckProcessPriority} VelocityProcessPriorityMonitor is performing it's periodic check of process priorities
239 23:16:35.402 [11820] (EVIndexAdminService) <12836> EV~I |Event ID: 41300 The Indexing Service is pending shutdown.|Requesting additional time for shutdown routines....
240 23:16:35.402 [11820] (EVIndexAdminService) <12836> EV-H {ServiceBaseEx.OnStop} Requesting additional time for Indexing Service to stop. Start time[오후 11:15:35], Log Time[오후 11:16:35], Elapsed Time[00:01:00.3727740 ms]
241 23:16:37.415 [11820] (EVIndexAdminService) <12836> EV-H {ServiceBaseEx.OnStop} Requesting additional time for Indexing Service to stop. Start time[오후 11:15:35], Log Time[오후 11:16:35], Elapsed Time[00:01:02.3851998 ms]
242 23:16:39.427 [11820] (EVIndexAdminService) <12836> EV-H {ServiceBaseEx.OnStop} Requesting additional time for Indexing Service to stop. Start time[오후 11:15:35], Log Time[오후 11:16:35], Elapsed Time[00:01:04.3976256 ms]
243 23:16:41.439 [11820] (EVIndexAdminService) <12836> EV-H {ServiceBaseEx.OnStop} Requesting additional time for Indexing Service to stop. Start time[오후 11:15:35], Log Time[오후 11:16:35], Elapsed Time[00:01:06.4100514 ms]
244 23:16:43.452 [11820] (EVIndexAdminService) <12836> EV-H {ServiceBaseEx.OnStop} Requesting additional time for Indexing Service to stop. Start time[오후 11:15:35], Log Time[오후 11:16:35], Elapsed Time[00:01:08.4224772 ms]
245 23:16:44.263 [11820] (EVIndexAdminService) <9252> EV-M {VelocityProcessHealthMonitor.CheckProcessPriority} VelocityProcessPriorityMonitor is performing it's periodic check of process priorities
246 23:16:45.464 [11820] (EVIndexAdminService) <12836> EV-H {ServiceBaseEx.OnStop} Requesting additional time for Indexing Service to stop. Start time[오후 11:15:35], Log Time[오후 11:16:35], Elapsed Time[00:01:10.4349030 ms]
247 23:16:47.477 [11820] (EVIndexAdminService) <12836> EV-H {ServiceBaseEx.OnStop} Requesting additional time for Indexing Service to stop. Start time[오후 11:15:35], Log Time[오후 11:16:35], Elapsed Time[00:01:12.4473288 ms]
248 23:16:49.489 [11820] (EVIndexAdminService) <12836> EV-H {ServiceBaseEx.OnStop} Requesting additional time for Indexing Service to stop. Start time[오후 11:15:35], Log Time[오후 11:16:35], Elapsed Time[00:01:14.4597546 ms]
249 23:16:51.127 [11820] (EVIndexAdminService) <9252> EV-L {ProcessManager.LeaseRenewal} Renewing the lease of the object EV Index Query Server. Current state of lease: Active
250 23:16:51.127 [11820] (EVIndexAdminService) <5876> EV-L {ProcessManager.LeaseRenewal} Renewing the lease of the object EV Index Volumes Processor. Current state of lease: Active
251 23:16:51.502 [11820] (EVIndexAdminService) <12836> EV-H {ServiceBaseEx.OnStop} Requesting additional time for Indexing Service to stop. Start time[오후 11:15:35], Log Time[오후 11:16:35], Elapsed Time[00:01:16.4721804 ms]
252 23:16:52.890 [6456] (EVIndexQueryServer) <10792> EV-L {SearchTaskGarbageCollector} [6ms] GC Collect and WaitForPendingFinalizers
253 23:16:53.514 [11820] (EVIndexAdminService) <12836> EV-H {ServiceBaseEx.OnStop} Requesting additional time for Indexing Service to stop. Start time[오후 11:15:35], Log Time[오후 11:16:35], Elapsed Time[00:01:18.4846062 ms]
255 23:16:53.592 [9016] (EVIndexVolumesProcessor) <8288> EV:L CBaseDirectoryServiceWrapper::CreateDirectoryService() - Entry [m_nNumTries = 40]
256 23:16:53.592 [9016] (EVIndexVolumesProcessor) <8288> EV:L CBaseDirectoryServiceWrapper::CreateDirectoryService() - Successfully communicated with an EV Directory Service on the local machine
257 23:16:54.278 [11820] (EVIndexAdminService) <9252> EV-M {VelocityProcessHealthMonitor.CheckProcessPriority} VelocityProcessPriorityMonitor is performing it's periodic check of process priorities
258 23:16:55.526 [11820] (EVIndexAdminService) <12836> EV~I |Event ID: 41300 The Indexing Service is pending shutdown.|Requesting additional time for shutdown routines....
259 23:16:55.526 [11820] (EVIndexAdminService) <12836> EV-H {ServiceBaseEx.OnStop} Requesting additional time for Indexing Service to stop. Start time[오후 11:15:35], Log Time[오후 11:16:55], Elapsed Time[00:01:20.4970320 ms]
260 23:16:57.539 [11820] (EVIndexAdminService) <12836> EV-H {ServiceBaseEx.OnStop} Requesting additional time for Indexing Service to stop. Start time[오후 11:15:35], Log Time[오후 11:16:55], Elapsed Time[00:01:22.5094578 ms]
261 23:16:59.551 [11820] (EVIndexAdminService) <12836> EV-H {ServiceBaseEx.OnStop} Requesting additional time for Indexing Service to stop. Start time[오후 11:15:35], Log Time[오후 11:16:55], Elapsed Time[00:01:24.5218836 ms]
262 23:17:01.564 [11820] (EVIndexAdminService) <12836> EV-H {ServiceBaseEx.OnStop} Requesting additional time for Indexing Service to stop. Start time[오후 11:15:35], Log Time[오후 11:16:55], Elapsed Time[00:01:26.5343094 ms]
267 23:17:03.576 [11820] (EVIndexAdminService) <12836> EV-H {ServiceBaseEx.OnStop} Requesting additional time for Indexing Service to stop. Start time[오후 11:15:35], Log Time[오후 11:16:55], Elapsed Time[00:01:28.5467352 ms]
268 23:17:04.294 [11820] (EVIndexAdminService) <5876> EV-M {VelocityProcessHealthMonitor.CheckProcessPriority} VelocityProcessPriorityMonitor is performing it's periodic check of process priorities
269 23:17:05.589 [11820] (EVIndexAdminService) <12836> EV-H {ServiceBaseEx.OnStop} Requesting additional time for Indexing Service to stop. Start time[오후 11:15:35], Log Time[오후 11:16:55], Elapsed Time[00:01:30.5591610 ms]
I am setting up a trigger dtrace for a particular user as it appears they are having archiving issues
on the step that advises - "DT Trigger>include .... " - do i just include the users name /alias here ?
Thanks
When EV encounters a corrupt message and cannot archive it should log a event with specific mailbox details and message details so that the messaging admins can look into this more easily.
Specially when archiving leaver mailbox using zero day policy it would be very useful.
Yesterday we had EV server queue pile up issue for all EV servers, As we checked the server and confirmed the below information.
1. Confirmed that the MSMQ A5 queues are piled up.
2. Verified all the EV services are running fine.
3. Checked the server event log and confirmed that there was SQL database instance connectivity issue. Please find below event logs
Log Name: Symantec Enterprise Vault
Source: Enterprise Vault
Date: 10/19/2012 5:03:51 PM
Event ID: 13397
Task Category: Storage Online
Level: Warning
Keywords: Classic
User: N/A
Computer: ev03.stf.nus.edu.sg
Description:
The connection 'Provider=SQLOLEDB;Server=evdb01;Database=EVStudentVaultStore1;Trusted_Connection=Yes' was lost and the system is waiting to reconnect (Thread Id: 11336)
For more information, see Help and Support Center at http://evevent.symantec.com/rosetta/showevent.asp?EvtID=13397
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Enterprise Vault " />
<EventID Qualifiers="32772">13397</EventID>
<Level>3</Level>
<Task>47</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2012-10-19T09:03:51.000000000Z" />
<EventRecordID>1974692</EventRecordID>
<Channel>Symantec Enterprise Vault</Channel>
<Computer>ev03.stf.nus.edu.sg</Computer>
<Security />
</System>
<EventData>
<Data>Provider=SQLOLEDB;Server=evdb01;Database=EVStudentVaultStore1;Trusted_Connection=Yes</Data>
<Data>11336</Data>
</EventData>
</Event>
Log Name: Symantec Enterprise Vault
Source: Enterprise Vault
Date: 10/19/2012 5:04:06 PM
Event ID: 13395
Task Category: Directory Service
Level: Warning
Keywords: Classic
User: N/A
Computer: ev03.stf.nus.edu.sg
Description:
The connection 'Provider=SQLOLEDB;Server=evdb01;Database=EnterpriseVaultDirectory;Trusted_Connection=yes' was lost and the system failed to reconnect (Thread Id: 5492)
For more information, see Help and Support Center at http://evevent.symantec.com/rosetta/showevent.asp?EvtID=13395
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Enterprise Vault " />
<EventID Qualifiers="32772">13395</EventID>
<Level>3</Level>
<Task>21</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2012-10-19T09:04:06.000000000Z" />
<EventRecordID>1974697</EventRecordID>
<Channel>Symantec Enterprise Vault</Channel>
<Computer>ev03.stf.nus.edu.sg</Computer>
<Security />
</System>
<EventData>
<Data>Provider=SQLOLEDB;Server=evdb01;Database=EnterpriseVaultDirectory;Trusted_Connection=yes</Data>
<Data>5492</Data>
</EventData>
</Event>
Log Name: Symantec Enterprise Vault
Source: Enterprise Vault
Date: 10/19/2012 5:04:22 PM
Event ID: 6578
Task Category: Migrator Server
Level: Error
Keywords: Classic
User: N/A
Computer: ev03.stf.nus.edu.sg
Description:
Abnormal error occurred
Object: CSSASCache
Reference: RE(1)/fe
For more information, see Help and Support Center at http://evevent.symantec.com/rosetta/showevent.asp?EvtID=6578
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Enterprise Vault " />
<EventID Qualifiers="49156">6578</EventID>
<Level>2</Level>
<Task>29</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2012-10-19T09:04:22.000000000Z" />
<EventRecordID>1974726</EventRecordID>
<Channel>Symantec Enterprise Vault</Channel>
<Computer>ev03.stf.nus.edu.sg</Computer>
<Security />
</System>
<EventData>
<Data>CSSASCache</Data>
<Data>RE(1)/fe</Data>
<Binary>5468652053514C2064617461626173652073657276657220666F72202332206973206E6F7420617661696C61626C653A202020202020436865636B2074686174207468652053514C205365727665722069732076616C696420616E642069732072756E6E696E67202020202020202020496E7465726E616C207265666572656E6365282338292020204465736372697074696F6E3A202020202020233120202020204164646974696F6E616C204D6963726F736F667420737570706C69656420696E666F726D6174696F6E3A2020202020536F757263653A2020202020202023332020204E756D6265723A20202020202020233420202053514C2053746174653A2020202023352020204E6174697665204572726F723A20233620202048524553554C54202023372020202020202020283078383030343334346129</Binary>
</EventData>
</Event
4. As we verified EV database cluster services and confirmed that the cluster resource are up.
5. As a workaround we performed cluster SQL database failover and failed back and the issue got fixed. Again we had same issue EV issue today.
Kindly find the below update.
n What type of mail archiving Domino or Exchange used?
Exchange 2007
n Version of Enterprise vault used??
EV 8.0
n EV server platform?
All EV Server are running windows 2008 R2
Hi,
We want to upgarde 20x EV FSA from 10.0.1 to 10.0.2, so basically the steps would be
1. Stop services in all 20 EV FSA Server
2. Upgrade the first EV Server and start Directory service, wait for event log, start storage wait for event log and start all other services
3. Upgrade rest of the EV servers one by one and start services
Correct?
Many Thanks
Guys - we're trying to perform a read-only DR on our EV 9.0.4 production implementation. We have the following:
production -
2+1 MSCS with archiving and journaling (We do not use archiving and has been disabled)
DA/CA
DR -
1 stand alone server to recover Journaling
DA/CA
- Different SQL server
We have all of the data replicated via centera/SAN replication. Do we just follow the Data-only recovery to recover only the Journaling server in DR without the MSCS?
Anyone have any insight on any specific updates we have to make for non-clustering DR? We really just want a read only DR and run some sample searches in DR to make sure it recovered but we will not be writing anything in the DR site.
Any help would be appreciated.
Hi!
Would like to ask advice on how to prepare server for DA 10 install.
According Install guide if DA install on dedicated server, EV server has to be installed first and DA after.
I went to prereq and install all aplications except Ev server. When I start install it i am getting errors and this is right b/c i did not have installed MSMQ and other EV server prereq which not required based on DA installation guide.
Can you please help to be clear on this?
Thank you
Is there a reg key to disable Virtual Vault on a Computer
Hi where can I get the latest service pack for EV version 8.0 ?
and I wonder if there is any caveats or issue when performing the upgrade directly after downloading the Service pack file is completed ?
Hi All,
Do I need to exclude anything when installing the SEP client into the Symantec EV 8.0 SP4 ?
or should I just perform push install and then reboot as normal ?
