Verifying Windows Server 2008 backup

  • Thread starter Thread starter Dominick
  • Start date Start date
D

Dominick

Guest
I have my first Windows Server 2008 system online int he network, and I
have Backup installed and operational. What I have done in the past, not
that sophisticated, is I have a batch file form my workstation that
would do an appropriate DIR command for every server and PC in our
network, so I could tell by size and date if backups ran the night
before. Took about 10 seconds to peruse the batch file output.

But now, I notice the new backup grabs the disk drive and uses it as a
dedicated resource -- it does not even show up in File Explorer. So how
can I determine remotely whether the backup worked or not?
 
Re: Verifying Windows Server 2008 backup


"Dominick" <at@yourservice.com> wrote in message
news:utVHYGEnIHA.1188@TK2MSFTNGP04.phx.gbl...
>I have my first Windows Server 2008 system online int he network, and I
>have Backup installed and operational. What I have done in the past, not
>that sophisticated, is I have a batch file form my workstation that would
>do an appropriate DIR command for every server and PC in our network, so I
>could tell by size and date if backups ran the night before. Took about 10
>seconds to peruse the batch file output.
>
> But now, I notice the new backup grabs the disk drive and uses it as a
> dedicated resource -- it does not even show up in File Explorer. So how
> can I determine remotely whether the backup worked or not?

The standard method to check the backup run is to examine
the backup log files. You could do it manually, which is
unsatisfactory because you tend to forget after a while. Automating
the process works much better: Use a command line mailer to send
you a copy of the log file once every 8 or so calendar days.
 
Re: Verifying Windows Server 2008 backup

Pegasus (MVP) wrote:
> "Dominick" <at@yourservice.com> wrote in message
> news:utVHYGEnIHA.1188@TK2MSFTNGP04.phx.gbl...
>> I have my first Windows Server 2008 system online int he network, and I
>> have Backup installed and operational. What I have done in the past, not
>> that sophisticated, is I have a batch file form my workstation that would
>> do an appropriate DIR command for every server and PC in our network, so I
>> could tell by size and date if backups ran the night before. Took about 10
>> seconds to peruse the batch file output.
>>
>> But now, I notice the new backup grabs the disk drive and uses it as a
>> dedicated resource -- it does not even show up in File Explorer. So how
>> can I determine remotely whether the backup worked or not?
>
> The standard method to check the backup run is to examine
> the backup log files. You could do it manually, which is
> unsatisfactory because you tend to forget after a while. Automating
> the process works much better: Use a command line mailer to send
> you a copy of the log file once every 8 or so calendar days.
>
>
Yes that is what I stumbled on. I modified my batch file to just check
the directory. My understanding is the log file gets created only on a
problem. I have run backup a could of times and the Log directory is empty.
 
Re: Verifying Windows Server 2008 backup


"Dominick" <at@yourservice.com> wrote in message
news:Ohw48xInIHA.3512@TK2MSFTNGP03.phx.gbl...
> Pegasus (MVP) wrote:
>> "Dominick" <at@yourservice.com> wrote in message
>> news:utVHYGEnIHA.1188@TK2MSFTNGP04.phx.gbl...
>>> I have my first Windows Server 2008 system online int he network, and I
>>> have Backup installed and operational. What I have done in the past, not
>>> that sophisticated, is I have a batch file form my workstation that
>>> would do an appropriate DIR command for every server and PC in our
>>> network, so I could tell by size and date if backups ran the night
>>> before. Took about 10 seconds to peruse the batch file output.
>>>
>>> But now, I notice the new backup grabs the disk drive and uses it as a
>>> dedicated resource -- it does not even show up in File Explorer. So how
>>> can I determine remotely whether the backup worked or not?
>>
>> The standard method to check the backup run is to examine
>> the backup log files. You could do it manually, which is
>> unsatisfactory because you tend to forget after a while. Automating
>> the process works much better: Use a command line mailer to send
>> you a copy of the log file once every 8 or so calendar days.
> Yes that is what I stumbled on. I modified my batch file to just check
> the directory. My understanding is the log file gets created only on a
> problem. I have run backup a could of times and the Log directory is
> empty.

