Forum Discussion

Josserand's avatar
Josserand
Level 4
16 years ago
Solved

EV 8SP3 - ArchiveBit problem

Hello All We are using netapp device for primary archive repository, so all file don't have archive bit reseted by backup process (snapshot methods). It was not a problem until now. Now, we are using TSM (DR550) to move old archive to secondary disk/tape device, by using collection/migration process on partition. the problem is that collection process is awaiting for archive bit reseting before procceed to collection and migration. We try to use the IgnoreArhiveBitTrigger.txt file without success, we get this problem http://seer.entsupport.symantec.com/docs/294372.htm , all archive data was staying in pending states until new file creation, because, we have journaling and 24/24 archiving run per day. so the file is just created once per day in the normal process. The side effect on this that EV let archive file in pending awaiting new trigger file creation. We cannot use this solution (creating a new trigger file every minute of the days and pray that EV will dot not create to many pending shortcuts during this time...when we try during 1 hour, we get thousand of mails in pending we error to revert. We try next to user attrib -a, but we have million of archived files per week and it s take too long (Around 40000 users in journaling now...) My question is : 1) Can we desactivate the control of backup file (awaiting backup) of the collection process? Registry key ? or something 2) On Netapp Side can we massevely desactivate archive bit state ? 2) Any idea ? ;0) Thanx !
  • Hello thx you for the feed back,

    But I cannot wait backup time to clear backup status for EV, becaue of journaling, so I finally use and old school method..attrib -a...

4 Replies


  • Hi Josserand,

    Make sure you create a new IgnoreArchiveBitTrigger.txt file. It has to have the date and time of the time you want the files to be cleared.
    use echo > vaultstorelocation\ignorearchivebittrigger.txt to create it. Do not copy an existing one, as it will not have the new date....

    when copied over, put the vaultstore in backup mode, take it out of it. that should do the trick.

    offical way:
    put in backupmode
    backup
    set triggerfile
    put in normal mode
    you can sort of verify by checking to see if after the last step the storagefilewatch process starts taking cpu..

    also in evmonitor you should see ' items awaiting backup'  go down after this.
  • Hello thx you for the feed back,

    But I cannot wait backup time to clear backup status for EV, becaue of journaling, so I finally use and old school method..attrib -a...
  • Hi,

    Are you just journalling or mailbox archiving as well?  If so is the journal data in the same vault store group as the mailbox archiving data?