Forum Discussion

levd's avatar
levd
Level 4
10 years ago

backup exec reports "jobs summary" include directory details

Hi,

 

Does anyone know how to include the directory details in the "jobs summary" report? Or how to create a basic report with directory details in it? Not only how many files and folder exists but the names of the folders in it etc.

 

Thanks,

LEVD

  • The following is a rudimentary perl script which I've used to pull that info out of the detailed TXT job log:

    #!c:/perl/bin/perl -w
    use strict;

    my ($in, $out, $buf, @wds, $w);
    my $DEBUG = 0;

    if ($#ARGV != 1) { &usage; }
    $in = $ARGV[0];
    $out = $ARGV[1];

    open(IN,$in)||die "Can't open $ARGV[0] ($!)\n";

    open(OUT,">$out")||die "Can't create output ($!)\n";
    while(<IN>) {
         chomp $_;
         $buf = $_;
         @wds = split /\s+/, $buf;
         $buf="";
         foreach $w (@wds) {
            if ( $DEBUG && ($w=~ /\\/ ) ) {print $w."\n"};
            if ($w =~ /\\/ ) {print OUT $w."\n";}
         }
    }

    close(IN);
    close(OUT);
    print "Check output file $out\n";
    exit 1;


    sub usage() {
        print "$0 Infile Outfile\n";
        exit 1;
    }

     

    If Symantec hasn't changed the format of the logs from Ver. 12, it'll work for a Windows format. There's a different format for *nix logs.

6 Replies

  • ...check the canned reports, or you can create a customised report with the specific fields you are looking at.

    Thanks!

  • I looked at the custom reports and cant find how to show backed up folder names etc.
    Do you have some more information?

  • ...if you increase the level of logging in your backup job log it will detail file and folder level at the expense of a larger job log size.

    Thanks!

  • ok thanks i allready did that in settings, but i guess i have to wait a bit more.

    Thanks!

     

  • The following is a rudimentary perl script which I've used to pull that info out of the detailed TXT job log:

    #!c:/perl/bin/perl -w
    use strict;

    my ($in, $out, $buf, @wds, $w);
    my $DEBUG = 0;

    if ($#ARGV != 1) { &usage; }
    $in = $ARGV[0];
    $out = $ARGV[1];

    open(IN,$in)||die "Can't open $ARGV[0] ($!)\n";

    open(OUT,">$out")||die "Can't create output ($!)\n";
    while(<IN>) {
         chomp $_;
         $buf = $_;
         @wds = split /\s+/, $buf;
         $buf="";
         foreach $w (@wds) {
            if ( $DEBUG && ($w=~ /\\/ ) ) {print $w."\n"};
            if ($w =~ /\\/ ) {print OUT $w."\n";}
         }
    }

    close(IN);
    close(OUT);
    print "Check output file $out\n";
    exit 1;


    sub usage() {
        print "$0 Infile Outfile\n";
        exit 1;
    }

     

    If Symantec hasn't changed the format of the logs from Ver. 12, it'll work for a Windows format. There's a different format for *nix logs.