missed backup
What we have are 2 windows clients, one on 5.3.4.0 and another on 5.3.4.8. Both of these clients consistently show missed, yet you can restart the scheduler service and it will communicate and pick up the schedule. The log on the client shows no attempt to start and the TSM server only has the standard messages when the attempt to contact a client fails. Gui and command line access from the client work just fine. I've asked those folks to verify certain things but have not heard back so I thought while waiting for a response I'd throw this out there. Besides the standard NIC/switch mismatch, which I have seen cause this, is there something DNS wise that might cause this and does anyone have any suggestions for other things to check? Geoff Gill TSM Administrator PeopleSoft Sr. Systems Administrator SAIC M/S-G1b (858)826-4062 Email: [EMAIL PROTECTED]
Re: missed backup
Hi, Hi, (dsm)sched.log and dsm(error).log at the client can give some extra info. Workaround could be to set the schedmode to polling. Regards, Karel -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Gill, Geoffrey L. Sent: dinsdag 20 maart 2007 16:58 To: ADSM-L@VM.MARIST.EDU Subject: missed backup What we have are 2 windows clients, one on 5.3.4.0 and another on 5.3.4.8. Both of these clients consistently show missed, yet you can restart the scheduler service and it will communicate and pick up the schedule. The log on the client shows no attempt to start and the TSM server only has the standard messages when the attempt to contact a client fails. Gui and command line access from the client work just fine. I've asked those folks to verify certain things but have not heard back so I thought while waiting for a response I'd throw this out there. Besides the standard NIC/switch mismatch, which I have seen cause this, is there something DNS wise that might cause this and does anyone have any suggestions for other things to check? Geoff Gill TSM Administrator PeopleSoft Sr. Systems Administrator SAIC M/S-G1b (858)826-4062 Email: [EMAIL PROTECTED] ÿþ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 y o u r e c e i v e t h i s e - m a i l i n e r r o r , p l e a s e n o t i f y t h e s e n d e r i m m e d i a t e l y a n d d e s t r o y i t . A s i t s i n t e g r i t y c a n n o t b e s e c u r e d o n t h e I n t e r n e t , t h e A t o s O r i g i n g r o u p l i a b i l i t y c a n n o t b e t r i g g e r e d f o r t h e m e s s a g e c o n t e n t . A l t h o u g h t h e s e n d e r e n d e a v o u r s t o m a i n t a i n a c o m p u t e r v i r u s - f r e e n e t w o r k , t h e s e n d e r d o e s n o t w a r r a n t t h a t t h i s t r a n s m i s s i o n i s v i r u s - f r e e a n d w i l l n o t b e l i a b l e f o r a n y d a m a g e s r e s u l t i n g f r o m a n y v i r u s t r a n s m i t t e d . O n a l l o f f e r s a n d a g r e e m e n t s u n d e r w h i c h A t o s O r i g i n s u p p l i e s g o o d s a n d / o r s e r v i c e s o f w h a t e v e r n a t u r e , t h e T e r m s o f D e l i v e r y f r o m A t o s O r i g i n e x c l u s i v e l y a p p l y . T h e T e r m s o f D e l i v e r y s h a l l b e p r o m p t l y s u b m i t t e d t o y o u o n y o u r r e q u e s t . A t o s O r i g i n N e d e r l a n d B . V . / U t r e c h t K v K U t r e c h t 3 0 1 3 2 7 6 2
Re: missed backup
(dsm)sched.log and dsm(error).log at the client can give some extra info. When you restart the scheduler there is an entry in the log that shows the next backup is scheduled for that night and then nothing else. There is nothing in the error log at all. No indication any communication was even attempted. Geoff Gill TSM Administrator PeopleSoft Sr. Systems Administrator SAIC M/S-G1b (858)826-4062 Email: [EMAIL PROTECTED]
Re: missed backup
On Mar 20, 2007, at 11:58 AM, Gill, Geoffrey L. wrote: ... I've asked those folks to verify certain things but have not heard back so I thought while waiting for a response I'd throw this out there. Besides the standard NIC/switch mismatch, which I have seen cause this, is there something DNS wise that might cause this and does anyone have any suggestions for other things to check? Geoff - See Schedule, missed in http://people.bu.edu/rbs/ ADSM.QuickFacts for common issues, and pointers to other info sources. The TSM Problem Determination Guide has a good section on pursuing this problem. Richard Sims
Re: missed backup
-Geoff Gill ADSM-L@VM.MARIST.EDU wrote: - What we have are 2 windows clients, one on 5.3.4.0 and another on 5.3.4.8. Both of these clients consistently show missed, yet you can restart the scheduler service and it will communicate and pick up the schedule. The log on the client shows no attempt to start and the TSM server only has the standard messages when the attempt to contact a client fails. Gui and command line access from the client work just fine. I've asked those folks to verify certain things but have not heard back so I thought while waiting for a response I'd throw this out there. Besides the standard NIC/switch mismatch, which I have seen cause this, is there something DNS wise that might cause this and does anyone have any suggestions for other things to check? We see this kind of behavior because of firewalls. In some cases the firewalls are dedicated systems controlling traffic between subnets. In other cases the firewalls are software running on the TSM client systems. When the client scheduler service starts up it attempts to bind to a TCP port specified by the tcpclientport option. If this port is not available the client software searches for an unused port to bind to. Once a suitable port is found the scheduler service connects to the TSM server and reports the port number. When the time comes to run a backup the server attempts to open a connection to the port on which the scheduler service is listening. It is fairly common at our site for a firewall to blockthe server to client connections when a new client is first set up.
missed backup files because of virus scanner
Hello, We just found out that one of our Novell clients has a Virus Scanner that is interfering with the nightly TSM incremental backup of a volume NTOVL1 is causing many files to be skipped because it's scans files during the backup and TSM thinks the files are open. Anyone else ever experienced this problem or something similar. Netware 6.5 SP2 TSM client 5.2.2 Thanks for any replies in advance
Missed Backup
TSM Server AIX 4.3.3 TSM Server Software 5.1.5.2 Why is it that anytime a client is removed from a schedule and added to a different one the backup is missed? This always happens from my recollection. No matter what the server version I have been it's happened. The only way I've seen around this is to stop and start the scheduler on the client after the client has been assigned to the new schedule. Geoff Gill TSM Administrator NT Systems Support Engineer SAIC E-Mail:mailto:[EMAIL PROTECTED] [EMAIL PROTECTED] Phone: (858) 826-4062 Pager: (877) 905-7154
Re: Missed Backup
Hi Geoff! You probably are using the scheduler in polling mode. Use prompted mode instead. Kindest regards, Eric van Loon KLM Royal Dutch Airlines -Original Message- From: Gill, Geoffrey L. [mailto:[EMAIL PROTECTED]] Sent: Friday, January 17, 2003 16:10 To: [EMAIL PROTECTED] Subject: Missed Backup TSM Server AIX 4.3.3 TSM Server Software 5.1.5.2 Why is it that anytime a client is removed from a schedule and added to a different one the backup is missed? This always happens from my recollection. No matter what the server version I have been it's happened. The only way I've seen around this is to stop and start the scheduler on the client after the client has been assigned to the new schedule. Geoff Gill TSM Administrator NT Systems Support Engineer SAIC E-Mail:mailto:[EMAIL PROTECTED] [EMAIL PROTECTED] Phone: (858) 826-4062 Pager: (877) 905-7154 ** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. **
Re: Missed Backup
Hi Gill! If you runing polling I can understand why you got this problem. Becuse the client is ask for his Scheduler every 12h. (Standard) What you can do is change it to 1h. Then he take your changes after a houre. And he automaticly takes your changeing when you have done it. But if you runing Prompted. Then I don´t understand why. Becuse the server is puching out the command to the client. And the Client have no idea which domain / scheduler he is in to. I hope you understan. If not. I try to have better English. ;-) Med Vänliga Hälsningar/Best Regards Christian Svensson --- Cristie Nordic AB Box 2 SE-131 06 Nacka Sweden Phone : +46-(0)8-641 96 30 Mobil : +46-(0)70-325 15 77 eMail : [EMAIL PROTECTED] MSN : [EMAIL PROTECTED] Gill, Geoffrey L. GEOFFREY.L. To: [EMAIL PROTECTED] [EMAIL PROTECTED] cc: Sent by: ADSM: Subject: Missed Backup Dist Stor Manager ADSM- [EMAIL PROTECTED] 2003-01-17 16:09 Please respond to ADSM: Dist Stor Manager TSM Server AIX 4.3.3 TSM Server Software 5.1.5.2 Why is it that anytime a client is removed from a schedule and added to a different one the backup is missed? This always happens from my recollection. No matter what the server version I have been it's happened. The only way I've seen around this is to stop and start the scheduler on the client after the client has been assigned to the new schedule. Geoff Gill TSM Administrator NT Systems Support Engineer SAIC E-Mail:mailto:[EMAIL PROTECTED] [EMAIL PROTECTED] Phone: (858) 826-4062 Pager: (877) 905-7154 inline: graycol.gifinline: ecblank.gifinline: pic16601.gif
Re: Missed Backup
It is a double check type situation... A schedule won't run unless the client node has had at least ONE opportunity to see that it is going to occur. Say schedmode is prompted and your q sched period is 24 (and for example, happens at 12:00 noon-ish) OK, if I were a ~bad admin~ I might try to schedule an event to run on a client that would run a command rm -R * not a pretty sight ! So that client node's admin checks his log at 13:00, sees things are normal... I sneak in and put my schedule on the TSM server at 14:00 to run at 15:00... see the problem ! Now to correct the situation of a node not picking up a schedule, just bounce the scheduler ONCE the alterations to schedules has taken place. First thing the client scheduler does upon starting is to ask the server ~what is going on, when...~ at that time the server will respond with the currently scheduled tasks (which will include your recent alterations) and thus things will be OK... *** JUST ANOTHER WAY TSM PROTECTS THINGS A WHOLE LOT BETTER THAN OTHER PRODUCTS * but I know I'm preaching to the choir Dwight E. Cook Software Application Engineer III Science Applications International Corporation 509 S. Boston Ave. Suite 220 Tulsa, Oklahoma 74103-4606 Office (918) 732-7109 -Original Message- From: Gill, Geoffrey L. [mailto:[EMAIL PROTECTED]] Sent: Friday, January 17, 2003 9:10 AM To: [EMAIL PROTECTED] Subject: Missed Backup TSM Server AIX 4.3.3 TSM Server Software 5.1.5.2 Why is it that anytime a client is removed from a schedule and added to a different one the backup is missed? This always happens from my recollection. No matter what the server version I have been it's happened. The only way I've seen around this is to stop and start the scheduler on the client after the client has been assigned to the new schedule. Geoff Gill TSM Administrator NT Systems Support Engineer SAIC E-Mail:mailto:[EMAIL PROTECTED] [EMAIL PROTECTED] Phone: (858) 826-4062 Pager: (877) 905-7154
Re: Missed Backup
What is your QUERYSCHEDPERIOD option set to on your clients? The default is 12 hours, which means the client only checks twice a day to see what it's next scheduled event is. So lets take the following scenario... A client was scheduled for a 10:00 pm backup. It last checked with the server at 11:00 am, so it will not check again before it is scheduled to backup. You change the association from the 10:00 pm schedule to a 8:00 pm schedule. The client is not aware of this change unless you stop/start the scheduler so it will query the server and pick this up. So when 10:00 pm come along, the client connects to the server, and then it finds out that it is no longer associated with the 10:00 pm schedule, so it will not backup, it queries to see what the next event is, and in this case, that would be 8:00 pm then next day. Had you changed the schedule to a later time, say 11:30 pm, it would indeed pick up the change and backup that night. But you may not always make the change to a later time. We set all of our clients to query every 2 hours, this way most changes will get picked up. You can go this by changing it in each OPT file on each client, or you can use CLIENT OPTIONSET on the server to send this out to all clients, but of course you will need to touch each node to do this also If you need more on this, let me know. Ryan Miller Principal Financial Group Tivoli Certified Consultant Tivoli Storage Manager v4.1 -Original Message- From: Gill, Geoffrey L. [mailto:[EMAIL PROTECTED]] Sent: Friday, January 17, 2003 9:10 AM To: [EMAIL PROTECTED] Subject: Missed Backup TSM Server AIX 4.3.3 TSM Server Software 5.1.5.2 Why is it that anytime a client is removed from a schedule and added to a different one the backup is missed? This always happens from my recollection. No matter what the server version I have been it's happened. The only way I've seen around this is to stop and start the scheduler on the client after the client has been assigned to the new schedule. Geoff Gill TSM Administrator NT Systems Support Engineer SAIC E-Mail:mailto:[EMAIL PROTECTED] [EMAIL PROTECTED] Phone: (858) 826-4062 Pager: (877) 905-7154
Re: Missed Backup
Geoff I think, but I could be wrong, that if you use dsmcad to handle the scheduler service that a restart is no longer required after changes. Cook, Dwight E wrote: It is a double check type situation... A schedule won't run unless the client node has had at least ONE opportunity to see that it is going to occur. Say schedmode is prompted and your q sched period is 24 (and for example, happens at 12:00 noon-ish) OK, if I were a ~bad admin~ I might try to schedule an event to run on a client that would run a command rm -R * not a pretty sight ! So that client node's admin checks his log at 13:00, sees things are normal... I sneak in and put my schedule on the TSM server at 14:00 to run at 15:00... see the problem ! Now to correct the situation of a node not picking up a schedule, just bounce the scheduler ONCE the alterations to schedules has taken place. First thing the client scheduler does upon starting is to ask the server ~what is going on, when...~ at that time the server will respond with the currently scheduled tasks (which will include your recent alterations) and thus things will be OK... *** JUST ANOTHER WAY TSM PROTECTS THINGS A WHOLE LOT BETTER THAN OTHER PRODUCTS * but I know I'm preaching to the choir Dwight E. Cook Software Application Engineer III Science Applications International Corporation 509 S. Boston Ave. Suite 220 Tulsa, Oklahoma 74103-4606 Office (918) 732-7109 -Original Message- From: Gill, Geoffrey L. [mailto:[EMAIL PROTECTED]] Sent: Friday, January 17, 2003 9:10 AM To: [EMAIL PROTECTED] Subject: Missed Backup TSM Server AIX 4.3.3 TSM Server Software 5.1.5.2 Why is it that anytime a client is removed from a schedule and added to a different one the backup is missed? This always happens from my recollection. No matter what the server version I have been it's happened. The only way I've seen around this is to stop and start the scheduler on the client after the client has been assigned to the new schedule. Geoff Gill TSM Administrator NT Systems Support Engineer SAIC E-Mail:mailto:[EMAIL PROTECTED] [EMAIL PROTECTED] Phone: (858) 826-4062 Pager: (877) 905-7154 -- Jim Kirkman AIS - Systems UNC-Chapel Hill 966-5884