I am not familiar with ntbackup.exe but I doubt very much
that its log file contains only problem reports. This would run
contrary to past practice and sheer common sense. Previoius
versions of ntbackup allowed you to examine the log files from
its GUI interface, provided that you were logged on under the
same account as the one used to run ntbackup.exe. Alternatively
one could search c:\documents and settings recursively for files
backup??.log. Many an administrator has claimed in this
newsgroup that they did not exist, and found that they did
indeed when checking more carefully. Have another look!
 
Re: Verifying Windows Server 2008 backup

"Pegasus (MVP)" <I.can@fly.com.oz> wrote in message
news:uJLHigJnIHA.4536@TK2MSFTNGP06.phx.gbl...
>
> "Dominick" <at@yourservice.com> wrote in message
> news:Ohw48xInIHA.3512@TK2MSFTNGP03.phx.gbl...
>> Pegasus (MVP) wrote:
>>> "Dominick" <at@yourservice.com> wrote in message
>>> news:utVHYGEnIHA.1188@TK2MSFTNGP04.phx.gbl...
>>>> I have my first Windows Server 2008 system online int he network, and I
>>>> have Backup installed and operational. What I have done in the past,
>>>> not that sophisticated, is I have a batch file form my workstation that
>>>> would do an appropriate DIR command for every server and PC in our
>>>> network, so I could tell by size and date if backups ran the night
>>>> before. Took about 10 seconds to peruse the batch file output.
>>>>
>>>> But now, I notice the new backup grabs the disk drive and uses it as a
>>>> dedicated resource -- it does not even show up in File Explorer. So how
>>>> can I determine remotely whether the backup worked or not?
>>>
>>> The standard method to check the backup run is to examine
>>> the backup log files. You could do it manually, which is
>>> unsatisfactory because you tend to forget after a while. Automating
>>> the process works much better: Use a command line mailer to send
>>> you a copy of the log file once every 8 or so calendar days.
>> Yes that is what I stumbled on. I modified my batch file to just check
>> the directory. My understanding is the log file gets created only on a
>> problem. I have run backup a could of times and the Log directory is
>> empty.
>
> I am not familiar with ntbackup.exe but I doubt very much
> that its log file contains only problem reports. This would run
> contrary to past practice and sheer common sense. Previoius
> versions of ntbackup allowed you to examine the log files from
> its GUI interface, provided that you were logged on under the
> same account as the one used to run ntbackup.exe. Alternatively
> one could search c:\documents and settings recursively for files
> backup??.log. Many an administrator has claimed in this
> newsgroup that they did not exist, and found that they did
> indeed when checking more carefully. Have another look!
>


Ntbackup is deprecated. It isn't in Server 2008. I'm not sure what logs are
available with 2008 as I haven't had much chance to test the backup feature.
All I can say is it's very different from ntbackup.

http://technet2.microsoft.com/windo...a834-43f9-9e8a-71aeb25fa4ad1033.mspx?mfr=true

--
Kerry Brown
MS-MVP - Windows Desktop Experience: Systems Administration
http://www.vistahelp.ca/phpBB2/
 
Re: Verifying Windows Server 2008 backup

Pegasus (MVP) wrote:
> "Dominick" <at@yourservice.com> wrote in message
> news:Ohw48xInIHA.3512@TK2MSFTNGP03.phx.gbl...
>> Pegasus (MVP) wrote:
>>> "Dominick" <at@yourservice.com> wrote in message
>>> news:utVHYGEnIHA.1188@TK2MSFTNGP04.phx.gbl...
>>>> I have my first Windows Server 2008 system online int he network, and I
>>>> have Backup installed and operational. What I have done in the past, not
>>>> that sophisticated, is I have a batch file form my workstation that
>>>> would do an appropriate DIR command for every server and PC in our
>>>> network, so I could tell by size and date if backups ran the night
>>>> before. Took about 10 seconds to peruse the batch file output.
>>>>
>>>> But now, I notice the new backup grabs the disk drive and uses it as a
>>>> dedicated resource -- it does not even show up in File Explorer. So how
>>>> can I determine remotely whether the backup worked or not?
>>> The standard method to check the backup run is to examine
>>> the backup log files. You could do it manually, which is
>>> unsatisfactory because you tend to forget after a while. Automating
>>> the process works much better: Use a command line mailer to send
>>> you a copy of the log file once every 8 or so calendar days.
>> Yes that is what I stumbled on. I modified my batch file to just check
>> the directory. My understanding is the log file gets created only on a
>> problem. I have run backup a could of times and the Log directory is
>> empty.
>
> I am not familiar with ntbackup.exe but I doubt very much
> that its log file contains only problem reports. This would run
> contrary to past practice and sheer common sense. Previoius
> versions of ntbackup allowed you to examine the log files from
> its GUI interface, provided that you were logged on under the
> same account as the one used to run ntbackup.exe. Alternatively
> one could search c:\documents and settings recursively for files
> backup??.log. Many an administrator has claimed in this
> newsgroup that they did not exist, and found that they did
> indeed when checking more carefully. Have another look!
>
>
NTBACKUP is not the server-based backup used in Windows Server 2008.
 
