Using IDR and CPS on Backup Exec and file exceptions

I've replaced NTbackup with Backup Exec 11d on an SBS 2003 Premium and just need help and advice with a few points.

1. The automated backup appears to work fine apart from the Job Status stating "Completed with exceptions"  
The 4 files are:
File is in use         : C:\Documents and Settings\Administrator\Local Settings\Temp\2\JET1.tmp
File is in use         : C:\Documents and Settings\Administrator\Local Settings\Temp\3\JET1.tmp
File is in use         : C:\WINDOWS\system32\dhcp\tmp.edb
File is in use         : C:\WINDOWS\system32\wins\winstmp.mdb

2a. Is IDR worth installing? I've seen several people on here criticise it. If not, what is the best recovery method using BE? The only two recoveries I've ever need to do meant spending a day setting up SBS and patching it, then letting the backup kick in (from NTbackup).

2b. How do you create a bootable diskette or even CD for SBS 2003 for a DR?

3. I'm having a problem installing CPS, as I the retail pack I bought had all the BE and Agent key (albeit with the BE key having a "0" instead of a "-".

Any ideas would be gratefully received.

Thanks,

Mike

mikeabc27Asked:
Who is Participating?
 
tomcahillConnect With a Mentor Commented:
I have found corrupt data rarely is corrupt.  At least when reported by BE.  A quick fix I have used successfully in the past is to cut and past the file in another directory, then cut and paste it back.  Re-run the backup and see if it is okay.

I have never used the IDR feature so I cannot comment on it.  I am going to look into it though.
0
 
tomcahillCommented:
To avoid the exceptions you need to enable the Advanced Open File.  (Tools, Options, Advanced Open File) (Or, in your jobs properties).

I don't believe that Backup Exec supports a boot disk recovery.  I think in a DR situation you need to install the OS and then load Backup Exec, then run a restore.

What is the problem you are having with CPS?

I am also drawing a blank, what does IDR stand for?
0
 
mikeabc27Author Commented:
Thanks for the advice on the exceptions Tom. I've ticked the box and tried another backup, but that failed with the following message:

Job name            : Backup 00001Job type            : BackupJob status          : Failed
Job log             : C:\Program Files\Symantec\Data\BEX_MPSERVER_00007.xml
Server name         : MPSERVERSelection list name : Backup 00001
Device name         : IBM 1Target name         : IBM 1Media set name      : Keep Data Infinitely - Do Not Allow Overwrite
All Media UsedLTO000002
Error category    : Resource ErrorsError             : e000fe36 - Corrupt data encountered.
See the job log for details.
For additional information regarding this error refer to link V-79-57344-65078

**********************************************************************

You're right BE doesn't support a boot diskette recovery.

IDR (Intelligent Data Recovery) is an option in BE. Under the Backup Strategy Tasks select "Prepare for Disaster Recovery" which takes you to the IDR Preparation Wizard. You can then create a Bootable CD or Tape (I'm using an IBM LTO2 on a X226 E Server which is not bootable) or copy the .dr file to a floppy (for manual restore). This combined with the coresponding backup tape "should" allow me to get out of an SBS reinstall and then restoring afterwards.    

I'm about to speak to Symantec about the CPS problem, which was a minor issue (key code problem).

Thanks,

Mike
0
Never miss a deadline with monday.com

The revolutionary project management tool is here!   Plan visually with a single glance and make sure your projects get done.

 
mikeabc27Author Commented:
Have to admit I was guilty of wanting to test your idea straightaway and there would have been about 20 users on it while it was backing up. Not a good time to backup. I'll try again when the scheduled backup starts at 1800 GMT, currently 1530. The inhouse database is written in Access and the problem files did were jetxx.tmp ones amongst others.

If that faiils, I'll cut and re-paste back like you suggest.

Thanks,

Mike

 
0
 
mikeabc27Author Commented:
I've ran a backup with Advanced Open File Option ticked and Automatically Select Open File Technology selected. Although now with only a few users are logged on remotely, I don't get any corrupted files, I still get the exceptions error on the same 4 files in my opening post with the "file in use" message.

The files cannot be copied, moved or deleted as they are in use.

Thanks,

Mike
0
 
tomcahillCommented:
it could mean that the VSS service is not working properly.  If you are using advanced file open then it should use the MS VSS (unless you purchased the symatnec add-on).

Try re-applying Windows Server SP2, that has fixed a lot of my clients BE VSS issues.
0
 
mikeabc27Author Commented:
VSS was set to manual and not started. I'll try a backup with it started.
0
 
mikeabc27Author Commented:

Failed again and Volume Shadow Copy turned itself off. Server will not install Server 2003 SP2 - downloads it, but just stays at the Installing stage.

The 4 missed files are :
File is in use         : C:\Documents and Settings\Administrator\Local Settings\Temp\2\JET1.tmp
File is in use         : C:\Documents and Settings\Administrator\Local Settings\Temp\3\JET1.tmp
File is in use         : C:\WINDOWS\system32\dhcp\tmp.edb
File is in use         : C:\WINDOWS\system32\wins\winstmp.mdb

The .tmp files are 0k and the oher 2 1Mb - do you think these being missing would cause a restore problem?
0
 
tomcahillCommented:
No they won't cause a restor problem.

However I would like to get SP2 re-installed.  That concerns me that it will not load.

Try rebooting the server. and installing again.
0
 
mikeabc27Author Commented:
No I've tried re-booting and tried several times, tried all suggestions in Micorosoft KB822798 and still it won't install.

It also took some time to get SBS SP1 installed.

0
 
tomcahillCommented:
hmm, how much ram does the server have?

Also, how much is being utilized?
0
 
mikeabc27Author Commented:
Thanks for persevering Tom.

4Gb installed, so on a 32 bit server already on the max. Some used by the onboard graphics.

Connecting remotely so cannot review memory usage/peaks at the moment, but will check later.

Thanks,

Mike
0
 
mikeabc27Author Commented:
Commit Charge (K)

Total (ave) 2263680
Limit  5886860
Peak 2430020

0
 
tomcahillCommented:
have you throttled the sql instances down?

check this out.
http://msmvps.com/blogs/bradley/archive/2005/02/04/34984.aspx

SQL can be taking up a lot of memory and that could be why SP2 and other installs take so long.
0
 
mikeabc27Author Commented:
No change I'm afraid
0
All Courses

From novice to tech pro — start learning today.