gwtmstmp - GroupWise Time Stamp Utility
gwtmstmp --postpath post_office_folder [--set] [--get] [--clear] [--backup] [--restore] [--retention] [--date mm/dd/yyyy] [--time hh:mm[am|pm]] [--gmttime seconds] [--userid groupwise_user_name] [--userdb user_database]
The GroupWise Backup Time Stamp utility (GWTMSTMP) places date and time information on user databases (userxxx.db) in order to support message backup, restore, and retention. The time stamp indicates the last time the database was backed up.
If a user deletes an item from his or her mailbox and purges it from the Trash, the item is removed from the user’s database only if the time stamp shows that the item has already been backed up. Otherwise, the item remains in the user’s database until the database is backed up, at which time it is purged from the database.
You can run GWTMSTMP on all user databases in a post office or on a single user database. No other databases are affected.
To ensure thorough user database backups, you can ensure that deleted items are not purged from users’ databases until they have been backed up. Two conditions must be met in order to provide this level of protection against loss of deleted items:
Theoption must be selected for the post office in the Administration Console ( object > > > ).
User databases (userxxx.db) must be time-stamped every time a backup is performed so that items can be purged only after they are backed up.
You can use GWTMSTMP to manually add the restore time stamp to the database. The restore time stamp is not required for any GroupWise feature to work properly. Its primary purpose is informational.
If you use a message retention application, the application should automatically add the retention time stamp after retaining the database’s messages. Any messages with dates that are newer than the retention time stamp cannot be purged from the database. You can use GWTMSTMP to manually add a retention time stamp.
If you use a message retention application, you might need to retain items more than once if you want to capture changes to personal subjects and personal attachments on items. You can use GWTMSTMP to manually update the retention time stamp on modified items, so that they are retained again.
(Required) Specifies the full path to the post office folder where the user databases to time-stamp are located.
Sets the current date and time (of backup, restore, or retention) on user databases.
Lists existing backup, restore, and retention time stamp information for user databases. If no time stamps are set, no times are displayed. If no other operational switch is used, --get is assumed.
Removes time stamps (of backup, restore, or retention) from user databases.
Specifies the type of time stamp (backup, restore, retention, or modified retention) on which to perform the get or set operation. If no time stamp type is specified, the operation is performed on the backup time stamp. Multiple time stamp types can be specified.
Specifies the date that you want placed on user databases. If no date is specified, the current date is used.
Use the format mm/dd/yyyy (for example, 05/18/2014 for May 18, 2014). If your locale does not use the mm/dd/yyyy format, use gwtmstmp --help to determine the format for your locale.
Specifies the time that you want placed on user databases. If no time is specified, 00:00 is used.
Use the format hh:mm, expressed in a 24-hour format (for example, 20:45) or expressed with the am or pm option (for example, 8:45pm).
Specifies the number of seconds since midnight on January 1, 1970 Greenwich Mean Time (GMT), that you want placed on the user databases.
Provides a specific GroupWise user name so that an individual user database can be time-stamped.
Provides a specific user database (userxxx.db) so that an individual user database can be time-stamped.
Displays the help information and exits.
This program normally runs as root.
Checks the existing time stamp on all GroupWise user databases in a post office.
Sets a current time stamp on all user databases in a post office.