Ntbackup (Windows Backup)

[Bob Felton]

Windows 2000 Server with SP4.

After doing a backup of c:\*.* and System State, the backup report
indicates many files were found open and not backed up. Are these
files necessary to fully restore the system to the state it was at at
time of backup? Are they required to do a restore at all? If yes,
how does one back them up so as to be able to fully restore the sytem
to the state it was at when backed up?

Tnx!

 

[Pegasus \(MVP\)]

You did not state the names of the files that were not
backed up. Are they system files?

You need to be aware of some limitations when backing
up the System State. If your disk gets corrupted or if it
fails then you will presumably want to restore Win2000
from your backup tape. This can be somewhat difficult,
seeing that you must start with a clean disk, with no tools
to read your tape.

These days, with disk prices at a very low level, it is
often easier to use an imaging product such as DriveImage
or Ghost, to create an image file of drive C: and store that
file on some other disk. Recovery is then very easy an can
be achieved in about 30 minutes. However, this only works
if you split your disk: Win2000 & applications go on C:, all
your data goes on D:.

 

[dcdon]

I think he is the same poster as the very next one, and he wants to do normal full tape backup
using NT backup.

BTW, Top of the evening to you. I hope this finds you in good spirits.

don
--------------



You did not state the names of the files that were not
backed up. Are they system files?

You need to be aware of some limitations when backing
up the System State. If your disk gets corrupted or if it
fails then you will presumably want to restore Win2000
from your backup tape. This can be somewhat difficult,
seeing that you must start with a clean disk, with no tools
to read your tape.

These days, with disk prices at a very low level, it is
often easier to use an imaging product such as DriveImage
or Ghost, to create an image file of drive C: and store that
file on some other disk. Recovery is then very easy an can
be achieved in about 30 minutes. However, this only works
if you split your disk: Win2000 & applications go on C:, all
your data goes on D:.

 

[Bob Felton]

The machine is a Windows domain controller running only those services
required for that function and file and print sharing, DNS, DHCP, and
McAfee NetShield.

The files listed on the report as not being backed up are:

UsrClass.dat UsrClass.dat.log
catalogs51FD000452.FDD catalogs51SM000452.SM
QTC_TEMP.000 QTC_TEMP.001
QTC_TEMP.002 adamm.log
pv1.ldb pv1.mdb
BeTopCat.idx BeTopCat.ldb
scepol.log dhcp.mdb
DhcpSrvLog.Sat j50.log (dhcp)
tmp.edb dns.log
ex031101.log j50.log (wins)
wins.mdb winstmp.mdb
JET7015.tmp JET8.tmp
JETE.tmp

To restore the system, I would first reinstall Windows 2000 Server
from the distribution CDROM, formating the drive with the same
partition structure prior to the reinstall. I would then invoke
Windows Backup (ntbackup) and restore from the most recent c:\*.* and
System State backup which is on both tape and an external USB HDD.

The server has two disks installed:

Disk 0: 18GB, partitioned into 4GB (system partition) and 14GB
(the 14GB partition was the "public" partition for user use until it
got filled up; all data was then moved to a newly installed drive)

Disk 1: 36GB, partioned as one partition (user use)

I have tried disk imaging products. However, the imaging products I
have purchased either do not support imagaing of a server disk or do
not support the particular scsi controller chip being used.

You did not state the names of the files that were not
backed up. Are they system files?

You need to be aware of some limitations when backing
up the System State. If your disk gets corrupted or if it
fails then you will presumably want to restore Win2000
from your backup tape. This can be somewhat difficult,
seeing that you must start with a clean disk, with no tools
to read your tape.

These days, with disk prices at a very low level, it is
often easier to use an imaging product such as DriveImage
or Ghost, to create an image file of drive C: and store that
file on some other disk. Recovery is then very easy an can
be achieved in about 30 minutes. However, this only works
if you split your disk: Win2000 & applications go on C:, all
your data goes on D:.

 

[Bob Felton]

Nope, I am not that poster.

I think he is the same poster as the very next one, and he wants to do normal full tape backup
using NT backup.

BTW, Top of the evening to you. I hope this finds you in good spirits.

don
--------------



