the nt master is in england, and the linux master is in ireland, so they should have similar localization settings. most of our environments are linux (7 across
the globe), and they all give the same output. our backup admin in england just runs bpdbjobs -ignore_parent_jobs and has 8 columns he wants defined (not sure where as it is windows) so he only sees those in the output, it the date gets formatted by bpdbjobs.
he is now bringing up a new environment in ireland on linux, and put the column definitions in bp.conf. he gets the columns he wants, but the month/day are switched between nt and linux so it screws up a spreadsheet that the data goes into.
on the 3 netbackup servers (all linux) in the u.s., i run bpdbjobs with the -all_columns and use a perl script to pick out data for reports when i need it.
thanks,
jerald
From: Martin, Jonathan [mailto:JMARTI05 AT intersil DOT com]
Sent: Tuesday, July 17, 2012 1:31 PM
To: Iverson, Jerald; veritas-bu
Subject: RE: [Veritas-bu] bpdbjobs comand output formatting
Which switch are you using with bpdbjobs? When I run bpdbjobs with the –all_columns switch on my Windows 2008 R2 Master running 7.1 I get UNIX time. Just a
shot in the dark here, but have you checked your localization settings in Windows? (Control Panel, Clock Language, Region)?
-Jonathan
From: veritas-bu-bounces AT mailman.eng.auburn DOT edu [mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu]
On Behalf Of Iverson, Jerald
Sent: Tuesday, July 17, 2012 2:20 PM
To: veritas-bu
Subject: [Veritas-bu] bpdbjobs comand output formatting
i have a bpdbjobs comand line output formatting question, netbackup 7.1.0.3.
on a nt netbackup master server, i have column definitions set to output the "started" column, and the output format shows up as dd/mm/yyyy hh:mm:ss, ex:
16/07/2012 19:00:46
on a linux netbackup master server, the bpdbjobs command gives me mm/dd/yy hh:mm:ss, ex:
07/16/12 21:00:38
is there any way to make them both behave the same?
thanks,
jerald
****************************************************************
Confidentiality Note: The information contained in this
message, and any attachments, may contain confidential
and/or privileged material. It is intended solely for the
person(s) or entity to which it is addressed. Any review,
retransmission, dissemination, or taking of any action in
reliance upon this information by persons or entities other
than the intended recipient(s) is prohibited. If you received
this in error, please contact the sender and delete the
material from any computer.
****************************************************************
