Skip to main content

Tape backup stops after 200-300GB ...

Thread needs solution

Hello,

we've done some further test with the new version of acronis backup advanced 12.5 current build and we've problems with tape backups: After 200-300GB the jobs stops without any message.

HP Proliant DL380 with SAS attached Quantum Scalar i40 with HP LTO6 drive, Windows Server 2012 R2 with Hyper-V and storage node agent, current drivers / firmware.

To resolve the problem we changed the source from local Hyper-V VMs to network ressources - same behavior.

Same hardware did tape backups without any problems using Acronis Backup Advanced 11.7 ...

Any ideas or suggestions?

Many thanks

Erik

0 Users found this helpful

Hello Erik,

After 200-300GB the jobs stops without any message. 

Could you clarify a bit on this point?

Do you mean that the job stops after writing 200-300 to a single tape? What does the activity associated with this backup say in the details? Does it claim that the backup was successful? What do you see in the backup locations/recovery points for this backup archive? 

Hello Igor,

thanks for supporting us. The task activity shows that currently 317GB are processed and 238GB written to tape pool. The source are 3 VMs with around 1,5TB. Task stopps and shows no longer activity or error since 4 hours.

On the alarm tab there is a message that the task seems to be frozen.

Tape pool shows currently no archives from today.

As I know from tests before the only thing i Can do now is to restart all Acronis related services on the source to cancel the job - click on "Cancel" on the activity changes nothing.

Many thanks,

Erik

Hi Igor,

I've done some further tests: Task deleted and recreated, no VMs but share with 500GB data as source and different tape - same behavior ...

Any idea?

Many thanks

Erik

Hello Erik,

Welcome to the club... sorry to tell you but I think the same problem as me and at least one other guy over in this thread: https://forum.acronis.com/forum/acronis-backup-125/backup-tape-freezes-…

...as such this problem should be know to Acronis for at least one month already, probably even longer than that...

You can "cancel" the frozen task by killing "service_process.exe" on the server that's being backed up... other than that I tried around a lot of stuff, reinstalled Acronis about 5 times, did tape diagnostics and whatnot...

I wonder if Acronis still has not realized that several people (maybe everyone with a tape device?) have this problem or they are just wasting their customers' time because they have no solution...

Hello, recently we discovered and fixed the issue with Quantum Scalar libraries. The fix is included in the upcoming update. Until that, please contact Acronis support, we will provide you a quick solution.

Hello,

 

i'm the other one experiencing the issue. I'm quite frustrated of being a beta tester for this release of product. Case openend on 10th of July, still pending...

In reply to by truwrikodrorow…

Andrey, Can you provide the new update no for reference? 

I'm using v.12.5.7641 (Backup management server) which having the same issue.

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 0
Comments: 29

Hi, all.

Erik, can you please follow steps to be clear that issues are related to Scalar i40 tape library.

You need move tape from drive to any slot.

1. Perform fast inventory. (switch off Full Inventory).

2. Move tape to drive. (If there is no one)

3. Move tape from drive to any slot.

If problem is related to Scalar library you will got error when moving tape from drive: 

|   Error code = 0x70
|   Valid = false
|   Segment number = 0
|   Sense key = 0x05 (Illegal request)
|   Reserved = 0x00
|   Incorrect length = false
|   End of media = false
|   File mark = false
|   Information = [0x00, 0x00, 0x00, 0x00]
|   Additional sense length = 0x0A
|   Command specific information = [0x00, 0x00, 0x00, 0x00]
|   Additional sense code = 0x53 (Unknown)
|   Additional sense code qualifier = 0x01 (UNLOAD TAPE FAILURE)
|   Field replaceable unit code = 0x00
|   Sense key specific = [0x80, 0x00, 0x00]

 

Hi EC Li, new update officially not released yet and I cannot share tis components outside. Please contact Acronis support, if your issues relates to Scalar libraries, they will be able to provide you temporary fix.

Hi Alexander,

done without error message. Or should I have a look into a log file for that error?

I've done a fast inventory (tape was in drive), selected the drive and move the tape to slot 6; after a few seconds it was done without any message.

