Re: NTBackup requires 18-23 hours to complete.



SBS backup does two backups of Exchange. One is a file based backup, including logfiles, the other is the 'Exchange Aware' backup, which commits the logfiles. I don't remember the exact details, but in order for both exchange and system state to be backed up in the one job, an SBS box has some custom settings.

When operating outside of SBS backup, or if using other backup methods in addition to SBS backup, one may need to make sure they don't step on each other.

I'd be inclined to either use SBS backup as-is; and leave the other methods out of the equation; but if that doesn't suit you - run the wizard and select 'do not use sbs backup' and do things your own way using whatever methods do suit you.

SBSbackup is designed to equal the lowest common denominator in a backup strategy that will restore the server.

--
Les Connor [SBS MVP]
________________________
Get the SBS BPA here:
http://support.microsoft.com/kb/940439/en-us


"Sean" <Sean@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:C6424499-229A-4475-B34E-0CC6C3072107@xxxxxxxxxxxxxxxx
Sorry didn't see your post in this thread.

I run the backup wizard and then customized the BKS file and excluded the
drives/folders that I don't want backed up. It works it just takes an
exceptionally long time to backup the exchange logs volume. I could exclude
it manually but then I wouldn't have the Exchange transaction logs backed up,
I'd have the Exchange Store though.

I've run NTBackup without the wizard on a few directories to see if I can
benchmark it's performance, but it's all over the place during business
hours. I've setup a scheduled backup tonight without the Logs and will see
how long it takes.
--
Sean


"Drasko" wrote:

"Sean" <Sean@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:6C2AAF37-A658-4013-BA4E-78BC0A3EE0E0@xxxxxxxxxxxxxxxx
> I'm looking for a solution to resolve the long time it takes for > NTBackup
> to
> complete on my SBS server. It seems everyone thinks I'm doing it wrong > and
> my
> backup/disaster plans are wrong and my choice of hardware is all wrong.
>
> I'm looking for a solution to a specific problem, the time it takes to
> complete a single backup. I'm not going to go out and throw USB drives
> into
> the mix since my plan uses other technologies, and I'm not going to go
> into
> them here since the plan is not the issue, it is the time it takes for
> NTBackup to complete.
>
> I welcome everyone's input, but I'm asking everyone to stay focused on > my
> problem and not continue to bash details that are not in question.
>
> Thanks and I hope I don't get flamed.

I'll repeat my question:

Sean!

Have you tried to make your own bks file with folders that you want to back
up? Create a simple batch file with ntbackup command line with options, and
make a schedule task to run daily?

Dra




.



Relevant Pages

  • Re: Exchange 2k SBS & M: drive
    ... You say "backup with the Exchange option in NTBackup" does this mean ... try this and scheduled it for a backup to a new folder I created in a ...
    (microsoft.public.exchange.admin)
  • Re: Exchange 2003 Backup
    ... for simpely backup of Datasets you can use the ... NTBackup, regard the restore issues you are able to restore data in item ... level by using Recovery groups. ... Circular logging is enabled but I will be doing an NTbackup of exchange ...
    (microsoft.public.exchange.admin)
  • Re: How to REALLY backup SBS2K3?
    ... If you back up the Exchange Store with the backup Wizard (or native ... NTBackup), you should be able to use a combination of the Exchange Recovery ...
    (microsoft.public.windows.server.sbs)
  • RE: ntbackup.exe hack with Exchange 2007, any negatives?
    ... not get NTBackup to see the Exchange 2007 information store. ... running ntbackup to remotely backup Exchange 2007. ... your Windows Server 2008/Exchange 2007 server, ...
    (microsoft.public.exchange.admin)
  • =?iso-8859-1?Q?Re:_Integrit=E4t_der_Datenbank_pr=FCfen?=
    ... Aber NTBACKUP funktioniert meist, wenn andere Produkte vielleicht ein problem haben ... ein "Backup mit NTBACKUP" ist immer eine guteIdee als Fehlersuche. ... dann ist es KEIN Exchange Problem sondern BackupSoftware ... Geht nicht -> "Eigentlich" sollte man das letzte erfolgreiche Backup restaurieren und die Logs anwenden lassen ...
    (microsoft.public.de.exchange)

Loading