tsm6 point-in-time restore to DR server question
We are on learning curve of bringing up our first TSM v6 server (6.2.1). We have a instance up and running. It's a single TSM instance running on AIX. It uses file devices to a DataDomain (via NFS). The DD replicates the storage pool, db backups, and the recovery plan to a second site. I'm now trying to setup a dedicated AIX server at a remote site for DR. I'm trying to do a point-in-time restore. I've been able to get a restore to work and bring up the TSM instance - GOOD. BUT, something is not right. The activelog files seems to be in the wrong place. On the main system, DB2 put all the files, active logs, and archive logs in the filesystems I specified, but put them down under a NODE000 subdirectory structure. After the restore, the mirrorlog has it's copy of the active log under a NODE000 subdir, BUT, the main activelog is NOT under that sudir. main system activelogs are in /activelog/NODE000/files mirrorlogs are in /mirrorlog/NODE000/files DR system activelogs are in /activelog/files== mirrorlogs are in /mirrorlog/NODE000/files It appears to be working, but this doesn't seem right! Any thoughts would be a big help. Rick - The information contained in this message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately, and delete the original message.
Exchange Point-In-Time restore?
Hi, This is probably a Del question, but how can I do a Point-In-Time restore to a PST file? When I browse in the new TSM for Exchange 6.4 client, I can either only restore the latest version to a PST or do a Point-In-Time restore to a SMTP Server or the Original destination. Maybe I'm blind but if this are typed in the Information center, please send me a direct link to that page. Best Regards Christian Svensson Cell: +46-70-325 1577 E-mail: christian.svens...@cristie.semailto:christian.svens...@cristie.se Säkra återläsningar...
Re: Point in time restore problem
In my experience much of the time to restore when using tape is traversing the actual tape to get to the file(s) that TSM is to restore. You may want to think of colocation for your primary storage pool and copy pool. Restore time seems to be one of the trade offs vs. shorter backup time, fewer tape hardware resources needed, less ethernet bandwidth, etc. when one uses TSM.
Re: Point in time restore problem
On Tue, 29 May 2007 09:49:18 +1000, Paul Dudley [EMAIL PROTECTED] said: Well, I will give it a go, but this just confirms my belief that TSM is the most user-unfriendly, frustrating, annoying, unwieldy IT system I have encountered in 22 years of IT work. Perhaps the frustration is at least partially rooted in the requirements. These seem poorly aligned with the strengths of the product. - Allen S. Rout
AW: Point in time restore problem
Dear Paul, you beeing unhappy with the product may want to re-think either of usage of TSM at all at your site or the necessity of the MODE=ABSOLUTE backup. I do not know anybody who generaly does regulare absolute backups in TSM for reasons you mentioned. For me, I had performance problem when restoring desktop and \documents and settings\ data from PC-clients. In contrast toyour mailing it was not caused by traversing recovery log, but by search times on LTO tapes. I solved my problem by placing backups of data concerned on a TSM DISK-based storage pool. This was quite simple perfect solution for my scenarioproblem. As far as I understood your epxlanation you merely want to use absolute because you have been told that.. etc. etc. I strongly believe that an general and unevaluated beeing told that is neither a sound reason to express either positive or negative verdicts of anything, including but not restricted to TSM, nor a wise motivation to do something in a particular way. best regards Juraj Salak, Austria -Ursprüngliche Nachricht- Von: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Im Auftrag von Paul Dudley Gesendet: Dienstag, 29. Mai 2007 01:49 An: ADSM-L@VM.MARIST.EDU Betreff: Re: Point in time restore problem Well, I will give it a go, but this just confirms my belief that TSM is the most user-unfriendly, frustrating, annoying, unwieldy IT system I have encountered in 22 years of IT work. Regards Paul -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of William Boyer Sent: Sunday, 27 May 2007 1:08 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Point in time restore problem Instead of doing a SELECTIVE backup on a periodic basis, which won't update the last backup date/time of the filespace, use the MODE=ABSOLUTE of the backup copygroup. In your domain, make a copy of the active policy set and change all the management class backup copygroups to MODE=ABSOLUTE instead of the default of MODIFIED. Then on your occasional timeframe, run an admin schedule to activate this policy set, do your backups which are incremental and then the next day run another admin schedule to activate your MODE=MODIFIED policyset. This way your schedules don't change and as far as the client is concerned you just ran a unqualified INCREMENTAL backup and the filespaces are updated. Since the active policyset will have ABSOLUTS, you'll get a copy of every file whether it's changed or not. I've been doing TSM not for over 8-years and this is the first time I've ever thought of a way to use multiple policyset definitions in a domain. Bill Boyer Backup my harddrive? How do I put it in reverse? - ?? -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Paul Dudley Sent: Saturday, May 26, 2007 8:59 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Point in time restore problem From what I read the standard incremental backup is restricted in that it only backs up new or changed files since the last incremental backup. However I have been told that we need to run absolute incremental backups on a periodic basis - these incremental backups backup all files whether they have changed or not, so that the Last Incr Date is updated, so that Point in time restores don't have to traverse through a huge transaction log and spend long periods of time restoring files that were later deleted. I quote from the dsmc help option for incremental backups: Mode: Permits you to back up only files that changed since the last backup (modified). Also permits you to back up the files whether they changed or not (absolute). What I want to know is if you can run an absolute backup from the command line on the client server. The end result I want to achieve from all of this, is to run full backups on a periodic basis so that when I have to perform a Point in time restore it does it quickly and does not have to traverse a huge transaction log and restore files that were later deleted. Regards Paul ANL - CELEBRATING 50 YEARS ANL DISCLAIMER This e-mail and any file attached is confidential, and intended solely to the named addressees. Any unauthorised dissemination or use is strictly prohibited. If you received this e-mail in error, please immediately notify the sender by return e-mail from your system. Please do not copy, use or make reference to it for any purpose, or disclose its contents to any person. Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet
Re: Point in time restore problem
Well, I will give it a go, but this just confirms my belief that TSM is the most user-unfriendly, frustrating, annoying, unwieldy IT system I have encountered in 22 years of IT work. Regards Paul -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of William Boyer Sent: Sunday, 27 May 2007 1:08 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Point in time restore problem Instead of doing a SELECTIVE backup on a periodic basis, which won't update the last backup date/time of the filespace, use the MODE=ABSOLUTE of the backup copygroup. In your domain, make a copy of the active policy set and change all the management class backup copygroups to MODE=ABSOLUTE instead of the default of MODIFIED. Then on your occasional timeframe, run an admin schedule to activate this policy set, do your backups which are incremental and then the next day run another admin schedule to activate your MODE=MODIFIED policyset. This way your schedules don't change and as far as the client is concerned you just ran a unqualified INCREMENTAL backup and the filespaces are updated. Since the active policyset will have ABSOLUTS, you'll get a copy of every file whether it's changed or not. I've been doing TSM not for over 8-years and this is the first time I've ever thought of a way to use multiple policyset definitions in a domain. Bill Boyer Backup my harddrive? How do I put it in reverse? - ?? -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Paul Dudley Sent: Saturday, May 26, 2007 8:59 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Point in time restore problem From what I read the standard incremental backup is restricted in that it only backs up new or changed files since the last incremental backup. However I have been told that we need to run absolute incremental backups on a periodic basis - these incremental backups backup all files whether they have changed or not, so that the Last Incr Date is updated, so that Point in time restores don't have to traverse through a huge transaction log and spend long periods of time restoring files that were later deleted. I quote from the dsmc help option for incremental backups: Mode: Permits you to back up only files that changed since the last backup (modified). Also permits you to back up the files whether they changed or not (absolute). What I want to know is if you can run an absolute backup from the command line on the client server. The end result I want to achieve from all of this, is to run full backups on a periodic basis so that when I have to perform a Point in time restore it does it quickly and does not have to traverse a huge transaction log and restore files that were later deleted. Regards Paul ANL - CELEBRATING 50 YEARS ANL DISCLAIMER This e-mail and any file attached is confidential, and intended solely to the named addressees. Any unauthorised dissemination or use is strictly prohibited. If you received this e-mail in error, please immediately notify the sender by return e-mail from your system. Please do not copy, use or make reference to it for any purpose, or disclose its contents to any person.
Re: Point in time restore problem
OK - can I perform an absolute/unqualified incremental backup from the command line using the dsmc command? If so then how? I cannot see the correct option to use under dsmc incr. Regards Paul -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Richard Sims Sent: Friday, 25 May 2007 9:07 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Point in time restore problem On May 25, 2007, at 12:39 AM, Paul Dudley wrote: Does a selective backup count as an absolute/unqualified Incremental backup? No; the two are rather different animals in their intent and operation. The major manifestation of this is the Last Incr Date report from Query Filespace being updated only when an unqualified Incremental backup runs to completion. Richard Sims ANL - CELEBRATING 50 YEARS ANL DISCLAIMER This e-mail and any file attached is confidential, and intended solely to the named addressees. Any unauthorised dissemination or use is strictly prohibited. If you received this e-mail in error, please immediately notify the sender by return e-mail from your system. Please do not copy, use or make reference to it for any purpose, or disclose its contents to any person.
Re: Point in time restore problem
On May 26, 2007, at 9:34 AM, Paul Dudley wrote: OK - can I perform an absolute/unqualified incremental backup from the command line using the dsmc command? If so then how? I cannot see the correct option to use under dsmc incr. There is no option... That's the whole point - it's unqualified: you are in no way restricting the incremental backup, which proceeds on the basis of inventory comparison with prior backups. This is the most basic TSM backup, as described in the client manual: Full and partial incremental backup If you select entire file systems, you are performing a full incremental backup. If you select a directory tree or individual files, you are performing a partial incremental backup. Read through the Backing up your data section of the client manual. The TSM Concepts redbook also helps explain the differences. Richard Sims
Re: Point in time restore problem
From what I read the standard incremental backup is restricted in that it only backs up new or changed files since the last incremental backup. However I have been told that we need to run absolute incremental backups on a periodic basis - these incremental backups backup all files whether they have changed or not, so that the Last Incr Date is updated, so that Point in time restores don't have to traverse through a huge transaction log and spend long periods of time restoring files that were later deleted. I quote from the dsmc help option for incremental backups: Mode: Permits you to back up only files that changed since the last backup (modified). Also permits you to back up the files whether they changed or not (absolute). What I want to know is if you can run an absolute backup from the command line on the client server. The end result I want to achieve from all of this, is to run full backups on a periodic basis so that when I have to perform a Point in time restore it does it quickly and does not have to traverse a huge transaction log and restore files that were later deleted. Regards Paul -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Richard Sims Sent: Saturday, 26 May 2007 11:57 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Point in time restore problem On May 26, 2007, at 9:34 AM, Paul Dudley wrote: OK - can I perform an absolute/unqualified incremental backup from the command line using the dsmc command? If so then how? I cannot see the correct option to use under dsmc incr. There is no option... That's the whole point - it's unqualified: you are in no way restricting the incremental backup, which proceeds on the basis of inventory comparison with prior backups. This is the most basic TSM backup, as described in the client manual: Full and partial incremental backup If you select entire file systems, you are performing a full incremental backup. If you select a directory tree or individual files, you are performing a partial incremental backup. Read through the Backing up your data section of the client manual. The TSM Concepts redbook also helps explain the differences. Richard Sims ANL - CELEBRATING 50 YEARS ANL DISCLAIMER This e-mail and any file attached is confidential, and intended solely to the named addressees. Any unauthorised dissemination or use is strictly prohibited. If you received this e-mail in error, please immediately notify the sender by return e-mail from your system. Please do not copy, use or make reference to it for any purpose, or disclose its contents to any person.
Re: Point in time restore problem
Instead of doing a SELECTIVE backup on a periodic basis, which won't update the last backup date/time of the filespace, use the MODE=ABSOLUTE of the backup copygroup. In your domain, make a copy of the active policy set and change all the management class backup copygroups to MODE=ABSOLUTE instead of the default of MODIFIED. Then on your occasional timeframe, run an admin schedule to activate this policy set, do your backups which are incremental and then the next day run another admin schedule to activate your MODE=MODIFIED policyset. This way your schedules don't change and as far as the client is concerned you just ran a unqualified INCREMENTAL backup and the filespaces are updated. Since the active policyset will have ABSOLUTS, you'll get a copy of every file whether it's changed or not. I've been doing TSM not for over 8-years and this is the first time I've ever thought of a way to use multiple policyset definitions in a domain. Bill Boyer Backup my harddrive? How do I put it in reverse? - ?? -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Paul Dudley Sent: Saturday, May 26, 2007 8:59 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Point in time restore problem From what I read the standard incremental backup is restricted in that it only backs up new or changed files since the last incremental backup. However I have been told that we need to run absolute incremental backups on a periodic basis - these incremental backups backup all files whether they have changed or not, so that the Last Incr Date is updated, so that Point in time restores don't have to traverse through a huge transaction log and spend long periods of time restoring files that were later deleted. I quote from the dsmc help option for incremental backups: Mode: Permits you to back up only files that changed since the last backup (modified). Also permits you to back up the files whether they changed or not (absolute). What I want to know is if you can run an absolute backup from the command line on the client server. The end result I want to achieve from all of this, is to run full backups on a periodic basis so that when I have to perform a Point in time restore it does it quickly and does not have to traverse a huge transaction log and restore files that were later deleted. Regards Paul -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Richard Sims Sent: Saturday, 26 May 2007 11:57 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Point in time restore problem On May 26, 2007, at 9:34 AM, Paul Dudley wrote: OK - can I perform an absolute/unqualified incremental backup from the command line using the dsmc command? If so then how? I cannot see the correct option to use under dsmc incr. There is no option... That's the whole point - it's unqualified: you are in no way restricting the incremental backup, which proceeds on the basis of inventory comparison with prior backups. This is the most basic TSM backup, as described in the client manual: Full and partial incremental backup If you select entire file systems, you are performing a full incremental backup. If you select a directory tree or individual files, you are performing a partial incremental backup. Read through the Backing up your data section of the client manual. The TSM Concepts redbook also helps explain the differences. Richard Sims ANL - CELEBRATING 50 YEARS ANL DISCLAIMER This e-mail and any file attached is confidential, and intended solely to the named addressees. Any unauthorised dissemination or use is strictly prohibited. If you received this e-mail in error, please immediately notify the sender by return e-mail from your system. Please do not copy, use or make reference to it for any purpose, or disclose its contents to any person.
Re: Point in time restore problem
On May 25, 2007, at 12:39 AM, Paul Dudley wrote: Does a selective backup count as an absolute/unqualified Incremental backup? No; the two are rather different animals in their intent and operation. The major manifestation of this is the Last Incr Date report from Query Filespace being updated only when an unqualified Incremental backup runs to completion. Richard Sims
Re: Point in time restore problem
Does a selective backup count as an absolute/unqualified Incremental backup? Regards Paul -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Richard Sims Sent: Wednesday, 23 May 2007 11:22 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Point in time restore problem On May 22, 2007, at 10:24 PM, Paul Dudley wrote: We perform incremental backups each night and occasional archive backups on our mail server (which is linux OS) I am currently performing a point in time restore via the GUI for an account on that mail server. The point in time is last Friday morning. However the restore seems to be restoring everything that was ever backed up in that account. At the time the account was 500 Mb in size - I am restoring this account to another location on the server and so far it has restored 1.8 Gb of data. Why is this happening? Why is it restoring files that were deleted or moved months ago? Paul - That manifestation is documented in the Admin Guide, under How IBM Tivoli Storage Manager Selects Files for Policy Operations: Incremental Backup, where that can happen if an unqualified Incremental backup is not done often enough for a file system. Point-in-time restorals can be interesting. Richard Sims ANL - CELEBRATING 50 YEARS ANL DISCLAIMER This e-mail and any file attached is confidential, and intended solely to the named addressees. Any unauthorised dissemination or use is strictly prohibited. If you received this e-mail in error, please immediately notify the sender by return e-mail from your system. Please do not copy, use or make reference to it for any purpose, or disclose its contents to any person.
Re: Point in time restore problem
Paul, you'd see this behaviour when restoring using the -todate-option instead of -pitdate. If the GUI doesn't bring the desired results, also try the CL-client. Good luck, best regards, Michael Am 23.05.2007 um 04:24 schrieb Paul Dudley: We perform incremental backups each night and occasional archive backups on our mail server (which is linux OS) I am currently performing a point in time restore via the GUI for an account on that mail server. The point in time is last Friday morning. However the restore seems to be restoring everything that was ever backed up in that account. -- Dipl.-Inform. (FH) Michael H. Bartl Mail: [EMAIL PROTECTED] SpaceNet AG, Technik Tel: 089 / 32356-151 Joseph-Dollinger-Bogen 14 Fax: 089 / 32356-299 D-80807 Muenchen http://www.space.net/ Vorstand: Sebastian v. Bomhard Aufsichtsratsvorsitzender: Alexander Grundner-Culemann Firmensitz: München, HRB: 136055 (Amtsgericht München) USt-IdNr.: DE813185279 Genug von Viren und Spam? SpaceNet_Mail hilft Ihnen - lesen Sie, wie SpaceNet_Mail beim Muenchner Verkehrs- und Tarifverbund erfolgreich eingesetzt wird: http://www.space.net/mvvnews/index.html Was wir sonst noch fuer Sie tun koennen, finden Sie unter: http://www.space.net/
Re: Point in time restore problem
On May 22, 2007, at 10:24 PM, Paul Dudley wrote: We perform incremental backups each night and occasional archive backups on our mail server (which is linux OS) I am currently performing a point in time restore via the GUI for an account on that mail server. The point in time is last Friday morning. However the restore seems to be restoring everything that was ever backed up in that account. At the time the account was 500 Mb in size - I am restoring this account to another location on the server and so far it has restored 1.8 Gb of data. Why is this happening? Why is it restoring files that were deleted or moved months ago? Paul - That manifestation is documented in the Admin Guide, under How IBM Tivoli Storage Manager Selects Files for Policy Operations: Incremental Backup, where that can happen if an unqualified Incremental backup is not done often enough for a file system. Point-in-time restorals can be interesting. Richard Sims
Point in time restore problem
We perform incremental backups each night and occasional archive backups on our mail server (which is linux OS) I am currently performing a point in time restore via the GUI for an account on that mail server. The point in time is last Friday morning. However the restore seems to be restoring everything that was ever backed up in that account. At the time the account was 500 Mb in size - I am restoring this account to another location on the server and so far it has restored 1.8 Gb of data. Why is this happening? Why is it restoring files that were deleted or moved months ago? Paul Dudley ANL IT Operations Dept. ANL Container Line [EMAIL PROTECTED] ANL - CELEBRATING 50 YEARS ANL DISCLAIMER This e-mail and any file attached is confidential, and intended solely to the named addressees. Any unauthorised dissemination or use is strictly prohibited. If you received this e-mail in error, please immediately notify the sender by return e-mail from your system. Please do not copy, use or make reference to it for any purpose, or disclose its contents to any person.
Point-in-time restore Notes database
Hello, I've got the following setup: TSM server 5.3.2.0 on Windows 2003 Lotus Notes 6.5.2 fixpack 2 running on Windows NT with TSM BA client 5.1.7.3 and TDP Notes 5.1.5.1 The backup scheme for the Notes server is: selective backup on friday evening incremental backup from monday evening till thursday evening archive log backup every 4 hours if the treshold is greater than 80% archive log backup at 04:00 AM without any treshold. I've restore a Notes database from the selective backup without activating it. I know that a mail was sent to the Notes database on 11/22 at 14:46. And as a transaction log backup ran at 11/23 at 04:00h, an entry for this mail must be found in the transaction logs. I start then the point-in-time restore from the CLI with following command: domdsmc activatedbs /applylogs=11/23/2005,06:00:00 The activatedbs ends with the following messages: 11/28/2005 01:45:24 PM Recovery Manager: Media Recovery complete for D:\Notes\Data\mail\testdb.nsf.dad, last update applied 11/22/2005 02:02:06 AM. How does it come that the last applied update is that old when you know that updates occured during the day and that an entry must be found in the transaction logs for it. The mail is of course not found. If I recover a bit further in time, the mail will be found in the Notes database. But you have to gamble for the exact date and time untill when the activatedbs must occur. Or is there a bug in the PIT restore? Or am I missing something? best regards, Kurt
Point in Time Restore Issue
I have a case where point in time restore is not working as I would expect. Here's the sequence: Day 1: Create file A, incremental backup. File A has active version, none inactive. Day 2: Delete file A, incremental backup. File A has no active version, 1 inactive. Day 3: Create a new file named A, incremental backup. File A has active version, 1 inactive. On day 4, do a PiT restore to the point after the backup on Day 2. File A is in the list with an inactive mark. It should not be in the list at all, since it was non-existent at the time of the backup. How do I get a restore list that contains just the files that existed at the time of the backup on Day 2? Bill Mansfield Logicalis
Re: Point in Time Restore Issue
Hmmm... I'm not sure there is a way to do what you are asking, outside of rolling back your TSM server database to Day 2 (which I would NOT recommend). While TSM, of course, recognizes that the file no longer exists at the time the backup on day 2 was made, it doesn't maintain a history of that information. The file was recreated and backed up on day 3, so now TSM has an active and inactive version of the file. But at this time, TSM has no knowledge of *why* the inactive file is inactive, so it doesn't distinguish between the scenarios where the file was simply changed and backed up again, versus where the file was deleted, expired by the next incremental, recreated, then backed up again. I suppose that, depending on how critical this is for you, you could dump the contents of the BACKUPS table to a file; then massage the data, looking for the active version and the most recent inactive version, and compare the former's BACKUP_DATE against the latter's DEACTIVATE_DATE. In the situation where the file simply changed and thus was backed up again, I would imagine the two dates would be identical, or at least within a few seconds of each other, while in your particular scenario, you'd see (about) a day's difference between the two dates. Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] IBM Tivoli Storage Manager support web page: http://www-306.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html The only dumb question is the one that goes unasked. The command line is your friend. Good enough is the enemy of excellence. Bill Mansfield [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 2005-11-01 12:03 Please respond to ADSM: Dist Stor Manager To ADSM-L@VM.MARIST.EDU cc Subject Point in Time Restore Issue I have a case where point in time restore is not working as I would expect. Here's the sequence: Day 1: Create file A, incremental backup. File A has active version, none inactive. Day 2: Delete file A, incremental backup. File A has no active version, 1 inactive. Day 3: Create a new file named A, incremental backup. File A has active version, 1 inactive. On day 4, do a PiT restore to the point after the backup on Day 2. File A is in the list with an inactive mark. It should not be in the list at all, since it was non-existent at the time of the backup. How do I get a restore list that contains just the files that existed at the time of the backup on Day 2? Bill Mansfield Logicalis
TSM Point in Time Restore Question
I will attemp to describe the background and my problem, it's my first time posting though so if some of the terminology is a bit off, I apoligize. I'm trying to restore files originally backed up to a netware server. Restoring back to a netware server using 4.5.3 of the tsm agent for netware. I've setup the java web agent so I can administer restores from a GUI. I want to a Point in Time restore from two years ago. I select the time and date and I notice that all of the files are actually from about 4 years ago. Those aren't the files that I want. So I turned off Point in Time and just selected to view all active/inactive files. I noticed that for one example of the file, there are about 24 instances of the file that were backedup between the date I selected for Point in Time and the date of backup actually displayed by the web GUI. There's actually tons of these files that going through and selecting each of them using the active/inactive view isn't practical. Any thoughts or ideas? I'm going to try doing the restore from a command line using /pitr and see if I get the same results, but I want to ask of y'all if either there's a bug, or I'm doing something wrong, or what, because this behavior just doesn't seem right. Of another note, I'm not sure how it picked thw 4 years back date for the files, as those weren't even the first backup dates for those files. There were another 5 dates of backups prior to the date that appeared in the GUI for the backup date displayed using the Point in Time. Thank you for your help.
Point in time restore problem
Point in time restore over the GUI shows not up all folder, subfolder and data i can see without chosing point in time. Testing the point in time on the commandline says 'ANS1302E No objects on server match query'. the restore of the data works fine without point in time. The problem was detected on TSM Client 5.2.0.6 for MS Windows 2000 and is also present in my testenvironment with Windows 2003 and Client 5.2.2.10. The managmentclass setup is proper, the dirmc is exact like the data in retention and versioning. Have i missed something educational? Thanks in advance regards joachim Joachim Paul Schaub Abraxas Informatik AG Beckenhofstrasse 23 CH-8090 Zürich Schweiz / Switzerland Telefon: +41 (043) 259 34 41 Telefax: +41 (043) 259 42 82 E-Mail: mailto:[EMAIL PROTECTED] Internet: http://www.abraxas.ch Abraxas - Das Immer-besser-Prinzip http://www.abraxas.ch/DasImmerBesserPrinzip ~~~
Re: Point in time restore problem
Your DIRMC retention should probably be NOLIMIT for the versions and the same retain extra as the longest management class retention. There isn't a version of the directory for the PIT you specified. Bill Boyer DSS, Inc. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Schaub Joachim Paul ABX-SECE-ZH Sent: Wednesday, August 25, 2004 9:47 AM To: [EMAIL PROTECTED] Subject: Point in time restore problem Point in time restore over the GUI shows not up all folder, subfolder and data i can see without chosing point in time. Testing the point in time on the commandline says 'ANS1302E No objects on server match query'. the restore of the data works fine without point in time. The problem was detected on TSM Client 5.2.0.6 for MS Windows 2000 and is also present in my testenvironment with Windows 2003 and Client 5.2.2.10. The managmentclass setup is proper, the dirmc is exact like the data in retention and versioning. Have i missed something educational? Thanks in advance regards joachim Joachim Paul Schaub Abraxas Informatik AG Beckenhofstrasse 23 CH-8090 Z|rich Schweiz / Switzerland Telefon: +41 (043) 259 34 41 Telefax: +41 (043) 259 42 82 E-Mail: mailto:[EMAIL PROTECTED] Internet: http://www.abraxas.ch Abraxas - Das Immer-besser-Prinzip http://www.abraxas.ch/DasImmerBesserPrinzip ~~~
Re: Point in time restore problem
There is a known problem with the way the gui works, versions and pit. The gui first searches the directory tree from the top down. The files exist at a pit but he directory version no longer exists, it can't display that branch of the tree. [EMAIL PROTECTED] 08/25/04 10:02AM Your DIRMC retention should probably be NOLIMIT for the versions and the same retain extra as the longest management class retention. There isn't a version of the directory for the PIT you specified. Bill Boyer DSS, Inc. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Schaub Joachim Paul ABX-SECE-ZH Sent: Wednesday, August 25, 2004 9:47 AM To: [EMAIL PROTECTED] Subject: Point in time restore problem Point in time restore over the GUI shows not up all folder, subfolder and data i can see without chosing point in time. Testing the point in time on the commandline says 'ANS1302E No objects on server match query'. the restore of the data works fine without point in time. The problem was detected on TSM Client 5.2.0.6 for MS Windows 2000 and is also present in my testenvironment with Windows 2003 and Client 5.2.2.10. The managmentclass setup is proper, the dirmc is exact like the data in retention and versioning. Have i missed something educational? Thanks in advance regards joachim Joachim Paul Schaub Abraxas Informatik AG Beckenhofstrasse 23 CH-8090 Z|rich Schweiz / Switzerland Telefon: +41 (043) 259 34 41 Telefax: +41 (043) 259 42 82 E-Mail: mailto:[EMAIL PROTECTED] Internet: http://www.abraxas.ch Abraxas - Das Immer-besser-Prinzip http://www.abraxas.ch/DasImmerBesserPrinzip ~~~
AW: Point in time restore problem
Thank you Bill, Aaron and Richard for your help I can see the light... Regards Joachim -Ursprüngliche Nachricht- Von: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Auftrag von Aaron Durkee Gesendet: Mittwoch, 25. August 2004 16:58 An: [EMAIL PROTECTED] Betreff: Re: Point in time restore problem There is a known problem with the way the gui works, versions and pit. The gui first searches the directory tree from the top down. The files exist at a pit but he directory version no longer exists, it can't display that branch of the tree. [EMAIL PROTECTED] 08/25/04 10:02AM Your DIRMC retention should probably be NOLIMIT for the versions and the same retain extra as the longest management class retention. There isn't a version of the directory for the PIT you specified. Bill Boyer DSS, Inc. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Schaub Joachim Paul ABX-SECE-ZH Sent: Wednesday, August 25, 2004 9:47 AM To: [EMAIL PROTECTED] Subject: Point in time restore problem Point in time restore over the GUI shows not up all folder, subfolder and data i can see without chosing point in time. Testing the point in time on the commandline says 'ANS1302E No objects on server match query'. the restore of the data works fine without point in time. The problem was detected on TSM Client 5.2.0.6 for MS Windows 2000 and is also present in my testenvironment with Windows 2003 and Client 5.2.2.10. The managmentclass setup is proper, the dirmc is exact like the data in retention and versioning. Have i missed something educational? Thanks in advance regards joachim Joachim Paul Schaub Abraxas Informatik AG Beckenhofstrasse 23 CH-8090 Z|rich Schweiz / Switzerland Telefon: +41 (043) 259 34 41 Telefax: +41 (043) 259 42 82 E-Mail: mailto:[EMAIL PROTECTED] Internet: http://www.abraxas.ch Abraxas - Das Immer-besser-Prinzip http://www.abraxas.ch/DasImmerBesserPrinzip ~~~
Re: point in time restore
Morning Geoff, -pitdate= -pittime=should be the two options to get you where you want to be. The only thing I can think of that would result in more allocated space being restored than the file system can handle would be if there was a lot of HSM migrated data from the file system and TSM is bringing back the actual files rather then just the stub file. Oh, well, one other thing maybe... that generally is against the rules of tsm say you have a file system /folks and under that you have directories /folks/bob /folks/dick /folks/jane and Susan wants in but has excessive files so she gets her own file system mounted at /folks/susan ~maybe~ it the user is trying to restore the files for filesystem /folks/susan (which isn't actually, currently mounted) so the files are going into the directory /folks/susan which is under the filesystem /folks just a thought... Dwight Gill, Geoffrey L. To: [EMAIL PROTECTED] GEOFFREY.L.GILL@cc: SAIC.COMSubject: point in time restore Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] .EDU 12/03/2003 10:06 PM Please respond to ADSM: Dist Stor Manager Hello all, I can't answer this question because I have never had to use a point in time restore function. It seems as though over the weekend a SAN controller upgrade has led to whole file systems lost and parts of others on a node. The person responsible wants to restore only those files that were on the system as of November 29th and not have it write over any existing files. The admin seems to think that because TSM is restoring more files than the file system can hold it is restoring more than it is supposed to. Can anyone lend a hand in describing if a point in time would do this and if so why? If the admin is doing this correctly why would the mount not have enough space if in fact he made it as large as it was previously? Thanks, Geoff Gill TSM Administrator NT Systems Support Engineer SAIC E-Mail: [EMAIL PROTECTED] Phone: (858) 826-4062 Pager: (877) 905-7154
point in time restore
Hello all, I can't answer this question because I have never had to use a point in time restore function. It seems as though over the weekend a SAN controller upgrade has led to whole file systems lost and parts of others on a node. The person responsible wants to restore only those files that were on the system as of November 29th and not have it write over any existing files. The admin seems to think that because TSM is restoring more files than the file system can hold it is restoring more than it is supposed to. Can anyone lend a hand in describing if a point in time would do this and if so why? If the admin is doing this correctly why would the mount not have enough space if in fact he made it as large as it was previously? Thanks, Geoff Gill TSM Administrator NT Systems Support Engineer SAIC E-Mail: [EMAIL PROTECTED] Phone: (858) 826-4062 Pager: (877) 905-7154
Re: Point in time restore vs Archiving
Hello Arnaud, *SM will treat the backup as 'full' for 35 days. If you change copymode from modified to absolute wont make a difference. But the amount of backup data will increase with absolute.. If I´m wrong, please correct me. //Henrik PAC Brion Arnaud [EMAIL PROTECTED]To: [EMAIL PROTECTED] LPINA.COMcc: (bcc: Henrik Wahlstedt) Sent by: ADSM: Subject: Re: Point in time restore vs Archiving Dist Stor Manager [EMAIL PROTECTED] EDU 2003-10-08 16:49 Please respond to ADSM: Dist Stor Manager Hi Henrik, If you want to have something equivalent to a full backup, shouldn't you use copymode absolute ? Else, only modified files would be backuped ... My 2 cents. Arnaud =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= | Arnaud Brion, Panalpina Management Ltd., IT Group | | Viaduktstrasse 42, P.O. Box, 4002 Basel - Switzerland | | Phone: +41 61 226 19 78 / Fax: +41 61 226 17 01 | =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Henrik Wahlstedt Sent: Wednesday, 08 October, 2003 13:20 To: [EMAIL PROTECTED] Subject: Re: Point in time restore vs Archiving Or, VERE nolimit VERD nolimit RETE 31 or 35 RETO 31 or 35 FREQ 0 //Henrik Karel Bos [EMAIL PROTECTED]To: [EMAIL PROTECTED] ON.COM cc: (bcc: Henrik Wahlstedt) Sent by: Subject: Re: Point in time restore vs Archiving ADSM: Dist Stor Manager [EMAIL PROTECTED] RIST.EDU 2003-10-08 13:07 Please respond to ADSM: Dist Stor Manager Hi, Something like: Versions Data 28 Exists Versions Data 28 Deleted Retain Extra28 Versions Retain Only Version 28 Copy Frequency 1 should work fine. Regard, Karel -Oorspronkelijk bericht- Van: Henrik Hansson [mailto:[EMAIL PROTECTED] Verzonden: woensdag 8 oktober 2003 13:02 Aan: [EMAIL PROTECTED] Onderwerp: Point in time restore vs Archiving I have a question regarding an issue regarding Archiving. Lets say I have a policy that says that I need to do FULL backups days a week for 4 weeks. Ofcourse I can do archive each day but then I think I don't use the functunallety in TSM. Is there a way of doing incremental backups that covers 4 weeks back in time? I have the following settings in my TSM for a backup group Backup Copy Groups : STANDARD ACTIVE STANDARD STANDARD Policy Domain Name STANDARD Policy Set Name ACTIVE Mgmt Class Name STANDARD Copy Group Name STANDARD Versions Data 5 Exists Versions Data 1 Deleted Retain Extra30 Versions Retain Only Version 60 Copy Mode MODIFIED Copy Serialization SHRSTATIC Copy Frequency 0 Copy DestinationBACKUPPOOL Do You
Re: Point in time restore vs Archiving
Henrik, You are correct . Point in time restore will enable recovery to the same state as if you had taken a full backup on that particular day. This is the way TSM was designed to work. Using absolute mode would have significant impact both on your media use and the size of your database. John Henrik Wahlstedt [EMAIL PROTECTED]@vm.marist.edu on 10/09/2003 08:22:42 AM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] Sent by:ADSM: Dist Stor Manager [EMAIL PROTECTED] To:[EMAIL PROTECTED] cc: Subject:Re: Point in time restore vs Archiving Hello Arnaud, *SM will treat the backup as 'full' for 35 days. If you change copymode from modified to absolute wont make a difference. But the amount of backup data will increase with absolute.. If I´m wrong, please correct me. //Henrik PAC Brion Arnaud [EMAIL PROTECTED]To: [EMAIL PROTECTED] LPINA.COMcc: (bcc: Henrik Wahlstedt) Sent by: ADSM: Subject: Re: Point in time restore vs Archiving Dist Stor Manager [EMAIL PROTECTED] EDU 2003-10-08 16:49 Please respond to ADSM: Dist Stor Manager Hi Henrik, If you want to have something equivalent to a full backup, shouldn't you use copymode absolute ? Else, only modified files would be backuped ... My 2 cents. Arnaud =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= | Arnaud Brion, Panalpina Management Ltd., IT Group | | Viaduktstrasse 42, P.O. Box, 4002 Basel - Switzerland | | Phone: +41 61 226 19 78 / Fax: +41 61 226 17 01 | =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Henrik Wahlstedt Sent: Wednesday, 08 October, 2003 13:20 To: [EMAIL PROTECTED] Subject: Re: Point in time restore vs Archiving Or, VERE nolimit VERD nolimit RETE 31 or 35 RETO 31 or 35 FREQ 0 //Henrik Karel Bos [EMAIL PROTECTED]To: [EMAIL PROTECTED] ON.COM cc: (bcc: Henrik Wahlstedt) Sent by: Subject: Re: Point in time restore vs Archiving ADSM: Dist Stor Manager [EMAIL PROTECTED] RIST.EDU 2003-10-08 13:07 Please respond to ADSM: Dist Stor Manager Hi, Something like: Versions Data 28 Exists Versions Data 28 Deleted Retain Extra28 Versions Retain Only Version 28 Copy Frequency 1 should work fine. Regard, Karel -Oorspronkelijk bericht- Van: Henrik Hansson [mailto:[EMAIL PROTECTED] Verzonden: woensdag 8 oktober 2003 13:02 Aan: [EMAIL PROTECTED] Onderwerp: Point in time restore vs Archiving I have a question regarding an issue regarding Archiving. Lets say I have a policy that says that I need to do FULL backups days a week for 4 weeks. Ofcourse I can do archive each day but then I think I don't use the functunallety in TSM. Is there a way of doing incremental backups that covers 4 weeks back in time? I have the following settings in my TSM for a backup group Backup Copy Groups : STANDARD ACTIVE STANDARD STANDARD Policy Domain Name STANDARD Policy Set Name ACTIVE Mgmt Class Name STANDARD Copy Group Name STANDARD Versions Data 5 Exists Versions Data 1 Deleted Retain Extra30 Versions Retain Only Version 60 Copy Mode MODIFIED Copy Serialization SHRSTATIC Copy Frequency 0 Copy DestinationBACKUPPOOL Do You think this would meet the 4 weeks restore policy. Thanx Med Vänlig Hälsning/ Best Regards _ Henrik Hansson --- The information contained in this message may be CONFIDENTIAL and is intended for the addressee only. Any unauthorised use, dissemination of the information or copying of this message is prohibited. If you are not the addressee, please notify the sender immediately by return e-mail and delete this message. Thank you. --- The information contained in this message may be CONFIDENTIAL and is intended for the addressee only. Any unauthorised use, dissemination of the information or copying of this message is prohibited. If you are not the addressee, please notify the sender immediately by return e-mail and delete this message. Thank you
Re: Point in time restore vs Archiving
Henrik, You're absolutely right, from a TSM perspective you'll have a virtual full backup, but my understanding of Mr Hansson question was that he really wanted to perform full backups everyday : I need to do FULL backups days a week for 4 weeks Probably an misinterpretation from my side ;-) Anyway he will choose ! Regards. Arnaud =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= | Arnaud Brion, Panalpina Management Ltd., IT Group | | Viaduktstrasse 42, P.O. Box, 4002 Basel - Switzerland | | Phone: +41 61 226 19 78 / Fax: +41 61 226 17 01 | =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Henrik Wahlstedt Sent: Thursday, 09 October, 2003 9:23 To: [EMAIL PROTECTED] Subject: Re: Point in time restore vs Archiving Hello Arnaud, *SM will treat the backup as 'full' for 35 days. If you change copymode from modified to absolute wont make a difference. But the amount of backup data will increase with absolute.. If I´m wrong, please correct me. //Henrik PAC Brion Arnaud [EMAIL PROTECTED]To: [EMAIL PROTECTED] LPINA.COMcc: (bcc: Henrik Wahlstedt) Sent by: ADSM: Subject: Re: Point in time restore vs Archiving Dist Stor Manager [EMAIL PROTECTED] EDU 2003-10-08 16:49 Please respond to ADSM: Dist Stor Manager Hi Henrik, If you want to have something equivalent to a full backup, shouldn't you use copymode absolute ? Else, only modified files would be backuped ... My 2 cents. Arnaud =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= | Arnaud Brion, Panalpina Management Ltd., IT Group | | Viaduktstrasse 42, P.O. Box, 4002 Basel - Switzerland | | Phone: +41 61 226 19 78 / Fax: +41 61 226 17 01 | =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Henrik Wahlstedt Sent: Wednesday, 08 October, 2003 13:20 To: [EMAIL PROTECTED] Subject: Re: Point in time restore vs Archiving Or, VERE nolimit VERD nolimit RETE 31 or 35 RETO 31 or 35 FREQ 0 //Henrik Karel Bos [EMAIL PROTECTED]To: [EMAIL PROTECTED] ON.COM cc: (bcc: Henrik Wahlstedt) Sent by: Subject: Re: Point in time restore vs Archiving ADSM: Dist Stor Manager [EMAIL PROTECTED] RIST.EDU 2003-10-08 13:07 Please respond to ADSM: Dist Stor Manager Hi, Something like: Versions Data 28 Exists Versions Data 28 Deleted Retain Extra28 Versions Retain Only Version 28 Copy Frequency 1 should work fine. Regard, Karel -Oorspronkelijk bericht- Van: Henrik Hansson [mailto:[EMAIL PROTECTED] Verzonden: woensdag 8 oktober 2003 13:02 Aan: [EMAIL PROTECTED] Onderwerp
Point in time restore vs Archiving
I have a question regarding an issue regarding Archiving. Lets say I have a policy that says that I need to do FULL backups days a week for 4 weeks. Ofcourse I can do archive each day but then I think I don't use the functunallety in TSM. Is there a way of doing incremental backups that covers 4 weeks back in time? I have the following settings in my TSM for a backup group Backup Copy Groups : STANDARD ACTIVE STANDARD STANDARD Policy Domain Name STANDARD Policy Set Name ACTIVE Mgmt Class Name STANDARD Copy Group Name STANDARD Versions Data 5 Exists Versions Data 1 Deleted Retain Extra30 Versions Retain Only Version 60 Copy Mode MODIFIED Copy Serialization SHRSTATIC Copy Frequency 0 Copy DestinationBACKUPPOOL Do You think this would meet the 4 weeks restore policy. Thanx Med Vänlig Hälsning/ Best Regards _ Henrik Hansson
Re: Point in time restore vs Archiving
Hi, Something like: Versions Data 28 Exists Versions Data 28 Deleted Retain Extra28 Versions Retain Only Version 28 Copy Frequency 1 should work fine. Regard, Karel -Oorspronkelijk bericht- Van: Henrik Hansson [mailto:[EMAIL PROTECTED] Verzonden: woensdag 8 oktober 2003 13:02 Aan: [EMAIL PROTECTED] Onderwerp: Point in time restore vs Archiving I have a question regarding an issue regarding Archiving. Lets say I have a policy that says that I need to do FULL backups days a week for 4 weeks. Ofcourse I can do archive each day but then I think I don't use the functunallety in TSM. Is there a way of doing incremental backups that covers 4 weeks back in time? I have the following settings in my TSM for a backup group Backup Copy Groups : STANDARD ACTIVE STANDARD STANDARD Policy Domain Name STANDARD Policy Set Name ACTIVE Mgmt Class Name STANDARD Copy Group Name STANDARD Versions Data 5 Exists Versions Data 1 Deleted Retain Extra30 Versions Retain Only Version 60 Copy Mode MODIFIED Copy Serialization SHRSTATIC Copy Frequency 0 Copy DestinationBACKUPPOOL Do You think this would meet the 4 weeks restore policy. Thanx Med Vänlig Hälsning/ Best Regards _ Henrik Hansson
Re: Point in time restore vs Archiving
Or, VERE nolimit VERD nolimit RETE 31 or 35 RETO 31 or 35 FREQ 0 //Henrik Karel Bos [EMAIL PROTECTED]To: [EMAIL PROTECTED] ON.COM cc: (bcc: Henrik Wahlstedt) Sent by: Subject: Re: Point in time restore vs Archiving ADSM: Dist Stor Manager [EMAIL PROTECTED] RIST.EDU 2003-10-08 13:07 Please respond to ADSM: Dist Stor Manager Hi, Something like: Versions Data 28 Exists Versions Data 28 Deleted Retain Extra28 Versions Retain Only Version 28 Copy Frequency 1 should work fine. Regard, Karel -Oorspronkelijk bericht- Van: Henrik Hansson [mailto:[EMAIL PROTECTED] Verzonden: woensdag 8 oktober 2003 13:02 Aan: [EMAIL PROTECTED] Onderwerp: Point in time restore vs Archiving I have a question regarding an issue regarding Archiving. Lets say I have a policy that says that I need to do FULL backups days a week for 4 weeks. Ofcourse I can do archive each day but then I think I don't use the functunallety in TSM. Is there a way of doing incremental backups that covers 4 weeks back in time? I have the following settings in my TSM for a backup group Backup Copy Groups : STANDARD ACTIVE STANDARD STANDARD Policy Domain Name STANDARD Policy Set Name ACTIVE Mgmt Class Name STANDARD Copy Group Name STANDARD Versions Data 5 Exists Versions Data 1 Deleted Retain Extra30 Versions Retain Only Version 60 Copy Mode MODIFIED Copy Serialization SHRSTATIC Copy Frequency 0 Copy DestinationBACKUPPOOL Do You think this would meet the 4 weeks restore policy. Thanx Med Vänlig Hälsning/ Best Regards _ Henrik Hansson --- The information contained in this message may be CONFIDENTIAL and is intended for the addressee only. Any unauthorised use, dissemination of the information or copying of this message is prohibited. If you are not the addressee, please notify the sender immediately by return e-mail and delete this message. Thank you.
Re: Point in time restore vs Archiving
But this doesn't cover you if you do a special backup in addition to the normal incremental. Then you now have 29 versions instead of 28, and there goes your 4-week recoverability. If I have a client that has a point-in-time recoverability requirement, I always set the VEREXIST and VERDELETE to NOLIMIT. That way I don't care how often they backup their data...they're covered. Bill Boyer DSS, Inc. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Karel Bos Sent: Wednesday, October 08, 2003 7:08 AM To: [EMAIL PROTECTED] Subject: Re: Point in time restore vs Archiving Hi, Something like: Versions Data 28 Exists Versions Data 28 Deleted Retain Extra28 Versions Retain Only Version 28 Copy Frequency 1 should work fine. Regard, Karel -Oorspronkelijk bericht- Van: Henrik Hansson [mailto:[EMAIL PROTECTED] Verzonden: woensdag 8 oktober 2003 13:02 Aan: [EMAIL PROTECTED] Onderwerp: Point in time restore vs Archiving I have a question regarding an issue regarding Archiving. Lets say I have a policy that says that I need to do FULL backups days a week for 4 weeks. Ofcourse I can do archive each day but then I think I don't use the functunallety in TSM. Is there a way of doing incremental backups that covers 4 weeks back in time? I have the following settings in my TSM for a backup group Backup Copy Groups : STANDARD ACTIVE STANDARD STANDARD Policy Domain Name STANDARD Policy Set Name ACTIVE Mgmt Class Name STANDARD Copy Group Name STANDARD Versions Data 5 Exists Versions Data 1 Deleted Retain Extra30 Versions Retain Only Version 60 Copy Mode MODIFIED Copy Serialization SHRSTATIC Copy Frequency 0 Copy DestinationBACKUPPOOL Do You think this would meet the 4 weeks restore policy. Thanx Med Vdnlig Hdlsning/ Best Regards _ Henrik Hansson
Re: Point in time restore vs Archiving
Hi Henrik, If you want to have something equivalent to a full backup, shouldn't you use copymode absolute ? Else, only modified files would be backuped ... My 2 cents. Arnaud =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= | Arnaud Brion, Panalpina Management Ltd., IT Group | | Viaduktstrasse 42, P.O. Box, 4002 Basel - Switzerland | | Phone: +41 61 226 19 78 / Fax: +41 61 226 17 01 | =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Henrik Wahlstedt Sent: Wednesday, 08 October, 2003 13:20 To: [EMAIL PROTECTED] Subject: Re: Point in time restore vs Archiving Or, VERE nolimit VERD nolimit RETE 31 or 35 RETO 31 or 35 FREQ 0 //Henrik Karel Bos [EMAIL PROTECTED]To: [EMAIL PROTECTED] ON.COM cc: (bcc: Henrik Wahlstedt) Sent by: Subject: Re: Point in time restore vs Archiving ADSM: Dist Stor Manager [EMAIL PROTECTED] RIST.EDU 2003-10-08 13:07 Please respond to ADSM: Dist Stor Manager Hi, Something like: Versions Data 28 Exists Versions Data 28 Deleted Retain Extra28 Versions Retain Only Version 28 Copy Frequency 1 should work fine. Regard, Karel -Oorspronkelijk bericht- Van: Henrik Hansson [mailto:[EMAIL PROTECTED] Verzonden: woensdag 8 oktober 2003 13:02 Aan: [EMAIL PROTECTED] Onderwerp: Point in time restore vs Archiving I have a question regarding an issue regarding Archiving. Lets say I have a policy that says that I need to do FULL backups days a week for 4 weeks. Ofcourse I can do archive each day but then I think I don't use the functunallety in TSM. Is there a way of doing incremental backups that covers 4 weeks back in time? I have the following settings in my TSM for a backup group Backup Copy Groups : STANDARD ACTIVE STANDARD STANDARD Policy Domain Name STANDARD Policy Set Name ACTIVE Mgmt Class Name STANDARD Copy Group Name STANDARD Versions Data 5 Exists Versions Data 1 Deleted Retain Extra30 Versions Retain Only Version 60 Copy Mode MODIFIED Copy Serialization SHRSTATIC Copy Frequency 0 Copy DestinationBACKUPPOOL Do You think this would meet the 4 weeks restore policy. Thanx Med Vänlig Hälsning/ Best Regards _ Henrik Hansson --- The information contained in this message may be CONFIDENTIAL and is intended for the addressee only. Any unauthorised use, dissemination of the information or copying of this message is prohibited. If you are not the addressee, please notify the sender immediately by return e-mail and delete this message. Thank you.
Re: nt client upgraded, point in time restore fails
Hello Joni, Did you ever get a resolution? We have encountered a sort of similar scenario... The details are a little different. AIX 5.1 TSM server 4.2.3.3 (not much longer though...) W2K client v5.1.5.9 also 5.2 Client gui does not display Inactive files when selected in drop-down. Client command line works ok. Larry McNutt Timken Company -Original Message- From: Joni Moyer [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 29, 2003 8:59 AM To: [EMAIL PROTECTED] Subject: nt client upgraded, point in time restore fails Hi everyone! I was wondering if anyone has had an issue when upgrading a windows client from 5.1.5 to 5.1.6.0 with the point in time restore? Apparently we aren't seing all of the files that should be there. The TSM server is on os/390 5.1.6.2. Any ideas? Thanks! Joni Moyer Systems Programmer [EMAIL PROTECTED] (717)975-8338 ** This message and any attachments are intended for the individual or entity named above. If you are not the intended recipient, please do not forward, copy, print, use or disclose this communication to others; also please notify the sender by replying to this message, and then delete it from your system. The Timken Company **
Re: nt client upgraded, point in time restore fails
See http://msgs.adsm.org/cgi-bin/get/adsm0103/207.html for one possible explanation. Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend. Good enough is the enemy of excellence. McNutt, Larry E. [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 07/31/2003 10:31 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Re: nt client upgraded, point in time restore fails Hello Joni, Did you ever get a resolution? We have encountered a sort of similar scenario... The details are a little different. AIX 5.1 TSM server 4.2.3.3 (not much longer though...) W2K client v5.1.5.9 also 5.2 Client gui does not display Inactive files when selected in drop-down. Client command line works ok. Larry McNutt Timken Company -Original Message- From: Joni Moyer [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 29, 2003 8:59 AM To: [EMAIL PROTECTED] Subject: nt client upgraded, point in time restore fails Hi everyone! I was wondering if anyone has had an issue when upgrading a windows client from 5.1.5 to 5.1.6.0 with the point in time restore? Apparently we aren't seing all of the files that should be there. The TSM server is on os/390 5.1.6.2. Any ideas? Thanks! Joni Moyer Systems Programmer [EMAIL PROTECTED] (717)975-8338 ** This message and any attachments are intended for the individual or entity named above. If you are not the intended recipient, please do not forward, copy, print, use or disclose this communication to others; also please notify the sender by replying to this message, and then delete it from your system. The Timken Company **
nt client upgraded, point in time restore fails
Hi everyone! I was wondering if anyone has had an issue when upgrading a windows client from 5.1.5 to 5.1.6.0 with the point in time restore? Apparently we aren't seing all of the files that should be there. The TSM server is on os/390 5.1.6.2. Any ideas? Thanks! Joni Moyer Systems Programmer [EMAIL PROTECTED] (717)975-8338
TDP SQL 2.2 Point in Time restore experiences
We have TSM server 4.2.1.9 and Windows clients 4.2.1.20. Also have SQL 7.0 and 2000. Using TDP SQL 2.2, new installs. Our SQL DBA wants to know of any user experiences doing point in time restores using logs or some of the more sophisticated TDP SQL stuff. Very useful if user has dadabases on several machines and has to restore them both to some single point in time. Thanks, MMS health-first.org made the following annotations on 03/28/02 10:00:18 -- This message is for the named person's use only. It may contain confidential, proprietary, or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it, and notify the sender. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. Health First reserves the right to monitor all e-mail communications through its networks. Any views or opinions expressed in this message are solely those of the individual sender, except (1) where the message states such views or opinions are on behalf of a particular entity; and (2) the sender is authorized by the entity to give such views or opinions. ==
Point in time restore for NT and/or Win 2000 system objects ??
Hello, Am I correct in reading the Tivoli doc's that with the 4.2 windows client, that point in time recovery of system object is ONLY supported for win2000? If so, is there any work around or experience out there for how to manage this on windows NT? Thanks, Keith
Point in time restore
Hi, Point in Time Trouble's on AIX. It seems that TSM expires dir's on the same way as the files; The policy's says: 3 extra versions. When you change a file regularly, after 3 backup's the oldest file disapears from tape. It seems that the same happend to the dir's, when a dir changes regular (by new or changing files) after 3 backup's the dir disapaers So, when i want to do a point in time restore, all the dir's with activity older than 3 day's are gone also ALL the files in that dir. This isn't right is it Does somebody have's a solution? TIA, Maurice van 't Loo The Netherlands
Re: Point in time restore
Hi Create a mgmtclass where you specify retentionperiod and versions for directories. Define option DIRMC mgmtclassname in the clients dsm.sys files - or via an option set on the server. Carsten Maurice van 't Loo [EMAIL PROTECTED] on 16-08-2001 10:35:35 Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc:(bcc: Carsten Moldrup/SCA/CSC) Subject: Point in time restore Hi, Point in Time Trouble's on AIX. It seems that TSM expires dir's on the same way as the files; The policy's says: 3 extra versions. When you change a file regularly, after 3 backup's the oldest file disapears from tape. It seems that the same happend to the dir's, when a dir changes regular (by new or changing files) after 3 backup's the dir disapaers So, when i want to do a point in time restore, all the dir's with activity older than 3 day's are gone also ALL the files in that dir. This isn't right is it Does somebody have's a solution? TIA, Maurice van 't Loo The Netherlands
Point-In-Time-Restore
Hy all, today again a question concerning Point-In-Time-Restore : Following situation : I did make backups of a node for more than half a year. Many files have prduced versions on the backup-server, a lot of files did not because they did not change since start of backup. My policy says it will keep 10 versions for lets say 3 month. Now I start a full backup of the whole client. I produce a new version of all files. For many of those files that had only produced one version up to this date, the retention-period will cause this older version to be deleted. Now I have to make a point-in-time restore to five days before. The old version of some files is deleted (because of retention-period), the new (but identical) file came later into the backup-server. Will my restore get this file or will it be missed ?? This question came up because some people around me wanted to make a full backup on a regular base. Server : AIX 4.3.3 TSM 3.7.4 Clients : TSM 3.7 Can anybody give me an answer (otherwise I have to build up some test-scenarios) ? Thanks Christoph
Re: Point-In-Time-Restore
today again a question concerning Point-In-Time-Restore : Following situation : I did make backups of a node for more than half a year. Many files have prduced versions on the backup-server, a lot of files did not because they did not change since start of backup. My policy says it will keep 10 versions for lets say 3 month. Now I start a full backup of the whole client. I produce a new version of all files. For many of those files that had only produced one version up to this date, the retention-period will cause this older version to be deleted. The timer to expire the older version starts when it was replaced. Thus the older version is available for 3 months, per the above example.
Re: Point-In-Time Restore
Andy- You make mention of "Depending on how often your directories change, this could potentially impact the size of our TSM database." What is the definition of when a directory changes. We've got some dirs that haven't changed since inception with respect to permissions, access right, ACL's, etc. Yet, they get backed up daily with incrementals. As such we are in the midst of a PIT restore issue ourselves. Moreover, taking the position that the GUI is DESIGNED to be crippled is most disheartening. Is this cripple feature also in the web interface? If it is, it nulls out ANY potential benefit of such an interface because if I have to use the command line to make sure I can do my job, then I'm most likely already sitting in front of the machine in question. This all reminds me of a brand of VCR that one aspiring salesperson tried to sell me, touting all the neat things I could do with the remote. When I asked for a demo of how to program recording the machine from its' front panel, I was informed it couldn't be done. I shopped for another brand. You see it's not that I would program from the front panel, it's that I could if I chose to. The functionality was available in both interfaces. Sometimes the obvious is to plain to see. Andy Raibeck Andrew_Raibeck@TTo: [EMAIL PROTECTED] IVOLI.COM cc: Sent by: "ADSM: Subject: Re: Point-In-Time Restore Dist Stor Manager" [EMAIL PROTECTED] .EDU 03/07/01 09:58 AM Please respond to "ADSM: Dist Stor Manager" For those of you who remember ADSM Versions 2 or earlier, our backup-archive GUI used to obtain a list of *all* backup versions before displaying the restore tree. Because the list of all backup versions can grow extremely large (i.e. millions of files), this presented two problem areas: memory shortages on the client machine (to retain the list of files in memory) and performance (because it takes a long time to build the list). Starting with Version 3, we took a different approach to how we get file backup information. Rather than try to obtain a list of all backup versions initially, we only obtain a list of the objects that you can immediately see on the screen. For example, when you crack open (click on the + sign) the "File level" in the restore tree, we just show the available filespaces, so that is the only information we get from the server. When you click on one of the file spaces, we get a list of files that are in the root directory of that filespace, which is then displayed on the right-hand side of the GUI. When you crack open the filespace, we get a list of available directories directly beneath that filespace. When you click on a directory, we get the list of files immediately under that directory. And so on and so forth. Because we are only getting lists of files for what you can see on the screen, the list is much smaller, so the GUI performance is vastly improved. The problem you are seeing with PIT restores via the GUI is in order to see the files, you first need to be able to see the directories (so you can click on them to see the files or crack them open to view their subdirec
Re: Point-In-Time Restore
Allen, What causes a directory to appear as changed is operating system and/or file system dependent. We check for changed directories the same as we do for files. Modification date may be a very common indicator of a changed directory. For example, by moving a file in or out of a directory on my Windows 2000 workstation will cause that directory's modification date to be changed. Hence it will be eligible for incremental backup. Yes, the web interface would have the same issues as the native GUI with regard to PIT restores. Regards, Andy Andy Raibeck IBM Tivoli Systems Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] "The only dumb question is the one that goes unasked." Allen Barth [EMAIL PROTECTED]@VM.MARIST.EDU on 03/13/2001 11:32:51 AM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: Point-In-Time Restore Andy- You make mention of "Depending on how often your directories change, this could potentially impact the size of our TSM database." What is the definition of when a directory changes. We've got some dirs that haven't changed since inception with respect to permissions, access right, ACL's, etc. Yet, they get backed up daily with incrementals. As such we are in the midst of a PIT restore issue ourselves. Moreover, taking the position that the GUI is DESIGNED to be crippled is most disheartening. Is this cripple feature also in the web interface? If it is, it nulls out ANY potential benefit of such an interface because if I have to use the command line to make sure I can do my job, then I'm most likely already sitting in front of the machine in question. This all reminds me of a brand of VCR that one aspiring salesperson tried to sell me, touting all the neat things I could do with the remote. When I asked for a demo of how to program recording the machine from its' front panel, I was informed it couldn't be done. I shopped for another brand. You see it's not that I would program from the front panel, it's that I could if I chose to. The functionality was available in both interfaces. Sometimes the obvious is to plain to see. Andy Raibeck Andrew_Raibeck@TTo: [EMAIL PROTECTED] IVOLI.COM cc: Sent by: "ADSM: Subject: Re: Point-In-Time Restore Dist Stor Manager" [EMAIL PROTECTED] .EDU 03/07/01 09:58 AM Please respond to "ADSM: Dist Stor Manager" For those of you who remember ADSM Versions 2 or earlier, our backup-archive GUI used to obtain a list of *all* backup versions before displaying the restore tree. Because the list of all backup versions can grow extremely large (i.e. millions of files), this presented two problem areas: memory shortages on the client machine (to retain the list of files in memory) and performance (because it takes a long time to build the list). Starting with Version 3, we took a different approach to how we get file backup information. Rather than try to obtain a list of all backup versions initially, we only obtain a list of the objects that you can immediately see on the screen. For example, when you crack open (click on the + sign) the "File level" in the restore tree, we just show the available filespaces, so that is the only information we get from the server. When you click on one of the file spaces, we get a list of files that are in the root directory of that filespace, which is then displayed on the right-hand side of the GUI. When you crack open the filespace, we get a list of available directories directly beneath that filespace. When you click on a directory, we get the list of files immediately under that directory. And so on and so forth. Because we are only getting lists of files for what you can see on the screen, the list is much smaller, so the GUI performance is vastly improved. The problem you are seeing with PIT restores via the GUI is in order to see the files, you first need to be able to see the directories (so you can click on them to see the files or crack them open to view their subdirectories). But if there are no directories that were backed up prior to your PIT specification, then there is no directory that can be displayed. Thus if there is no displayed directory, there is nothing for you to click on or crack open. The command line interface does not rely on the ability to display directories before it can display its files and subdirectories, so this is why it does not have the problem. Directories are bound to the management class (within the policy domain) that has the highest "Retain only version" (RETONLY) se
Re: Point-In-Time Restore
vice with your users that states how far back you will support PIT restores via the GUI. Then you can create a managment class for your directories with VEREXISTS=NOLIMIT, VERDELETED=NOLIMIT, and RETEXTRA=ndays, where 'ndays' is the number of days to which you will guarantee PIT restores via the GUI. For example, if you want to be able to go back up to 30 days, then set RETEXTRA=30. Beyond 30 days, you will need to use the CLI. Regards, Andy Andy Raibeck IBM Tivoli Systems Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] "The only dumb question is the one that goes unasked." "Richard L. Rhodes" [EMAIL PROTECTED]@VM.MARIST.EDU on 03/07/2001 12:36:50 AM Please respond to [EMAIL PROTECTED] Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: Point-In-Time Restore This brings up lots of questions: 1) How do you "keep enough directories" to enable PIT for the gui? 2) How would you not have enough directories to enable PIT if you have enough file versions to do PIT? 2) What does the cmd line client do differently than the gui? In other words, I'm not sure what exactly IBM is saying is wrong and what I should do to prevent it. Any clarification is appreciated! Rick On 7 Mar 2001, at 7:31, bel Kaj-Flemming wrote: Hi. Some month ago I ran into the same problem. Called Tivoli support for help. They told: working as designed. You will have to use the command line interface to restore. -CUT--- Hello, This issue has already been discussed with development. There are 2 methods for enabling PIT restores. The first method is to keep enough versions of directories to enable the PIT restore in the GUI. The second is to use the command line for PIT restores. The decision to enable PIT restores from the GUI is up to administration. Enabling PIT restores from the GUI can mean increased resource costs. Enabling PIT restores from the GUI require extra versions of directories, these extra versions require more disk space and more entries in the database to keep track of the entries. The DIRMC option is discussed earlier in Chapter 11 Managing Client Data Using Policies. Development is aware that GUI PIT restores can appear inconsistent. APAR IC25961 and IC24733 were opened and closed SUG (suggestion). In both cases the issue was acknowledged and stated to be working as designed. I hope that this helps to clarify the situation. Regards, Level 2 Tucson -CUT--- Kaj -Original Message- From: Steven Abrey [mailto:[EMAIL PROTECTED]] Sent: 7. marts 2001 06:32 To: [EMAIL PROTECTED] Subject: Point-In-Time Restore Hi, I have been trying to do a Point In Time Restore from the Backup/Restore Gui, but I only get a fraction of the files that should exist. I am running 3.7.3 TSM server with the 3.1.07 Backup/Restore gui tool. Sometimes, whole directory's don't exist and normally only the files that have been backed up within the last week or so, show up. Any Help will be most appreciated Steven Abrey Network Support Analyst Credit Union Australia Phone : 07 - 3365 0231 Fax : 07 - 3365 0295 Email : [EMAIL PROTECTED] -- Mit freundlichen Gren Bernhard Unold begin:vcard n:Unold;Bernhard tel;work:+49 7071/29-80130 x-mozilla-html:FALSE adr:;; version:2.1 email;internet:[EMAIL PROTECTED] fn:Bernhard Unold end:vcard
Re: Point-In-Time Restore
Hi Bernhard, A policy domain may have many management classes, each with different file retention criteria. Within a given directory, it is possible to have some files bound to one management class, other files bound to another management class, still other files bound to a third management class, etc. Maybe one class says to keep files for 14 days, another says to keep files for 180 days, and the third management class says to keep files for 365 days. Also, you may add files to the directory over time, and set your INCLUDE processing to bind them to different management classes. Directories are bound to the management class with the longest RETONLY setting so that, after you delete the directory (and its files and subdirectories) from the client machine, you can at least recover the most recent backup copy and the directory in which that file resided. TSM has no way of knowing that you intend to keep *all* files on a particular machine, now and forever, for only 14 days, so it can not decide to use a management class for directories with a smaller RETONLY setting. But if *you* know you intend to keep all files on a particular machine for only 14 days (like in the example you gave), you can do a couple of things: 1) Use the DIRMC option to bind directories to the same management class that your files use. 2) Create a new policy domain to which the machine's node will belong that has only the one management class with the 14-day criterion. Regarding your questions about what is in a directory and what is stored for a directory: in older file systems like like the DOS FAT file system, directories were indeed nothing more than just a mechanism for organizing how files are stored withing the file system. But for other file systems like on UNIX and NetWare, and newer Windows file systems like NTFS, directories now have attributes (like security, ownership, etc.) associated with them that files stored withing those directories can inherit. So it is important that TSM be able to back up and restore the attributes for the directories as well. In answer to some of your specific questions that may not have been covered above: Q: What can I do with the directory if the files belonging to it are expired? A: Techincally you could restore the directory itself, although that would most likely be of little practical use. But other than that, there is nothing more you can really do with it. Q: What is the state or content of the directory restored PIT to day 1 (from the example below)? A: Whatever the state or content was at the time it was backed up. (I am not trying to be "flip" here, but I am not sure what the point of this question is.) Q: Is it possible to restore MyFile.txt to the version of day 1 if the directory backup belonging to it is expired? A: Yes, with the exception that you can not restore that version with the PIT restore feature from the GUI. Regards, Andy Andy Raibeck IBM Tivoli Systems Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] "The only dumb question is the one that goes unasked." Bernhard Unold [EMAIL PROTECTED]@VM.MARIST.EDU on 03/08/2001 02:17:33 AM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: Point-In-Time Restore Hello, Andy I understand your arguments, but want to know the benefits of the method to store the directory not in the same manner as the files. For Example from a certain computer we do a archive, we want to keep for 14 days. But the directories are kept for 365 days. So storage is wasted on tape and in the db. For special purpose we have a mgmtclass without any limits. Now some clients store their directories there at incremental backup. No good idea!! What is stored for a directory entry? What can i do with the directory, if the files belonging to it are expired? In your example: What is the state or content of the directory restored PIT to day 1? Is it possible to restore Myfile to the version of day 1 if the directory backup belonging to it is expired? My idea is to store the directories together with the files. This would solve a lot of problems. Best regard Bernhard Unold Andy Raibeck schrieb: For those of you who remember ADSM Versions 2 or earlier, our backup-archive GUI used to obtain a list of *all* backup versions before displaying the restore tree. Because the list of all backup versions can grow extremely large (i.e. millions of files), this presented two problem areas: memory shortages on the client machine (to retain the list of files in memory) and performance (because it takes a long time to build the list). Starting with Version 3, we took a different approach to how we get file backup information. Rather than try to obtain a list of all backup versions initially, we only obtain a list of the objects that you can immediately see on the screen.
Re: Point-In-Time Restore
Thanks Andy, We've tried to get an answer to this question since we first put in TSM (3rd qtr last year), but couldn't find an answer, including from support. Your example exactly describes our situation, but, our systems don't appear to act like your describing. We have a domain called "AIX" with the following mgt classes: vde rev vdd rto aix 14 14 14 14 (dflt) aix1m 32 32 32 32 aix2m 62 62 62 62 aixorac 2 1 1 90 (oracle backups) All our directories go into the last class aixorac with the largest RetainOnlyVersion, just as you describe. When I fire up the gui, changed the date to point back a month, point to a filespace that is bound to aix2m (2 month PIT), and go to a directory that changes every day - every thing looks OK! The directory shows up in the gui with all it's files. I don't seem to be able to duplicate the situation you describe! We've wondered about this directory issues, but didn't think there was a problem given that it appeared to be working. I fugured it created the directory from the files that exist in it. Any thoughts? Rick On 7 Mar 2001, at 7:58, Andy Raibeck wrote: Day 1: File C:\MyDir\MyFile.txt is backed up. MyDir is bound to CLASS1 and MyFile.txt is bound to CLASS2. Day2: File C:\MyDir\MyFile.txt is changed. The MyDir directory is also changed. When the backup runs, MyDir will be backed up. Because only 1 version is kept, the version that was created on Day 1 is deleted. MyFile.txt is also backed up and bound to CLASS2. There are now 2 versions of MyFile.txt. Now you need to do a PIT restore back to Day 1. However, since there is only one backup version of MyDir, created on Day 2, it will not be displayed in the GUI when you PIT criteria specifies Day 1.
Re: Point-In-Time Restore
For those of you who remember ADSM Versions 2 or earlier, our backup-archive GUI used to obtain a list of *all* backup versions before displaying the restore tree. Because the list of all backup versions can grow extremely large (i.e. millions of files), this presented two problem areas: memory shortages on the client machine (to retain the list of files in memory) and performance (because it takes a long time to build the list). Starting with Version 3, we took a different approach to how we get file backup information. Rather than try to obtain a list of all backup versions initially, we only obtain a list of the objects that you can immediately see on the screen. For example, when you crack open (click on the + sign) the "File level" in the restore tree, we just show the available filespaces, so that is the only information we get from the server. When you click on one of the file spaces, we get a list of files that are in the root directory of that filespace, which is then displayed on the right-hand side of the GUI. When you crack open the filespace, we get a list of available directories directly beneath that filespace. When you click on a directory, we get the list of files immediately under that directory. And so on and so forth. Because we are only getting lists of files for what you can see on the screen, the list is much smaller, so the GUI performance is vastly improved. The problem you are seeing with PIT restores via the GUI is in order to see the files, you first need to be able to see the directories (so you can click on them to see the files or crack them open to view their subdirectories). But if there are no directories that were backed up prior to your PIT specification, then there is no directory that can be displayed. Thus if there is no displayed directory, there is nothing for you to click on or crack open. The command line interface does not rely on the ability to display directories before it can display its files and subdirectories, so this is why it does not have the problem. Directories are bound to the management class (within the policy domain) that has the highest "Retain only version" (RETONLY) setting, without regard to the number of versions that are kept. If two management classes have the same RETONLY setting, then you can not predict which class will be used. If the management class with the largest RETONLY setting maintains only 1 version, this will still be the class to which directories are bound. Call this management class CLASS1 On the other hand, you might have files that are bound to another management class, say, CLASS2, with a lower RETONLY setting but maintains, say, 10 versions if the file exists (number of versions when file is deleted is not pertinent here). So here is a scenario: Day 1: File C:\MyDir\MyFile.txt is backed up. MyDir is bound to CLASS1 and MyFile.txt is bound to CLASS2. Day2: File C:\MyDir\MyFile.txt is changed. The MyDir directory is also changed. When the backup runs, MyDir will be backed up. Because only 1 version is kept, the version that was created on Day 1 is deleted. MyFile.txt is also backed up and bound to CLASS2. There are now 2 versions of MyFile.txt. Now you need to do a PIT restore back to Day 1. However, since there is only one backup version of MyDir, created on Day 2, it will not be displayed in the GUI when you PIT criteria specifies Day 1. The key for PIT restores from the GUI, then, is to ensure that each directory has a backup version that is at least as old as the oldest file or subdirectory contained within that directory. I don't think there is any great way to ensure that you can *always* do a PIT restore from the GUI unless you have a management class for directories that basically keeps all versions of directory backups forever (NOLIMIT). Depending on how often your directories change, this could potentially impact the size of our TSM database. The best compromise would be to establish a term of service with your users that states how far back you will support PIT restores via the GUI. Then you can create a managment class for your directories with VEREXISTS=NOLIMIT, VERDELETED=NOLIMIT, and RETEXTRA=ndays, where 'ndays' is the number of days to which you will guarantee PIT restores via the GUI. For example, if you want to be able to go back up to 30 days, then set RETEXTRA=30. Beyond 30 days, you will need to use the CLI. Regards, Andy Andy Raibeck IBM Tivoli Systems Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] "The only dumb question is the one that goes unasked." "Richard L. Rhodes" [EMAIL PROTECTED]@VM.MARIST.EDU on 03/07/2001 12:36:50 AM Please respond to [EMAIL PROTECTED] Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: Point-In-Time Restore This brings up lots of questions: 1) How do you "keep enough directories" to enable PIT for the gui? 2) Ho
Point-In-Time Restore
Hi, I have been trying to do a Point In Time Restore from the Backup/Restore Gui, but I only get a fraction of the files that should exist. I am running 3.7.3 TSM server with the 3.1.07 Backup/Restore gui tool. Sometimes, whole directory's don't exist and normally only the files that have been backed up within the last week or so, show up. Any Help will be most appreciated Steven Abrey Network Support Analyst Credit Union Australia Phone : 07 - 3365 0231 Fax : 07 - 3365 0295 Email : [EMAIL PROTECTED]
Re: Why does a point in time restore try to restore deleted files .
It was deleted on or around the 15th October
Thanks
Marc
_
Marc Layne
Product Manager - Services, Storage and Software Solutions
Faritec
Mobile: +27 82 4169086email: [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
Office: + 27 21 7629702 http://www.faritec.co.za/
_
-Original Message-
From: Joel Fuhrman [mailto:[EMAIL PROTECTED]]
Sent: 27 February 2001 09:19
To: [EMAIL PROTECTED]
Subject: Re: Why does a point in time restore try to restore deleted
files.
On what date and time was the file deleted.
On Tue, 27 Feb 2001, Marc Layne wrote:
Hi All
I posted a question yesterday about point in time restore but i wish to
clarify my question. Basically i need to know why if a file was backed up
on
the 10 October 2000 and subsequently deleted, and i do a point in time
restore to February 23 2001.. why is it trying to restore the deleted
file.
PIT restore is done via the GUI. Even if i am doing full backups..surely
if
the file odes not exist..(has been deleted) then PIT restore should not
try
and restore it . I run a Expire inventory every day.
rete=30
reto=10
TSM ver 3.7 for NT server
TSM ver 3.7 for NT client
Thanks
Marc
_
Marc Layne
Product Manager - Services, Storage and Software Solutions
Faritec
Mobile: +27 82 4169086email: [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
Office: + 27 21 7629702 http://www.faritec.co.za/
http://www.faritec.co.za/
_
"This message may contain information which is confidential, private or
privileged in nature. If you are not the intended recipient, you may not
peruse, use, disseminate, distribute or copy this message or file which is
attached to this message. If you have received this message in error,
please notify the sender immediately by e-mail, facsimile or telephone
and
thereafter return and/or destroy the original message.
Any views of this communication are those of the sender except where the
sender specifically states them to be those of Faritec (Proprietary)
Limited
("Faritec") and/or Midrange Distribution Services (Pty) Ltd.
Please note that the recipient must scan this e-mail and any attached
files
for viruses and the like. While we do everything possible to protect
information from viruses, Faritec accepts no liability of whatever nature
for any loss, liability, damage or expense resulting directly or
indirectly
from the access and/or downloading of any files which are attached to this
e-mail message."
"This message may contain information which is confidential, private or
privileged in nature. If you are not the intended recipient, you may not
peruse, use, disseminate, distribute or copy this message or file which is
attached to this message. If you have received this message in error,
please notify the sender immediately by e-mail, facsimile or telephone and
thereafter return and/or destroy the original message.
Any views of this communication are those of the sender except where the
sender specifically states them to be those of Faritec (Proprietary) Limited
("Faritec") and/or Midrange Distribution Services (Pty) Ltd.
Please note that the recipient must scan this e-mail and any attached files
for viruses and the like. While we do everything possible to protect
information from viruses, Faritec accepts no liability of whatever nature
for any loss, liability, damage or expense resulting directly or indirectly
from the access and/or downloading of any files which are attached to this
e-mail message."
Why does a point in time restore try to restore deleted files.
Hi All
I posted a question yesterday about point in time restore but i wish to
clarify my question. Basically i need to know why if a file was backed up on
the 10 October 2000 and subsequently deleted, and i do a point in time
restore to February 23 2001.. why is it trying to restore the deleted file.
PIT restore is done via the GUI. Even if i am doing full backups..surely if
the file odes not exist..(has been deleted) then PIT restore should not try
and restore it . I run a Expire inventory every day.
rete=30
reto=10
TSM ver 3.7 for NT server
TSM ver 3.7 for NT client
Thanks
Marc
_
Marc Layne
Product Manager - Services, Storage and Software Solutions
Faritec
Mobile: +27 82 4169086email: [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
Office: + 27 21 7629702 http://www.faritec.co.za/
http://www.faritec.co.za/
_
"This message may contain information which is confidential, private or
privileged in nature. If you are not the intended recipient, you may not
peruse, use, disseminate, distribute or copy this message or file which is
attached to this message. If you have received this message in error,
please notify the sender immediately by e-mail, facsimile or telephone and
thereafter return and/or destroy the original message.
Any views of this communication are those of the sender except where the
sender specifically states them to be those of Faritec (Proprietary) Limited
("Faritec") and/or Midrange Distribution Services (Pty) Ltd.
Please note that the recipient must scan this e-mail and any attached files
for viruses and the like. While we do everything possible to protect
information from viruses, Faritec accepts no liability of whatever nature
for any loss, liability, damage or expense resulting directly or indirectly
from the access and/or downloading of any files which are attached to this
e-mail message."
Re: Why does a point in time restore try to restore deleted files.
On what date and time was the file deleted.
On Tue, 27 Feb 2001, Marc Layne wrote:
Hi All
I posted a question yesterday about point in time restore but i wish to
clarify my question. Basically i need to know why if a file was backed up on
the 10 October 2000 and subsequently deleted, and i do a point in time
restore to February 23 2001.. why is it trying to restore the deleted file.
PIT restore is done via the GUI. Even if i am doing full backups..surely if
the file odes not exist..(has been deleted) then PIT restore should not try
and restore it . I run a Expire inventory every day.
rete=30
reto=10
TSM ver 3.7 for NT server
TSM ver 3.7 for NT client
Thanks
Marc
_
Marc Layne
Product Manager - Services, Storage and Software Solutions
Faritec
Mobile: +27 82 4169086email: [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
Office: + 27 21 7629702 http://www.faritec.co.za/
http://www.faritec.co.za/
_
"This message may contain information which is confidential, private or
privileged in nature. If you are not the intended recipient, you may not
peruse, use, disseminate, distribute or copy this message or file which is
attached to this message. If you have received this message in error,
please notify the sender immediately by e-mail, facsimile or telephone and
thereafter return and/or destroy the original message.
Any views of this communication are those of the sender except where the
sender specifically states them to be those of Faritec (Proprietary) Limited
("Faritec") and/or Midrange Distribution Services (Pty) Ltd.
Please note that the recipient must scan this e-mail and any attached files
for viruses and the like. While we do everything possible to protect
information from viruses, Faritec accepts no liability of whatever nature
for any loss, liability, damage or expense resulting directly or indirectly
from the access and/or downloading of any files which are attached to this
e-mail message."
Point in time restore trying to restore files that have been dele ted off the system
Hi All
I have the following problem.For one of our Windows NT systems we run a
full backup of the D partition every day. e do this so that the batch of
tapes used can be sent to another city where a develpment environment can be
refreshed. Now what is happening is that some files that were backed up in
september or october last year are still appearing as active within the TSM
database, even though these files have been deleted. So when trying to run a
point in time restore to the previous day, it is looking for older tapes
where these older deleted files are stored.These tapes ahve already been
sent back.
Even after the retain only parameter expires these files are still seen as
been active on the system. Even if i change the retaino=20 days and
retaine=10 days .. four months down the line these files are still active
and are not expiring.
Either the deleted files are not been marked as such (inactivated) or there
is a bug somewhere..
Environment:
TSM Server ver 3.7.1 on Windows NT service pack 6
TSM client for Windows NT ver 3.7.3
vere= 14
verd= 2
retaine= 30
retaino= 10
Thanks
Marc
_
Marc Layne
Product Manager - Services, Storage and Software Solutions
Faritec
Mobile: +27 82 4169086email: [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
Office: + 27 21 7629702 http://www.faritec.co.za/
http://www.faritec.co.za/
_
"This message may contain information which is confidential, private or
privileged in nature. If you are not the intended recipient, you may not
peruse, use, disseminate, distribute or copy this message or file which is
attached to this message. If you have received this message in error,
please notify the sender immediately by e-mail, facsimile or telephone and
thereafter return and/or destroy the original message.
Any views of this communication are those of the sender except where the
sender specifically states them to be those of Faritec (Proprietary) Limited
("Faritec") and/or Midrange Distribution Services (Pty) Ltd.
Please note that the recipient must scan this e-mail and any attached files
for viruses and the like. While we do everything possible to protect
information from viruses, Faritec accepts no liability of whatever nature
for any loss, liability, damage or expense resulting directly or indirectly
from the access and/or downloading of any files which are attached to this
e-mail message."
