Source Control Integration - Bareos Bug Tracker

master 858a8a64 2014-07-11 13:09 Marco van Wieringen Ported: N/A Details Diff	Some tweaks to copy/migrate config. The folllowing changes were made: - The copy and migration jobs up until now always needed that you specify a storage in the Job while most of the time it was never used as the real storage used also depends on what the original Job used for storage. This patch tries to relax the need for specifying a read storage and tries to always use the info of the original pool used by the previous Job being copied or migrated or the original storage settings of the Job itself. When you start a copy or migration you now don't see the somewhat random read storage that can change along the way but only the write storage. In essence it should also not matter what read storage is used as long its the right read storage. - We can now have migration and copy jobs without a dummy client setting but this means that the %c variable of the Job will not be filled and as such you won't see the client name in the completion mail subject. So we now copy the client pointer from the actual previous Job that is migrated or copied so that we do have the proper client name and also the client name of the actual client the migration or copy was done for an no longer the dummy name it was before. - Analog to using the client from the previous Job we also use the fileset and job level of the previous Job so that the copy migrate now always looks similar to the original Job its copying e.g. no longer a backup level incremental when copying/migrating a full level Job. - Try to be smart about when to use data spooling. Only use the Job data spooling setting when not enabled yet. e.g. when the JCR already has data spooling enabled we don't want to disable it because the Job has no explicit setting. - Restored printing of the client/fileset/level in the copy/migrate overview something we removed in a previous patch when we removed the explicit need for specifying these settings. Now that we set the correct information in the copy/migrate setup we can again print this data and now also show the correct info if you configure your copy/migrate jobs using the new config syntax e.g. without setting a dummy client and fileset.
	mod - src/console/console.c	Diff File
	mod - src/dird/dird_conf.c	Diff File
	mod - src/dird/job.c	Diff File
	mod - src/dird/migrate.c	Diff File
	mod - src/dird/ua_run.c	Diff File
master 01808dd7 2014-07-11 13:09 Marco van Wieringen Ported: N/A Details Diff	Sync LMDB code.
	mod - src/lmdb/lmdb.h	Diff File
	mod - src/lmdb/mdb.c	Diff File
	mod - src/lmdb/midl.c	Diff File
	mod - src/lmdb/midl.h	Diff File
playground d8ddbb76 2014-07-11 11:09 mvwieringen Ported: N/A Details Diff	Sync LMDB code.
	mod - src/lmdb/lmdb.h	Diff File
	mod - src/lmdb/mdb.c	Diff File
	mod - src/lmdb/midl.c	Diff File
	mod - src/lmdb/midl.h	Diff File
playground 9bd429c8 2014-07-11 11:09 mvwieringen Ported: N/A Details Diff	Some tweaks to copy/migrate config. The folllowing changes were made: - The copy and migration jobs up until now always needed that you specify a storage in the Job while most of the time it was never used as the real storage used also depends on what the original Job used for storage. This patch tries to relax the need for specifying a read storage and tries to always use the info of the original pool used by the previous Job being copied or migrated or the original storage settings of the Job itself. When you start a copy or migration you now don't see the somewhat random read storage that can change along the way but only the write storage. In essence it should also not matter what read storage is used as long its the right read storage. - We can now have migration and copy jobs without a dummy client setting but this means that the %c variable of the Job will not be filled and as such you won't see the client name in the completion mail subject. So we now copy the client pointer from the actual previous Job that is migrated or copied so that we do have the proper client name and also the client name of the actual client the migration or copy was done for an no longer the dummy name it was before. - Analog to using the client from the previous Job we also use the fileset and job level of the previous Job so that the copy migrate now always looks similar to the original Job its copying e.g. no longer a backup level incremental when copying/migrating a full level Job. - Try to be smart about when to use data spooling. Only use the Job data spooling setting when not enabled yet. e.g. when the JCR already has data spooling enabled we don't want to disable it because the Job has no explicit setting. - Restored printing of the client/fileset/level in the copy/migrate overview something we removed in a previous patch when we removed the explicit need for specifying these settings. Now that we set the correct information in the copy/migrate setup we can again print this data and now also show the correct info if you configure your copy/migrate jobs using the new config syntax e.g. without setting a dummy client and fileset.
	mod - src/console/console.c	Diff File
	mod - src/dird/dird_conf.c	Diff File
	mod - src/dird/job.c	Diff File
	mod - src/dird/migrate.c	Diff File
	mod - src/dird/ua_run.c	Diff File
playground 06e24092 2014-07-11 11:09 mvwieringen Ported: N/A Details Diff	Create an empty rados object in d_open when O_CREAT is set.
	mod - src/stored/backends/rados_device.c	Diff File
playground 02f3e709 2014-07-11 11:09 mvwieringen Ported: N/A Details Diff	Sync LMDB code.
	mod - src/lmdb/lmdb.h	Diff File
	mod - src/lmdb/mdb.c	Diff File
	mod - src/lmdb/midl.c	Diff File
	mod - src/lmdb/midl.h	Diff File
