Re: NTBackup requires 18-23 hours to complete.

Note that while SBSBackup does use NTbackup, they are not entirely the same thing. I'm not sure if you use SBSbackup, or only the native NTbackup to configure your backups. I also don't know what part DPM might play in all of this, if any.

Considering you want something different than SBSBackup offers, I'd suggest you run the backup configuration wizard and elect *not* to use SBS backup, and do your configuration via NTbackup, or a third party backup application.

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


"Sean" <Sean@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:B3143E79-3B3C-4E96-8558-5866D54321E3@xxxxxxxxxxxxxxxx
Les,
I understand that NTBackup wants to do everything all at once, but I belive
that is where it is hurting itself. I eliminated the 2 volumes that were
taking approx 6 hours and 8+ hours from my backup job and ran it last night.
I had to cancel it this morning since it wasn't finished with the remaining
volumes which should have taken 4-5 hours and it wasn't 50% through that.

Somewhere NTBackup is either a lower priority or is not working correctly.
IT is not my drives as I have run robocopy batches on them copying/verify
50GB and it didn't take < 1 hour to complete. Seems only NTBackup is having
trouble with throughput.

--
Sean


"Les Connor [SBS MVP]" wrote:

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: NTBackup requires 18-23 hours to complete.
    ... going to spend the money to buy huge usb drives. ... that I am using SBS and I know it works, but that something is wrong in the ... else, I never implied that the SBS backup didn't work, only that the wizard ... NTBackup due to the wizards insistance on including ...
    (microsoft.public.windows.server.sbs)
  • Re: Disk with NTDS failing
    ... using NTBackup to usb drive starts at 5:00 pm. ... Backup Exec to DLT tape starts at 11:00 pm. ... on total server restores using NTBackup. ... I put those onto the replacement drive, with the same drive letter, and SBS ...
    (microsoft.public.windows.server.sbs)
  • Re: NtBackup hangs during scheduled backups
    ... In your logs, ntbackup isn't starting. ... You may try deleting them all if they exist, and then try sbsbackup wizard, which will create a scheduled backup. ... Les Connor [SBS MVP] ...
    (microsoft.public.windows.server.sbs)
  • Re: NTBackup requires 18-23 hours to complete.
    ... troubleshooting involved replacing my existing hardware with USB drives, ... Les Connor [SBS MVP] ... else, I never implied that the SBS backup didn't work, only that the ... NTBackup due to the wizards insistance on ...
    (microsoft.public.windows.server.sbs)
  • Re: Backup continues to fail
    ... seems like it is a red herring of some sort. ... Les Connor [SBS MVP] ... > has been around for a while, going tback to Win2K and CDRW drive backup ... >> SBSbackup will run tonight - tomorrow we'll see the result. ...
    (microsoft.public.windows.server.sbs)