That method would be rather inefficient, as you would need to be very familiar with the filesystems in question to know what files have never changed since the original backup, and if not, you would basically be resorting to hunting and pecking to see if a particular file has the earliest backup date. Much easier to just query the database directly to get this information and be certain.
Mel Dennis Backup Systems Engineer Siemens IT Solutions and Services, Inc. PGST Data Center Operations 4400 Alafaya Trail MC Q1-108 Orlando, FL 32826 Tel.: 407-736-2360 Mob: 321-356-9366 Fax: 407-243-0260 mailto:[EMAIL PROTECTED] www.usa.siemens.com/it-solutions -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Fred Johanson Sent: Thursday, August 23, 2007 12:10 PM To: [email protected] Subject: Re: [ADSM-L] First Backup day Why not use the gui to look up some unchanging system file, as in the OS? The creation date should show when first backed up. -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Dennis, Melburn IT7 Sent: Thursday, August 23, 2007 11:05 AM To: [email protected] Subject: Re: [ADSM-L] First Backup day There are two ways to find this information. The first option is the easiest. By default TSM retains the session summary of backups (scheduled and unscheduled) for 30 days. If you know that the backups for these nodes were within that period then you can query the 'summary' table to see the earliest day of backup for a specific node. If the backups began earlier than that, then you will be forced to query the 'backup' table (which is a pain as the archive and backup tables in TSM are the largest and can usually take a really long time to query) and look for the oldest backup date of the files that node contains. Here are the examples of the two queries mentioned: Querying the summary table: select entity,start_time from summary where activity='BACKUP' and entity='NODENAME' order by start_time Querying the backup table: select node_name,backup_date from backups where node_name='NODENAME' order by backup_date Hope this helps! Mel Dennis Backup Systems Engineer Siemens IT Solutions and Services, Inc. PGST Data Center Operations 4400 Alafaya Trail MC Q1-108 Orlando, FL 32826 Tel.: 407-736-2360 Mob: 321-356-9366 Fax: 407-243-0260 mailto:[EMAIL PROTECTED] www.usa.siemens.com/it-solutions -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Shawn Drew Sent: Thursday, August 23, 2007 11:48 AM To: [email protected] Subject: [ADSM-L] First Backup day We have a request to provide the first day backups were run for a list of nodes. The registration date isn't good, as there is a several day lag from registration to first backup. These dates are older than the age of the event and activity log. Can anyone suggest a select statement for this? ________________________________________________ Shawn Drew Data Protection Engineer Core IT Production Office: 212.471.6998 Mobile: 917.774.8141 This message and any attachments (the "message") is intended solely for the addressees and is confidential. If you receive this message in error, please delete it and immediately notify the sender. Any use not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval. The Internet can not guarantee the integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will) not therefore be liable for the message if modified. Please note that certain functions and services for BNP Paribas may be performed by BNP Paribas RCC, Inc. -------------------------------- Ce message et toutes les pieces jointes (ci-apres le "message") sont etablis a l'intention exclusive de ses destinataires et sont confidentiels. Si vous recevez ce message par erreur, merci de le detruire et d'en avertir immediatement l'expediteur. Toute utilisation de ce message non conforme a sa destination, toute diffusion ou toute publication, totale ou partielle, est interdite, sauf autorisation expresse. L'internet ne permettant pas d'assurer l'integrite de ce message, BNP PARIBAS (et ses filiales) decline(nt) toute responsabilite au titre de ce message, dans l'hypothese ou il aurait ete modifie. Veuillez noter que certaines fonctions et certains services pour BNP PARIBAS peuvent etre fournis par BNP Paribas RCC, Inc.
