Differences

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

--- cookbook:backupexec [2018/12/28 03:59] – [Example Synchronization Definition] Scott Cunliffe
+++ cookbook:backupexec [2025/01/21 22:07] (current) – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
 ====== BackupExec ======
-[[https://en.wikipedia.org/wiki/Backup_Exec|BackupExec]] is Symantec's (previously Veritas) small business backup solution and depending on the version, allows [[object:volume|Volume]] information to be extracted via command line, Windows Power Shell and ODBC.
+[[https://en.wikipedia.org/wiki/Backup_Exec|BackupExec]] is Veritas's small business backup solution and depending on the version, allows [[object:volume|Volume]] information to be extracted via:
-When [[object:volume|Volumes]] are new, they will appear in the Scratch Media Set, but as they are used they are assigned to a specific Media Set. Unlike Symantec's [[cookbook:netbackup|NetBackup]] product, when [[object:volume|Volumes]] expire, by default, they are not moved back into the Scratch Media Set.
+  - Command line, or
+  - Windows Power Shell, or
+  - ODBC.
-===== The bemcmd command =====
+When [[object:volume|Volumes]] are new, they will appear in the Scratch Media Set, but as they are used they are assigned to a specific Media Set.
-<note tip>When BackupExec is installed a number of predefined reports are created. The ID of each prefedined report varies from one installation to the next.</note>
+Unlike Veritas's [[cookbook:netbackup|NetBackup]] product, when [[object:volume|Volumes]] expire, by default, they are not moved back into the Scratch Media Set.
-====  BackupExec 2010 and below:  Extracting Volume information using the command line interface ====
-<sxh>
+=====  The Command Line Interface =====
+The Command Line Interface was used in BackupExec 2010 and below.
+<note tip>When BackupExec is installed a number of predefined reports are created. The ID of each predefined report varies from one installation to the next.</note>
+==== Sample Command Line Syntax ====
+<code>
 bemcmd -o402 -r25 -ft:4 -f:"BE.csv" > "BE-CMD.txt" 2>&1
-</sxh>
+</code>
+=====   The Windows Powershell interface =====
+The Windows Powershell interface replaced the Command Line Interface in BackupExec 2012.
-====  BackupExec 2012 and above: Extracting Volume information using the Windows Power Shell interface ====
+==== Sample Powershell Script ====
-<sxh>
+<code>
 cd "C:\Program Files\Symantec\Backup Exec\Modules\BEMCLI"
 import-module BEMCLI
@@ Line 30: / Line 43: @@
 #
-# Initialize the outout array
+# Initialize the output array
 #
 $Records = @()
@@ Line 44: / Line 57: @@
-$Records | Export-CSV -notype BE.cs
+$Records | Export-CSV -notype BE.csv
-</sxh>
+</code>
 ===== Synchronization =====
@@ Line 54: / Line 67: @@
   - The CSV output file.
-  - Command line arguments that instruct the program how to process volumes.
+  - Command line arguments that instructs the program how to process volumes.
   - A synchronization definition file that instructs the program how to interpret the CSV output.
@@ Line 62: / Line 75: @@
 Call the TapeTrack Sync module and process the output created by the Powershell script.
-<sxh>
+<code>
 powershell.exe -NoProfile -file "BE-List.ps1" -executionpolicy RemoteSigned
 TMSS10Sync -S user:-password@server -a -d BE.ttidef < BE.csv
-</sxh>
+</code>
 Where:
@@ Line 78: / Line 91: @@
 **BE.ttidef**
-<sxh>
+<code>
 #
 # Set the Customer and Media as literal values as they never change
@@ Line 108: / Line 121: @@
 RemoveSpaces(DESCRIPTION);
 #
-</sxh>
+</code>
-<-  ^ :cookbook:introduction|Cookbook ^ :cookbook:dataprotector|Data Protector Sync Cookbook->
+<-  ^ :cookbook:introduction|Cookbook ^ :cookbook:commvault|Commvault Sync Cookbook->
+{{tag> cookbook}}