Resuming failed backup

[Guest Ben]

I am using Windows Backup (NTbackup.exe) to backup 1TB of files to a network

drive. Because it takes 36 hours for this to complete, the chance of it

failing is high.

 

Can I resume a failed backup (without resorting to a subsequent differential

backup)?

 

Is robocopy a better solution for what I'm doing? My concern is with with

"in use" files, (ie. a PST files was causing Robocopy to stop, retry, stop

retry endlessly).

 

What is your recommendation, besides using a third party tool.

 

Your help is greatly appreciated.

 

-Ben

[Guest Pegasus \(MVP\)]

Re: Resuming failed backup

 

 

"Ben" <Ben@discussions.microsoft.com> wrote in message

news:673984AC-2BBB-42DA-8A59-3D63F91012E9@microsoft.com...

>I am using Windows Backup (NTbackup.exe) to backup 1TB of files to a

>network

> drive. Because it takes 36 hours for this to complete, the chance of it

> failing is high.

>

> Can I resume a failed backup (without resorting to a subsequent

> differential

> backup)?

>

> Is robocopy a better solution for what I'm doing? My concern is with with

> "in use" files, (ie. a PST files was causing Robocopy to stop, retry, stop

> retry endlessly).

>

> What is your recommendation, besides using a third party tool.

>

> Your help is greatly appreciated.

>

> -Ben

>

>

 

Having a backup job that takes 36 hours is unacceptable

for two reasons:

a) As you say, the chances of it failing are high.

b) It could take up to 36 hours to retrieve a file.

 

I would prefer robocopy any time. It would let you

retrieve files instantly. You should invoke it inside

a batch file and precede it with a command that checks if

Outlook is active or not. Note that robocopy has a switch

that sets the number of retries.

 

Note that robocopy won't back up the System State.

You can still use ntbackup for this part of the job.

[Guest Ben]

Re: Resuming failed backup

 

Pegasus,

 

Thank you for that answer, it is exactly what I wanted to hear.

 

I am now using Robocopy for file backups (with switches to accomidate "in

use" files)

I am using NTBackup.exe to make an ASR for system state.

 

-Ben

 

"Pegasus (MVP)" <I.can@fly.com> wrote in message

news:uZrVnYh%23HHA.4432@TK2MSFTNGP02.phx.gbl...

>

> "Ben" <Ben@discussions.microsoft.com> wrote in message

> news:673984AC-2BBB-42DA-8A59-3D63F91012E9@microsoft.com...

>>I am using Windows Backup (NTbackup.exe) to backup 1TB of files to a

>>network

>> drive. Because it takes 36 hours for this to complete, the chance of it

>> failing is high.

>>

>> Can I resume a failed backup (without resorting to a subsequent

>> differential

>> backup)?

>>

>> Is robocopy a better solution for what I'm doing? My concern is with

>> with

>> "in use" files, (ie. a PST files was causing Robocopy to stop, retry,

>> stop

>> retry endlessly).

>>

>> What is your recommendation, besides using a third party tool.

>>

>> Your help is greatly appreciated.

>>

>> -Ben

>>

>>

>

> Having a backup job that takes 36 hours is unacceptable

> for two reasons:

> a) As you say, the chances of it failing are high.

> b) It could take up to 36 hours to retrieve a file.

>

> I would prefer robocopy any time. It would let you

> retrieve files instantly. You should invoke it inside

> a batch file and precede it with a command that checks if

> Outlook is active or not. Note that robocopy has a switch

> that sets the number of retries.

>

> Note that robocopy won't back up the System State.

> You can still use ntbackup for this part of the job.

>

[Guest Pegasus \(MVP\)]

Re: Resuming failed backup

 

Thanks for the feedback. If you want to do a really fine

job then you could put the robocopy command inside

a batch file, followed by a few more lines of code that

extract the summary and send it to you automatically

by EMail.

 

 

"Ben" <ben@mcpbooks.com> wrote in message

news:O%23nyP9u%23HHA.3800@TK2MSFTNGP03.phx.gbl...

> Pegasus,

>

> Thank you for that answer, it is exactly what I wanted to hear.

>

> I am now using Robocopy for file backups (with switches to accomidate "in

> use" files)

> I am using NTBackup.exe to make an ASR for system state.

>

> -Ben

>

> "Pegasus (MVP)" <I.can@fly.com> wrote in message

> news:uZrVnYh%23HHA.4432@TK2MSFTNGP02.phx.gbl...

>>

>> "Ben" <Ben@discussions.microsoft.com> wrote in message

>> news:673984AC-2BBB-42DA-8A59-3D63F91012E9@microsoft.com...

>>>I am using Windows Backup (NTbackup.exe) to backup 1TB of files to a

>>>network

>>> drive. Because it takes 36 hours for this to complete, the chance of it

>>> failing is high.

>>>

>>> Can I resume a failed backup (without resorting to a subsequent

>>> differential

>>> backup)?

>>>

>>> Is robocopy a better solution for what I'm doing? My concern is with

>>> with

>>> "in use" files, (ie. a PST files was causing Robocopy to stop, retry,

>>> stop

>>> retry endlessly).

>>>

>>> What is your recommendation, besides using a third party tool.

>>>

>>> Your help is greatly appreciated.

>>>

>>> -Ben

>>>

>>>

>>

>> Having a backup job that takes 36 hours is unacceptable

>> for two reasons:

>> a) As you say, the chances of it failing are high.

>> b) It could take up to 36 hours to retrieve a file.

>>

>> I would prefer robocopy any time. It would let you

>> retrieve files instantly. You should invoke it inside

>> a batch file and precede it with a command that checks if

>> Outlook is active or not. Note that robocopy has a switch

>> that sets the number of retries.

>>

>> Note that robocopy won't back up the System State.

>> You can still use ntbackup for this part of the job.

>>

>

>