Ayuda de vídeo de Screencast

Catalog Schedule

Created: 07 Febrero 2013 • Updated: 11 Febrero 2013 | 5 comments
el cuadro de los Alex Zn
Se ha solucionado este problema. Vea la solución.


Is it possible, to schedule everyday catalog operations for all my tapes ?

Comentarios ComentariosIr al último comentario

el cuadro de los V4

What are causes for you to schedule cataloging media everyday

el cuadro de los Kiran Bandi

Not at all required and not possible. Whenever BE performs a backup, catalog for that backup data will be created and saved in CATALOGS folder under BE installation directory. Without truncation enabled, catalog will be retained untill the respective media gets overwritten within the same installation of BE. With truncation enabled, only header files of the catalog will be kept and you would need to catalog the media ONLY incase of restore. And cataloging a tape can take so long depending on the capacity of the data exist on that media.


el cuadro de los pkh

It is possible to schedule the BEMCLI Submit-BECatalogMediaJob cmdlet to to the catalog, but why would you need to do so on a daily basis. 

el cuadro de los Alex Zn

It is not so simple to explain. I have test environment with they own media server, for some reasons I need periodically perform agent (SQL) restore backups that was made by production media server on production environment. So the case is that clients in test environment and in production environment may have the same IP, so I cannot simply perform restore from my production server to test environment. What i need to do is make available backups of production server to test server, the only possible way is sharing tape library. So production server make backups, than test server perform cataloging of all media and then restore data to test clients. Am I clear?

el cuadro de los pkh

If you just need to replicate SQL databases from the production to the test environment, are you aware of this option for the SQL backup job, "Create on-disk copies of SQL backups to be placed on the SQL Server where the database is located"?  (See page 817 of the Admin Guide).

You can ship this copy to the test environment and then use SQL Studio to restore the database.  This might be a better option.