• Facebook
  • RSS Feed
  • Instagram
  • LinkedIn
  • Twitter
Jul 012008
 

I just finished helping an engineer get NBU migrations working from Enterprise Vault (EV).  He had set everything up in text book style, but still he was not getting anything migrated.  His event log was saying :

0 Saveset(s) were collected into 0 Collection(s).

0 file(s) were migrated to secondary storage

The run completed in 0 hour(s), 0 minute(s), 0 second(s).

At first I thought that this was because he has only test data.  By default we don’t collect if we don’t find more than 15 files in the “hours” folder for each day.  i.e. we’re going to create a CAB file for the day, but won’t unless we find at least 15 files in that day.

First of all we added this registry key, and restarted the storage service :

MinimumFilesInCollection

Location


HKEY_LOCAL_MACHINE
 SOFTWARE
  KVS
   Enterprise Vault    Storage

Content

DWORD

Maximum value: 25000.

Minimum value: 1

Setting a value of 0 forces the default (15) to be used .

Description

When creating collections, MinimumFilesInCollection controls the minimum number of saveset files in a collection. The collection is not created unless there are at least this number of savesets to be added.

Still no joy.

We then dtrace’d storagefilewatch and evstgofflineopns to see if that would tell us what is happening.  The output of that DID show us what is wrong :

EV:M Collector is walking the directory tree for Partition 12039DD547090F34A899831D7AFCC68651q10000dbawl11.nbuev.vxindia.veritas.com
EV:L The Collector for Partition 12039DD547090F34A899831D7AFCC68651q10000dbawl11.nbuev.vxindia.veritas.com is parsing directory E:Enterprise Vault Storesvaultstore1 Ptn12008
EV:L The Collector for Partition 12039DD547090F34A899831D7AFCC68651q10000dbawl11.nbuev.vxindia.veritas.com is parsing directory E:Enterprise Vault Storesvaultstore1 Ptn120081
EV:L The Collector for Partition 12039DD547090F34A899831D7AFCC68651q10000dbawl11.nbuev.vxindia.veritas.com is parsing directory E:Enterprise Vault Storesvaultstore1 Ptn1200813
EV:L The Collector for Partition 12039DD547090F34A899831D7AFCC68651q10000dbawl11.nbuev.vxindia.veritas.com is parsing directory E:Enterprise Vault Storesvaultstore1 Ptn12008139
EV:L The Collector for Partition 12039DD547090F34A899831D7AFCC68651q10000dbawl11.nbuev.vxindia.veritas.com is going to Collect file E:Enterprise Vault Storesvaultstore1 Ptn12008139135500000000000~200801030937410000~0.DVS
EV:M The Collector for Partition 12039DD547090F34A899831D7AFCC68651q10000dbawl11.nbuev.vxindia.veritas.com determined the file E:Enterprise Vault Storesvaultstore1 Ptn12008139135500000000000~200801030937410000~0.DVS as not safe for Collection
EV:M The Collector for Partition 12039DD547090F34A899831D7AFCC68651q10000dbawl11.nbuev.vxindia.veritas.com did not create a Collection as either the Collection was too small or it did not contain enough files. Collection size = 0 bytes, number of files = 0>

This means that the vault store is set to keep safety copies.  By default we won’t put the DVS files in to a CAB file if they’ve not been made safe, ie backed up.  A quick workaround on this test system was to run :-

attrib -A *.* /s

That was run from a DOS prompt in the folder on disk containing the vault store files.

After that, a collection run happened successfully, and data begun migrating to NBU.

 

If you enjoyed this post, please consider leaving a comment or subscribing to the RSS feed to have future articles delivered to your feed reader.

 Leave a Reply

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>

(required)

(required)