Am 14.04.2011 08:33, schrieb James Harper:
> The "last modified" datestamp on MSSQL database files doesn't get
> changed unless the actual file dimensions change (eg it 'grows') or when
> the file is closed. This means that an incremental backup won't
> necessarily back up the database files unless they have changed.
> Accurate won't catch this either as the metadata it uses will be
> identical.
>
> Is there a way to force the backup of specific unchanged files during an
> incremental or differential backup? Eg:
>
> Option {
> File = "C:/database/mydb.mdf"
> Always Back Up = Yes
> }
>
> Thanks
>
> James
Hi,
does the file change at all? If so, you can just adjust the metadata
that Accurate uses to compare checksums. That is done in the fileset:
http://bacula.org/5.0.x-manuals/en/main/main/Configuring_Director.html#8553
Regards,
Christian Manal
------------------------------------------------------------------------------
Benefiting from Server Virtualization: Beyond Initial Workload
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve
application availability and disaster protection. Learn more about boosting
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
