Backup Central

Hi folks,

I desperately need to generate a CSV file on a regular basis of the jobs being done in Backup Express. I can find how to generate a CSV file by stepping through the pdf procedures, but do not know how to automate this. Any ideas? Would the best thing be to just use post-scripts when jobs complete to append to a file and work that way?

Thanks.

Gregg Yurchak

Hi Gregg,

I started work on a perl script scanning through the masterlogs (last day) but then I started using BEXreporter so there was no need.

The codes e.g. SNBLH_xxxxx are the messages and I'm looking at text position xx after space.

Here is part of my code so that you can use the idea.

if ($testtape eq "SNBJH_3462J") { # This is a Tape Backup!!!
$jobid = getvalue("SNBJH_3208J",14,\@data);
$jobname = getvalue("SNBJH_3208J",11,\@data);
$nodename = getvalue("SNBJH_3462J",14,\@data);
$jobtype = getvalue_chopped("SNBJH_3208J",20,\@data);
$rc = gettapejobrc("SNBSCH5674J","SNBSCH5705J",16,\@data);
$starttime = gettime("SNBSCH5607J",\@data);
$endtime = getendtime(\@data);
}
elsif ($testndmp eq "backup_ads" || $testndmp eq "backup_ads_incr" || $testdp eq "SNBDPH_327J") { # This is a NDMP Backup!!!
$jobid = getvalue("SNBJH_3208J",14,\@data);
$jobname = getvalue("SNBJH_3208J",11,\@data);
$nodename = getvalue_chopped("SNBJH_3257J",12,\@data);
$jobtype = getvalue_chopped("SNBJH_3208J",20,\@data);
$rc = gettapejobrc("SNBSCH5674J","SNBSCH5705J",16,\@data);
$starttime = gettime("SNBSCH5607J",\@data);
$endtime = getendtime(\@data);
}
elsif ($testxrs eq "SNBSVH_220J") { # This is a XRS Backup!!!
$jobid = getvalue("SNBSVH_220J",11,\@data);
$jobname = getvalue_chopped("SNBSVH_220J",13,\@data);
$nodename = getvalue_chopped("SNBSVH_278J",13,\@data);
$nodename =~ s/node\(//;
$jobtype = getvalue_chopped("SNBSVH_220J",15,\@data);
$rc = getvalue_chopped("SNBSVH_255J",16,\@data);
$starttime = gettime("SNBSCH5607J",\@data);
$endtime = gettime("SNBSVH_255J",\@data);
}

Best regards

Chris

BEX doesn’t have report within the GUI to show this but we can get the information from a command line. Dumping the schedule in this way does not give all of the details of your scheduled environment, any exceptions, holidays, etc. will not appear in the output. This procedure simply dumps out what BEX has scheduled for a given range of time. This information is generally useful for reviewing your expected schedule. You will need to invoke a command line on your master server to run the ‘syncui’ program. If you are unfamiliar with this please refer to KB A006654.
Run Syncui from the BEX command prompt on the master server by running the following command:
syncui
The ‘syncui’ program will start and wait for interactive input. You will need to know the master server host name or IP address. Please replace MSERVER below with the master server host name or IP address. The schedule list requires a date range. This is represented by two groups of yyyy mm dd which represent the start and end dates in 4-digit year, 2-digit month, and 2-digit day format. Please enter the following syncui commands:
c s MSERVER sssched
sched list yyyy mm dd yyyy mm dd
quit
By way of example, if our master server name is “bex32ms” and we are interested in displaying the schedule for Sept 1st 2010 through Sept 10th 2010, you would use the following command sequence:
syncui
c s bex32ms sssched
sched list 2010 09 01 2010 09 10
quit
For larger enterprises, you may want to directly send the ‘sched list’ output to a file for review. You can use the –f parameter followed immediately by a file name (no space before) to capture this. So given the example above, if you needed to capture this to a file you can use:
sched list -fschedule.txt 2010 09 01 2010 09 10
Output will print to the screen, and it will also be saved to a file called ‘schedule.txt’.
Example output appears below.
--------------------------------------------------------------------------------
SID JOB NAME MM/DD HH:MM RET SUBTYPE STATUS MM/DD HH:MM JOBID
--------------------------------------------------------------------------------
0 migtest2-BASE 09/01 13:00 7 0 WAITING
0 migtest-BASE 09/01 14:00 7 0 WAITING
0 6mo_job-INCR 09/01 17:38 45 0 WAITING
0 migtest2-BASE 09/02 13:00 7 0 WAITING
0 migtest-BASE 09/02 14:00 7 0 WAITING
0 6mo_job-INCR 09/02 17:38 45 0 WAITING
0 migtest2-BASE 09/03 13:00 7 0 WAITING
0 migtest-BASE 09/03 14:00 7 0 WAITING
0 6mo_job-INCR 09/03 17:38 45 0 WAITING
0 migtest2-BASE 09/04 13:00 7 0 WAITING
0 migtest-BASE 09/04 14:00 7 0 WAITING
0 migtest2-BASE 09/05 13:00 7 0 WAITING
0 migtest-BASE 09/05 14:00 7 0 WAITING
0 6mo_job-BASE 09/05 17:37 45 0 WAITING
0 migtest2-BASE 09/06 13:00 7 0 WAITING
0 migtest-BASE 09/06 14:00 7 0 WAITING
0 6mo_job-INCR 09/06 17:39 45 0 WAITING
0 migtest2-BASE 09/07 13:00 7 0 WAITING
0 migtest-BASE 09/07 14:00 7 0 WAITING
0 6mo_job-INCR 09/07 17:39 45 0 WAITING
0 migtest2-BASE 09/08 13:00 7 0 WAITING
0 migtest-BASE 09/08 14:00 7 0 WAITING
0 6mo_job-INCR 09/08 17:39 45 0 WAITING
0 migtest2-BASE 09/09 13:00 7 0 WAITING
0 migtest-BASE 09/09 14:00 7 0 WAITING
0 6mo_job-INCR 09/09 17:39 45 0 WAITING
0 migtest2-BASE 09/10 13:00 7 0 WAITING
0 migtest-BASE 09/10 14:00 7 0 WAITING
0 6mo_job-INCR 09/10 17:39 45 0 WAITING