You say ' it detects drives and paths successfully ' - what about the robot? Below is the output of bpps -x. Partner Accredited Certified. Is there more than one media server connected to the library? Below is the Output of. Glad to know all is well. Handy NetBackup Links. Post Reply. Preview Exit Preview.
You must be signed in to add attachments. Whilst NetBackup may detect the issue, it is not caused by NetBackup. The cause of read and write errors are usually an issue with the tape drive or media cartridge.
This exact error message can be caused by mis-configuration of the drives. If the issue remains after this is checked, your hardware vendor should be able to help to find the root cause. NetBackup keeps track of how much data the OS has written to the device. NetBackup then asks the tape device for its position at the end of each write. If this position does not match NetBackup's calculation then the job will fail with a media write error. A simple block check cannot show if a full rewind happened, but when a position check fails, it is most likely that the reported position is less than the calculated position.
If a full rewind has occurred, the NetBackup header on the tape will have been wiped. The tape cannot be read and the data on the media is lost. This causes a rewind of the drive as it is being written to. This event cannot be seen by NetBackup, and is only found after, when the block position check fails. If the issue is a position error rather than a full rewind the bptm log will contain a message like:. However, Veritas has produced a NetBackup 7. NetBackup 7.
Upgrade to the new ATDD driver to fix the issue. NetBackup passes data to the OS, one block at a time, to be written to the tape drive. NetBackup has no concept of tape capacity. In theory, it would keep writing to the same tape "forever". The tape drive firmware detects when the tape physically passes the logical end-of-tape. It then sets a 'flag' in the tape driver. There is still enough physical space on the tape for the current block to be written, so this completes successfully.
NetBackup then tries to send the next block of data but the tape driver refuses, as the 'tape full' flag is set. The driver passes this 'tape full' message to the OS, which then passes it to NetBackup. Only once this has happened will NetBackup request the tape be changed.
There are no settings in NetBackup that control tape capacity. Your hardware vendor or OS support should be able to help to find the root cause. NetBackup has no concept of 'read only'. This is set by the tape drive, often by means of a small, physical, switch on the tape cartridge.
This is then reported to NetBackup by the drive's firmware. So, if a tape is being shown as 'read only' this issue cannot be the fault of NetBackup. NetBackup does not directly 'Inventory' a library. It only asks the library to report on which tapes it contains and where they are stored. If NetBackup cannot 'see' a tape it is because the library is not reporting it.
This is not caused by NetBackup. This error is seen in the bptm log, may be referenced in the A great way to look into this issue is to use the robtest command. See for more details. Robtest does not use any NetBackup commands.
This makes it a good way to rule out NetBackup from being the source of the issue. A job hangs on the tape mount, failing with status 98 after some time, but the OS can use the tape. A few cases have been seen in which tapes are physically loaded into the tape drive.
At first glance it might seem that NetBackup is at fault, however, in these cases it was found that the fault was caused by the tape drive firmware. If they do not work there is an issue with the library. Description: The tape drive has an error which requires the tape cartridge to be ejected for error recovery.
Mar 14 server02 tldcd []: [ID daemon. The formal resolution for this issue Etrack is included in the following release:.
Drives are down in Device Manager. It's just that I can not move cartriges without know which slots are available. Thanks in advance. RE: can't inventory my robot MIS. Option and run the inventory or 2 apply the 5.
Ensure that the robot is available and is configured with the correct device path. If the daemon will still not start, perform the following: 1.
0コメント