>>> 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
>>> }
>>>
>>
>> you could create a backup job with just that file in it and run it
> always
>
On Thu, 14 Apr 2011 12:37:35 + (UTC), Thomas Mueller
wrote:
> Am Thu, 14 Apr 2011 16:33:14 +1000 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
Am Thu, 14 Apr 2011 16:33:14 +1000 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 databa
>
> 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
If this is a Linux system just use "touch" to update the timestamps on the file
---Guy
(via iPhone)
On 14 Apr 2011, at 08:54, Christian Manal
wrote:
> Am 14.04.2011 08:33, schrieb James Harper:
>> The "last modified" datestamp on MSSQL database files doesn't get
>> changed unless the actual fi
On Thu, 14 Apr 2011 09:54:09 +0200, Christian Manal
wrote:
> 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 increme
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
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 eithe