I wonder that you suspect the problem in the library process, because our hanging test job did not fill up the whole tape (LTO6, amount aof data to backup around 550GB) so for me there is no need to change the tape when the job processing...?

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 0
Comments: 29

 I wonder that you suspect the problem in the library process

Upper was mentioned about problems with Scalar Libraries when moving tapes from drive to slot. You have have rejected this suspisions. Is clear now that current problem the same we thought. 

Or should I have a look into a log file for that error?

No moving of tape should have fail if there is a problem we are all expected.

 

For the further investigations it is required to read other logs. I am interested in debug logs.

Please change information level to debug level in configuration files. You need change text level="info" to level="debug" in the next files:

  • C:\Program Files\Acronis\ARSM\arsm.config - channel 'arsm'
  • C:\Program Files\Acronis\BackupAndRecovery\mms.config - channel 'backup-api'
  • C:\Program Files\Acronis\StorageNode\ss.config - channel 'backup-api'

Run backup and wait for issue. After that please send files (may be via message here):

  • C:\ProgramData\Acronis\BackupAndRecovery\ARSM\arsm.log
  • C:\ProgramData\Acronis\BackupAndRecovery\MMS\backup-api.0.log
  • C:\ProgramData\Acronis\BackupAndRecovery\ASN\backup-api.0.log

Revert information level in logs I wonder that you suspect the problem in the library process because it will trace a lot of messages.

 

Hello again,

FYI I have tried this and enabled the debug logs as suggested. None of the logs produce any helpful output.

I started my backup at 16:45, it started writing to tape at 16:51 according to backup-api.0.log and I can confirm as I was watching the tape loader interface during that time. The backup then froze at exactly 17:52.

The backup-api.0.log inside the MMS folder did not log anything...

The arsm.0.log repeated the same few messages during the backup and after it froze:
2017-08-25T17:38:37:637+01:00 7544 I00000000: Session of client '90520B31-1BCF-44BB-A8F5-E36F51B0E9BB' successfully refreshed.
2017-08-25T17:38:37:637+01:00 7544 D00000000: << `anonymous-namespace'::RemovableStorageManagerImpl::LockMedia ID=44 took 0.000 seconds.
2017-08-25T17:42:37:639+01:00 8152 D00000000: >> `anonymous-namespace'::RemovableStorageManagerImpl::LockMedia ID=45
2017-08-25T17:42:37:639+01:00 8152 I00000000: Session of client '90520B31-1BCF-44BB-A8F5-E36F51B0E9BB' successfully refreshed.
2017-08-25T17:42:37:639+01:00 8152 D00000000: << `anonymous-namespace'::RemovableStorageManagerImpl::LockMedia ID=45 took 0.000 seconds.
2017-08-25T17:46:37:639+01:00 7072 D00000000: >> `anonymous-namespace'::RemovableStorageManagerImpl::LockMedia ID=46
2017-08-25T17:46:37:639+01:00 7072 I00000000: Session of client '90520B31-1BCF-44BB-A8F5-E36F51B0E9BB' successfully refreshed.
2017-08-25T17:46:37:639+01:00 7072 D00000000: << `anonymous-namespace'::RemovableStorageManagerImpl::LockMedia ID=46 took 0.000 seconds.
2017-08-25T17:50:37:639+01:00 3496 D00000000: >> `anonymous-namespace'::RemovableStorageManagerImpl::LockMedia ID=47
2017-08-25T17:50:37:639+01:00 3496 I00000000: Session of client '90520B31-1BCF-44BB-A8F5-E36F51B0E9BB' successfully refreshed.
2017-08-25T17:50:37:639+01:00 3496 D00000000: << `anonymous-namespace'::RemovableStorageManagerImpl::LockMedia ID=47 took 0.000 seconds.
2017-08-25T17:54:37:639+01:00 7096 D00000000: >> `anonymous-namespace'::RemovableStorageManagerImpl::LockMedia ID=48
2017-08-25T17:54:37:639+01:00 7096 I00000000: Session of client '90520B31-1BCF-44BB-A8F5-E36F51B0E9BB' successfully refreshed.
2017-08-25T17:54:37:639+01:00 7096 D00000000: << `anonymous-namespace'::RemovableStorageManagerImpl::LockMedia ID=48 took 0.000 seconds.
2017-08-25T17:58:37:641+01:00 7752 D00000000: >> `anonymous-namespace'::RemovableStorageManagerImpl::LockMedia ID=49
2017-08-25T17:58:37:641+01:00 7752 I00000000: Session of client '90520B31-1BCF-44BB-A8F5-E36F51B0E9BB' successfully refreshed.
2017-08-25T17:58:37:641+01:00 7752 D00000000: << `anonymous-namespace'::RemovableStorageManagerImpl::LockMedia ID=49 took 0.000 seconds.
2017-08-25T18:02:37:641+01:00 4232 D00000000: >> `anonymous-namespace'::RemovableStorageManagerImpl::LockMedia ID=50
2017-08-25T18:02:37:641+01:00 4232 I00000000: Session of client '90520B31-1BCF-44BB-A8F5-E36F51B0E9BB' successfully refreshed.
2017-08-25T18:02:37:641+01:00 4232 D00000000: << `anonymous-namespace'::RemovableStorageManagerImpl::LockMedia ID=50 took 0.000 seconds.
2017-08-25T18:06:37:641+01:00 4224 D00000000: >> `anonymous-namespace'::RemovableStorageManagerImpl::LockMedia ID=51
2017-08-25T18:06:37:641+01:00 4224 I00000000: Session of client '90520B31-1BCF-44BB-A8F5-E36F51B0E9BB' successfully refreshed.

