Alerts in event viewer
Hello, I want to backup my exchange server using TDP. The quesion i am having is that , will i get alerts related to log files in the event viewer or there will be no alert? When i use simple BA client , my event viewer is full of alerts due to failed backup of log files -- Best Regards Ashish Sharma ST Microelectronics Ltd. 919717003853
Re: Alerts in event viewer
You have two options: 1) stop Exchange Server and use TSM Client to make offline backup; 2) install TDP for SQL and make online backups for Exchange database (database files and logs have to be excluded from normal TSM Client backup). Good luck! Grigori G. Solonovitch Senior Technical Architect Information Technology Bank of Kuwait and Middle East http://www.bkme.com Phone: (+965) 2231-2274 Mobile: (+965) 99798073 E-Mail: g.solonovi...@bkme.com Please consider the environment before printing this Email -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of ashish sharma Sent: Thursday, December 17, 2009 12:08 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Alerts in event viewer Hello, I want to backup my exchange server using TDP. The quesion i am having is that , will i get alerts related to log files in the event viewer or there will be no alert? When i use simple BA client , my event viewer is full of alerts due to failed backup of log files -- Best Regards Ashish Sharma ST Microelectronics Ltd. 919717003853 Please consider the environment before printing this Email. This email message and any attachments transmitted with it may contain confidential and proprietary information, intended only for the named recipient(s). If you have received this message in error, or if you are not the named recipient(s), please delete this email after notifying the sender immediately. BKME cannot guarantee the integrity of this communication and accepts no liability for any damage caused by this email or its attachments due to viruses, any other defects, interception or unauthorized modification. The information, views, opinions and comments of this message are those of the individual and not necessarily endorsed by BKME.
Re: Alerts in event viewer
Hello Grigori, I know TDP can backup exchange but just want to confirm that does it gives any type of alerts in event viewer while backing up changing files? On Thu, Dec 17, 2009 at 3:34 PM, Grigori Solonovitch g.solonovi...@bkme.com wrote: You have two options: 1) stop Exchange Server and use TSM Client to make offline backup; 2) install TDP for SQL and make online backups for Exchange database (database files and logs have to be excluded from normal TSM Client backup). Good luck! Grigori G. Solonovitch Senior Technical Architect Information Technology Bank of Kuwait and Middle East http://www.bkme.com Phone: (+965) 2231-2274 Mobile: (+965) 99798073 E-Mail: g.solonovi...@bkme.com Please consider the environment before printing this Email -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of ashish sharma Sent: Thursday, December 17, 2009 12:08 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Alerts in event viewer Hello, I want to backup my exchange server using TDP. The quesion i am having is that , will i get alerts related to log files in the event viewer or there will be no alert? When i use simple BA client , my event viewer is full of alerts due to failed backup of log files -- Best Regards Ashish Sharma ST Microelectronics Ltd. 919717003853 Please consider the environment before printing this Email. This email message and any attachments transmitted with it may contain confidential and proprietary information, intended only for the named recipient(s). If you have received this message in error, or if you are not the named recipient(s), please delete this email after notifying the sender immediately. BKME cannot guarantee the integrity of this communication and accepts no liability for any damage caused by this email or its attachments due to viruses, any other defects, interception or unauthorized modification. The information, views, opinions and comments of this message are those of the individual and not necessarily endorsed by BKME. -- Best Regards Ashish Sharma ST Microelectronics Ltd. 919717003853
Re: Alerts in event viewer
Hello Ashish, TDP for SQL is integrated with MS SQL Server and will not give any alerts in case of correct configuration. Regards, Grigori G. Solonovitch Senior Technical Architect Information Technology Bank of Kuwait and Middle East http://www.bkme.com Phone: (+965) 2231-2274 Mobile: (+965) 99798073 E-Mail: g.solonovi...@bkme.com Please consider the environment before printing this Email -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of ashish sharma Sent: Thursday, December 17, 2009 1:30 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Alerts in event viewer Hello Grigori, I know TDP can backup exchange but just want to confirm that does it gives any type of alerts in event viewer while backing up changing files? On Thu, Dec 17, 2009 at 3:34 PM, Grigori Solonovitch g.solonovi...@bkme.com wrote: You have two options: 1) stop Exchange Server and use TSM Client to make offline backup; 2) install TDP for SQL and make online backups for Exchange database (database files and logs have to be excluded from normal TSM Client backup). Good luck! Grigori G. Solonovitch Senior Technical Architect Information Technology Bank of Kuwait and Middle East http://www.bkme.com Phone: (+965) 2231-2274 Mobile: (+965) 99798073 E-Mail: g.solonovi...@bkme.com Please consider the environment before printing this Email -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of ashish sharma Sent: Thursday, December 17, 2009 12:08 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Alerts in event viewer Hello, I want to backup my exchange server using TDP. The quesion i am having is that , will i get alerts related to log files in the event viewer or there will be no alert? When i use simple BA client , my event viewer is full of alerts due to failed backup of log files -- Best Regards Ashish Sharma ST Microelectronics Ltd. 919717003853 Please consider the environment before printing this Email. This email message and any attachments transmitted with it may contain confidential and proprietary information, intended only for the named recipient(s). If you have received this message in error, or if you are not the named recipient(s), please delete this email after notifying the sender immediately. BKME cannot guarantee the integrity of this communication and accepts no liability for any damage caused by this email or its attachments due to viruses, any other defects, interception or unauthorized modification. The information, views, opinions and comments of this message are those of the individual and not necessarily endorsed by BKME. -- Best Regards Ashish Sharma ST Microelectronics Ltd. 919717003853 This email message and any attachments transmitted with it may contain confidential and proprietary information, intended only for the named recipient(s). If you have received this message in error, or if you are not the named recipient(s), please delete this email after notifying the sender immediately. BKME cannot guarantee the integrity of this communication and accepts no liability for any damage caused by this email or its attachments due to viruses, any other defects, interception or unauthorized modification. The information, views, opinions and comments of this message are those of the individual and not necessarily endorsed by BKME.
Re: Alerts in event viewer
Hi, Using the TDP its ment for doing online (thus changing) back-ups. It will let you back-up the database and log files, without giving errors if succesfull. In case of errors it will be logged into the log files and windows event viewer. Based on the error message corrective actions can be taken. As noted, the files back-upped in the TDP back-up should be excluded from normal file system back-ups. Kind regards, Karel -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of ashish sharma Sent: donderdag 17 december 2009 11:30 To: ADSM-L@VM.MARIST.EDU Subject: Re: Alerts in event viewer Hello Grigori, I know TDP can backup exchange but just want to confirm that does it gives any type of alerts in event viewer while backing up changing files? On Thu, Dec 17, 2009 at 3:34 PM, Grigori Solonovitch g.solonovi...@bkme.com wrote: You have two options: 1) stop Exchange Server and use TSM Client to make offline backup; 2) install TDP for SQL and make online backups for Exchange database (database files and logs have to be excluded from normal TSM Client backup). Good luck! Grigori G. Solonovitch Senior Technical Architect Information Technology Bank of Kuwait and Middle East http://www.bkme.com Phone: (+965) 2231-2274 Mobile: (+965) 99798073 E-Mail: g.solonovi...@bkme.com Please consider the environment before printing this Email -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of ashish sharma Sent: Thursday, December 17, 2009 12:08 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Alerts in event viewer Hello, I want to backup my exchange server using TDP. The quesion i am having is that , will i get alerts related to log files in the event viewer or there will be no alert? When i use simple BA client , my event viewer is full of alerts due to failed backup of log files -- Best Regards Ashish Sharma ST Microelectronics Ltd. 919717003853 Please consider the environment before printing this Email. This email message and any attachments transmitted with it may contain confidential and proprietary information, intended only for the named recipient(s). If you have received this message in error, or if you are not the named recipient(s), please delete this email after notifying the sender immediately. BKME cannot guarantee the integrity of this communication and accepts no liability for any damage caused by this email or its attachments due to viruses, any other defects, interception or unauthorized modification. The information, views, opinions and comments of this message are those of the individual and not necessarily endorsed by BKME. -- Best Regards Ashish Sharma ST Microelectronics Ltd. 919717003853 ÿþD i t b e r i c h t i s v e r t r o u w e l i j k e n k a n g e h e i m e i n f o r m a t i e b e v a t t e n e n k e l b e s t e m d v o o r d e g e a d r e s s e e r d e . I n d i e n d i t b e r i c h t n i e t v o o r u i s b e s t e m d , v e r z o e k e n w i j u d i t o n m i d d e l l i j k a a n o n s t e m e l d e n e n h e t b e r i c h t t e v e r n i e t i g e n . A a n g e z i e n d e i n t e g r i t e i t v a n h e t b e r i c h t n i e t v e i l i g g e s t e l d i s m i d d e l s v e r z e n d i n g v i a i n t e r n e t , k a n A t o s O r i g i n n i e t a a n s p r a k e l i j k w o r d e n g e h o u d e n v o o r d e i n h o u d d a a r v a n . H o e w e l w i j o n s i n s p a n n e n e e n v i r u s v r i j n e t w e r k t e h a n t e r e n , g e v e n w i j g e e n e n k e l e g a r a n t i e d a t d i t b e r i c h t v i r u s v r i j i s , n o c h a a n v a a r d e n w i j e n i g e a a n s p r a k e l i j k h e i d v o o r d e m o g e l i j k e a a n w e z i g h e i d v a n e e n v i r u s i n d i t b e r i c h t . O p a l o n z e r e c h t s v e r h o u d i n g e n , a a n b i e d i n g e n e n o v e r e e n k o m s t e n w a a r o n d e r A t o s O r i g i n g o e d e r e n e n / o f d i e n s t e n l e v e r t z i j n m e t u i t s l u i t i n g v a n a l l e a n d e r e v o o r w a a r d e n d e L e v e r i n g s v o o r w a a r d e n v a n A t o s O r i g i n v a n t o e p a s s i n g . D e z e w o r d e n u o p a a n v r a a g d i r e c t k o s t e l o o s t o e g e z o n d e n . T h i s e - m a i l a n d t h e d o c u m e n t s a t t a c h e d a r e c o n f i d e n t i a l a n d i n t e n d e d s o l e l y f o r t h e a d d r e s s e e ; i t m a y a l s o b e p r i v i l e g e d . I f
Re: [adsm] Netware restore problem/question
Bill, I'd be suspicious of a Java issue...are you seeing the contents of other directories? -Lloyd On Wed, 16 Dec 2009 14:18:02 -0500 Bill Boyer bjdbo...@verizon.net wrote: Netware 6.0 server running TSM client 5.2.5. The user is using the web client to restore some files in a directory. That directory is not shown/listed. Even using the show active/inactive option. Looking in the dsmsched.log file, I can see that files are actively being backed up from that directory as current as of last night. I think my question is.will the TSM web client only display directories/files that the current user can restore based on permission? And is the web client using the saved (NWPFILE) information? TIA, Bill Boyer --
Re: TDP SQL connection error
Mario, Not sure if this is related, but if you are doing a scripted install, I have seen problems (specifically at tdp 5.5.2.0) where the scripted install appears to work correctly, but these type of errors pop up when you try to run a backup. the cause is 3 prereqs that the scripted install does not check or install. If you run the install/upgrade manually, the prereqs will be displayed and you can choose to have them installed for you. After that everything will work. BTW, my SQLServer engineer swears that these prereqs are in place prior to my install, but for whatever reason the tdp install doesn't recognize them until it installs them itself. -steve -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Sanju Chacko Sent: Wednesday, December 16, 2009 10:50 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TDP SQL connection error This error usually comes when there is an issue with pre-reqs install. Did you try repair on TDP? Thanks, Sanju -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Mario Behring Sent: Thursday, December 17, 2009 12:52 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TDP SQL connection error Hi list, I´ve installed TDP for SQL 5.5.1 on a Windows 2008 Server with Microsoft SQL Server 2008. I am getting the error below when trying to connect the TDP for SQL agent using thetdpsqlc query SQL command: C:\Program Files\Tivoli\TSM\TDPSqltdpsqlc query SQL IBM Tivoli Storage Manager for Databases: Data Protection for Microsoft SQL Server Version 5, Release 5, Level 0.0 (C) Copyright IBM Corporation 1997, 2007. All rights reserved. Connecting to SQL Server, please wait... ACO5422E Received the following from the MS SQL server: Could not load file or assembly 'Microsoft.SqlServer.Smo, Version=9.0.242.0, Culture=neutral, Public KeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified. The tdpsqlc query tsm command connnects to the TSM Server without errors. I´ve already searched the Microsoft website and instaleld the Microsoft SQL Server 2008 Management Objects package.but the error remains. Mario - Please see the following link for the BlueCross BlueShield of Tennessee E-mail disclaimer: http://www.bcbst.com/email_disclaimer.shtm
Re: TSM Client Schedules failing...
On Dec 17, 2009, at 12:03 AM, Kiran-Systems wrote: I am using TSM Server and client V5.5.0.0. My schedules are getting failed with the following error. ANS4008E Error processing '/vol01': file is temporarily unavailable I am backing up file server with GPFS file system on RHEL. That seems to be a gross problem which, as such, should be readily identifiable. Check your /var/log/messages log for indications, as well as dsmerror.log. Look back to your last successful backups from this file system and see what changed since then. Check whether the same UID performing the backup can traverse the file system at the OS level. Look for problems with the way the file system was mounted. And, of course, look for impeding locks. Also, note that you are running base level TSM software, which is a Bad Idea when maintenance is available, where odd problems can be experienced for lack of software updates. Richard Sims
Backing up just one folder (again)
I'd like to raise once more a question that I'd previously asked here http://www.mail-archive.com/adsm-l@vm.marist.edu/msg80653.html How do I backup just one specific location from a drive attached to a Windows PC? In the above mentioned thread two ways were suggested: 1. Heinz Flemming suggested to construct an exclude list in the way as shown below. 2. Howard Coles suggested to create a different simpler construction in the form: EXCLUDE C:\...\* INCLUDE C:\backmeup\...\* 3. Richard Sims advised to create adhoc client schedule with explicit inc c:\backmeup. The first approach is good in that it's very targeted and backs up only what's required, nothing else. The downside is that the the creation of such exclude list is extremely tedious task. Recently I was requested to back up a list of 5 different folders from drive E:. Just look at the monstrous exclude list that I had to create in order to get the job done! Of course, this can be scripted but then another question arises of processing efficiency of such lengthy exclude-include lists. I don't event know how to measure it. The second approach is much more laconic but the downside is that is picks up each and every directory on the drive, and if the target drive contains deeply nested hierarchy of folders that can add up to database bloat. The third approach is more seemingly more straightforward, but seems to be impractical on larger scale. Do I really want to create and maintain dozens of adhoc schedules for dozens of different clients? This would also place the burden of adopting the schedules for new/removed paths on me instead of local Windows admin. On UNIX machines there is a dsm.sys option - VIRTUALMOUNTPOINT that does exactly that - defines a virtual mount point for a file system if you want to consider files for backup that begin with a specific directory within that file system. I couldn't find equivalent option for Windows client. While writing the monster exclude below, I was telling myself: There must be a better way.. EXCLUDE.DIR E:\reports_lectures_models[ abcdefghijklmnopqrstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\reports_lectures_model[ abcdefghijklmnopqrtuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\reports_lectures_mode[ abcdefghijkmnopqrstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\reports_lectures_mod[ abcdfghijklmnopqrstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\reports_lectures_mo[ abcefghijklmnopqrstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\reports_lectures_m[ abcdefghijklmnpqrstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\reports_lectures_[ abcdefghijklnopqrstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\reports_lectures[ abcdefghijklmnopqrstuvwxyz01234567...@#$%^()+=-.`~§±]* EXCLUDE.DIR E:\reports_lecture[ abcdefghijklmnopqrtuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\reports_lectur[ abcdfghijklmnopqrstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\reports_lectu[ abcdefghijklmnopqstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\reports_lect[ abcdefghijklmnopqrstvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\reports_lec[ abcdefghijklmnopqrsuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\reports_le[ abdefghijklmnopqrstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\reports_l[ abcdfghijklmnopqrstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\reports_[ abcdefghijkmnopqrstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\reports[ abcdefghijklmnopqrstuvwxyz01234567...@#$%^()+=-.`~§±]* EXCLUDE.DIR E:\report[ abcdefghijklmnopqrtuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\repor[ abcdefghijklmnopqrsuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\repo[ abcdefghijklmnopqstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\rep[ abcdefghijklmnpqrstuvwxyz01234567...@#$%^()_+=-.`~§±]* *EXCLUDE.DIR E:\re[ abcdefghijklmnoqrstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\r[ abcdfghijklmnopqrstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\general[ abcdefghijklmnopqrstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\genera[ abcdefghijkmnopqrstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\gener[ bcdefghijklmnopqrstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\gene[ abcdefghijklmnopqstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\gen[ abcdfghijklmnopqrstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\ge[ abcdefghijklmopqrstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\g[ abcdfghijklmnopqrstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\experiments[ abcdefghijklmnopqrstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\experiment[ abcdefghijklmnopqrtuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\experimen[ abcdefghijklmnopqrsuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\experime[ abcdefghijklmopqrstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\experim[ abcdfghijklmnopqrstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\experi[ abcdefghijklnopqrstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR
Re: TSM 5.3.4 Policy problem
Zhang, It is good practice to validate the policyset before activating it. After updating the copygroup, run validate po DOMAIN_NAME POLICYSET_NAME. BERTAUT TCHUISE TSM/NetApp Storage Administrator Legg Mason Technology Services *410-580-7032 btchu...@leggmason.com -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of William ZHANG Sent: Thursday, December 17, 2009 12:24 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM 5.3.4 Policy problem Hello Skylar, Do you mean, update copygroup DOM_SRV SET_SRV MC_90DAYS STANDARD verexists=60 verdeleted=60 retextra=60 retonly=60 active policyset DOM_SRV SET_SRV Then, update copygroup DOM_SRV ACTIVE MC_90DAYS STANDARD verexists=60 verdeleted=60 retextra=60 retonly=60 active policyset DOM_SRV ACTIVE Right? tsm: SHITSM01q copygroup PolicyPolicyMgmt Copy Versions Versions Retain Retain DomainSet Name Class Group Data DataExtraOnly NameName NameExists Deleted Versions Version - - - - --- DOM_SRV ACTIVEMC_90DAYS STANDARD 2 1 90 90 DOM_SRV SET_SRV MC_90DAYS STANDARD 2 1 60 60 STANDARD ACTIVESTANDARD STANDARD 2 1 30 60 STANDARD STANDARD STANDARD STANDARD 2 1 30 60 -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Skylar Thompson Sent: Thursday, December 17, 2009 12:44 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM 5.3.4 Policy problem You actually want to modify the copy group from your inactive policy set. In most cases this should be STANDARD rather than ACTIVE. You then swap STANDARD and ACTIVE with ACTIVATE POLICYSET DOM_SRV ACTIVE. William ZHANG wrote: Hello, Thanks Grigori,Karel, I want to retain deleted data 60days in TSM. So should I input: Update copygroup DOM_SRV ACTIVE MC_90DAYS type=backup verexists=60 verdeleted=60 retextra=60 retonly=60 But got error, said, active policy cannot be modified, So could anyone can tell me how can I modified my policy set and copygroup so that I can get what I want? Many thanks! William -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Bos, Karel Sent: Wednesday, December 16, 2009 6:27 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM 5.3.4 Policy problem I would take a look at the RETExtra/Only parm of the copy group, they manage the data by date instead of versions. Managing retention time using the versions parameters can give some unintended results (an extra backup of a changed file will reduce the period you can restore from for instance). Kind regards, Karel -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Grigori Solonovitch Sent: woensdag 16 december 2009 10:31 To: ADSM-L@VM.MARIST.EDU Subject: Re: TSM 5.3.4 Policy problem Yes, but it is better to use 60 instead of 59. Grigori G. Solonovitch Senior Technical Architect Information Technology Bank of Kuwait and Middle East http://www.bkme.com Phone: (+965) 2231-2274 Mobile: (+965) 99798073 E-Mail: g.solonovi...@bkme.com Please consider the environment before printing this Email -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of William ZHANG Sent: Wednesday, December 16, 2009 12:28 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TSM 5.3.4 Policy problem Hello All, I meet a problem, If I want to retain deleted data 60days in TSM, what commands should I input to modified policy in TSM? should the versions data exists and versions data deleted be modified from 2 to 59 , right? These are my configuration: --- tsm: SHITSM01q copygroup PolicyPolicyMgmt Copy Versions Versions Retain Retain DomainSet Name Class Group Data DataExtraOnly NameName NameExists Deleted Versions Version - - - - --- DOM_SRV ACTIVEMC_90DAYS STANDARD 2 1 90 90 DOM_SRV SET_SRV MC_90DAYS STANDARD90 90 90 90 STANDARD ACTIVESTANDARD STANDARD 2 1 30 60 STANDARD STANDARD STANDARD STANDARD 2 1 30 60
Re: Backing up just one folder (again)
Michael You could use windows utilities/powershell to list the entire directory tree that you want backed up and save the list in a file, then feed this list into the dsmc incremental command with the -filelist option. Regards Steve Steven Harris TSM Admin, Sydney Australia Michael Green wrote: I'd like to raise once more a question that I'd previously asked here http://www.mail-archive.com/adsm-l@vm.marist.edu/msg80653.html How do I backup just one specific location from a drive attached to a Windows PC? In the above mentioned thread two ways were suggested: 1. Heinz Flemming suggested to construct an exclude list in the way as shown below. 2. Howard Coles suggested to create a different simpler construction in the form: EXCLUDE C:\...\* INCLUDE C:\backmeup\...\* 3. Richard Sims advised to create adhoc client schedule with explicit inc c:\backmeup. The first approach is good in that it's very targeted and backs up only what's required, nothing else. The downside is that the the creation of such exclude list is extremely tedious task. Recently I was requested to back up a list of 5 different folders from drive E:. Just look at the monstrous exclude list that I had to create in order to get the job done! Of course, this can be scripted but then another question arises of processing efficiency of such lengthy exclude-include lists. I don't event know how to measure it. The second approach is much more laconic but the downside is that is picks up each and every directory on the drive, and if the target drive contains deeply nested hierarchy of folders that can add up to database bloat. The third approach is more seemingly more straightforward, but seems to be impractical on larger scale. Do I really want to create and maintain dozens of adhoc schedules for dozens of different clients? This would also place the burden of adopting the schedules for new/removed paths on me instead of local Windows admin. On UNIX machines there is a dsm.sys option - VIRTUALMOUNTPOINT that does exactly that - defines a virtual mount point for a file system if you want to consider files for backup that begin with a specific directory within that file system. I couldn't find equivalent option for Windows client. While writing the monster exclude below, I was telling myself: There must be a better way.. EXCLUDE.DIR E:\reports_lectures_models[ abcdefghijklmnopqrstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\reports_lectures_model[ abcdefghijklmnopqrtuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\reports_lectures_mode[ abcdefghijkmnopqrstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\reports_lectures_mod[ abcdfghijklmnopqrstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\reports_lectures_mo[ abcefghijklmnopqrstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\reports_lectures_m[ abcdefghijklmnpqrstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\reports_lectures_[ abcdefghijklnopqrstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\reports_lectures[ abcdefghijklmnopqrstuvwxyz01234567...@#$%^()+=-.`~§±]* EXCLUDE.DIR E:\reports_lecture[ abcdefghijklmnopqrtuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\reports_lectur[ abcdfghijklmnopqrstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\reports_lectu[ abcdefghijklmnopqstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\reports_lect[ abcdefghijklmnopqrstvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\reports_lec[ abcdefghijklmnopqrsuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\reports_le[ abdefghijklmnopqrstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\reports_l[ abcdfghijklmnopqrstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\reports_[ abcdefghijkmnopqrstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\reports[ abcdefghijklmnopqrstuvwxyz01234567...@#$%^()+=-.`~§±]* EXCLUDE.DIR E:\report[ abcdefghijklmnopqrtuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\repor[ abcdefghijklmnopqrsuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\repo[ abcdefghijklmnopqstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\rep[ abcdefghijklmnpqrstuvwxyz01234567...@#$%^()_+=-.`~§±]* *EXCLUDE.DIR E:\re[ abcdefghijklmnoqrstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\r[ abcdfghijklmnopqrstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\general[ abcdefghijklmnopqrstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\genera[ abcdefghijkmnopqrstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\gener[ bcdefghijklmnopqrstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\gene[ abcdefghijklmnopqstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\gen[ abcdfghijklmnopqrstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\ge[ abcdefghijklmopqrstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\g[ abcdfghijklmnopqrstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\experiments[ abcdefghijklmnopqrstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\experiment[ abcdefghijklmnopqrtuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR
TDP for Exchange AD error
Hi list, I´ve just installed the TDP for Exchange 6.1.1.0 on a Windows 2003 Server running MSCS.when trying to verify my installation I got the error message below: C:\Program Files\Tivoli\TSM\TDPExchangetdpexcc query exchange /excserv=excluster IBM Tivoli Storage Manager for Mail: Data Protection for Microsoft Exchange Server Version 6, Release 1, Level 1.0 (C) Copyright IBM Corporation 1998, 2009. All rights reserved. Querying Exchange Server to gather storage group information, please wait... The operation could not be performed because object 'EXCLUSTER' could not be found on domain controller 'domain.controller.local'. The object 'EXCLUSTER' is the actual Cluster Nodename, not the machine hostname, as recommended by TDP for Exchange Installation and Configuration Guide. This is a 2 node MSCS simple configuration. I´ve checked the AD and the object exists there. Any ideas? Mario
Re: TDP for Exchange AD error
Mario With Exchange 2007, the user running the backups has to have Exchange admin rights defined in AD. Local System is no longer enough. Check that. Regards Steve Steven Harris TSM Admin Sydney Australia Mario Behring wrote: Hi list, I´ve just installed the TDP for Exchange 6.1.1.0 on a Windows 2003 Server running MSCS.when trying to verify my installation I got the error message below: C:\Program Files\Tivoli\TSM\TDPExchangetdpexcc query exchange /excserv=excluster IBM Tivoli Storage Manager for Mail: Data Protection for Microsoft Exchange Server Version 6, Release 1, Level 1.0 (C) Copyright IBM Corporation 1998, 2009. All rights reserved. Querying Exchange Server to gather storage group information, please wait... The operation could not be performed because object 'EXCLUSTER' could not be found on domain controller 'domain.controller.local'. The object 'EXCLUSTER' is the actual Cluster Nodename, not the machine hostname, as recommended by TDP for Exchange Installation and Configuration Guide. This is a 2 node MSCS simple configuration. I´ve checked the AD and the object exists there. Any ideas? Mario No virus found in this incoming message. Checked by AVG - www.avg.com Version: 9.0.716 / Virus Database: 270.14.111/2569 - Release Date: 12/17/09 06:52:00
Re: Alerts in event viewer
Just a slight correction here In order to perform online backups of your Exchange Server, you should be using Data Protection for Exchange not Data Protection for SQL. Thanks, Del ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 12/17/2009 05:04:32 AM: [image removed] Re: Alerts in event viewer Grigori Solonovitch to: ADSM-L 12/17/2009 05:06 AM Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU Please respond to ADSM: Dist Stor Manager You have two options: 1) stop Exchange Server and use TSM Client to make offline backup; 2) install TDP for SQL and make online backups for Exchange database (database files and logs have to be excluded from normal TSM Client backup). Good luck!
Re: Alerts in event viewer
yes, i plan to use TDP for microsoft exchange server On Thu, Dec 17, 2009 at 8:41 PM, Del Hoobler hoob...@us.ibm.com wrote: Just a slight correction here In order to perform online backups of your Exchange Server, you should be using Data Protection for Exchange not Data Protection for SQL. Thanks, Del ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 12/17/2009 05:04:32 AM: [image removed] Re: Alerts in event viewer Grigori Solonovitch to: ADSM-L 12/17/2009 05:06 AM Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU Please respond to ADSM: Dist Stor Manager You have two options: 1) stop Exchange Server and use TSM Client to make offline backup; 2) install TDP for SQL and make online backups for Exchange database (database files and logs have to be excluded from normal TSM Client backup). Good luck! -- Best Regards Ashish Sharma ST Microelectronics Ltd. 919717003853
Re: TSM 5.3.4 Policy problem
Activate makes the activated policy set the active one by copying that policy set into active. It does not change the policy set that is activated. Each domain has only one ACTIVE policy set. The command ACTIVATE POLICYSET DOM_SRC STANDARD will copy the policy set STANDARD into DOM_SRC ACTIVE. but since the query didn't show a STANDARD policy set in the domain DOM_SRC, with the desired copygroup, there most likely is not a STANDARD policy set in that domain, and the command will fail. Domain DOM_SRC has 2 policy sets with copygroups, ACTIVE, which is a copy of whatever policy set was last activated, and SET_SRV, which is presumably the policy last activated since it is the only one in DOM_SRC with copygroups defined. To update the ACTIVE policy set in domain DOM_SRC, issue the update commands for the management classes and copygroups in DOM_SRC SET_SRV, then issue the VALIDATE (to see any possible issues) and ACTIVATE commands for DOM_SRC SET_SRV - ACTIVATE POLICYSET DOM_SRC SET_SRV - this will copy the current contents of the SET_SRV policy into ACTIVE. For the domain STANDARD, if the changes are needed there also, you would do the same thing for policy set STANDARD, so the commands would be issued to STANDARD STANDARD The 6.1 Administration Center has some features to assist in managing domains. It hides policy sets from the user, and shows changes since last activation in the management class notebook, or in the Manage Pending Changes form. You can make the changes to the management classes using the management class notebook, then activate from the Manage Pending Changes actions, which will do the validate before activation, and if there are any validation messages, display them and give you an option to continue with activation or resolve the issues. Carol Trible IBM Tivoli Storage Manager Development tri...@us.ibm.com Skylar Thompson skyl...@u.washington.edu Yeah, I typo'd the activate statement. It should be: ACTIVATE POLICYSET DOM_SRC STANDARD This will actually rename STANDARD to ACTIVE, and ACTIVE to STANDARD. William ZHANG wrote: Hello Skylar, Do you mean, update copygroup DOM_SRV SET_SRV MC_90DAYS STANDARD verexists=60 verdeleted=60 retextra=60 retonly=60 active policyset DOM_SRV SET_SRV Then, update copygroup DOM_SRV ACTIVE MC_90DAYS STANDARD verexists=60 verdeleted=60 retextra=60 retonly=60 active policyset DOM_SRV ACTIVE Right? tsm: SHITSM01q copygroup PolicyPolicyMgmt Copy Versions Versions Retain Retain DomainSet Name Class Group Data DataExtraOnly NameName NameExists Deleted Versions Version - - - - --- DOM_SRV ACTIVEMC_90DAYS STANDARD 2 1 90 90 DOM_SRV SET_SRV MC_90DAYS STANDARD 2 1 60 60 STANDARD ACTIVESTANDARD STANDARD 2 1 30 60 STANDARD STANDARD STANDARD STANDARD 2 1 30 60 -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Skylar Thompson Sent: Thursday, December 17, 2009 12:44 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM 5.3.4 Policy problem You actually want to modify the copy group from your inactive policy set. In most cases this should be STANDARD rather than ACTIVE. You then swap STANDARD and ACTIVE with ACTIVATE POLICYSET DOM_SRV ACTIVE. William ZHANG wrote: Hello, Thanks Grigori,Karel, I want to retain deleted data 60days in TSM. So should I input: Update copygroup DOM_SRV ACTIVE MC_90DAYS type=backup verexists=60 verdeleted=60 retextra=60 retonly=60 But got error, said, active policy cannot be modified, So could anyone can tell me how can I modified my policy set and copygroup so that I can get what I want? Many thanks! William -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Bos, Karel Sent: Wednesday, December 16, 2009 6:27 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM 5.3.4 Policy problem I would take a look at the RETExtra/Only parm of the copy group, they manage the data by date instead of versions. Managing retention time using the versions parameters can give some unintended results (an extra backup of a changed file will reduce the period you can restore from for instance). Kind regards, Karel -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Grigori Solonovitch Sent: woensdag 16 december 2009 10:31 To: ADSM-L@VM.MARIST.EDU Subject: Re: TSM 5.3.4 Policy problem Yes, but it is better to use 60 instead of 59. Grigori G. Solonovitch Senior Technical Architect
Re: TSM 5.3.4 Policy problem
If you REALLY want to keep data in TSM for 60 days, you need Update copygroup DOM_SRV ACTIVE MC_90DAYS type=backup verexists=nolimit verdeleted=nolimit retextra=60 retonly=60 Otherwise, multiple backups run during a day can result in files expiring in less than 60 days. David William ZHANG william.zh...@st.com 12/16/2009 11:27 PM Hello, Thanks Grigori,Karel, I want to retain deleted data 60days in TSM. So should I input: Update copygroup DOM_SRV ACTIVE MC_90DAYS type=backup verexists=60 verdeleted=60 retextra=60 retonly=60 But got error, said, active policy cannot be modified, So could anyone can tell me how can I modified my policy set and copygroup so that I can get what I want? Many thanks! William -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Bos, Karel Sent: Wednesday, December 16, 2009 6:27 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM 5.3.4 Policy problem I would take a look at the RETExtra/Only parm of the copy group, they manage the data by date instead of versions. Managing retention time using the versions parameters can give some unintended results (an extra backup of a changed file will reduce the period you can restore from for instance). Kind regards, Karel -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Grigori Solonovitch Sent: woensdag 16 december 2009 10:31 To: ADSM-L@VM.MARIST.EDU Subject: Re: TSM 5.3.4 Policy problem Yes, but it is better to use 60 instead of 59. Grigori G. Solonovitch Senior Technical Architect Information Technology Bank of Kuwait and Middle East http://www.bkme.com Phone: (+965) 2231-2274 Mobile: (+965) 99798073 E-Mail: g.solonovi...@bkme.com Please consider the environment before printing this Email -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of William ZHANG Sent: Wednesday, December 16, 2009 12:28 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TSM 5.3.4 Policy problem Hello All, I meet a problem, If I want to retain deleted data 60days in TSM, what commands should I input to modified policy in TSM? should the versions data exists and versions data deleted be modified from 2 to 59 , right? These are my configuration: --- tsm: SHITSM01q copygroup PolicyPolicyMgmt Copy Versions Versions Retain Retain DomainSet Name Class Group Data DataExtraOnly NameName NameExists Deleted Versions Version - - - - --- DOM_SRV ACTIVEMC_90DAYS STANDARD 2 1 90 90 DOM_SRV SET_SRV MC_90DAYS STANDARD90 90 90 90 STANDARD ACTIVESTANDARD STANDARD 2 1 30 60 STANDARD STANDARD STANDARD STANDARD 2 1 30 60 --- tsm: SHITSM01q domain f=d Policy Domain Name: DOM_SRV Activated Policy Set: SET_SRV Activation Date/Time: 05/10/2007 11:09:44 Days Since Activation: 951 Activated Default Mgmt Class: MC_90DAYS Number of Registered Nodes: 3 Description: Backup Retention (Grace Period): 60 Archive Retention (Grace Period): 1,095 Last Update by (administrator): ADMIN Last Update Date/Time: 07/30/2009 11:30:05 Managing profile: Changes Pending: Yes Policy Domain Name: STANDARD Activated Policy Set: STANDARD Activation Date/Time: 05/09/2007 12:41:05 Days Since Activation: 952 Activated Default Mgmt Class: STANDARD Number of Registered Nodes: 1 Description: Installed default policy domain. Backup Retention (Grace Period): 30 Archive Retention (Grace Period): 365 Last Update by (administrator): SERVER_CONSOLE Last Update Date/Time: 05/09/2007 12:41:05 Managing profile: Changes Pending: No --- tsm: SHITSM01q mgmtclass PolicyPolicyMgmt Default Description DomainSet Name Class Mgmt NameName Class ? - - - - DOM_SRV ACTIVEMC_90DAYS Yes DOM_SRV SET_SRV MC_90DAYS Yes STANDARD ACTIVESTANDARD Yes Installed default management class. STANDARD
TDPExch cannot find hostname on domain controller
Hi list, I´ve just installed the TDP for Exchange 6.1.1.0 on a Windows 2003 Server running MSCS.when trying to verify my installation I got the error message below: C:\Program Files\Tivoli\TSM\TDPExchangetdpexcc query exchange /excserv=excluster IBM Tivoli Storage Manager for Mail: Data Protection for Microsoft Exchange Server Version 6, Release 1, Level 1.0 (C) Copyright IBM Corporation 1998, 2009. All rights reserved. Querying Exchange Server to gather storage group information, please wait... The operation could not be performed because object 'EXCLUSTER' could not be found on domain controller 'domain.controller.local'. The object 'EXCLUSTER' is the actual Cluster Nodename, not the machine hostname, as recommended by TDP for Exchange Installation and Configuration Guide. This is a 2 node MSCS simple configuration. I´ve checked the AD and the object exists there. Any ideas? Mario
Re: TSM 5.3.4 Policy problem
Erm, can't update the active policy set :) Update copygroup DOM_SRV SET_SRV MC_90DAYS type=backup verexists=nolimit verdeleted=nolimit retextra=60 retonly=60 Validate and activate the set afterwards. Kind regards, Karel -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of David E Ehresman Sent: donderdag 17 december 2009 17:24 To: ADSM-L@VM.MARIST.EDU Subject: Re: TSM 5.3.4 Policy problem If you REALLY want to keep data in TSM for 60 days, you need Update copygroup DOM_SRV ACTIVE MC_90DAYS type=backup verexists=nolimit verdeleted=nolimit retextra=60 retonly=60 Otherwise, multiple backups run during a day can result in files expiring in less than 60 days. David William ZHANG william.zh...@st.com 12/16/2009 11:27 PM Hello, Thanks Grigori,Karel, I want to retain deleted data 60days in TSM. So should I input: Update copygroup DOM_SRV ACTIVE MC_90DAYS type=backup verexists=60 verdeleted=60 retextra=60 retonly=60 But got error, said, active policy cannot be modified, So could anyone can tell me how can I modified my policy set and copygroup so that I can get what I want? Many thanks! William -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Bos, Karel Sent: Wednesday, December 16, 2009 6:27 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM 5.3.4 Policy problem I would take a look at the RETExtra/Only parm of the copy group, they manage the data by date instead of versions. Managing retention time using the versions parameters can give some unintended results (an extra backup of a changed file will reduce the period you can restore from for instance). Kind regards, Karel -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Grigori Solonovitch Sent: woensdag 16 december 2009 10:31 To: ADSM-L@VM.MARIST.EDU Subject: Re: TSM 5.3.4 Policy problem Yes, but it is better to use 60 instead of 59. Grigori G. Solonovitch Senior Technical Architect Information Technology Bank of Kuwait and Middle East http://www.bkme.com Phone: (+965) 2231-2274 Mobile: (+965) 99798073 E-Mail: g.solonovi...@bkme.com Please consider the environment before printing this Email -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of William ZHANG Sent: Wednesday, December 16, 2009 12:28 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TSM 5.3.4 Policy problem Hello All, I meet a problem, If I want to retain deleted data 60days in TSM, what commands should I input to modified policy in TSM? should the versions data exists and versions data deleted be modified from 2 to 59 , right? These are my configuration: --- tsm: SHITSM01q copygroup PolicyPolicyMgmt Copy Versions Versions Retain Retain DomainSet Name Class Group Data DataExtraOnly NameName NameExists Deleted Versions Version - - - - --- DOM_SRV ACTIVEMC_90DAYS STANDARD 2 1 90 90 DOM_SRV SET_SRV MC_90DAYS STANDARD90 90 90 90 STANDARD ACTIVESTANDARD STANDARD 2 1 30 60 STANDARD STANDARD STANDARD STANDARD 2 1 30 60 --- tsm: SHITSM01q domain f=d Policy Domain Name: DOM_SRV Activated Policy Set: SET_SRV Activation Date/Time: 05/10/2007 11:09:44 Days Since Activation: 951 Activated Default Mgmt Class: MC_90DAYS Number of Registered Nodes: 3 Description: Backup Retention (Grace Period): 60 Archive Retention (Grace Period): 1,095 Last Update by (administrator): ADMIN Last Update Date/Time: 07/30/2009 11:30:05 Managing profile: Changes Pending: Yes Policy Domain Name: STANDARD Activated Policy Set: STANDARD Activation Date/Time: 05/09/2007 12:41:05 Days Since Activation: 952 Activated Default Mgmt Class: STANDARD Number of Registered Nodes: 1 Description: Installed default policy domain. Backup Retention (Grace Period): 30 Archive Retention (Grace Period): 365 Last Update by (administrator): SERVER_CONSOLE Last Update Date/Time: 05/09/2007 12:41:05 Managing profile: Changes Pending: No --- tsm: SHITSM01q mgmtclass PolicyPolicyMgmt Default
Re: Backing up just one folder (again)
Hi, on *NIX you have an option to use VIRTUALMOUNTPOINT for this. There is no such thing in Windows. So if you cannot go through the door, try the window :) Share the folder you want to backup and use the share as a DOMAIN parameter. Example: machine name: WinPC folder: e:\whatever\myfolder shared as backupme DOMAIN \\WinPC\backupme Your scheduler must run under account with rights to access the share (so not the LocalSystem) Harry From: Michael Green mishagr...@gmail.com To: ADSM-L@VM.MARIST.EDU Sent: Thu, December 17, 2009 1:43:08 PM Subject: [ADSM-L] Backing up just one folder (again) I'd like to raise once more a question that I'd previously asked here http://www.mail-archive.com/adsm-l@vm.marist.edu/msg80653.html How do I backup just one specific location from a drive attached to a Windows PC? In the above mentioned thread two ways were suggested: 1. Heinz Flemming suggested to construct an exclude list in the way as shown below. 2. Howard Coles suggested to create a different simpler construction in the form: EXCLUDE C:\...\* INCLUDE C:\backmeup\...\* 3. Richard Sims advised to create adhoc client schedule with explicit inc c:\backmeup. The first approach is good in that it's very targeted and backs up only what's required, nothing else. The downside is that the the creation of such exclude list is extremely tedious task. Recently I was requested to back up a list of 5 different folders from drive E:. Just look at the monstrous exclude list that I had to create in order to get the job done! Of course, this can be scripted but then another question arises of processing efficiency of such lengthy exclude-include lists. I don't event know how to measure it. The second approach is much more laconic but the downside is that is picks up each and every directory on the drive, and if the target drive contains deeply nested hierarchy of folders that can add up to database bloat. The third approach is more seemingly more straightforward, but seems to be impractical on larger scale. Do I really want to create and maintain dozens of adhoc schedules for dozens of different clients? This would also place the burden of adopting the schedules for new/removed paths on me instead of local Windows admin. On UNIX machines there is a dsm.sys option - VIRTUALMOUNTPOINT that does exactly that - defines a virtual mount point for a file system if you want to consider files for backup that begin with a specific directory within that file system. I couldn't find equivalent option for Windows client. While writing the monster exclude below, I was telling myself: There must be a better way.. EXCLUDE.DIR E:\reports_lectures_models[ abcdefghijklmnopqrstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\reports_lectures_model[ abcdefghijklmnopqrtuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\reports_lectures_mode[ abcdefghijkmnopqrstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\reports_lectures_mod[ abcdfghijklmnopqrstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\reports_lectures_mo[ abcefghijklmnopqrstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\reports_lectures_m[ abcdefghijklmnpqrstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\reports_lectures_[ abcdefghijklnopqrstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\reports_lectures[ abcdefghijklmnopqrstuvwxyz01234567...@#$%^()+=-.`~§±]* EXCLUDE.DIR E:\reports_lecture[ abcdefghijklmnopqrtuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\reports_lectur[ abcdfghijklmnopqrstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\reports_lectu[ abcdefghijklmnopqstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\reports_lect[ abcdefghijklmnopqrstvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\reports_lec[ abcdefghijklmnopqrsuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\reports_le[ abdefghijklmnopqrstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\reports_l[ abcdfghijklmnopqrstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\reports_[ abcdefghijkmnopqrstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\reports[ abcdefghijklmnopqrstuvwxyz01234567...@#$%^()+=-.`~§±]* EXCLUDE.DIR E:\report[ abcdefghijklmnopqrtuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\repor[ abcdefghijklmnopqrsuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\repo[ abcdefghijklmnopqstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\rep[ abcdefghijklmnpqrstuvwxyz01234567...@#$%^()_+=-.`~§±]* *EXCLUDE.DIR E:\re[ abcdefghijklmnoqrstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\r[ abcdfghijklmnopqrstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\general[ abcdefghijklmnopqrstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\genera[ abcdefghijkmnopqrstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\gener[ bcdefghijklmnopqrstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\gene[ abcdefghijklmnopqstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\gen[ abcdfghijklmnopqrstuvwxyz01234567...@#$%^()_+=-.`~§±]*
Re: [adsm] Netware restore problem/question
Yes, just not that specific directory. -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Lloyd Dieter Sent: Thursday, December 17, 2009 6:44 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [adsm] Netware restore problem/question Bill, I'd be suspicious of a Java issue...are you seeing the contents of other directories? -Lloyd On Wed, 16 Dec 2009 14:18:02 -0500 Bill Boyer bjdbo...@verizon.net wrote: Netware 6.0 server running TSM client 5.2.5. The user is using the web client to restore some files in a directory. That directory is not shown/listed. Even using the show active/inactive option. Looking in the dsmsched.log file, I can see that files are actively being backed up from that directory as current as of last night. I think my question is.will the TSM web client only display directories/files that the current user can restore based on permission? And is the web client using the saved (NWPFILE) information? TIA, Bill Boyer --
VMFULL delete
Is there a way to delete a VMFULL backup? For example, a VM full image is taken and some time later, the VM is deleted from the VMware complex. This last backup will never be mark inactive. Is there a way to later delete this backup? It is part of the VMFULL filespace.
Re: Backing up just one folder (again)
Another way, although it may not be practical for you is to create each of these directories on a mount point. Basically take a new disk and mount it in the directory in question and move the data to it. Then you only have to use domain statements to include/exclude file systems. This is the Unix method of mounting disks, but it is available in Windows to get rid of drive letters. Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Michael Green Sent: Thursday, December 17, 2009 6:43 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Backing up just one folder (again) I'd like to raise once more a question that I'd previously asked here http://www.mail-archive.com/adsm-l@vm.marist.edu/msg80653.html How do I backup just one specific location from a drive attached to a Windows PC? In the above mentioned thread two ways were suggested: 1. Heinz Flemming suggested to construct an exclude list in the way as shown below. 2. Howard Coles suggested to create a different simpler construction in the form: EXCLUDE C:\...\* INCLUDE C:\backmeup\...\* 3. Richard Sims advised to create adhoc client schedule with explicit inc c:\backmeup. The first approach is good in that it's very targeted and backs up only what's required, nothing else. The downside is that the the creation of such exclude list is extremely tedious task. Recently I was requested to back up a list of 5 different folders from drive E:. Just look at the monstrous exclude list that I had to create in order to get the job done! Of course, this can be scripted but then another question arises of processing efficiency of such lengthy exclude-include lists. I don't event know how to measure it. The second approach is much more laconic but the downside is that is picks up each and every directory on the drive, and if the target drive contains deeply nested hierarchy of folders that can add up to database bloat. The third approach is more seemingly more straightforward, but seems to be impractical on larger scale. Do I really want to create and maintain dozens of adhoc schedules for dozens of different clients? This would also place the burden of adopting the schedules for new/removed paths on me instead of local Windows admin. On UNIX machines there is a dsm.sys option - VIRTUALMOUNTPOINT that does exactly that - defines a virtual mount point for a file system if you want to consider files for backup that begin with a specific directory within that file system. I couldn't find equivalent option for Windows client. While writing the monster exclude below, I was telling myself: There must be a better way.. EXCLUDE.DIR E:\reports_lectures_models[ abcdefghijklmnopqrstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\reports_lectures_model[ abcdefghijklmnopqrtuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\reports_lectures_mode[ abcdefghijkmnopqrstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\reports_lectures_mod[ abcdfghijklmnopqrstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\reports_lectures_mo[ abcefghijklmnopqrstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\reports_lectures_m[ abcdefghijklmnpqrstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\reports_lectures_[ abcdefghijklnopqrstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\reports_lectures[ abcdefghijklmnopqrstuvwxyz01234567...@#$%^()+=-.`~§±]* EXCLUDE.DIR E:\reports_lecture[ abcdefghijklmnopqrtuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\reports_lectur[ abcdfghijklmnopqrstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\reports_lectu[ abcdefghijklmnopqstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\reports_lect[ abcdefghijklmnopqrstvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\reports_lec[ abcdefghijklmnopqrsuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\reports_le[ abdefghijklmnopqrstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\reports_l[ abcdfghijklmnopqrstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\reports_[ abcdefghijkmnopqrstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\reports[ abcdefghijklmnopqrstuvwxyz01234567...@#$%^()+=-.`~§±]* EXCLUDE.DIR E:\report[ abcdefghijklmnopqrtuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\repor[ abcdefghijklmnopqrsuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\repo[ abcdefghijklmnopqstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\rep[ abcdefghijklmnpqrstuvwxyz01234567...@#$%^()_+=-.`~§±]* *EXCLUDE.DIR E:\re[ abcdefghijklmnoqrstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\r[ abcdfghijklmnopqrstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\general[ abcdefghijklmnopqrstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\genera[ abcdefghijkmnopqrstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\gener[ bcdefghijklmnopqrstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\gene[ abcdefghijklmnopqstuvwxyz01234567...@#$%^()_+=-.`~§±]* EXCLUDE.DIR E:\gen[ abcdfghijklmnopqrstuvwxyz01234567...@#$%^()_+=-.`~§±]*
collocation increases tape mounts while backup
We are using an IBM3584 and don't use any kind of collocation. We have found the migration process from diskpool to tape collocates data by node and therefore already does a decent job of grouping node data together. The only time you may see better performance with collocation is with a server that has alot of little files that change often and those nodes should probably be stored on VTL or DISK rather than tape. +-- |This was sent by jeff.je...@sentry.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +--
Problems with an incremental backup of a file server
Can a normal incremental job run and complete? If you can run a normal backup then uninstall and reinstall the journal. If not see if you can run a Windows Backup. If the WB fails then its an OS problem and not related to TSM. +-- |This was sent by jeff.je...@sentry.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +--
Re: collocation increases tape mounts while backup
In that case you must be using collocation (albeit by accident). You may want to look at group collocation as it sounds like your tapes are probably underutilised. Unless that is you have manly fewer, bigger clients. Steven Langdale Global Information Services EAME SAN/Storage Planning and Implementation ( Phone : +44 (0)1733 584175 ( Mob: +44 (0)7876 216782 ü Conference: +44 (0)208 609 7400 Code: 331817 + Email: steven.langd...@cat.com EVILUTION tsm-fo...@backupcentral.com Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 17/12/2009 20:45 Please respond to ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject [ADSM-L] collocation increases tape mounts while backup Caterpillar: Confidential Green Retain Until: 16/01/2010 We are using an IBM3584 and don't use any kind of collocation. We have found the migration process from diskpool to tape collocates data by node and therefore already does a decent job of grouping node data together. The only time you may see better performance with collocation is with a server that has alot of little files that change often and those nodes should probably be stored on VTL or DISK rather than tape. +-- |This was sent by jeff.je...@sentry.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +--
Re: collocation increases tape mounts while backup
On Dec 17, 2009, at 5:31 PM, Steven Langdale wrote: In that case you must be using collocation (albeit by accident). Not really... Remember that, within Migpr, migration operates serially by node, and thus you get a certain amount of same-node data clumped together on sequential media. It's not collocation, but affords some temporal node data co-residency which incidentally helps restoral times in the short term. Of course, one should architect storage utilization, and not depend upon happenstance. Richard Sims
Re: TSM 5.3.4 Policy problem
Hi All, Thanks for your help! When I input: ACTIVATE POLICYSET DOM_SRC SET_SRV TSM give a message: ANR1557W The space management migration destination in management class MC_90DAYS does Not refer to a defined storage pool: SPACEMGPOOL. If this pooll does not exist when policy set SET_SRV is activated, clients will fail When using this management class to migrate space-managed files to the server. But actually,my stgpool are DISK_SRV and LTO3_BCK_SRV, not SPACEMGPOOL, So, Can I go on with activate command? please see output below: -- tsm: SHITSM01q stgpool Storage Device Estimated Pct Pct High Low Next Stora- Pool Name Class Name Capacity Util Migr Mig Mig ge Pool Pct Pct --- -- -- - - --- --- DISK_SRVDISK180 G 33.7 33.7 70 50 LTO3_BCK_S- RV LTO3_ARCH_- LTO30.0 M 0.0 0.0 90 70 SRV LTO3_BCK_S- LTO3 74,826 G 41.4 69.0 90 70 RV LTO3_CPDR LTO30.0 M 0.0 0.0 90 70 -- tsm: SHITSM01q mgmtclass f=d Policy Domain Name: DOM_SRV Policy Set Name: ACTIVE Mgmt Class Name: MC_90DAYS Default Mgmt Class ?: Yes Description: Space Management Technique: None Auto-Migrate on Non-Use: 0 Migration Requires Backup?: Yes Migration Destination: SPACEMGPOOL Last Update by (administrator): ADMIN Last Update Date/Time: 05/09/2007 15:36:48 Managing profile: Changes Pending: No Policy Domain Name: DOM_SRV Policy Set Name: SET_SRV Mgmt Class Name: MC_90DAYS Default Mgmt Class ?: Yes Description: Space Management Technique: None Auto-Migrate on Non-Use: 0 Migration Requires Backup?: Yes Migration Destination: SPACEMGPOOL Last Update by (administrator): ADMIN Last Update Date/Time: 05/09/2007 15:36:48 Managing profile: Changes Pending: No Policy Domain Name: STANDARD Policy Set Name: ACTIVE Mgmt Class Name: STANDARD Default Mgmt Class ?: Yes Description: Installed default management class. Space Management Technique: None Auto-Migrate on Non-Use: 0 Migration Requires Backup?: Yes Migration Destination: SPACEMGPOOL Last Update by (administrator): SERVER_CONSOLE Last Update Date/Time: 05/09/2007 12:41:05 Managing profile: Changes Pending: No Policy Domain Name: STANDARD Policy Set Name: STANDARD Mgmt Class Name: STANDARD Migration Requires Backup?: Yes Migration Destination: SPACEMGPOOL Last Update by (administrator): SERVER_CONSOLE Last Update Date/Time: 05/09/2007 12:41:05 Managing profile: Changes Pending: No Policy Domain Name: STANDARD Policy Set Name: STANDARD Mgmt Class Name: STANDARD more... (ENTER to continue, 'C' to cancel) Default Mgmt Class ?: Yes Description: Installed default management class. Space Management Technique: None Auto-Migrate on Non-Use: 0 Migration Requires Backup?: Yes Migration Destination: SPACEMGPOOL Last Update by (administrator): SERVER_CONSOLE Last Update Date/Time: 05/09/2007 12:41:05 Managing profile: Changes Pending: No --- Thanks , Best Regards, william -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Carol Trible Sent: Thursday, December 17, 2009 11:25 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM 5.3.4 Policy problem Activate makes the activated policy set the active one by copying that policy set into active. It does not change the policy set that is activated. Each domain has only one ACTIVE policy set. The command ACTIVATE POLICYSET DOM_SRC STANDARD will copy the policy set STANDARD into DOM_SRC ACTIVE. but since the query didn't show a STANDARD policy set in the domain DOM_SRC, with the desired copygroup, there most likely is not a STANDARD policy set in that domain, and the command will fail. Domain DOM_SRC has 2 policy sets with copygroups, ACTIVE, which is a copy of whatever policy set was last activated, and SET_SRV, which is presumably the policy last activated since it is the only one in DOM_SRC with copygroups defined. To update the ACTIVE policy set in domain DOM_SRC, issue the update commands for the management classes and copygroups in DOM_SRC SET_SRV, then
