BE 12.5 Job Ready, no media server available

[cdp]

Hi as for the subject I've this problem.

On a Win2003 server.

Already update drivers, reapired installation, reinstall the software, and so as discused in all the forums.

Alsa change the tape drive (hp 920) and so on.

The drive works fine with Library and tape tools from Hp and also with Ntbackup ....

any idea?

Thank you!

Carlo

p.s. media server is the same my server the service is running and bla bla bla

[CraigV]

Hi Carlo,

The TN below has a couple of troubleshooting steps that are worth looking into:

http://www.symantec.com/business/support/index?page=content&id=TECH55748

Also make sure that your media server isn't paused for some reason. Check the server name under Devices and right-click it...if it is paused, choose the Unpause option.

Thanks!

[MusSeth]

Disable windows removable storage service....restart backup exec services and than check

[cdp]

Hi Craig,

thank you for the response.

Alredy done that troubleshooting ... no way out :(

Also backup on disk give me the same problem ....

Carlo

[pkh]

If you have the HP Insight software running on your media server, uninstall it.

[cdp]

Hi Mus Seth and Pkh

no insight software running ... rsm service was in manual, put it into disabled ... still not working

Carlo

[CraigV]

...open up BEutility.exe and run a repair of the BEDB.

I assume you're using the Symantec drivers for the drive?

Thanks!

[cdp]

nada niet ... still not working

attached bediag

[cdp]

Ummmh it seems that be doesn't stop discovery service here is addman.log

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

[4448] 07/26/13 16:01:33.388 Adamm Log Started! ("VMWARE-SRVMNG", 1000, {B233552E-6A97-4ED5-A575-7AA17A548B20})

Adamm Info: Version 12.5, Build 2213, 32bit

OS Info: Windows Server 2003, Build 3790, Service Pack 2

Database Driver Info: SQLSRV32.DLL, 03.86.3959

Database Server Info: Server Name = "VMWARE-SRVMNG", Active Node = ""

Database Connection String: "DRIVER=SQL Server;SERVER=vmware-srvmng\BkupExec;DATABASE=BEDB;App=BEWS PVL"

DateTimeSync: Local = 2013/07/26 16:01:33, System = 2013/07/26 14:01:33 GMT, Database = 2013/07/26 14:01:33 GMT

Shared Storage Authorization: Yes

TSM Authorization: Yes

SPO Installed and Authorized: No

Library Expansion Options: Unlimited

Treat all LTO devices as if they are in UMD certified device list: DioAllLto = 0x0001

Use UMD certified device list: DioDrivers = 0x0002

[5320] 07/26/13 16:01:33.419 Read Device Records - start 

[5320] 07/26/13 16:01:33.466 Read Device Records - end

[5320] 07/26/13 16:01:33.606 iSCSI Discovery - start 

The iSCSI initiator software does not appear to be installed on this system

[5320] 07/26/13 16:01:33.606 iSCSI Discovery - end 

[5320] 07/26/13 16:01:33.606 Registry SCSI Discovery - start 

[5320] 07/26/13 16:01:33.622 Registry SCSI Discovery - end 

[5320] 07/26/13 16:01:33.622 Device Name Discovery - start 

[5320] 07/26/13 16:01:53.622 Device Name Discovery - end 

[5320] 07/26/13 16:01:53.622 B2D Discovery - start 

[5320] 07/26/13 16:01:53.684 B2D Discovery - end 

[5320] 07/26/13 16:01:53.684 ADSM Discovery - start 

[5320] 07/26/13 16:01:53.684 ADSM Discovery - end 

[5320] 07/26/13 16:01:53.684 USB/Firewire Discovery - start 

[5320] 07/26/13 16:01:53.700 USB/Firewire Discovery - end 

[5320] 07/26/13 16:01:53.700 Iomega REV Discovery - start 

[5320] 07/26/13 16:01:53.700 Iomega REV Discovery - end 

[5320] 07/26/13 16:01:53.700 Read NDMP Server Records - start 

[5320] 07/26/13 16:01:53.700 Read NDMP Server Records - end

[5320] 07/26/13 16:01:53.700 DeviceIo Discovery - start

[5320] 07/26/13 16:01:54.622 DeviceIo Discovery - end

[5320] 07/26/13 16:01:54.622 DeviceIo Devices:

Scsi Address

Prt :Bus :Tar :Lun   Attributes

-------------------  -------------------------------------------------------------------------------

0003:0000:0003:0000  DeviceIo[01]: "HP      Ultrium 3-SCSI  HU10725W9G", Cert=Y, "\\.\Tape0"

-------------------  -------------------------------------------------------------------------------

[5320] 07/26/13 16:01:54.622 Device Registry:

Scsi Address

Prt :Bus :Tar :Lun   Attributes

-------------------  -------------------------------------------------------------------------------

0000:0000:0000:0000  "atapi", (Port Driver)

-------------------  -------------------------------------------------------------------------------

0001:0000:0000:0000  "atapi", (Port Driver)

-------------------  -------------------------------------------------------------------------------

0002:0000:0000:0000  "adpAHCI", (Port Driver)

-------------------  -------------------------------------------------------------------------------

0003:0000:0000:0000  "symmpi", (Port Driver)

0003:0000:0003:0000  "HP      Ultrium 3-SCSI  D22D", (Tape Device), "\\.\Tape0"

-------------------  -------------------------------------------------------------------------------

9999:0016:0001:0000  "VERITAS Backup To Disk  1.00", "\\.\Bkup2Dsk"

9999:0016:0003:0000  "VERITAS Backup To Disk  1.00", "\\.\Bkup2Dsk"

9999:0016:0004:0000  "VERITAS Backup To Disk  1.00", "\\.\Bkup2Dsk"

-------------------  -------------------------------------------------------------------------------

[5320] 07/26/13 16:01:54.622 PnP Device Paths:

Scsi Address

Prt     :Bus     :Tar     :Lun       Device Path

-----------------------------------  ---------------------------------------------------------------

00000003:00000000:00000003:00000000  \\?\scsi#sequential&ven_hp&prod_ultrium_3-scsi&rev_d22d#6&2c53fab2&0&000300#{53f5630b-b6bf-11d0-94f2-00a0c91efb8b}

-----------------------------------  ---------------------------------------------------------------

[5320] 07/26/13 16:01:54.622 Read Device Inquiries - start

[5320] 07/26/13 16:01:54.622 Device: \\.\Tape0

[5320] 07/26/13 16:01:54.731 Device: \\.\Bkup2Dsk

[5320] 07/26/13 16:01:54.934 Device: \\.\Bkup2Dsk

[MusSeth]

Is backup exec updated...please run live update and make sp4 and hotfixes are applied to it..... Is your backup exec server physical server or virtual machine...

[Kunal_Mudliyar1]

Medium changer is not showing up in the adamm log, is it missing in the device manager.

Can you post a screenshot of the device manager and the storage or the devices tab of bakcup exec

and assuming you have religiously followed

http://www.symantec.com/docs/TECH24414

The could also be with the database but quite rare

you can try with the blank database

http://www.symantec.com/docs/TECH66780

read NOTE on the technote before you proceed

[cdp]

Shit!

If I delete the db everithing works fine

... still investagating I don't want to reconfigure all

[Kunal_Mudliyar1]

Try copy database

http://www.symantec.com/docs/TECH49757

It will deattach the reatach the database and use the old databases mdf and ldf files

might fix othewise you need to reconfigure

As I said database corruption is rare but it happens, good news is nothing is wrong with the hardware or the configuration

[cdp · Accepted solution]

Hi,

I do have to delete the db via beutility and recereate an empty one.

Rewrite all jobs ... and it works!

Thak you to everybody for suggestions!

Have a nice week!

Carlo