Forum Discussion

Bogdanl's avatar
Bogdanl
Level 4
8 years ago
Solved

Incremental backup has the same size as a full backup

Hello,

Could you please let me know if you have any ideas why the incremental backups has the same size as a full backup ? This happened only on the GPFS Filesystem. The filesystems are mounted directly on the media server and for the other backups everything works fine !

The data backup are Unix

The policies backup Unix data (ascii files) on a GPFS filesystem

Version of NBU is 7.6

The timestamp of files has not been modified

Thank you

 

  • After remove  the accelerator i noticed an improvement for incremental backup compare to last week, this workaround seems to be OK. Thank you all for your answers !

11 Replies

  • Probably a silly question, but can you confirm that the Full and Incr schedules are in the same policy?

    For troubleshooting, please ensure that bpbkar log folder exists on the client with logging level at 3.
    Please copy the log after next Incr backup to bpbkar.txt and upload here.
    • Bogdanl's avatar
      Bogdanl
      Level 4

      Hello Marianne,

      Yes, the Full and Incr schedules are in the same policy .

      Incremental  is configured to use  option “ Based on archive bit”, do you think we can safely switch to “ Based on timestamp”?

      Thank you

      • Marianne's avatar
        Marianne
        Level 6

        'Archive Bit' is only applicable to Windows clients.

        For Unix/Linux, NBU uses mtime.
        See this extract from the Admin Guide: 
        https://www.veritas.com/content/support/en_US/doc/18716246-126559472-0/v41780104-126559472

        Customers can choose to have NetBackup use the ctime and the mtime of the file to determine what files to include in an incremental backup. Normally, these two options are used together, but there may be some sites that want to use one without the other. By default, NetBackup uses only the mtime of the file to determine what files and directories to back up.