Video Screencast Help

Upgrading indexes to 64bit and the cachelocation

Created: 19 Oct 2012 • Updated: 08 Nov 2012 | 6 comments
GertjanA's picture
This issue has been solved. See solution.

Hello all,

Looking for experience from the field:

I am in a relatively large environment (10mbx archiving servers) where there is extensive use of VaultCache for laptop-users.

The cache location (currently set at the default of 20GB with 10 concurrent connections) is on all these servers around 18 to 19gb.

If we upgrade to EV10, when starting to upgrade indexes, what is the best way to use this cache-location?

If I keep the settings as they are, does this mean upgrading indexes will either not happen (due to cache-location being full) or will it go really slow (due to waiting for space to become available). IT is possible to extend the cache-location location, but not with very large amounts.

Would it be best to disable VaultCache for laptop users during the time indexes are upgraded?

Would i need to add new servers, using these as indexing servers only? Will the upgrade of the indexes use the location on the new indexservers, or will it use the cache-location on the server where the 32bit index sits?

Is it possible to 'seperate' the cache used for index upgrades and VC builds?

IF you have had a similar environment, how did you do it?

Thanks.

Gertjan

Comments 6 CommentsJump to latest comment

Rob.Wilcox's picture

AFAIK the cache location is used a bit like Exchange Server (or SQL Server) RAM.  It'll all be used up if it can be, by whatever grabs it first.  However that being said is the volume it sits on just 20 Gb?  Or just the setting in the VAC?  I _think_ Vault Cache DB files will be deleted to free up space when the index rebuild starts.

GertjanA's picture

Hi Rob,

No, the disks are a little larger, but as we need to upgrade to w2008r2 anyway, that might be 'adjustable'.

Can you find out the i_think_ ?

Thank you, Gertjan, MCSE, MCITP,MCTS, SCS, STS
Company: www.t2.nl

www.quadrotech-it.com

www.symantec.com/visi

JesusWept3's picture

the DB files will be deleted upon successful download from the customer, but again thats a _think_ issue, maybe Ben Heymink could tell you on here (since VC/VV is his baby)

Rob.Wilcox's picture

I can confirm that the db files will be deleted when a client downloads it succsesfully.  The question becomes :

What happens if the cache location is 'full' (and another db create request comes in)

What happens if the cache location is 'full' (and an index upgrade, or rebuild request is issued)

Ben Heymink's picture

Someone called? :-)

Index rebuilds in EV10 don't make use of the Cache location, so rebuild away! And in fact, the component responsible for monitoring that cache location (and deleting files if needed) is looking specifically at the size of the four folders within it combined, anything outside of these folders won't count towards the cache size:

  • ByteRange
  • Search
  • Upload
  • VCBuilds

Index rebuilds will happen wherever your Index Locations are set to, so as long as you have the disk space, you're good to go, Vault Cache shouldn't be affected.

 
SOLUTION
Rob.Wilcox's picture

And with regards to that little cache location:

2,351 15:33:47.494 [1,972] (EVMonitoring) <4084> EV-H {CacheManager} A file rename event has occurred in the cache; updating File list..
2,352 15:33:47.494 [1,972] (EVMonitoring) <4084> EV-H {CacheManager} (Old file: 18378D6688DDF754589DF8D82ECDF12261p10000evsql.ev.local.tmp)
2,353 15:33:47.494 [1,972] (EVMonitoring) <4084> EV-H {CacheManager} (New file: 18378D6688DDF754589DF8D82ECDF12261p10000evsql.ev.local.pst)
2,354 15:33:47.523 [1,972] (EVMonitoring) <4084> EV-H {CacheManager} Adding file to file list..
2,355 15:33:47.523 [1,972] (EVMonitoring) <4084> EV-H {CacheManager} Updating cache Size: Old:0
2,356 15:33:47.523 [1,972] (EVMonitoring) <4084> EV-H {CacheManager} Updating cache Size: New:580297728
2,357 15:33:47.552 [1,972] (EVMonitoring) <3532> EV-H {ContentCacheAssembler.CB_FinishedJob} CCRM: CCB Notify: Finished Job 18378D6688DDF754589DF8D82ECDF12261p1
0000evsql.ev.local
2,358 15:33:47.554 [1,972] (EVMonitoring) <3532> EV-H {ContentCacheRequestManager.CleanUpThread} CCRM: Cleaning Up thread (0) on Job 18378D6688DDF754589DF8D82EC
DF12261p10000evsql.ev.local...
2,359 15:33:47.554 [1,972] (EVMonitoring) <3532> EV-H {ContentCacheRequestManager.GenerateFinalXML} CCRM: Generating final XML for CleanUpThread..
2,361 15:33:47.554 [1,972] (EVMonitoring) <3532> EV:L CBaseDirectoryServiceWrapper::CreateDirectoryService() - Entry [m_nNumTries = 1]
2,362 15:33:47.555 [1,972] (EVMonitoring) <3532> EV:L CBaseDirectoryServiceWrapper::CreateDirectoryService() - Will try to connect to EV Directory Service on EV
SQL
2,363 15:33:47.624 [1,972] (EVMonitoring) <3532> EV:L VaultCoCreateInstanceEx: IsLocalMachineExtendedCheck returned true for server [EVSQL]  as the IP Address m
atched that of the local machine
2,366 15:33:47.662 [1,972] (EVMonitoring) <3532> EV:M CDirectoryVaultObject::GetAttributeListFromType Attribute list for type AdminJobEntry : AdminJobEntryId,Si
teEntryId,UniqueJobId,JobType,JobState,JobDescription,JobAuthor,RestartJob,RetryCount,StartTime,EndTime,Parameters
2,370 15:33:47.662 [1,972] (EVMonitoring) <3532> EV:L CBaseDirectoryServiceWrapper::CreateDirectoryService() - Entry [m_nNumTries = 40]
2,371 15:33:47.690 [1,972] (EVMonitoring) <3532> EV:L CBaseDirectoryServiceWrapper::CreateDirectoryService() - Successfully communicated with an EV Directory Se
rvice on the local machine
2,372 15:33:47.728 [1,972] (EVMonitoring) <5076> EV-H {ContentCacheAssembler.PerformBuild} CCRM: Exiting build thread.
^^ The above is a single DB file being built from a client request
 
