Unsolved

This post is more than 5 years old

2 Intern

 • 

243 Posts

2354

December 24th, 2010 00:00

Report - last successful full backup

I'm making a report to indicate last successful full backup of savesets (and also a second version of this where I filter the results to report only before a specified date).  However I've noticed when comparing to mminfo output that some of the information is erroneous, I was wondering if anyone has any suggestions as to why this data is not working correctly.

My report is something like this:

Backup Save Set Details

(server, sub name,group,schedule,client,save set,domain name,queue start)

(period=epoch to current time, no interval)

(node=default)

(conditions: level=full AND status=success)

(no limit)

(Order by Queue Start ascending, no limit)

(no smoothing)

I

V

Group By [I believe this is where the report is failing as it is not clear how the grouping would respond with a date]

(Default Duration=Max, Number=Max, Percent=Average, String=last, GroupBy1/2/3: Server, Client, Saveset)

(Fields drop: Sub Name, Group, Schedule, Domain Name)

I

V

Join the following data source (this is to remove inactive clients from the results):

Backup Client Config

(Server, Sub Name, Client)

(Time default settings)

(Node defaults)

(Conditions: active=true)

(no limit, no order)

I

V

Order

(Order by client, ascending)

(Drop Sub Name)

The following is amended to for the report to report when the backup time is before a specified time:

(Conditions: queue start less than start time)

Any suggestions to fix this gladly accepted!

2 Intern

 • 

243 Posts

January 4th, 2011 01:00

1122 Last successful full saveset backup details Data Protection false false 1 com.sysdm.wysdm.guireport.renderers.tablebased.table.DetailedTableRenderer last save set details Backup Save Set Details true 0 0 3 0 -1 0 agent_name String sub_name String group_name String schedule_name String client_name String job_name String domain_name String queuestart Date
backupjob Level Full -1 0 false defaultDurationOperation java.lang.String Max defaultNumberOperation java.lang.String Max defaultPercentOperation java.lang.String Average defaultStringOperation java.lang.String All groupBy1 com.sysdm.wysdm.reporter.ReportFieldDef Server groupBy2 com.sysdm.wysdm.reporter.ReportFieldDef Client groupBy3 com.sysdm.wysdm.reporter.ReportFieldDef Save Set groupBy4 com.sysdm.wysdm.reporter.ReportFieldDef None groupBy5 com.sysdm.wysdm.reporter.ReportFieldDef None Server String Client String Save Set String Queue Start Date Backup Client Config true 0 1 2 2 -1 0 agent_name String sub_name String client_name String
client_config Active 1 -1 0 true Server String Client String Save Set String Queue Start Date Sub Name String orderField com.sysdm.wysdm.reporter.ReportFieldDef Client orderPolicy java.lang.String Ascending Server String Client String Save Set String Queue Start Date true Server String true Client String true Save Set String true Queue Start Date true true User Selected User Selected User Selected User Selected User Selected User Selected User Selected User Selected top

147 Posts

January 8th, 2011 14:00

ah I have done a report where it shows all failed backups for the last 24 hrs (or whatever time window) and then I had a column to show the "last successful run" which reported the date

I can't find the report though.. it was quite hard to write at the time.

only help I can really offer is to watch out for that group by operator, I am pretty sure it looks at the primary keys (ones in bold), which you may have to use set key operators to unset some fields as primary keys

2 Intern

 • 

243 Posts

January 10th, 2011 03:00

Thanks for the advice Jason, I'm going to review the primary keys in this report and see if that may be a cause of the issue.

No Events found!

Top