You did not state the names of the files that were not
backed up. Are they system files?

You need to be aware of some limitations when backing
up the System State. If your disk gets corrupted or if it
fails then you will presumably want to restore Win2000
from your backup tape. This can be somewhat difficult,
seeing that you must start with a clean disk, with no tools
to read your tape.

These days, with disk prices at a very low level, it is
often easier to use an imaging product such as DriveImage
or Ghost, to create an image file of drive C: and store that
file on some other disk. Recovery is then very easy an can
be achieved in about 30 minutes. However, this only works
if you split your disk: Win2000 & applications go on C:, all
your data goes on D:.

 

[Pegasus \(MVP\)]

The locked files you report seem to belong to two classes:
- Temporary files - you do not need those for a system restoration
- Application-specific files - you may need them for a restoration.
Make sure to close down all apps ***before*** you attempt a
backup so that locked files get unlocked.

AFAIK you cannot restore Win2000 into C:\WinNT if c:\WinNT is
your current Win2000 system folder. Your plan to restore Win2000
by reinstalling Win2000 off a CD seems to be flawed. I believe you
must install the temporary copy of Win2000 into something other than
C:\WinNT - which you can only do if you apply some tricks.

While it is true that some products such as DriveImage will not
work on servers (unless you buy the expensive server version),
this restriction does not apply if you use the DriveImage emergency
recovery disk. I have done it lots of times.

The machine is a Windows domain controller running only those services
required for that function and file and print sharing, DNS, DHCP, and
McAfee NetShield.

The files listed on the report as not being backed up are:

UsrClass.dat UsrClass.dat.log
catalogs51FD000452.FDD catalogs51SM000452.SM
QTC_TEMP.000 QTC_TEMP.001
QTC_TEMP.002 adamm.log
pv1.ldb pv1.mdb
BeTopCat.idx BeTopCat.ldb
scepol.log dhcp.mdb
DhcpSrvLog.Sat j50.log (dhcp)
tmp.edb dns.log
ex031101.log j50.log (wins)
wins.mdb winstmp.mdb
JET7015.tmp JET8.tmp
JETE.tmp

To restore the system, I would first reinstall Windows 2000 Server
from the distribution CDROM, formating the drive with the same
partition structure prior to the reinstall. I would then invoke
Windows Backup (ntbackup) and restore from the most recent c:\*.* and
System State backup which is on both tape and an external USB HDD.

The server has two disks installed:

Disk 0: 18GB, partitioned into 4GB (system partition) and 14GB
(the 14GB partition was the "public" partition for user use until it
got filled up; all data was then moved to a newly installed drive)

Disk 1: 36GB, partioned as one partition (user use)

I have tried disk imaging products. However, the imaging products I
have purchased either do not support imagaing of a server disk or do
not support the particular scsi controller chip being used.

 

[Enkidu]

Like Pegasus says. In addition the things that appear to be giving you
trouble are Indexing Services (I think), wins, and dhcp. In addition
is UserClass a user on the machine? If so, he should be logged off.
The services could be stopped with a script.

Cheers,

Cliff

The machine is a Windows domain controller running only those services
required for that function and file and print sharing, DNS, DHCP, and
McAfee NetShield.

The files listed on the report as not being backed up are:

UsrClass.dat UsrClass.dat.log
catalogs51FD000452.FDD catalogs51SM000452.SM
QTC_TEMP.000 QTC_TEMP.001
QTC_TEMP.002 adamm.log
pv1.ldb pv1.mdb
BeTopCat.idx BeTopCat.ldb
scepol.log dhcp.mdb
DhcpSrvLog.Sat j50.log (dhcp)
tmp.edb dns.log
ex031101.log j50.log (wins)
wins.mdb winstmp.mdb
JET7015.tmp JET8.tmp
JETE.tmp

To restore the system, I would first reinstall Windows 2000 Server
from the distribution CDROM, formating the drive with the same
partition structure prior to the reinstall. I would then invoke
Windows Backup (ntbackup) and restore from the most recent c:\*.* and
System State backup which is on both tape and an external USB HDD.

The server has two disks installed:

