cancel
Showing results for 
Search instead for 
Did you mean: 

Backup Not Recognized after SP4 Update

dark_moonx1
Level 3

Hi all,

We have recently purchased a GL380P G8 server and installed Windows Server 2008. We've come to know that BE 12.5 needs updates in order to connect to the said server. Doing a LiveUpdate gave us SP4 and a couple of Hotfixes which installed fine (after a couple of attempts, LU1812 error). Now, after the SP4 and Hotfixes, we've experienced a couple of issues with BE 12.5.

 

First one, running an Inventory job on a backup tape succeeds (with old backups and new tapes), however, Cataloging the tapes would just eject the tape (old and brand new ones). Alerts gives "Media is unrecognised." which is kinda odd since these were backups made before updating to SP4 and only a week or two ago. We've noticed that after doing an inventory, the "Media Label" (in Devices tab and then selecting the tape drive) is blank and the "Allocated Date" is the date today, not the date that was supposedly the backup's. I've already ran a Quick Erase on the tapes which succeeded, but after doing an inventory, still the same issue.

Running a backup job ALSO ejects the tape (erased tape).

This happens to all tapes - old and new.

 

Second issue, RAWS for the Server 2008 was successfully installed and updated (after installing SP4). and was included in the "User-defined selections" in the backup job. However, accessing/opening the said server would give an error:

 "Failed to log on to Microsoft Windows.

Ensure that your logon credentials are correctly entered (which is correct as it's the same one being used by our other 2 servers)"

Accessing the administrative share (C$/D$) of that 2008 server succeeds without any problem.

 

Server: Windows 2003 Enterprise 32-bit

Tape Drive: HP StorageWorks Ultrium 1760

Media: HP Ultrium LTO4 1.6TB cartridge

1 ACCEPTED SOLUTION

Accepted Solutions

CraigV
Moderator
Moderator
Partner    VIP    Accredited

...have you tried to uninstall SP4? You need to uninstall the RAWS agent from the Win2K8 server and then reinstall it. See if this resolves the speed issue, and then try installing SP4 again.

Thanks!

View solution in original post

6 REPLIES 6

CraigV
Moderator
Moderator
Partner    VIP    Accredited

Hi,

 

Did you install the latest BE drivers for the tape drive? If not, use tapeinst.exe to do so, and then try again.

Along with this it might be worth your while to update the firmware on that tape drive.

Lastly, is the RAWS agent started up on the Win2K8 server?

Thanks!

dark_moonx1
Level 3

Hi Craig,

I've installed the tape drive using the Device Config Wizard in BE12.5. Prior to SP4 update, backups were running fine. 

The RAWS agent IS running in the 2008 server.

By the way, in the second issue, it was mentioned that the Log on has a batch job privilege (which is being sorted with our main office) as we are a child domain.

Tape driver is from Symantec, updating the said driver installs drivers from HP.

CraigV
Moderator
Moderator
Partner    VIP    Accredited

...have you tried to uninstall SP4? You need to uninstall the RAWS agent from the Win2K8 server and then reinstall it. See if this resolves the speed issue, and then try installing SP4 again.

Thanks!

dark_moonx1
Level 3

I'll try this and get back to you Craig. Thanks.

dark_moonx1
Level 3

Hi Craig,

I've uninstalled SP4 and the hotfixes then restarted. I've run another Inventory job afterwards, and guess what, the media details when selecting the tape drive shows the CORRECT details (Media Label, Allocated Date, etc). 

Currently running a Catalog job and seems the tape has no indication of being ejected - compared to earlier with SP4 installed where the tape always gets ejected.

Would be running a backup tonight to see what happens. Would update by tomorrow.

dark_moonx1
Level 3

OK, seems that backup is working WITHOUT the SP4 update. Only thing remaining is the access to the 2008 server. 

Oddly enough, service packs should address issues with earlier releases, though this doesn't look the case with this update. 

Would work out the details and fixes for the second issue (most likely authentication in the group policy).

Thanks Craig!