Job enters queued state prior to completion

[Paul_Defiglio]

Hi

Details - Veritas 9.1 on a Windows 2003 server.

We are using a DLT VS80 (40/80Gb) and the backup goes into a queued state just before it completes. If I remove a 2gb folder from the job it completes successfully which leads me to believe the tape drive has reached its limit (though I would expect more in terms of capacity as its backing up files that will compress).
Compression is enabled from the device and the job script but why doesn�t Veritas prompt to insert media (rather than going into queued state) - I believe we have inserted a 2nd tape but the backup doesn�t continue and the status doesn�t change. If anyone has an opinion on the tape capacity also then I would be grateful.

Thanks in advanced.

[priya_khire]

Hello,

What are you backing up in the job? What is the size of the backup? Since when does the problem occur? Check if you get any alert messages in the alerts tab within backup exec. Also look for errors in the event logs in Windows.

Are you runing an o verwrite job or an append job? In case you want it to span to another media, choose the option to append to media -overwrite if no appendable media is available.

Revert with details.

Note : If we do not receive your reply within two business days, this post would be marked �assumed answered� and would be moved to �answered questions� pool.

Regards.

[Paul_Defiglio]

Hi

1. Data backup contains drawings/images/Office documents etc. The backup job is 48Gb in total - if I remove a 1gb folder then the backup completes - if the 1gb share is re-added the backup gets to 48Gb and teh job status would then changes to queued state.(as opposed to prompting for a 2nd media). Data growth has menat that this problem has only started to occur (i.e reached the 48gb mark)

2. No alerts are reported within verits or via Windows event logs.

3. Job is set to overwrite media. I dont want to append the backup to another media I want the backup job to prompt me if the tape has run out of capacity.

Many Thanks

[Sharvari_Deshmu]

Hello,

Which type of compression are you using?

What is the Overwrite protection level that you have set?

Please see the technote:

http://seer.support.veritas.com/docs/199542.htm

Thanks,

NOTE : If we do not receive your reply within two business days, this post would be marked assumed answered and would be moved to answered questions pool.

[Paul_Defiglio]

Hi

1. Hardware compression is enabled on the device properties and the backup job compression type.
2. The overwrite protection level is None (Overwrite scratch media).

regards

[Paul_Defiglio]

Can you please respond to my last post.

Thanks

[tejashree_Bhate]

Hello,

From the following link install the latest drivers

(title) VERITAS Backup Exec (tm) 9.1 - Device Driver Installer (20050115) - Includes Tape Driver Release (20041231) and Robotic Library Release (45) (Intel Only
http://support.veritas.com/docs/273853



Note:- if we do not receive your reply within two business days, this post would be assumed answered and archived.


Thanks.

[Ken_Putnam]

You will almost certainly never see 80 GB on a 40/80 tape. 2:1 compressikon is marketing glitz, not engineering promise. Anything over 1:1 is gravy, and what yo get is what you get. I generally figure on about 1.3:1 until a partitcular share has been backed up several times and I can strt averaging.

At 1.3:1, you hsould get about 51-52 GB before the backup stops and asks for a new tape. And Yes,. BackupExec SHOULD post an alert to insert Overwriteable media and press OK to continue.

You may have autorespond enabled, and the alert may be responsed to with CANCEL, or the alert may be timing out before you get in in the monring.

[Paul_Defiglio]

OK wil linstall these drivers and respond Tues am.

[Paul_Defiglio]

Cheers Ken for that helpful post. I would expect a bit more than 48Gb but would also expect Backup Exec to prompt for a new media. The autorespond in question is in Tools/Options/Preferences isnt it? This is not flagged.

Thanks!

[Sharvari_Deshmu]

Hello,


Thanks for the update please let us konw whether the issue is resolved.

Regards,

NOTE : If we do not receive your reply within two business days, this post would be marked assumed answered and would be moved to answered questions pool.

[Paul_Defiglio]

Hi

Sorry I seem to have given you some wrong information. The version of Backup Exec is actually 9.0 hence the updated tape drivers for 9.1dont work with this version. I cant seem to locate an update to 9.1 on the website - is this still available? If not do you have tape drivers for 9.0.

Regards

[Deepali_Badave]

Hello,

Please refer the following technote:



http://seer.support.veritas.com/docs/264658.htm





http://seer.support.veritas.com/docs/262414.htm





http://seer.support.veritas.com/docs/261695.htm





http://support.veritas.com/dsl/dslselect_ddProduct_BEWNT.htm


Note:this is a free upgrade.

NOTE : If we do not receive your reply within two business days, this post would be marked assumed answered and would be moved to answered questions pool.

[Ken_Putnam]

Just grab the v9.1 install and install on top of the existing code. V9.1 will accept your v9.0 serial(s)


v9.1.4691.1 here
http://seer.support.veritas.com/docs/264658.htm

SP4a here
http://seer.support.veritas.com/docs/280008.htm

HotFix 56 here
http://seer.support.veritas.com/docs/282260.htm

v9.1 driver pack here
http://seer.support.veritas.com/docs/273853.htm

[Paul_Defiglio]

Upgraded to 9.1 which did seem to work Veritas now fails to start because of the following 3 services:

Backup Exec Device & Media Service
The dependency service does not exist or has been marked for deletion.

Backup Exec Server
The dependency service or group failed to start.

Backup Exec Job Engine
The dependency service or group failed to start.

Also
Description: The Backup Exec Device & Media Service service depends on the following nonexistent service: MSSQL$BKUPEXEC

The above service is also missing and so presume that it was present before the update. The update did seme to complete sucessfully but was installed remotely via Terminal Server (would this make a difference). No MSSQL software exists on the server also. Tried a repair but this fails. Checked the install logs and this appears:

ERROR: Failed to install MSDE 2000 BKUPEXEC instance.
Please review C:\WINDOWS\MSDE_BKUPEXEC.log for more details.


Only information I can see in the MSDE log is -
MSI (s) (B4:94): Product: Microsoft SQL Server Desktop Engine -- Installation operation failed.

Please can you assist?

Thanks

[Ken_Putnam]

Never tried to install on a terminal Server muself, but see

http://support.veritas.com/docs/272371
http://support.veritas.com/docs/242598

[Gauri_Ketkar]

Hi,

Please update us on the account uder which backup exec services running except remote agent is Domain Admin account ?

What are the event Ids generated under applicatin event logs ?



Update us on the same and revert for any further Query
Hope this will help you


Thank you
Gauri

[Paul_Defiglio]

Please can you reply to my last thread as a veritas update has left us with without working backup software.

[Paul_Defiglio]

Hi

1. Domain Admin Account is used.
2. Event ID's generated are

1015 - Failed to connect to server. Error: 0x800401F0

11708 - Product: Microsoft SQL Server Desktop Engine -- Installation operation failed.

Installing MSDE on its own fails even when using the command line to set the BKUPEXEX account and password -

11708 - Product: Microsoft SQL Server Desktop Engine -- Installation operation failed.

MSDE log - Product: Microsoft SQL Server Desktop Engine -- Installation operation failed.

Tried from remote session and also from the console.

[Paul_Defiglio]

Thanks Ken the second URL works a treat. Uninstalled Terminal Services and ran the repair - all OK (Veritas now 9.1)

Updated the tape drivers also so will see if I can get more then 48Gb out of the tape drive.

Will report back tomorrow.

Thanks again!!!