Forum Discussion

SSR1's avatar
SSR1
Level 4
12 years ago

Files are being collected but not migrated

 

 

Hello.

I have a problem with EV 10.0.3 and error 41008. Files are being collected but not migrated to Secondary Storage. New items awaiting backup or replication.

We have backup of vault partition on BackUp Exec 2010 R3, and we are using BackUp Exec migrator.

On Vault Store Properties is set remove safety coppies immediately after archive.

SQL Database is backuped daily by ArcServe BackUp.

Could you tell me what we are doing wrong because we have lot of savesets that have not yet been backed up or replicated for Vault Store.

When I open WatchFile table I see that all items have ItemSecured set to False not to True.

DTrace log is in attachment.

Enterprise Vault
Information Governance
Windows 7
  • Rob_Wilcox1's avatar
    Rob_Wilcox1
    12 years ago

    Oh okay, didn't see that in the original post about using ArcServe for part of it, and Backup Exec for part of it.

     

    So the general process is:

    * Set backup mode on vault stores

    * Set backup mode on index locations

    * Do SQL backups

    * Do backups of index locations and vault store partitions (*1)

    * Clear backup mode on index locations

    * Clear backup mode on Vault Stores

     

    *1 -> Some people only backup active, open, partitions, and closed partitions at different frequencies/schedules.

     

    So.. the bit about the number of items awaiting backup - if you're seeing that (and it sounds like you are) comes from the backup of vault store partitions.  If you're using the Archive Bit, then perhaps that's not being cleared by the backup software.

22 Replies

Sort By
  • Rob_Wilcox1's avatar
    Rob_Wilcox1
    Level 6
    12 years ago

    What is the dtrace of?  (I mean I see a storage restart somewhere in there... amongst other things)

     

    Why are there three DTRACEs?

  • SSR1's avatar
    SSR1
    Level 4
    12 years ago

    Three files for three trace options: storageServer, storageFileWatch, StorageCrawler. Here is the tracelog for storagefilewatch only in the attachment. Log is divided into 3 parts,  because of 1 log file can only be 100mb.

  • SSR1's avatar
    SSR1
    Level 4
    12 years ago

    Has anyone such problem? I have no way to solve it.

  • Rob_Wilcox1's avatar
    Rob_Wilcox1
    Level 6
    12 years ago

    You need to run a DTRACE of the collection/migration process.  I didn't see any start of the collection process in the traces you provided.. 

    My question was really relating to what are you DTRACEing, not in terms of which components, but what operation did you perform afterwards?  I also would expect ONE DTRACE.. not 3.

    Does your partition use a trigger file, or the archive bit?  Is ArcServe successfully handling whichever option you have chosen?

  • SSR1's avatar
    SSR1
    Level 4
    12 years ago

    Partions use the archive bit. ArcServe is succesfully handling whichever option I have chosen. Now I'm running DTRACE of the collection issue. I didn't find collection\migration process in dtrace options. There are only collection issue and migration issue separately.

  • Rob_Wilcox1's avatar
    Rob_Wilcox1
    Level 6
    12 years ago

    <snip>

    Partions use the archive bit. ArcServe is succesfully handling whichever option I have chosen

    </snip>

    How are you verifying that?

    Do you have system status warning messages about the number of items awaitng backup? Do you have EVOM where you can see the number of items awaiting back, or even the simple Vault Store Group reports show the information, I think.

  • SSR1's avatar
    SSR1
    Level 4
    12 years ago

    Yes I have messages in EV about items awaiting backup or replication and that there are some number savesets that have not yet been backed up or replicated for VaultStore. And such message for each partition.

  • Rob_Wilcox1's avatar
    Rob_Wilcox1
    Level 6
    12 years ago

    Then ArcServe is not correctly processing the backup.

    Either it's not resetting the archive bit, or can't.

    If it can't then you'd need to use one of the trigger file mechanisms.  If it can, but isn't, you'd need to investigate the ArcServe side of things to see why that is.

    Once that's fixed...  the collections, and migration should then be fine. (I think)

  • SSR1's avatar
    SSR1
    Level 4
    12 years ago

    And one thing, I cannot see any tasks of migration in Back Up Exec, where backup exec agent migration  is set to back up to tape. ArcServe is backs up only SQL database of EV and shrink logs. 

  • Rob_Wilcox1's avatar
    Rob_Wilcox1
    Level 6
    12 years ago

    Oh okay, didn't see that in the original post about using ArcServe for part of it, and Backup Exec for part of it.

     

    So the general process is:

    * Set backup mode on vault stores

    * Set backup mode on index locations

    * Do SQL backups

    * Do backups of index locations and vault store partitions (*1)

    * Clear backup mode on index locations

    * Clear backup mode on Vault Stores

     

    *1 -> Some people only backup active, open, partitions, and closed partitions at different frequencies/schedules.

     

    So.. the bit about the number of items awaiting backup - if you're seeing that (and it sounds like you are) comes from the backup of vault store partitions.  If you're using the Archive Bit, then perhaps that's not being cleared by the backup software.