Forum Discussion

gkman's avatar
gkman
Level 5
8 years ago

track directory

we have two servers (windows) that are running out of space. after a quick check we found that most space is consumed by the growing size of the track directory of the Netbackup client. I googled i...
  • sdo's avatar
    sdo
    8 years ago

    1) Sounds like a track log for a cluster hasn't been configured, and so a cluster failover will cause the backup of the cluster resources to use a stale track log.  Some links for track log placement:

    How to redirect the NetBackup Accelerator track log to a different location
    http://www.veritas.com/docs/000068640

    ...and a very useful post from MortenSeeberg here, which seems to be more informative/useful than the tech note just above:

    https://vox.veritas.com/t5/Articles/Accelerator-backup-of-Windows-Cluster-systems/ta-p/813666

    .

    2) I not aware of exactly how Accelerator works, but I did once look inside some of the files and they are some kind of binary proprietary format for which I never seen any documentation, so I'm not sure that it's going to be possible to explain exactly why the track log is twice the size of the other.

    3) Have a look at the folder name structure, look at where the policy names fit in the structure, and see if you have some track logs for old policy names that no longer exist, as these can be deleted, e.g. from a time before the client was clustered.

gkman's avatar
gkman
Level 5

netbackup is 7.7.2 across all servers and clients. 
and no netapp filers are being backed-up (how is it relevant?)

I am still unclear about the track logs- I understand they are integral for the accelerator, but what exactly is saved in them? why are they so big? it seems (compared to other servers) like an anomaly that needs at least some cleaning- I have a hard time believing it requires more than 10GB.

  • gkman's avatar
    gkman
    Level 5
    8 years ago

    now that I see the formula I guess it is possible for it to reach 10GB.

    however, I did not mention before (I thought it was irrelevant) that both servers are part of the same failover cluster. raising some new questions:

    1) shouldn't the track log sit on a cluster resource that will be failed over too? what happens when the servers are in two policies, one for the cluster and the second for the OS- where should the track log be?
    2) why is the track log 10GB on one server and twice as much on the second?

    thanks for the help

    • sdo's avatar
      sdo
      Moderator
      8 years ago

      1) Sounds like a track log for a cluster hasn't been configured, and so a cluster failover will cause the backup of the cluster resources to use a stale track log.  Some links for track log placement:

      How to redirect the NetBackup Accelerator track log to a different location
      http://www.veritas.com/docs/000068640

      ...and a very useful post from MortenSeeberg here, which seems to be more informative/useful than the tech note just above:

      https://vox.veritas.com/t5/Articles/Accelerator-backup-of-Windows-Cluster-systems/ta-p/813666

      .

      2) I not aware of exactly how Accelerator works, but I did once look inside some of the files and they are some kind of binary proprietary format for which I never seen any documentation, so I'm not sure that it's going to be possible to explain exactly why the track log is twice the size of the other.

      3) Have a look at the folder name structure, look at where the policy names fit in the structure, and see if you have some track logs for old policy names that no longer exist, as these can be deleted, e.g. from a time before the client was clustered.