Download

jblackett's picture
download
Reads:

3960

Score:
0
Comments:

2

Content Synchronization Status Report Set

Author Info

11 April 2011 - 1:02pm
Submitted by: jblackett

(View Disclaimer)

Report Set Description

Have you ever wanted to quickly find out whether a Primary Server was fully sync'd? This set of reports allows you to run a Content Sync Status Summary report shown below:

cssshot3.png

These pie charts show you the overall status for the servers in the zone. You can then move to the Details tab where you can see the detailed status of each Content Server in the zone. This document contains a section for each Parent Primary Server in the zone, as shown below:

cssshot4.png

From here you can drill down to a more detailed view of an individual server. The details for that server shows the content sync status of each bundle, policy or update that has been included for content replication to the select content server.

cssshot5.png

Installation Instructions

To import these reports into your ZENworks Report Server do the following:

1) Ensure that the Novell ZENworks Reports/Custom Reports/Custom Reports Library has been created in the ZRS report hierarchy as shown below:

cssshot1.png

2) Extract the contents of the ZIP file to a folder on your ZRS server.

3) Open a terminal window (Linux) or Command Prompt (Windows).

4) Change to the directory where you extracted the zip file.

5) Execute the 'zman asc ' command to save the credentials for the specified user name so that the zman commands executed by the scripts can be executed silently.

6) Execute either import.sh or import.bat. This will create a Content Sync Status folder and a Drilldown subfolder and then import the reports.

3) Execute either the import.sh or import

Known Issues

If you are running 'zman' on a Primary using an alternate port you need to add the -p parameter to each of the zman commands in the script.

Because of the nature of the queries used to determine synchronization status if you have a large number of bundles, policies, updates, or content servers or a large content repository it may take a few minutes for the report to execute. Additionally, the database platform being used may impact the amount of time taken to execute the report. As an example in a zone with a Sybase database and approximately 8000 bundles, 100000 pieces of content, and 3 content servers this report takes approximately 30 seconds to execute.

These reports use custom SQL queries to generate the report data as the data needed is not currently exposed as ZENworks Universe Objects.

Editor's Note: Because the setup.sh script is just a series of zman commands, you can speed up the execution by using the zman batch-execute command, e.g.
zman bex setup.sh
which will be quicker, because zman only needs to authenticate once, instead of authenticating for each command.

AttachmentSize
content_sync_status.zip699.21 KB

Disclaimer: As with everything else at Cool Solutions, this content is definitely not supported by Novell (so don't even think of calling Support if you try something and it blows up).

It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.




User Comments

kjhurni's picture

Awesome article!

Submitted by kjhurni on 14 April 2011 - 1:37pm.

This is awesome, thanks for taking the time to post this. I'd give you 5 Stars, but it seems to be unavailable.

dsambit's picture

These reports run for Sybase only

Submitted by dsambit on 27 June 2011 - 5:21am.

These reports will work against Sybase database only. The MSSQL and Oracle compatible reports will be uploaded soon.

© 2013 Novell