Re: TSM skipping some local drives
We had this happen to us also. A Win-something server worked fine until the TSM client software was upgraded. The E: drive stopped getting backed up. We noticed and IE error when starting things up so the box's admin upgraded IE and the problem went away. I can get more details from our Win/NT admin if you want. Nancy Reeves Technical Support, Wichita State University [EMAIL PROTECTED] 316-978-3860 -- David Wentworth wrote: Hello. I have TSM installed on two Windows 2000 servers. One server has TSM 4.1.1 and the other one has 5.1.0.1. Both of them are skipping a local drive. I think Domain all-local is the default. I tried making it explicit but it didn't help. One server (with TSM 4.1.1) has a C: and E: drive. C: gets backed up but not E:. The other server (with TSM 5.1.0.1) has a C:, D: and E: drive. On that on C: and E: get backed up but not D:. The problem only happens with the scheduler service. If I log on as an administrator and run an incremental backup manually all the local drives get backed up. If anyone has any suggestions I would love to hear them. Regards, Dave David Wentworth UC Office of the President
Re: TSM skipping some local drives -- solved
Sias, You were right. Thanks! The scheduler service was logging in as Local System account. I thought that account automatically had permissions to the file system, but apparently not. Yesterday I gave the local System group full control of the drive that wasn't backing up and last night the drive got backed up. It probably doesn't need full control but I thought I'd try that to start. Dave At 07:40 PM 11/19/2002 -0500, Sias Dealy wrote: Dave, Your right that domain all-local is the default. Since you are able to backup the local drive manually but not via the schedul. I would check the permission for the schedule service to see if it have the proper permission to access the local drive. I had a simular issue about a year ago. It turn out that the scheduler service did not have the proper permission to access the local drive. I just gave the scheduler service administrator rights and that worked for me. Sias Get your own 800 number Voicemail, fax, email, and a lot more http://www.ureach.com/reg/tag On, David Wentworth ([EMAIL PROTECTED]) wrote: Hello. I have TSM installed on two Windows 2000 servers. One server has TSM 4.1.1 and the other one has 5.1.0.1. Both of them are skipping a local drive. I think Domain all-local is the default. I tried making it explicit but it didn't help. One server (with TSM 4.1.1) has a C: and E: drive. C: gets backed up but not E:. The other server (with TSM 5.1.0.1) has a C:, D: and E: drive. On that on C: and E: get backed up but not D:. The problem only happens with the scheduler service. If I log on as an administrator and run an incremental backup manually all the local drives get backed up. If anyone has any suggestions I would love to hear them. Regards, Dave David Wentworth UC Office of the President
Re: TSM skipping some local drives -- solved
Dave, It isn't necessary to run the service as an administrator to access the local drive. What usually happens is that the administrator removes the everyone group from NTFS permissions as part of their security setup. If that is done, you must add the system account from the local SAM back into the NTFS permissions. If you're running a domain, you'll have to select the local security context to see that account. Once that is done, any service running as Local System can access the drive / folder / file. Tab Trepagnier TSM Administrator Laitram Corporation David Wentworth [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 11/20/2002 11:51 AM Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Re: TSM skipping some local drives -- solved Sias, You were right. Thanks! The scheduler service was logging in as Local System account. I thought that account automatically had permissions to the file system, but apparently not. Yesterday I gave the local System group full control of the drive that wasn't backing up and last night the drive got backed up. It probably doesn't need full control but I thought I'd try that to start. Dave At 07:40 PM 11/19/2002 -0500, Sias Dealy wrote: Dave, Your right that domain all-local is the default. Since you are able to backup the local drive manually but not via the schedul. I would check the permission for the schedule service to see if it have the proper permission to access the local drive. I had a simular issue about a year ago. It turn out that the scheduler service did not have the proper permission to access the local drive. I just gave the scheduler service administrator rights and that worked for me. Sias Get your own 800 number Voicemail, fax, email, and a lot more http://www.ureach.com/reg/tag On, David Wentworth ([EMAIL PROTECTED]) wrote: Hello. I have TSM installed on two Windows 2000 servers. One server has TSM 4.1.1 and the other one has 5.1.0.1. Both of them are skipping a local drive. I think Domain all-local is the default. I tried making it explicit but it didn't help. One server (with TSM 4.1.1) has a C: and E: drive. C: gets backed up but not E:. The other server (with TSM 5.1.0.1) has a C:, D: and E: drive. On that on C: and E: get backed up but not D:. The problem only happens with the scheduler service. If I log on as an administrator and run an incremental backup manually all the local drives get backed up. If anyone has any suggestions I would love to hear them. Regards, Dave David Wentworth UC Office of the President
Re: TSM skipping some local drives -- solved
Tab, Thanks. That's exactly what happened. I have it working now that I've given System NTFS permissions. Dave At 04:36 PM 11/20/2002 -0600, you wrote: Dave, It isn't necessary to run the service as an administrator to access the local drive. What usually happens is that the administrator removes the everyone group from NTFS permissions as part of their security setup. If that is done, you must add the system account from the local SAM back into the NTFS permissions. If you're running a domain, you'll have to select the local security context to see that account. Once that is done, any service running as Local System can access the drive / folder / file. Tab Trepagnier TSM Administrator Laitram Corporation David Wentworth [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 11/20/2002 11:51 AM Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Re: TSM skipping some local drives -- solved Sias, You were right. Thanks! The scheduler service was logging in as Local System account. I thought that account automatically had permissions to the file system, but apparently not. Yesterday I gave the local System group full control of the drive that wasn't backing up and last night the drive got backed up. It probably doesn't need full control but I thought I'd try that to start. Dave At 07:40 PM 11/19/2002 -0500, Sias Dealy wrote: Dave, Your right that domain all-local is the default. Since you are able to backup the local drive manually but not via the schedul. I would check the permission for the schedule service to see if it have the proper permission to access the local drive. I had a simular issue about a year ago. It turn out that the scheduler service did not have the proper permission to access the local drive. I just gave the scheduler service administrator rights and that worked for me. Sias Get your own 800 number Voicemail, fax, email, and a lot more http://www.ureach.com/reg/tag On, David Wentworth ([EMAIL PROTECTED]) wrote: Hello. I have TSM installed on two Windows 2000 servers. One server has TSM 4.1.1 and the other one has 5.1.0.1. Both of them are skipping a local drive. I think Domain all-local is the default. I tried making it explicit but it didn't help. One server (with TSM 4.1.1) has a C: and E: drive. C: gets backed up but not E:. The other server (with TSM 5.1.0.1) has a C:, D: and E: drive. On that on C: and E: get backed up but not D:. The problem only happens with the scheduler service. If I log on as an administrator and run an incremental backup manually all the local drives get backed up. If anyone has any suggestions I would love to hear them. Regards, Dave David Wentworth UC Office of the President
Re: TSM skipping some local drives
Dave, Your right that domain all-local is the default. Since you are able to backup the local drive manually but not via the schedul. I would check the permission for the schedule service to see if it have the proper permission to access the local drive. I had a simular issue about a year ago. It turn out that the scheduler service did not have the proper permission to access the local drive. I just gave the scheduler service administrator rights and that worked for me. Sias Get your own 800 number Voicemail, fax, email, and a lot more http://www.ureach.com/reg/tag On, David Wentworth ([EMAIL PROTECTED]) wrote: Hello. I have TSM installed on two Windows 2000 servers. One server has TSM 4.1.1 and the other one has 5.1.0.1. Both of them are skipping a local drive. I think Domain all-local is the default. I tried making it explicit but it didn't help. One server (with TSM 4.1.1) has a C: and E: drive. C: gets backed up but not E:. The other server (with TSM 5.1.0.1) has a C:, D: and E: drive. On that on C: and E: get backed up but not D:. The problem only happens with the scheduler service. If I log on as an administrator and run an incremental backup manually all the local drives get backed up. If anyone has any suggestions I would love to hear them. Regards, Dave David Wentworth UC Office of the President
Re: TSM skipping some local drives
David, Are the servers Microsoft Cluster servers? You have to setup the client for cluster environment if that is the case to get the cluster drives backed up. regards, Manuel - Original Message - From: David Wentworth [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, November 20, 2002 1:29 AM Subject: TSM skipping some local drives Hello. I have TSM installed on two Windows 2000 servers. One server has TSM 4.1.1 and the other one has 5.1.0.1. Both of them are skipping a local drive. I think Domain all-local is the default. I tried making it explicit but it didn't help. One server (with TSM 4.1.1) has a C: and E: drive. C: gets backed up but not E:. The other server (with TSM 5.1.0.1) has a C:, D: and E: drive. On that on C: and E: get backed up but not D:. The problem only happens with the scheduler service. If I log on as an administrator and run an incremental backup manually all the local drives get backed up. If anyone has any suggestions I would love to hear them. Regards, Dave David Wentworth UC Office of the President
