cancel
Showing results for 
Search instead for 
Did you mean: 

Restore Failing

gtmjha
Level 1

Hi All,

we are facing an issue with a simple flat file restore of MS windows policy. changes we made in our environment is we have upgraded our media server OS from 2008 to 2012. After upgrading the OS, media server's itself backup started failing with below error---

Jun 21, 2019 1:05:17 PM - Error bptm (pid=9580) The tape device at index -1 has a maximum block size of 65536 bytes, a buffer size of 262144 cannot be usedJun 21, 2019 1:05:17 PM - Warning bptm (pid=9580) media id JBS103 load operation reported an error

After that we have Changed the value in file called “SIZE_DATA_BUFFERS” in the location <INSTALL_PATH>\NetBackup\db\config\ and adjusted the buffer size to match tape buffers size 65536 byte from 262144 byte.  and backup starts working fine. 

 

Now i am trying to restore a data which was backedup prior to upgrade and it is failing with below error.


Jun 21, 2019 5:13:33 AM - begin Restore
Jun 21, 2019 5:13:35 AM - number of images required: 1
Jun 21, 2019 5:13:35 AM - media needed: JBS018
Jun 21, 2019 5:13:35 AM - media needed: JBS015
Jun 21, 2019 5:13:39 AM - restoring from image JBSPBACKUP_1559469211
Jun 21, 2019 5:13:39 AM - Info bpbrm (pid=6552) JBSPBACKUP is the host to restore to
Jun 21, 2019 5:13:40 AM - Info bpbrm (pid=6552) telling media manager to start restore on client
Jun 21, 2019 5:13:41 AM - Info bpbrm (pid=9248) JBSPBACKUP is the host to restore to
Jun 21, 2019 5:13:42 AM - connecting
Jun 21, 2019 5:13:44 AM - requesting resource JBS018
Jun 21, 2019 5:13:44 AM - Info bptm (pid=8208) Waiting for mount of media id JBS018 (copy 1) on server JBSPBACKUP.
Jun 21, 2019 5:13:44 AM - started process bptm (pid=8208)
Jun 21, 2019 5:13:44 AM - mounting JBS018
Jun 21, 2019 5:13:45 AM - granted resource JBS018
Jun 21, 2019 5:13:45 AM - granted resource HP.ULTRIUM5-SCSI.000
Jun 21, 2019 5:13:45 AM - Info bpbrm (pid=9248) start tar32 on client
Jun 21, 2019 5:13:47 AM - Info bptm (pid=8208) INF - Waiting for mount of media id JBS018 on server JBSPBACKUP for reading.
Jun 21, 2019 5:13:49 AM - Info tar32 (pid=6772) Restore started.
Jun 21, 2019 5:13:49 AM - connected; connect time: 0:00:00
Jun 21, 2019 5:14:59 AM - mounted JBS018; mount time: 0:01:15
Jun 21, 2019 5:14:59 AM - Info bptm (pid=8208) JBS018
Jun 21, 2019 5:15:02 AM - Info bptm (pid=8208) INF - Waiting for positioning of media id JBS018 on server JBSPBACKUP for reading.
Jun 21, 2019 5:15:02 AM - positioning JBS018 to file 1
Jun 21, 2019 5:15:02 AM - positioned JBS018; position time: 0:00:00
Jun 21, 2019 5:15:30 AM - begin reading
Jun 21, 2019 5:15:33 AM - Error bptm (pid=8208) cannot read image from media id JBS018, drive index 0, err = 234
Jun 21, 2019 5:15:41 AM - Info tar32 (pid=6772) done. status: 0
Jun 21, 2019 5:15:41 AM - Info tar32 (pid=6772) done. status: 0 - the requested operation was successfully completed
Jun 21, 2019 5:15:43 AM - Info bpbrm (pid=6552) child done, status 0
Jun 21, 2019 5:15:44 AM - Info bpbrm (pid=6552) got ERROR 85 from media manager
Jun 21, 2019 5:15:45 AM - restored from image JBSPBACKUP_1559469211;

 

 

i already tried to change the buffer value back to old on but still failing, MEDIA & MASTER version is same i.e 8.1.2

 

 

please help. 

1 REPLY 1

Marianne
Level 6
Partner    VIP    Accredited Certified

Dropping buffer size for backups seems like a workaround, not a solution.
The backup was written with higher buffer size, meaning that you need to fix the buffer issue.

Please have a look at this TN: https://www.veritas.com/support/en_US/article.100008923

Cause

 The most common causes:

1. The restore media server's SIZE_DATA_BUFFER value does not match the backup tape block size.
2. The SCSI controller and/or SCSI controller driver cannot handle large block size 

Since the HBA/controller was not changed, the default W2012 OS driver probably only supports 64K.
Look for W2012 vendor driver for the make/model HBA in the server. 

Please also ensure that the vendor tape driver is installed, and not the default Windows drivers.