Loading...
Loading...
Data Protection Advisor is not able to collect backup job data successfully from HP Data Protector via the Jobmonitor request. Within the dpaagent.log with debug low enabled the following messages where seen: DBG1 18064.9236 20191211:154907 com.base.ctime - testDateTimeFormat(): checking domingo, 20 de octubre de 2019, 12:00:10 with %cDBG1 18064.9236 20191211:154907 com.base.ctime - testDateTimeFormat(): no matchDBG1 18064.9236 20191211:154907 com.base.ctime - testDateTimeFormat(): checking domingo, 20 de octubre de 2019, 12:00:10 with %x %XDBG1 18064.9236 20191211:154907 com.base.ctime - testDateTimeFormat(): no matchDBG1 18064.9236 20191211:154907 com.base.ctime - testDateTimeFormat(): checking domingo, 20 de octubre de 2019, 12:00:10 with %x, %XDBG1 18064.9236 20191211:154907 com.base.ctime - testDateTimeFormat(): no matchDBG1 18064.9236 20191211:154907 agent.mod.dp - dpGetSessionTimeformat(): failed to calculate suitable time format for session times
The time format in HP Data Protector is in Spanish and is using the word "de" in the date. For example: domingo, 20 de octubre de 2019, 12:00:10Data Protection Advisor is not able understand the date with any of it's default date formats.
This issue can be resolved by manually setting the "Time format used to parse session and job start and end times" option in the DataProtector Job Monitor request. Below are the steps to complete this: Go to Inventory > Object Library > Applications > Select the Data Protector serverIn the Details popup box, click on the Data Collection tab.Select the DataProtector Job Monitor request.Click the edit button in the bottom left.In the Edit Effective Request popup, scroll to the bottom to Options. Click in the value field next to "Time format used to parse session and job start and end times" to input the correct time format for the Data Protector server.Click OK to save and close the Effective Request popupClick OK to save and close the Details popup Note: The DPA agent makes use of the Unix Standard STRPTIME format. Further information on this format is listed below after the following example: If the time format in the dpaagent.log is: domingo, 20 de octubre de 2019, 12:00:10 Then the following Unix Standard STRPTIME format would be used: %A, %d de %B de %Y, %H:%M:%S. Below is some further information on the Unix Standard STRPTIME format and a list of possible variables: %% - The % character.%a or %A - The weekday name according to the current locale, inabbreviated form or the full name.%b or %B or %h - The month name according to the current locale, inabbreviated form or the full name.%c - The date and time representation for the current locale.%C - The century number (0-99).%d or %e - The day of month (1-31).%D - Equivalent to %m/%d/%y . (This is the American style date, very confusing to non-Americans, especially since %d/%m/%y is widely used in Europe. The ISO 8601 standard format is %Y-%m-%d .)%H - The hour (0-23).%I - The hour on a 12-hour clock (1-12).%j - The day number in the year (1-366).%m - The month number (1-12).%M - The minute (0-59).%n - Arbitrary whitespace.%p - The locale s equivalent of AM or PM. (Note: there may be none.)%r - The 12-hour clock time (using the locale s AM or PM). In the POSIX locale equivalent to %I:%M:%S %p . If t_fmt_ampm is empty in the LC_TIME part of the current locale then the behavior is undefined.%R - Equivalent to %H:%M .%S - The second (0-60; 60 may occur for leap seconds; earlier also 61 was allowed).%t - Arbitrary whitespace.%T - Equivalent to %H:%M:%S .%U - The week number with Sunday the first day of the week (0-53). The first Sunday of January is the first day of week 1.%w - The weekday number (0-6) with Sunday = 0.%W - The week number with Monday the first day of the week (0-53). The first Monday of January is the first day of week 1.%x - The date, using the locale s date format.%X - The time, using the locale s time format.%y - The year within century (0-99). When a century is not otherwise specified, values in the range 69-99 refer to years in the twentieth century (1969-1999); values in the range 00-68 refer to years in the twenty-first century (2000-2068).%Y - The year, including century (for example, 1991).Some field descriptors can be modified by the E or O modifier characters to indicate that an alternative format or specification should be used. If the alternative format or specification does not exist in the current locale, the unmodified field descriptor is used.The E modifier specifies that the input string may contain alternative locale-dependent versions of the date and time representation: %Ec - The locale s alternative date and time representation.%EC - The name of the base year (period) in the locale s alternative representation.%Ex - The locale s alternative date representation.%EX - The locale s alternative time representation.%Ey - The offset from %EC (year only) in the locale s alternative representation.%EY - The full alternative year representation.The O modifier specifies that the numerical input may be in an alternative locale-dependent format: %Od or %Oe - The day of the month using the locale s alternative numeric symbols; leading zeros are permitted but not required.%OH - The hour (24-hour clock) using the locale s alternative numeric symbols.%OI - The hour (12-hour clock) using the locale s alternative numeric symbols.%Om - The month using the locale s alternative numeric symbols.%OM - The minutes using the locale s alternative numeric symbols.%OS - The seconds using the locale s alternative numeric symbols.%OU - The week number of the year (Sunday as the first day of the week) using the locale s alternative numeric symbols.%Ow - The number of the weekday (Sunday=0) using the locale s alternative numeric symbols.%OW - The week number of the year (Monday as the first day of the week) using the locale s alternative numeric symbols.%Oy - The year (offset from %C) using the locale s alternative numeric symbols. Contact Dell EMC Technical Support for further details or information.
Click on a version to see all relevant bugs
Dell Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.