playground 5ce0058f 2014-07-11 11:09 mvwieringen Ported: N/A Details Diff	Some tweaks to copy/migrate config. The folllowing changes were made: - The copy and migration jobs up until now always needed that you specify a storage in the Job while most of the time it was never used as the real storage used also depends on what the original Job used for storage. This patch tries to relax the need for specifying a read storage and tries to always use the info of the original pool used by the previous Job being copied or migrated or the original storage settings of the Job itself. When you start a copy or migration you now don't see the somewhat random read storage that can change along the way but only the write storage. In essence it should also not matter what read storage is used as long its the right read storage. - We can now have migration and copy jobs without a dummy client setting but this means that the %c variable of the Job will not be filled and as such you won't see the client name in the completion mail subject. So we now copy the client pointer from the actual previous Job that is migrated or copied so that we do have the proper client name and also the client name of the actual client the migration or copy was done for an no longer the dummy name it was before. - Analog to using the client from the previous Job we also use the fileset and job level of the previous Job so that the copy migrate now always looks similar to the original Job its copying e.g. no longer a backup level incremental when copying/migrating a full level Job. - Try to be smart about when to use data spooling. Only use the Job data spooling setting when not enabled yet. e.g. when the JCR already has data spooling enabled we don't want to disable it because the Job has no explicit setting. - Restored printing of the client/fileset/level in the copy/migrate overview something we removed in a previous patch when we removed the explicit need for specifying these settings. Now that we set the correct information in the copy/migrate setup we can again print this data and now also show the correct info if you configure your copy/migrate jobs using the new config syntax e.g. without setting a dummy client and fileset.
	mod - src/console/console.c	Diff File
	mod - src/dird/dird_conf.c	Diff File
	mod - src/dird/job.c	Diff File
	mod - src/dird/migrate.c	Diff File
	mod - src/dird/ua_run.c	Diff File
playground 04d2bffd 2014-07-11 11:09 mvwieringen Ported: N/A Details Diff	Create an empty rados object in d_open when O_CREAT is set.
	mod - src/stored/backends/rados_device.c	Diff File
master 993db346 2014-07-06 13:59 Marco van Wieringen Ported: N/A Details Diff	Update AUTHORS.
	mod - AUTHORS	Diff File
bareos-13.2 bb6a87bb 2014-07-06 13:59 Marco van Wieringen Ported: N/A Details Diff	Update AUTHORS.
	mod - AUTHORS	Diff File
bareos-13.2 c591eb6e 2014-07-06 11:59 mvwieringen Ported: N/A Details Diff	Update AUTHORS.
	mod - AUTHORS	Diff File
bareos-12.4 0fd9d702 2014-07-06 11:59 mvwieringen Ported: N/A Details Diff	Update AUTHORS.
	mod - AUTHORS	Diff File
master 2d87ed5b 2014-07-06 11:59 mvwieringen Ported: N/A Details Diff	Update AUTHORS.
	mod - AUTHORS	Diff File
master 06fc51c7 2014-07-02 18:27 Philipp Storz Committer: Marco van Wieringen Ported: N/A Details Diff	Set correct definition of _REPARSE_DATA_BUFFER It seems that our definition of _REPARSE_DATA_BUFFER was missing a Member called Flags. See here: http://msdn.microsoft.com/en-us/library/windows/hardware/ff552012%28v=vs.85%29.aspx
	mod - src/win32/compat/include/compat.h	Diff File
master 13d2925e 2014-07-02 16:27 pstorz Committer: mvwieringen Ported: N/A Details Diff	Set correct definition of _REPARSE_DATA_BUFFER It seems that our definition of _REPARSE_DATA_BUFFER was missing a Member called Flags. See here: http://msdn.microsoft.com/en-us/library/windows/hardware/ff552012%28v=vs.85%29.aspx
	mod - src/win32/compat/include/compat.h	Diff File
master 9708f26f 2014-07-01 17:53 Marco van Wieringen Ported: N/A Details Diff	Fix compiler warning.
	mod - src/filed/accurate_lmdb.c	Diff File
master 5c39919b 2014-07-01 16:54 Marco van Wieringen Ported: N/A Details Diff	Enable systemd support for RHEL7 and CentOS7.
	mod - platforms/packaging/bareos.spec	Diff File
master a9d2cf13 2014-07-01 15:53 mvwieringen Ported: N/A Details Diff	Fix compiler warning.
	mod - src/filed/accurate_lmdb.c	Diff File
master df7a3770 2014-07-01 14:54 mvwieringen Ported: N/A Details Diff	Enable systemd support for RHEL7 and CentOS7.
	mod - platforms/packaging/bareos.spec	Diff File
bareos-13.2 4ed9f08d 2014-07-01 14:54 mvwieringen Ported: N/A Details Diff	Enable systemd support for RHEL7 and CentOS7.
	mod - platforms/packaging/bareos.spec	Diff File
bareos-12.4 54df6a83 2014-07-01 14:54 mvwieringen Ported: N/A Details Diff	Enable systemd support for RHEL7 and CentOS7.
	mod - platforms/packaging/bareos.spec	Diff File
master 0f0f2408 2014-06-30 16:46 Marco van Wieringen Ported: N/A Details Diff	Make the build flags setable via a define.
	mod - platforms/win32/winbareos32.spec	Diff File
	mod - platforms/win32/winbareos64.spec	Diff File
master 6c9467fd 2014-06-30 14:46 mvwieringen Ported: N/A Details Diff	Make the build flags setable via a define.
	mod - platforms/win32/winbareos32.spec	Diff File
	mod - platforms/win32/winbareos64.spec	Diff File
bareos-13.2 242f5ae8 2014-06-30 14:46 mvwieringen Ported: N/A Details Diff	Make the build flags setable via a define.
	mod - platforms/win32/winbareos32.spec	Diff File
	mod - platforms/win32/winbareos64.spec	Diff File
master 72344c48 2014-06-30 12:43 Philipp Storz Committer: Marco van Wieringen Ported: N/A Details Diff	Fix typo for Vista Compat in make call Now we call make correctly to use the vista stuff.
	mod - platforms/win32/winbareos32.spec	Diff File
	mod - platforms/win32/winbareos64.spec	Diff File

Reporting new Issues is disabled, please Report new Issues at https://github.com/bareos/bareos/issues

Changesets: bareos