Backup Exec 8.6 for Win2k log errors 2

[CFeyrer]

I am getting the log error "Unable to attach to \\NFITS1\System?State". I have made sure that the WINNT folder share on NFITS1 is set up properly per Veritas's tech note, and it is -- at least it corresponds to Veritas screenshots in their technote.

I also am getting the error ""Unable to attach to \\BACKOFFICE2\Microsoft Information Store\First Storage Group." I have stopped Veritas services, made the registry modification requested, and noted that a previous administrator had already made this change. So, neither tech notes advice has solved the problem thusfar.

Any help would be appreciated!

Chris Feyrer

 

[vwleppo]

I am also getting that same message, "unable to attach to DATA02\system?state." I've tried everything that veritas has said, but nothing is working. Any ideas?

Thanks,
Will Leppo

 

[packdragon]

I once read a Veritas technote regarding this and it pointed to a domain security policy restriction. On one of the machines that Backup Exec can't attach to, open up Local Security Settings and go to Security Options. The first item listed is Additional restrictions for anonymous connections. I think if it's set to "do not allow enumeration of SAM accounts and shares" then Backup Exec is unable to attach to the system state. It requires anonymous access for that.

Note that changing this option to a less secure one makes the machine more vulnerable. If this machine is not behind a firewall, you may want to consider an alternative. For one of my machines, I have NTBackup backing up the system state onto the hard disk of another machine. I then have Backup Exec back up that file.

- Zoe, that's ZOH-EEE, get it right please
- Just a little ol' MCP at Solien Technology
-

http://www.solien.com

 

[CFeyrer]

I'm pretty new to this -- what files comprise the System state, where should I point NTBackup and how do I get BackupExec to recognize it as a system share to be backed up? Thanks for your help!

Chris

 

[packdragon]

If it's a Windows 2000 machine, then "System State" should be a selectable item when browsing through a backup application.

Could you rephrase your question? Are you asking how to get Backup Exec to back up the backup you made with NTBackup?

- Zoe, that's ZOH-EEE, get it right please
- Just a little ol' MCP at Solien Technology
-

http://www.solien.com

 

[CFeyrer]

Actually this is a two part question (pardon my newbie-ness!).
1. How do I get NTBackup to backup the system state to the target volume (let's say the target volume is DATA2, and the system state is from DATA1).
2. How do I get BackupExec to add this volume backup to its job?

Thank you!

Chris

 

[packdragon]

Open NTBackup on the machine you want to back up by typing "ntbackup" in the Run box. Click the Backup Wizard button and it will step you through the process of selecting what and where to back up. You can specify the destination to be another computer on the network.

Now in Backup Exec add this NTBackup to your backup job in one of two ways:

1) Create a folder for the NTBackup backup location, then select it for a Backup Exec job.

2) Run one complete NTBackup so a file exists, then add that to the Bacukp Exec job.


- Zoe, that's ZOH-EEE, get it right please
- Just a little ol' MCP at Solien Technology
-

http://www.solien.com

 

[CFeyrer]

Can this be automated? I would like this to be part of an existing overnight backup job -- and I'd want to make sure that NTBackup finishes its work, backing up the volume to a particular folder, then BackupExec would back up that file next.

 

[packdragon]

You can automate it by scheduling the NTBackup and scheduling the Backup Exec job, but I don't know of any way to have the two appliations talk to each other. You can't tell Backup Exec, "Back up this file as soon as NTBackup finishes it." You'll have to estimate how long it'll take and give it enough time for one to finish before the other starts.

Hey, if you think I've been helpful, could you give me a shiny star for it? They fascinate me... ;-)

- Zoe, that's ZOH-EEE, get it right please
- Just a little ol' MCP at Solien Technology
-

http://www.solien.com

 

[dogmata]

Registry editor:

HKLM\software\veritas\backup exec\engine\ntfs > change the restrict anonymous support value to 1 > cycle all backup exec services

- try backing up the system state.
- if that fails in the same hive create a reg dword key called useAdSSCheck > value should be 0, cycle the BE services > run another test Backup of system state

Cheers
Dog

 

[CFeyrer]

Create the second key in:
HKLM\software\veritas\backup exec\engine\ntfs ?

Just verifying, thanks!

Chris

 

[dogmata]

CHRIS: yep, thats the one > note: upper/lower case should be as above

Let me know how you go
Dog

 

[CFeyrer]

That fixed it! What did that second registry entry set?

Chris

 

[packdragon]

Thanks dogmata, I'm going to give this solution a try too. You deserve the star here, not me.

- Zoe, that's ZOH-EEE, get it right please
- Just a little ol' MCP at Solien Technology
-

http://www.solien.com

 

[packdragon]

I checked my registry keys. I already had useAdSSCheck set to 0, but I don't have the "restrict anonymous support" one there. What exactly is it called, so I can create it and set it to 1?

- Zoe, that's ZOH-EEE, get it right please
- Just a little ol' MCP at Solien Technology
-

http://www.solien.com

 

[packdragon]

Nevermind, I found it on another machine. It's just called "Restrict Anonymous Support" duuhhh don't I feel dumb.

Anyway, so I made sure the values of each dword is as described above and stopped and stopped/restarted all Backup Exec services. Afterwards I tried to do a test backup of the system state I couldn't attach to before. I can't even attach to the DC for backup selection! It asks me to log in, and the backup exec user account we use for backups won't work. The odd thing is I am able to navigate to the other DC, it doesn't ask for a login. I guess I'd better compare the settings between the two DCs...

- Zoe, that's ZOH-EEE, get it right please
- Just a little ol' MCP at Solien Technology
-

http://www.solien.com

 

[dogmata]

Cheers for the star and feedback guys !

Packdragon:


What may be a good test is:

A) Create a new user (domain Admin + Admin grps only) in AD.
B) In the local security policies > user rights assignment> on this "problem" DC, explicitely grant this new account : access this computer from the network, log an as a service, act as part of OS
C) Log on to the media server with this account, change all your BE services on the media server to start with this new account
D) within BE interface: create a new "log on" > make it a "common" a/c rather than restricted, make it the default account
E) Create a new selection list (as BE will associate user accounts with the selection lists, so if you let an old job run as your test backup it will be trying to attach with the old account)

See how you go with that

Cheers
Dog

 

[dogmata]

PAckdragon : forgot to mention that the above was assuming you are using Backup Exec 9.0 ? If not forget about point D) ( point E doesnt really apply either but still create a new job for the test)and do this instead

- stop all services and change them to start witht the new a/c but dont start the services > drill down to your backup exec\nt\data directory and rename a file called BEWINUI.UNI (password databse for BE, you can hack it but renaming is far easier, just a refresh basically) > then start all BE services

Dog

 

[packdragon]

Thanks for the tips Dog! I'm actually using BE 8.5 in this case. By "a/c" do you mean "account"? Pardon the density. It's so hot this summer A/C keeps translating into Air Conditioning for me. %-)

- Zoe, that's ZOH-EEE, get it right please
- Just a little ol' MCP at Solien Technology
-

http://www.solien.com

 

[dogmata]

PACKDRAGON: Yep, sorry a/c stands for account ie. the new user account

Cheers
Dog