Disk 0: 18GB, partitioned into 4GB (system partition) and 14GB
(the 14GB partition was the "public" partition for user use until it
got filled up; all data was then moved to a newly installed drive)

Disk 1: 36GB, partioned as one partition (user use)

I have tried disk imaging products. However, the imaging products I
have purchased either do not support imagaing of a server disk or do
not support the particular scsi controller chip being used.

 

[Bob Felton]

The only users setup on the machine are administrator, backup, and two
other "administrator" accounts. "UserClass" is not a user, either on
the machine or in Active Directory. When the c:\*.* and System State
backup is done, account "administrator" is logged on to the server
and no user machines are logged in either. Stopping the services
prior to performing the backup is a good idea. Thanks!

 

[Bob Felton]

It was my understanding based on MSKB article 301254 that a system
could be fully restored using the method I outlined. If this article
lies, then I need to know so I can implement another, fullproof,
method of being able to restore the system to the state of the last
System State backup.

The locked files you report seem to belong to two classes:
- Temporary files - you do not need those for a system restoration
- Application-specific files - you may need them for a restoration.
Make sure to close down all apps ***before*** you attempt a
backup so that locked files get unlocked.

AFAIK you cannot restore Win2000 into C:\WinNT if c:\WinNT is
your current Win2000 system folder. Your plan to restore Win2000
by reinstalling Win2000 off a CD seems to be flawed. I believe you
must install the temporary copy of Win2000 into something other than
C:\WinNT - which you can only do if you apply some tricks.

While it is true that some products such as DriveImage will not
work on servers (unless you buy the expensive server version),
this restriction does not apply if you use the DriveImage emergency
recovery disk. I have done it lots of times.

 

[Pegasus \(MVP\)]

The article talks about restoration in case of data loss. It does not
talk about a complete rebuild. Anyway, as I said before, I ***believe**
that your method won't work - I don't know for sure. If you don't like
the imaging method I proposed then you should do this for your
own peace of mind:

- Buy or borrow a suitable hard disk (they are cheap)
- Try your method

No matter what the result, this will be an extremely valuable
exercise for you - you will be able to tell your manager with complete
confidence that you can restore the system from a backup tape.

It was my understanding based on MSKB article 301254 that a system
could be fully restored using the method I outlined. If this article
lies, then I need to know so I can implement another, fullproof,
method of being able to restore the system to the state of the last
System State backup.

 

[Bob Felton]

Good idea to try the procedure. However, SCSI drives arent't cheap.
I would have to convince my client of the need to buy one to try the
method.

The article talks about restoration in case of data loss. It does not
talk about a complete rebuild. Anyway, as I said before, I ***believe**
that your method won't work - I don't know for sure. If you don't like
the imaging method I proposed then you should do this for your
own peace of mind:

- Buy or borrow a suitable hard disk (they are cheap)
- Try your method

No matter what the result, this will be an extremely valuable
exercise for you - you will be able to tell your manager with complete
confidence that you can restore the system from a backup tape.

 

[Pegasus \(MVP\)]

Try it with a cheap IDE disk. The machine will still load the
driver for your SCSI adapter, and you can check under Services
if that driver is indeed active after the restoration.

Good idea to try the procedure. However, SCSI drives arent't cheap.
I would have to convince my client of the need to buy one to try the
method.

 

[Bob Felton]

Should I disconnect the SCSI drives when I do the test? Will the fact
that the drive configuration in the backed up system state being for
SCSI drives only have any affect on the operation of the system after
the test restore to a previously non-existent IDE drive? i.e., a
reboot after the restore to check for proper server configuration.

Try it with a cheap IDE disk. The machine will still load the
driver for your SCSI adapter, and you can check under Services
if that driver is indeed active after the restoration.

 

[Pegasus \(MVP\)]

Yes, you MUST disconnect the SCSI drives during the restoration,
since you don't want to run any risk of them being affected in some
way.

If you never had any IDE drives installed then you may experience
some problems after the test restoration. You can probably avoid
them by doing this:

- Install the IDE drive as a slave disk in your current system
- Take the backup
- Disconnect the SCSI disks
- Make the IDE drive the master disk
- Perform your restoration

