Hi,

24.05.2008 15:46, Robin Bonin wrote:
> Thanks for the reply.
> 
> The reason I brought up ntbackup, is because that is what I use to
> backup our exchange store,

Yeah, that's one of the things you really need ntbackup for, currently.

> and in reading the documentation for
> ntbackup is where I learned normal vs diff vs incremental backups.
> 
> After thinking through it a little more,
> 
> I should be able to make
> a full backup of exchange once a month,  (40 Gig)
> a diff backup every day (size would grow each day by a few 100 megs)
> and then an incremental backup once a week (should be about the same
> size as the last diff backup)

Erm... in Baculas terms, that would be the other way around. A full, a 
weekly differential,. and daily incrementals. I don't know ntbackups 
terminology good enough to be sure it uses the same terminology, though.

> If there is a crash mid month, I would have to restore the full
> backup, all the weekly inc backups up to that day, then that days diff
> backup.

Similar - The full, the latest differential, and all subsequent 
incrementals in Baculas terms. That's what happens if you restore to 
the most recent state.

> These exchange backups will be dropped on to a backup drive in the
> server, then I will have bacula backup the contents of that drive
> (incremental only) to archive, and move the files off the server.
> 
> Any comments on this setup? I saw in the bacula wiki the option of
> backing up and exchange store, I but I have done restores from
> ntbackup backups before, and I feel safe with that setup. Also the
> wiki didn't mention if it could do other backups other than full.

The exchange agent is still not ready for production use, I believe, 
so I'd recommend to use your suggested approach. Especially if you 
know how to do your work with ntbackup.

Actually, the only important thing for you is to make sure you have 
all the data needed by ntbackup in case of a restore. That's rather 
easily done with Bacula today. The only downside is that a restore is 
a two-step process with longer downtime than strictly necessary.

Anyway, I believe what you want to do comes down to this:
Use ntbackup to run daily backups of your exchange data.
Use Bacula to safely store (or archive) these dumps.

In case of a restore, restore the dumps through Bacula and use 
ntbackup to restore the actual exchange data.

That's completey reasonable IMO.

Arno


> Thanks
> Robin
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Bacula-users mailing list
> Bacula-users AT lists.sourceforge DOT net
> https://lists.sourceforge.net/lists/listinfo/bacula-users
> 

-- 
Arno Lehmann
IT-Service Lehmann
www.its-lehmann.de

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users