VHD Backup2Tape turns Tape Offline
Hi, we have some issue with a BE15 Installation on a 2012 R2 Hyper-V Host. Server has an internal Tape Drive LTO-6 and a NAS as iSCSI Target attached. After weeks of normal function one day the bac...
Forum Discussion
Perhaps the tape is full. Did you check whether there is an outstanding alert asking you to insert an overwritable tape into the tape drive?
Hi pkh,
media set is 4 days overwrite/append. Tapes are on daily basis so always 6+ days.
There is a daily inventory job 15 minutes before the daily backup tasks making sure the tape is correctly recognized.
The jobs are defined as "append or overwrite, if no appendable media is availabe" (2nd checkbox).
There are also no outstanding alerts with tape change request.
best regards
Torsten
When BE takes the tape drive offline, it should throw some alerts and put some entries in the adamm.log file. Do you see any alerts? Cn you post the adamm.log file?
What SAS HBA/controller are you using for the tape drive? Hopefully it is not a RAID controller, unless it is one of the few certified ones. see https://www.veritas.com/support/en_US/article.000038683
Hyper-V Host with 5 VMs (50-2500GB each)
2500GB = 2.5TB which is the native uncompressed capacity of a LTO6 tape. To backup all your 5 VM's, you must be using compression. Depending on your data type, compression can vary hence you may have exceed the capacity of your tape.
There are also no outstanding alerts with tape change request.
Note that these alerts go away when the job is cancelled or BE services are restarted. You would have to check for such alerts when the problem occurs.
- Controller is a H240 SAS HBA
- hardware compression was and is activated
- a copy of the whole data from disk to tape consumes 2.02 TB on a 2.38 TB Tape. Compression ratio is 1.3:1 so there is space left (300+GB)
- the error occurs after 255GB on an empty tape (overwritable / not appendable) always with the same VHD
- there was no media request in the warning history after 2017/11/23.
- i tested the VM exclusively and was "live on stage" when the tape turned offline. there was no media request for i knew when it would happen
- there is a Tape0 and a Tape1 (Tape0 was replaced due to hardware error a few months ago and is still listed as "deactived") Tape1 is the only present tape device
ADAMM LOG attached
best regards
Is the H240 set to Simple mode, rather than RAID mode? It appears to be a dual mode card and only one mode would support tape. https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-c04496620
These entries from the adamm.log appear to either be a SAS communications failure or the tape device simply vanished. But I agree that your description of the issue and the apparent reproducability of the issue make me suspicious of the data also. Unfortunately, I personally know of no data that could cause this sort of scenario.
[37756] 11/23/17 10:13:02.718 DeviceIo: 00:02:01:00 - Refresh handle on "\\.\Tape1", SCSI cmd 16, new handle ffffffff, error 2
[37756] 11/23/17 10:13:02.718 DeviceIo: FindVanishedDevice: SwitchOver Adapter Info NULL for pathIde=2
[37756] 11/23/17 10:13:02.718 DeviceIo: Failed to find new device for "\\.\Tape1"
[37756] 11/23/17 10:13:02.718 DeviceIo: 00:02:01:00 - Refresh handle on "\\.\Tape1", SCSI cmd 1a, new handle ffffffff, error 2
[37756] 11/23/17 10:13:02.718 DeviceIo: FindVanishedDevice: SwitchOver Adapter Info NULL for pathIde=2
[37756] 11/23/17 10:13:02.718 DeviceIo: Failed to find new device for "\\.\Tape1"
[37756] 11/23/17 10:13:03.219 DeviceIo: 00:02:01:00 - Refresh handle on "\\.\Tape1", SCSI cmd 00, new handle ffffffff, error 2
[37756] 11/23/17 10:13:03.219 DeviceIo: FindVanishedDevice: SwitchOver Adapter Info NULL for pathIde=2
[37756] 11/23/17 10:13:03.219 DeviceIo: Failed to find new device for "\\.\Tape1"
[37756] 11/23/17 10:13:03.720 PvlDrive::DisableAccess() - ReserveDevice failed, offline device
Drive = 1012 "Bandlaufwerke 0002"
ERROR = 0x0000001F (ERROR_GEN_FAILURE)
[37756] 11/23/17 10:13:03.735 PvlDrive::UpdateOnlineState()
Drive = 1012 "Bandlaufwerke 0002"
ERROR = The device is offline!
