Video Screencast Help
Scheduled Maintenance: Symantec Connect is scheduled to be down Saturday, April 19 from 10am to 2pm Pacific Standard Time (GMT: 5pm to 9pm) for server migration and upgrades.
Please accept our apologies in advance for any inconvenience this might cause.

Enterprise Vault and PartitionSecuredNotification.XML

Created: 13 May 2013
Rob.Wilcox's picture
0 0 Votes
Login to vote

 

In a previous blog I mentioned that there are effectively two trigger file mechanisms, the PartitionSecuredNotification.XML is the new kid on the block having only been introduced in Enterprise Vault 8. The file has a specific format, and is something that needs to be created by your backup software.  The file looks like this:
 
<?xml version="1.0" encoding="utf-8" ?>
  <PartitionSecuredNotification
  xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance
  xsi:noNamespaceSchemaLocation="PartitionSecuredNotification.xsd">
  <VendorName>required free form string</VendorName>
  <VendorAppType>required free form string</VendorAppType>
  <PartitionSecuredDateTime> 2008-03-25T09:30:10+05:30 </PartitionSecuredDateTime>
  <VendorTransactionId>optional string</VendorTransactionId> </PartitionSecuredNotification>
 
You can see here that there is the PartitionSecuredDateTime, which is used by the Enterprise Vault post-processing action (StorageFileWatch). Items prior to this date/time (down to the second, you will notice) are considered to be backed up and 'secure', so they can be turned in to placeholders/stubs/shortcuts as determined by the time of item, and the policy which relate to them.
 
Software like Symantec NetBackup 7.1 (and higher) use this mechanism, and also some replication software like QUADROtech evNearSync use it as well.