2,417 15:34:37.961 [1,972] (EVMonitoring) <4080> EV-H {ContentCacheFileServer.HouseKeeper} CCFS: Checking for unused download slots...
^^^ Occurs once per minute
 
2,436 15:35:10.136 [1,972] (EVMonitoring) <4084> EV-H {CacheManager} A file rename event has occurred in the cache; updating File list..
2,437 15:35:10.136 [1,972] (EVMonitoring) <4084> EV-H {CacheManager} (Old file: 28378D6688DDF754589DF8D82ECDF12261p10000evsql.ev.local.pst)
2,438 15:35:10.136 [1,972] (EVMonitoring) <4084> EV-H {CacheManager} (New file: A28378D6688DDF754589DF8D82ECDF12261p10000evsql.ev.local.pst)
2,439 15:35:10.162 [1,972] (EVMonitoring) <4084> EV-H {CacheManager} Adding file to file list..
2,440 15:35:10.162 [1,972] (EVMonitoring) <4084> EV-H {CacheManager} Updating cache Size: Old:580297728
2,441 15:35:10.162 [1,972] (EVMonitoring) <4084> EV-H {CacheManager} Updating cache Size: New:1160595456
^^ Now I start to slowly .. copy a file in, and rename it...
 
2,454 15:35:23.373 [1,972] (EVMonitoring) <4084> EV-H {CacheManager} A file rename event has occurred in the cache; updating File list..
2,455 15:35:23.373 [1,972] (EVMonitoring) <4084> EV-H {CacheManager} (Old file: 38378D6688DDF754589DF8D82ECDF12261p10000evsql.ev.local.pst)
2,456 15:35:23.373 [1,972] (EVMonitoring) <4084> EV-H {CacheManager} (New file: A38378D6688DDF754589DF8D82ECDF12261p10000evsql.ev.local.pst)
2,457 15:35:23.373 [1,972] (EVMonitoring) <4084> EV-H {CacheManager} Adding file to file list..
2,458 15:35:23.373 [1,972] (EVMonitoring) <4084> EV-H {CacheManager} Updating cache Size: Old:1160595456
2,459 15:35:23.373 [1,972] (EVMonitoring) <4084> EV-H {CacheManager} Updating cache Size: New:1740893184
 
2,473 15:35:45.401 [1,972] (EVMonitoring) <4084> EV-H {CacheManager} A file rename event has occurred in the cache; updating File list..
2,474 15:35:45.401 [1,972] (EVMonitoring) <4084> EV-H {CacheManager} (Old file: 38378D6688DDF754589DF8D82ECDF12261p10000evsql.ev.local.pst)
2,475 15:35:45.401 [1,972] (EVMonitoring) <4084> EV-H {CacheManager} (New file: A48378D6688DDF754589DF8D82ECDF12261p10000evsql.ev.local.pst)
2,476 15:35:45.427 [1,972] (EVMonitoring) <4084> EV-H {CacheManager} Adding file to file list..
2,477 15:35:45.427 [1,972] (EVMonitoring) <4084> EV-H {CacheManager} Updating cache Size: Old:1740893184
2,478 15:35:45.427 [1,972] (EVMonitoring) <4084> EV-H {CacheManager} Updating cache Size: New:2321190912
 
