Centera with no replication

I believe that's to do with the storage file watch setting.  You've told the partition to check for a trigger file, but you never actually set the trigger file on the partition, so it's telling you it hasn't been able to do a scan.  Since you are removing safety copies immediately after backup then this setting is irrelevent.  If you change the partition to use the archive attribute under the backup tab then this message will go away. 

Here an interesting article about this,

http://www.symantec.com/business/support/index?page=content&id=TECH68881&actp=search&viewlocale=en_US&searchid=1314084505124.

I hope this helps you as much as it helped me ( I'm in the same situation) 

Hi,

This is a "security" feature which was introduced with the version 8 they are in fact waiting for the answer from the second node ( even if you don't have any) to delete the entries from the watchfile table and archiveJournal table. I have exactly the same behaviour and I contected Symantec to know how to solve it....this implies modifications in some tables of the db. I would advise you to contect the Symantec support in order to get all the info's on how to " solve" this

Thank you Sandrine and Sortid. The tech article was very helpful.  I see Backup Complete column = 0 for all the columns, which means awaiting backup.

Since we are not running backups and no centera replication, the olny way I see is to run a script nightly and set that column to 1.  I will verify this with support as you suggest before implementing it.

Thanks again. 

Fremont

I agree.  It's a very vague tech note.

I confirmed with Symantec Support.  You need to set the "Ignore Backup" entry in the partition entry table to True.  However this is not retro-active.  Waiting for the procedure to flush the watchfile table.