Forum Discussion

Oriol_Cerba's avatar
12 years ago

'en cola'

Buenos dias.

Tenemos instalado un Veritas Backup Exec 12.5 y acabo de adquirir nuevos soportes (hp lto-3 ultrium RW). Disponemos de una biblioteca robótica Hp 1x8 G2 AUTOLDR.

Aunque la capacidad es de 800Gb, cuando la copia llega a las 400Gb, el trabajo se queda 'en cola' y no da ningún tipo de alarma, por lo que no acabo de entender que sucede. En tipo de soporte los parámetros son :

tipos soporte : LTO3,

Grupo de soportes : conservar datos indefinidamente, no permitir,

protecion reemplazo : Infinito-No permitir reemplazo

Agregable hasta : No agregable (soportes completos)

Admite cifrado de hardware : No

 

En lista de soportes, me aparece la misma etiqueta con dos descripciones, una que dice soporte desconocido, y otra en blanco, con propiedades distintas en cuanto al dato agregable hasta que en una indica 'No agregable' y en el otro indica 'Infinito permitir agregacion'. En este último en propiedades me da que no hay datos copiados.

 

Gracias.

  • Run tapeinst.exe from BE installation directory to install symantec drivers.

    It is enabled on device, but backup job also should be configured to use Compression. Check in Job properties/description. 

    EDIT: Have a look at this TN: http://www.symantec.com/docs/TECH6098

  • Now I'm baking up some files so I'll change the drivers later.

     

    In job properties I've hardware, if not none. I've changed this to 'Hardware, if not , software'

     

     

  • I think the trypical compression ratio is even lower, more like 1.2 - 1.3

  • Colin: I would be very interested to know if BE is capable of getting anything better than 2:1, and NOT on text files only.

    I haven't seen this...I believe IBM follows a 3:1 compression ration but this falls outside of the standards for LTO it seems...

    Thanks!

  • Anda a la solapa de alertas y responde todas las que tengas, no importa lo que sean, dale OK a todo.

    A veces pasa que por una alerta olvidada, te jode la vida. 

     

    Saludo,.

  • Cleared the solution...please explain how accepting all alerts fixed your compression problem...

    Thanks!

  • CraigV, Some alerts can bother if are not replied in time and you leave them there, I mean, they still there waitnig for a "Yes, ok, do it" or a "No, dont' do it", some of these are most regarding to media you know, like "Tape 00001L3 is write protected, are you sure you want to delete it", that alert message is linked to a backup job, and I saw several times that one specific job didn't run because an alert wasn't replied for months. I saw it a lot times when I worked as a TSE for Sym; Or pause/unapause the server, that was the second thing I do when I face some issue like this; If this doesn't work then I check what are you trynig to backup, (a SQL db, exchange, etc..) and then I login on those servers to check if everything is ok. It's a time consuming task if none of those works. Hope it helps for start a basic troubleshooting.

     

    Oriol, espero que hayas podido resolver el problema limpiado las alertas. Saludos! 

     

    EDIT: I can´t remember the exact text of the warning for "Tape 00001L3 is write protected, are you sure you want to delete it" but it was something like that. 

  • I understand that...well aware! HOWEVER...the OP enquired about tape compression, a physical issue. So how does an alert ensure that a tape doesn't get decent compression. I've seen a lot of forum topics, and done a lot of work with BE (9.1, 10d, 11d, 12.5, 2010 R1/R2/R3) and never seen or heard of an alert causing compression issues.

    That is why the solution has been cleared pending proper explanation. WHat you have added above doesn't tie in with what you stated or the OP is experiencing.

    Thanks!

  • Well, I was talking about the "en cola" issue, (queued), not about the compression .