on 12-11-2013 12:10 PM
This is a perl script (unix) that helps map client historical data and policy information to a specified client in a one-click, one-command solution. The advantage of this script is its capability to provide average start times and average run times along with the policy schedule's backup windows so that backup customers can get a good estimate of when their backups are running. Usage is below:
USAGE: client_to_policy_map.pl -client <client> [-hours <hours>] <client> - The name of the client you wish to inspect. <hours> - How many hours back you want to average (defaults to 672).
The average run times and average start times are determined by how many hours ago you wish to use backups from. This defaults to 672, which is about 28 days.
Sample Output
SCHEDULE: Name: site1clients-Dedup Active: 0 Residence: nbudedupe01-pd Schedule: Daily_Incremental Retention Level: 2 weeks Day of Week: 3,1;4,1;5,1;6,1;7,1;3,2;4,2;5,2;6,2;7,2;3,3;4,3;5,3;6,3;7,3;3,4;4,4;5,4;6,4;7,4;3,5;4,5;5,5;6,5;7,5 Tue: 01:30:00 - 04:00:00 Wed: 01:30:00 - 04:00:00 Thu: 01:30:00 - 04:00:00 Fri: 01:30:00 - 04:00:00 Sat: 01:30:00 - 04:00:00 Average Start Time: 01:34:32 Average Elapsed Time: 00:05:55
For information about the thought process and further development being worked on for this script, please go to: https://www-secure.symantec.com/connect/blogs/finding-policy-information-client-command-line-scripti....
Hi Alan,
This sounds really good and really want to test it out. Quick questions please:
1. What location am i expected to save this script? Is it meant to be initiated from the client or the master servers?
2. Do you have a window version of this script?
Regards,
Dolapo
Dolly,
This script should run on master server and not from the client.
You can save the script to your user directory as Alan has given the full path of the command so you do need to worry about the location.