If it was my machine then I would use DriveImage to copy
drive C: from the SCSI drive to my IDE drive, then test the
whole thing. This would take 30 minutes of elapsed time,
and five minutes of my own time. But then you're not much
in favour of DriveImage . . .

Should I disconnect the SCSI drives when I do the test? Will the fact
that the drive configuration in the backed up system state being for
SCSI drives only have any affect on the operation of the system after
the test restore to a previously non-existent IDE drive? i.e., a
reboot after the restore to check for proper server configuration.

 

[Bob Felton]

Thanks for your continued responses, Pegasus. Much appreciated.

I purchased a copy of Drive Image 2002 last year believing it would
work on a Windows 2000 Server OS. It did not, so I shelved it. I
looked at Power Quest's support web site for Drive Image product
documentation and did a search on ERD and did not find any reference
to it. Can you advise how this disk is created? Does it boot into
some form of DOS to do its "magic"? If it boots into some form of
Linux, then I can't use it as Linux does not support the SCSI
controller chip being used in the server (Gateway server class
machine). I also purchased NovaStor's Instant Recovery which does
work on a server OS (it runs from a boot disk that boots Linux), but I
discovered it didn't support the SCSI chip set. And, per their web
site, Linux still doesn't support the chip set.

Yes, you MUST disconnect the SCSI drives during the restoration,
since you don't want to run any risk of them being affected in some
way.

If you never had any IDE drives installed then you may experience
some problems after the test restoration. You can probably avoid
them by doing this:

- Install the IDE drive as a slave disk in your current system
- Take the backup
- Disconnect the SCSI disks
- Make the IDE drive the master disk
- Perform your restoration

If it was my machine then I would use DriveImage to copy
drive C: from the SCSI drive to my IDE drive, then test the
whole thing. This would take 30 minutes of elapsed time,
and five minutes of my own time. But then you're not much
in favour of DriveImage . . .

 

[Pegasus \(MVP\)]

My copy of DriveImage is much older, so my advice would be
of limited use.

I have just spent some time on the PowerQuest site. It seems
the PowerQuest RecoveryEnvironment (PQRE) is the function
you require under DriveImage2002. Have you looked at it in
detail? The PowerQuest search function lists numerous hits
for PQRE!

Thanks for your continued responses, Pegasus. Much appreciated.

I purchased a copy of Drive Image 2002 last year believing it would
work on a Windows 2000 Server OS. It did not, so I shelved it. I
looked at Power Quest's support web site for Drive Image product
documentation and did a search on ERD and did not find any reference
to it. Can you advise how this disk is created? Does it boot into
some form of DOS to do its "magic"? If it boots into some form of
Linux, then I can't use it as Linux does not support the SCSI
controller chip being used in the server (Gateway server class
machine). I also purchased NovaStor's Instant Recovery which does
work on a server OS (it runs from a boot disk that boots Linux), but I
discovered it didn't support the SCSI chip set. And, per their web
site, Linux still doesn't support the chip set.

 

[Bob Felton]

Seems PQRE is only in the "V7" version of Drive Image, not the "2002"
version I have. Also, from the V7 User's Guide, PQRE is only for
restoring an image, not creating one. So, the "sever" version of
Drive Image is still required to be able to create an image from a
machine running Windows 2000 Server.

Have you heard of Active Disk Image from LSoft Technologies? See
www.disk-image.net? Any comments? Thanks!

My copy of DriveImage is much older, so my advice would be
of limited use.

I have just spent some time on the PowerQuest site. It seems
the PowerQuest RecoveryEnvironment (PQRE) is the function
you require under DriveImage2002. Have you looked at it in
detail? The PowerQuest search function lists numerous hits
for PQRE!

 

[Pegasus \(MVP\)]

Since PQDI4 meets all my requirements (including creating
server images!) I have not looked at other packages.

Seems PQRE is only in the "V7" version of Drive Image, not the "2002"
version I have. Also, from the V7 User's Guide, PQRE is only for
restoring an image, not creating one. So, the "sever" version of
Drive Image is still required to be able to create an image from a
machine running Windows 2000 Server.

Have you heard of Active Disk Image from LSoft Technologies? See
www.disk-image.net? Any comments? Thanks!