2,495 15:36:07.802 [1,972] (EVMonitoring) <4084> EV-H {CacheManager} A file rename event has occurred in the cache; updating File list..
2,496 15:36:07.802 [1,972] (EVMonitoring) <4084> EV-H {CacheManager} (Old file: 38378D6688DDF754589DF8D82ECDF12261p10000evsql.ev.local.pst)
2,497 15:36:07.802 [1,972] (EVMonitoring) <4084> EV-H {CacheManager} (New file: A58378D6688DDF754589DF8D82ECDF12261p10000evsql.ev.local.pst)
2,498 15:36:07.827 [1,972] (EVMonitoring) <4084> EV-H {CacheManager} Adding file to file list..
2,499 15:36:07.827 [1,972] (EVMonitoring) <4084> EV-H {CacheManager} Updating cache Size: Old:2321190912
2,500 15:36:07.827 [1,972] (EVMonitoring) <4084> EV-H {CacheManager} Updating cache Size: New:2901488640
 
2,523 15:36:30.395 [1,972] (EVMonitoring) <4084> EV-H {CacheManager} A file rename event has occurred in the cache; updating File list..
2,524 15:36:30.395 [1,972] (EVMonitoring) <4084> EV-H {CacheManager} (Old file: 38378D6688DDF754589DF8D82ECDF12261p10000evsql.ev.local.pst)
2,525 15:36:30.395 [1,972] (EVMonitoring) <4084> EV-H {CacheManager} (New file: A68378D6688DDF754589DF8D82ECDF12261p10000evsql.ev.local.pst)
2,526 15:36:30.423 [1,972] (EVMonitoring) <4084> EV-H {CacheManager} Adding file to file list..
2,527 15:36:30.423 [1,972] (EVMonitoring) <4084> EV-H {CacheManager} Updating cache Size: Old:2901488640
2,528 15:36:30.423 [1,972] (EVMonitoring) <4084> EV-H {CacheManager} Updating cache Size: New:3481786368
^^ After this rename, I'm now 'over' my cache limit
 
2,529 15:36:30.423 [1,972] (EVMonitoring) <4084> EV-H {CacheManager} The cache size has now been exceeded. Running deletion...
2,530 15:36:30.525 [1,972] (EVMonitoring) <4088> EV-H {CacheManager} Checking the 6 files in the 'VCBuilds' folder for expired items.
2,531 15:36:30.525 [1,972] (EVMonitoring) <4088> EV-H {CacheManager} Setting CacheState to 'Full'
2,532 15:36:30.525 [1,972] (EVMonitoring) <4088> EV-H {CacheManager} CacheStatus change: Full
2,533 15:36:30.525 [1,972] (EVMonitoring) <4088> EV-H {CacheManager} No 'ByteRange' items exist to delete, moving onto 'Upload'.
2,534 15:36:30.559 [1,972] (EVMonitoring) <4088> EV~W
Event ID: 41099 The specified cache location has reached the maximum specified size.
The Cache Manager will now delete the oldest items to free up space. If necessary you can edit the server's properties in the Administration Console to increase
 the size of the Cache.
^^ Nice event which is logged
 
2,535 15:36:30.559 [1,972] (EVMonitoring) <4088> EV-H {CacheManager} Deleting C:\evcache\VCBuilds\18378D6688DDF754589DF8D82ECDF12261p10000evsql.ev.local.pst
^^ Deletes the oldest file, even though the user hasn't download it yet (so the end user Outlook Add-in would request this again 'at some point')
 
2,536 15:36:30.559 [1,972] (EVMonitoring) <4088> EV-H {CacheManager} Resetting CacheState to 'Available'
2,537 15:36:30.559 [1,972] (EVMonitoring) <4084> EV-H {CacheManager} A PST Delete event has occurred in the cache; updating file list..
2,538 15:36:30.559 [1,972] (EVMonitoring) <4088> EV-H {CacheManager} CacheStatus change: Available
2,539 15:36:30.559 [1,972] (EVMonitoring) <4084> EV-H {CacheManager} (Checking file: C:\evcache\VCBuilds\18378D6688DDF754589DF8D82ECDF12261p10000evsql.ev.local.
pst)
2,540 15:36:30.559 [1,972] (EVMonitoring) <4088> EV-H {CacheManager} Sleeping for 900s
2,541 15:36:30.559 [1,972] (EVMonitoring) <4084> EV-H {CacheManager} (Removing file: C:\evcache\VCBuilds\18378D6688DDF754589DF8D82ECDF12261p10000evsql.ev.local.
pst)
^^ Finished deleting the file