I thought of something a little quicker and seems to be working...

-  separated nodes by windows/unix
-  on granted proxy access to my client for all the nodes
-  ran a loop to "dsmc q backup /usr/bin/sh -asnode=$i" assuming this
would not have been modified since it was backed up initially.  This seems
to be working.
-  will run something similar for windows as soon as I find a good file to
look for (something that is immune to service packs...)

-Shawn

________________________________________________
Shawn Drew
Data Protection Engineer
Core IT Production




Internet
[EMAIL PROTECTED]

Sent by: [email protected]
08/23/2007 03:40 PM
Please respond to
[email protected]


To
ADSM-L
cc

Subject
Re: [ADSM-L] First Backup day





Hi Shawn,

use this sql to find the oldest backup date -

select min(backup_date) from backups
where node_name = 'NODE' and filespace_name = '\\node\c$'

It will return just one line of output. The filespace criteria is
optional.
I use it because we have nodes with old filespaces like '\\node-nt\c$'.

Bill Colwell
Draper lab



> -----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: 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
>
> 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.

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.

Reply via email to