Re: [Bacula-users] force backup of unchanged file in incremental backup

2011-04-14 Thread Christian Manal 
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

Re: [Bacula-users] force backup of unchanged file in incremental backup

2011-04-14 Thread Jérôme Blion 
On Thu, 14 Apr 2011 09:54:09 +0200, Christian Manal
moen...@informatik.uni-bremen.de 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 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
 

Hello, 

AFAIK, you should never backup MSSQL databases when they are running. If
you do so, the database will try to recover from a crash and you can loose
data pieces. Files do not reflect the status of the database.

You should back it up correctly, using a database agent (eg: Litespeed) or
SQL scripts to dump it then archive it.
If you do so, you will be able to backup transaction log too and will be
able to perform PIT restores.
You could start from the catalog backup job to adapt it to your needs.

For Mysql, there is one interesting way : flush tables with read lock +
LVM snapshot. Files are coherent, and backed up at the exact same time.
Perhaps you could use a similar way to backup database's files.


HTH.
Jerome Blion.

--
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

Re: [Bacula-users] force backup of unchanged file in incremental backup

2011-04-14 Thread Guy 
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 moen...@informatik.uni-bremen.de 
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 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

--
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

Re: [Bacula-users] force backup of unchanged file in incremental backup

2011-04-14 Thread James Harper 
 
 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#8
553
 

Yes the file changes, so an md5 hash will be sufficient. The databases
are only a few hundred MB so the cost of calculating the hash shouldn't
be an issue. Unless bacula can use the archive bit, which does get set
correctly, this might be the only way.

The file _always_ changes between backups, so a fast way to do what I
want would be to add a flag to accurate that says assume this file has
always changed. I'll post that request on the dev list.

Thanks

James


--
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

Re: [Bacula-users] force backup of unchanged file in incremental backup

2011-04-14 Thread Thomas Mueller 
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 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
 }
 

you could create a backup job with just that file in it and run it always 
as full. 

- Thomas


--
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

Re: [Bacula-users] force backup of unchanged file in incremental backup

2011-04-14 Thread Jérôme Blion 
On Thu, 14 Apr 2011 12:37:35 + (UTC), Thomas Mueller
tho...@chaschperli.ch 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 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
 }
 
 
 you could create a backup job with just that file in it and run it
always 
 as full. 
 
 - Thomas

I think his goal is to recreate some differential backups for MSSQL (RMAN
provides it for Oracle).
To do that, he needs to know which datafiles moved... If you perform a
touch on each of them, it's not a differential backup but a full one.

Are we sure that all data pieces have been flushed to disk before the VSS
snapshot occurred ?

HTH.
Jerome Blion.

--
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

Re: [Bacula-users] force backup of unchanged file in incremental backup

2011-04-14 Thread Thomas Mueller 

 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
 as full.

 - Thomas

 I think his goal is to recreate some differential backups for MSSQL (RMAN
 provides it for Oracle).

you can't do a Differential or Incremental backup of MSSQL data files. 
this would require a FD plugin or another tool.

 To do that, he needs to know which datafiles moved... If you perform a
 touch on each of them, it's not a differential backup but a full one.

 Are we sure that all data pieces have been flushed to disk before the VSS
 snapshot occurred ?

yes, MSSQL provides a VSS Plugin. so MSSQL knows when it has to flush 
to disk.

- Thomas

--
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