Re: Verifying Windows Server 2008 backup


"Dominick" <at@yourservice.com> wrote in message
news:uzufp1OnIHA.4536@TK2MSFTNGP06.phx.gbl...
> Pegasus (MVP) wrote:
>> "Dominick" <at@yourservice.com> wrote in message
>> news:Ohw48xInIHA.3512@TK2MSFTNGP03.phx.gbl...
>>> Pegasus (MVP) wrote:
>>>> "Dominick" <at@yourservice.com> wrote in message
>>>> news:utVHYGEnIHA.1188@TK2MSFTNGP04.phx.gbl...
>>>>> I have my first Windows Server 2008 system online int he network, and
>>>>> I have Backup installed and operational. What I have done in the past,
>>>>> not that sophisticated, is I have a batch file form my workstation
>>>>> that would do an appropriate DIR command for every server and PC in
>>>>> our network, so I could tell by size and date if backups ran the night
>>>>> before. Took about 10 seconds to peruse the batch file output.
>>>>>
>>>>> But now, I notice the new backup grabs the disk drive and uses it as a
>>>>> dedicated resource -- it does not even show up in File Explorer. So
>>>>> how can I determine remotely whether the backup worked or not?
>>>> The standard method to check the backup run is to examine
>>>> the backup log files. You could do it manually, which is
>>>> unsatisfactory because you tend to forget after a while. Automating
>>>> the process works much better: Use a command line mailer to send
>>>> you a copy of the log file once every 8 or so calendar days.
>>> Yes that is what I stumbled on. I modified my batch file to just check
>>> the directory. My understanding is the log file gets created only on a
>>> problem. I have run backup a could of times and the Log directory is
>>> empty.
>>
>> I am not familiar with ntbackup.exe but I doubt very much
>> that its log file contains only problem reports. This would run
>> contrary to past practice and sheer common sense. Previoius
>> versions of ntbackup allowed you to examine the log files from
>> its GUI interface, provided that you were logged on under the
>> same account as the one used to run ntbackup.exe. Alternatively
>> one could search c:\documents and settings recursively for files
>> backup??.log. Many an administrator has claimed in this
>> newsgroup that they did not exist, and found that they did
>> indeed when checking more carefully. Have another look!
> NTBACKUP is not the server-based backup used in Windows Server 2008.

Fine. I would now check the documentation for the logging
facilities included in the Windows Server 2008 backup solution.
I refuse to believe that flawless runs are not fully logged.
 
Re: Verifying Windows Server 2008 backup

"Pegasus (MVP)" wrote:

> I refuse to believe that flawless runs are not fully logged.

Also strikes me that if you're doing a disk-based backup, then having one on
which you CAN'T check the results conventionally is throwing-away the
greatest advantages of this method of working (transparency and
dependability) over tape backups.

MS Robocopy might be a better alternative. Or the proprietary software,
Second Copy.
 
Re: Verifying Windows Server 2008 backup

Anteaus wrote:
> "Pegasus (MVP)" wrote:
>
>> I refuse to believe that flawless runs are not fully logged.
>
> Also strikes me that if you're doing a disk-based backup, then having one on
> which you CAN'T check the results conventionally is throwing-away the
> greatest advantages of this method of working (transparency and
> dependability) over tape backups.
>
> MS Robocopy might be a better alternative. Or the proprietary software,
> Second Copy.
>
>
The backup software is really good - lots of very nice features.
Excellent status support when you are on the machine. But no readable
status through a batch file from what I can see.

If anyone who is actually using the product would care to comment, chip
in if you see something I have missed. I appreciate all the comments,
but conjecture doesn't get me too far.
 
Back
Top