Arcserve 11.0 E6304 Unexpected SCSI Sense Code 1

[oliv421]

I have this error when my windows 2000 SP4 server start. I can't "auto config" when I launch the unit config. I have scsi move error.

Do you have a idea about this error and how I can solve this problem

thanks a lot

PS : excuse me for my english. I am French :-(

 

[davidmichel]

See Which Driver Should I Use? faq478-3987
Get the update to 11.1

http://supportconnectw.ca.com/public/storage/basbr111_supp.asp

If it still fails put the Tape Engine in debug.

 

[gagz]

I'm having this same problem, and I don't understand that faq. I went into device manager and disabled my tape drive driver, and my medium changer driver. Is that what I was supposed to do? Doesn't make sense to me. NOw the device manager in arcserve doesn't see the tape drive under the library. I have arcserve 11 and am still in the initial phases of setting it up, but can't get past this...

 

[davidmichel]

Answer to your question is yes.

Normal order would be to
disable devices
restart system
run the Device Configuration utility.

 

[gagz]

ok, so i just did all that... tried the restore again, and boom, e6300 and e6304... I've already gone the driver route of the adaptec card in the server, and replaced the 9' scsi cable with a 3 footer, but nothing seems to be working... on a positive note, this is the first time it got past 20%, actually made it to 37%...

any other ideas???

For what its work, I have a compaq server running windows server 2003, a quantum m1500 library w/ one drive, and an adaptec 29160 card in the server...

merry xmas everyone.

 

[davidmichel]

It would have been much better starting a new thread with the details instead of tagging on to some other issue that is kind of like but not really and saying it is the same thing.

Make sure the HP storage agent is not collecting SCSI information.

 

[andrew2000]

Gagz,
Have you solved the problem yet? I have been fighting with this for a month and have tried everything I can imagine.

Any luck?

I am also using an Adaptec card.

Thanks,
Andrew

 

[gagz]

It ended up being a problem with the SQL agent configuration, because the problem only occurred during restores from the agent. Are you using the sql agent?

 

[andrew2000]

Gagz,
No, I am not using the SQL agent and mine is only happening during backups. It's the exact same problem though, as my backup gets about 1/3rd of the way done I get hit with the same errors.

Thanks for replying...
Andrew

 

[gagz]

Andrew-

Here's exactly what the contract that fixed the problem said... maybe you can take something from it and apply it to your situation, maybe not:

Affter turning on some extensive debugging, we were able to isolate the problem down to the communcations between the SQL agent and the Backup server itself. There were 2 significant changes that we made on each server that directly related to a successful backup and restore of a database via Arcserve. After testing again on a different SQL server, the default agent settings are adequate going forward so no additional changes will need to be made to future SQL servers in need of being backed up.

Following are the registry entries that were made on the SQL server and the backup server (amt-backup) respectively.

On Database Server:

HKLM\Software\ComputerAssociates\BrightStor ARCserve Backup\DSAgent\CurrentVersion\agent\dbasql@mssql
Set 'UseTCP' to 0

This is the property of the agent that forces it to use TCP as opposed to named pipes. For some reason, this was set to 1 previously, even though the GUI reflected the agent to use TCP/IP as the protocol.

On Backup Server:

HKLM\Software\ComputerAssociates\Brightstor ARCserve Backup\Base\Tash\Common\DBAgentSettings

New Dword Value:
SQLProtocol Value=0

It is necessary to restart the CA RPC services on the backup server and on the database server after these changes have been made.


There are also a few suggestions and steps necessary to ensure proper backup and restore of SQL databases.

Backing up

1. Ensure the agent CA services are running on the SQL server.
2. Use the "backup" Active Directory account to access the server via RPC communications
3. Always use the "sa" account or equivalent when performing database operations such as a backup or restore

Restoring

1. Launch the ARCServe manager software and select the restore option.
2. It is recommended, but not necessary to restore by Session.
3. Select the database session that you want restored and select it.
4. Right - click the same session and select "Agent Options".
5. Change the name of the MDF and the LDF files in the available dialog to either reflect a database that does not exist or a blank database created through SQL Enterprise Manager. This is important so that the .mdf and .ldf files can be written to the drive before being restored to SQL. If the database name and.or file is there prior to restore, the potential exists for locking and related problems.
6. Select the 'Destination' tab and uncheck "Restore files to their original locations"
7. Navigate throught the tree to the domain, then to the SQL Server where the database is to be restored. Expand the server and select 'Microsoft SQL Server'.
8. In the destination bar at the top of the screen, be sure to append the database name to the following information:

\\ERPPEGASUS\dbasql@MSSQLSERVER

It should look like this when ready to restore

\\ERPPEGASUS\dbasql@MSSQLSERVER\testdb

where 'testdb' is the name of the database to either be created or restored to within SQL.

9. Submit the job and you will be prompted for credentials. There are 2 options - one for Windows connectivity and one for the DB AGent. Select the AD account for the WIndows RPC communications (machine) and an 'sa' or security equivalent account for the DB Agent.