Differences

This shows you the differences between two versions of the page.

--- software:backupexec [2013/10/06 20:09] – created superwizard
+++ software:backupexec [2015/11/07 22:36] – superwizard
@@ Line 1: / Line 1: @@
+====== system lock chk bkup sw cfg ======
+From: https://www.veritas.com/support/en_US/article.TECH67698
+<code>
+HKLM\software\Symantec\Backup Exec for Windows\Adamm\Disable Library Door Lock
+</code>
+{{ :software:disblelibrarydoorlock.jpg?300 |}}
+====== Catalog Location ======
+From: http://serverfault.com/questions/259324/how-to-backup-symantec-backup-execs-catalog
+    look at the catalog settings in the Options menu, under "Settings" and "Catalog", and see
+    where the catalogs are stored
+====== Catalog Period ======
+From: http://serverfault.com/questions/259324/how-to-backup-symantec-backup-execs-catalog
+    I wonder if your catalog retention period is set to an exceedingly long period, regular
+    catalog pruning operations aren't taking place, or something has gone crazy. I'd have a
+    look at the catalog settings in the Options menu, under "Settings" and "Catalog", and see
+    what the retention period looks like. Do you see any odd "alerts" re: catalogs?
+====== Backup Exec tapes refuse to catalog ======
+From: http://pcloadletter.co.uk/2012/02/08/backup-exec-tapes-refuse-to-catalog/
+    The workaround was was to select the problem tapes in the Media tab, associate them with
+    the Retired Media Media Set, then right-click and delete them from the media view. This
+    removes any mention of that media from Backup Exec’s database. Then rescan the autoloader’s
+    slots in the Devices tab, and run an Inventory job on them all. Finally, run the Catalog job
+    once again – then it works.
 ====== How to run a dump database with the Backup Exec for Windows Servers Utility (BEUtility) to backup the database file to hard disk ======