Hi Richard! Do you really think storing this information will have such a large impact on the database? Storing restore information shouldn't use more database space than storing backup information? If the accounting records are the only source to obtain this information, I'm out of luck, because I haven't accounting turned on at the moment... I'm asked for this information because suddenly we have 6 AIX nodes with a corrupt filespace and they aren't all running the same application. We like to rule out a TSM restore to be the cause... Kindest regards, Eric van Loon KLM Royal Dutch Airlines
-----Original Message----- From: Richard Sims [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 31, 2003 14:27 To: [EMAIL PROTECTED] Subject: Re: SQL statement >I'm looking for an SQL statement which returns all restores (nodes and >filenames) done by my clients. >I'm not much of an SQL wizard, so maybe someone is willing to help me or >give me a hint? Eric - I don't believe that such capability exists. Certainly, storing minutiae like that would be quite costly in terms of server space and overhead. You may be thinking toward the Restores table; but that was introduced in v3 as part of Restartable Restores, for an active restoral. I think the best you can do is glean restoral statistics from the accounting records. Detail restoral logs from the client systems might be preservable, if your organization so mandated as part of business integrity. Richard Sims, BU ********************************************************************** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. **********************************************************************