The backup-api.0.log inside the ASN folder grew to 800 MB in size because it writes a log entry for every few kilobytes written to tape, but this one also just stops once the job freezes:
2017-08-25 17:52:20:122 5884 I00000000: Tape: Written size=65536
2017-08-25 17:52:20:122 5884 I00000000: Tape: Write. Size=65536, cache level='regular data'
2017-08-25 17:52:20:122 5884 I00000000: Tape: Written size=65536
2017-08-25 17:52:20:122 5884 I00000000: Tape: Write. Size=65536, cache level='regular data'
2017-08-25 17:52:20:122 5884 I00000000: Tape: Written size=65536
2017-08-25 17:52:20:122 5884 I00000000: Tape: Write. Size=65536, cache level='regular data'
2017-08-25 17:52:20:122 5884 I00000000: Tape: Written size=65536
2017-08-25 17:52:20:122 5884 I00000000: Tape: Write. Size=65536, cache level='regular data'
2017-08-25 17:52:20:122 5884 I00000000: Tape: Written size=65536
2017-08-25 17:52:20:123 1476 I00000000: Tape: ReadPosition 1755164672, size = 4096
2017-08-25 17:52:20:123 1476 I00000000: Read from cache Position = 1755164672, size = 4096
2017-08-25 17:52:20:123 1476 I00000000: Tape: from cache read 4096 bytes.
2017-08-25 17:52:20:124 1476 I00000000: Tape: ReadPosition 1755168768, size = 4096
2017-08-25 17:52:20:124 1476 I00000000: Read from cache Position = 1755168768, size = 4096
2017-08-25 17:52:20:124 1476 I00000000: Tape: from cache read 4096 bytes.
2017-08-25 17:52:20:124 1476 I00000000: Tape: ReadPosition 1755172864, size = 4096
2017-08-25 17:52:20:124 1476 I00000000: Read from cache Position = 1755172864, size = 4096
2017-08-25 17:52:20:124 1476 I00000000: Tape: from cache read 4096 bytes.
2017-08-25 17:52:20:124 1476 I00000000: Tape: ReadPosition 1755176960, size = 4096
2017-08-25 17:52:20:124 1476 I00000000: Read from cache Position = 1755176960, size = 4096
2017-08-25 17:52:20:124 1476 I00000000: Tape: from cache read 4096 bytes.
2017-08-25 17:52:20:125 1476 I00000000: Tape: ReadPosition 1755181056, size = 4096
2017-08-25 17:52:20:125 1476 I00000000: Read from cache Position = 1755181056, size = 4096
2017-08-25 17:52:20:125 1476 I00000000: Tape: from cache read 4096 bytes.
2017-08-25 17:52:20:125 1476 I00000000: Tape: ReadPosition 1755185152, size = 4096
2017-08-25 17:52:20:125 1476 I00000000: Read from cache Position = 1755185152, size = 4096
2017-08-25 17:52:20:125 1476 I00000000: Tape: from cache read 4096 bytes.
2017-08-25 17:52:20:126 1476 I00000000: Tape: ReadPosition 1755189248, size = 4096
2017-08-25 17:52:20:126 1476 I00000000: Read from cache Position = 1755189248, size = 4096
2017-08-25 17:52:20:126 1476 I00000000: Tape: from cache read 4096 bytes.
2017-08-25 17:52:20:126 1476 I00000000: Tape: ReadPosition 1755193344, size = 4096
2017-08-25 17:52:20:126 1476 I00000000: Read from cache Position = 1755193344, size = 4096
2017-08-25 17:52:20:126 1476 I00000000: Tape: from cache read 4096 bytes.
2017-08-25 17:52:20:128 1476 I00000000: Tape: ReadPosition 1755197440, size = 4096
2017-08-25 17:52:20:128 1476 I00000000: Read from cache Position = 1755197440, size = 4096
2017-08-25 17:52:20:128 1476 I00000000: Tape: from cache read 4096 bytes.
2017-08-25 17:52:20:128 1476 I00000000: Tape: ReadPosition 1755201536, size = 4096
2017-08-25 17:52:20:128 1476 I00000000: Read from cache Position = 1755201536, size = 4096
2017-08-25 17:52:20:128 1476 I00000000: Tape: from cache read 4096 bytes.
2017-08-25 17:52:20:128 1476 I00000000: Tape: ReadPosition 1755205632, size = 4096
2017-08-25 17:52:20:128 1476 I00000000: Read from cache Position = 1755205632, size = 4096
2017-08-25 17:52:20:128 1476 I00000000: Tape: from cache read 4096 bytes.
2017-08-25 17:54:37:639 6028 I00000000: Refreshing locks of tape resources in ARSM. ClientID = '90520B31-1BCF-44BB-A8F5-E36F51B0E9BB'
2017-08-25 17:58:37:641 6028 I00000000: Refreshing locks of tape resources in ARSM. ClientID = '90520B31-1BCF-44BB-A8F5-E36F51B0E9BB'
2017-08-25 18:02:37:641 6028 I00000000: Refreshing locks of tape resources in ARSM. ClientID = '90520B31-1BCF-44BB-A8F5-E36F51B0E9BB'
2017-08-25 18:06:37:641 6028 I00000000: Refreshing locks of tape resources in ARSM. ClientID = '90520B31-1BCF-44BB-A8F5-E36F51B0E9BB'
2017-08-25 18:10:37:641 6028 I00000000: Refreshing locks of tape resources in ARSM. ClientID = '90520B31-1BCF-44BB-A8F5-E36F51B0E9BB'
2017-08-25 18:14:37:641 6028 I00000000: Refreshing locks of tape resources in ARSM. ClientID = '90520B31-1BCF-44BB-A8F5-E36F51B0E9BB'
2017-08-25 18:18:37:641 6028 I00000000: Refreshing locks of tape resources in ARSM. ClientID = '90520B31-1BCF-44BB-A8F5-E36F51B0E9BB'
2017-08-25 18:22:37:642 6028 I00000000: Refreshing locks of tape resources in ARSM. ClientID = '90520B31-1BCF-44BB-A8F5-E36F51B0E9BB'
2017-08-25 18:26:37:647 6028 I00000000: Refreshing locks of tape resources in ARSM. ClientID = '90520B31-1BCF-44BB-A8F5-E36F51B0E9BB'
2017-08-25 18:30:37:649 6028 I00000000: Refreshing locks of tape resources in ARSM. ClientID = '90520B31-1BCF-44BB-A8F5-E36F51B0E9BB'

 

So these logs don't help either...

 

Regards,
Thomas

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 0
Comments: 29

Hello, Thomas.

From your logs I see that tape part of backups is waiting for data from archiver but it is absent. So I guess that the hang is in the archiving process.

Here https://forum.acronis.com/comment/423507#comment-423507 problem was solved with custom archive3.dll.

Please try that dll to check if issue will be resolved.

 

Good morning,

it works - more than 1TB written on tape without any problem ...

Great work Acronis!