Re: backing up snap servers via nt cleints
Tim, Have you tried to add also objects="s:" in your 'define schedule' command ? Or else you can try to add objects="\\snap305572\share1" in the same command. G.Danan Backup Avenue - Original Message - From: "Tim Brown" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, March 22, 2002 2:06 PM Subject: backing up snap servers via nt cleints we have snap servers mounted to nt servers as for example drive s: i have the domain statement in the dsm.opt file coded as domain c: d: s: This appears in the beginning of the schedule log file Incremental backup of volume 'S:' This appears later ANS1228E Sending of object '\\snap305572\share1' failed ANS1063E Invalid path specification This was working prior to vesion Version 4 Release 2, Level 1.20 if i run dsmc inc from a dos window the S: drive gets backed up ok Is anyone else using adsm to back up snap servers and if so how is there a different way to code this drive in dsm.opt Tim Brown Systems Specialist Information Systems Central Hudson Gas & Electric tel: 845-486-5643 fax: 845-586-5921
Re: Can TSM be a time machine ?
Several client machines are off (which explains why the scheduled backup is missed); so I would not suspect the client itself. It looks that the server is putting down a time-stamp by itself which is not related to anything relevant. Maybe a clue: what does the "Actual Start Date" mean when the schedule is "missed" ? This applies whether or not it is before or after the "Scheduled Start Date". Gilles Danan - Original Message - From: "David Longo" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, August 29, 2001 2:55 PM Subject: Re: Can TSM be a time machine ? My very first check would be to see if each of the clients and the *SM server are synced up to the same time. Even if supposedly they are, double check them. David Longo >>> [EMAIL PROTECTED] 08/29/01 06:38AM >>> We have seen very strange behavior in the reports given by TSM for past scheduled backups. In particular, some node names repeatedly show that the actual start date is BEFORE the scheduled start date. All clients are in polling mode. We have no randomization (set to 0). Other node names never show this (actual start date is past scheduled start date). Samples of sql query of the EVENTS table are below. We have TSM Server 4.1 on AIX, clients are Windows NT or 98, version 4.1.2.0 or 4.1.2.12. Has anyone out there experienced such things ? Gilles Danan - SCHEDULED_START: 2001-07-29 04:00:00.00 ACTUAL_START: 2001-07-29 02:00:20.00 DOMAIN_NAME: BK20_ARCH_DOM SCHEDULE_NAME: 4H_DAILY NODE_NAME: vers_008 STATUS: Missed RESULT: REASON: SCHEDULED_START: 2001-08-16 20:00:00.00 ACTUAL_START: 2001-08-16 09:57:53.00 DOMAIN_NAME: BK10_ARCH_DOM SCHEDULE_NAME: 20H_DAILY_C NODE_NAME: vers_014 STATUS: Completed RESULT: 0 REASON: SCHEDULED_START: 2001-08-12 06:00:00.00 ACTUAL_START: 2001-08-12 05:00:18.00 DOMAIN_NAME: BK20_ARCH_DOM SCHEDULE_NAME: 6H_DAILY NODE_NAME: vers_001 STATUS: Missed RESULT: REASON: "MMS " made the following annotations on 08/29/01 09:01:34 -- This message is for the named person's use only. It may contain confidential, proprietary, or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it, and notify the sender. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. Health First reserves the right to monitor all e-mail communications through its networks. Any views or opinions expressed in this message are solely those of the individual sender, except (1) where the message states such views or opinions are on behalf of a particular entity; and (2) the sender is authorized by the entity to give such views or opinions. ==
Can TSM be a time machine ?
We have seen very strange behavior in the reports given by TSM for past scheduled backups. In particular, some node names repeatedly show that the actual start date is BEFORE the scheduled start date. All clients are in polling mode. We have no randomization (set to 0). Other node names never show this (actual start date is past scheduled start date). Samples of sql query of the EVENTS table are below. We have TSM Server 4.1 on AIX, clients are Windows NT or 98, version 4.1.2.0 or 4.1.2.12. Has anyone out there experienced such things ? Gilles Danan - SCHEDULED_START: 2001-07-29 04:00:00.00 ACTUAL_START: 2001-07-29 02:00:20.00 DOMAIN_NAME: BK20_ARCH_DOM SCHEDULE_NAME: 4H_DAILY NODE_NAME: vers_008 STATUS: Missed RESULT: REASON: SCHEDULED_START: 2001-08-16 20:00:00.00 ACTUAL_START: 2001-08-16 09:57:53.00 DOMAIN_NAME: BK10_ARCH_DOM SCHEDULE_NAME: 20H_DAILY_C NODE_NAME: vers_014 STATUS: Completed RESULT: 0 REASON: SCHEDULED_START: 2001-08-12 06:00:00.00 ACTUAL_START: 2001-08-12 05:00:18.00 DOMAIN_NAME: BK20_ARCH_DOM SCHEDULE_NAME: 6H_DAILY NODE_NAME: vers_001 STATUS: Missed RESULT: REASON:
Re: Directory to restore not visible from GUI
We checked that, but the user does have access to the files as an admin. Also, other directories with the same access rights are seen in the restore part of the GUI and can be restored from. Thanks for the reply anyway. Gilles - Original Message - From: "Loon, E.J. van - SPLXM" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, August 22, 2001 10:31 AM Subject: Re: Directory to restore not visible from GUI > Hi Gilles! > Could it be that the user who is doing the restore is not a local NT > administrator? If he has no write access to the files, he can't restore > them. > Kindest regards, > Eric van Loon > KLM Royal Dutch Airlines > > -Original Message- > From: Gilles Danan [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, August 21, 2001 19:40 > To: [EMAIL PROTECTED] > Subject: Directory to restore not visible from GUI > > > We have a NT 4.0 client with TSM v 4.1.2.12 who cannot restore a particular > directory from the GUI. > The directory is not even visible from the tree, whereas other directories > placed at the same level are visible and can be restored normally. > What is strange is that files and subdirs within this directory have been > backed up (we see activity and entries in the DB) and we can see files and > subdirs using the command line (query backup command). > > Can this be due to illegal characters in the directory name, so that it is > not recognized by the GUI. > > Server is AIX with TSM 4.1 > > Thanks in advance. > > Gilles Danan > > > ** > 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. > ** >
Directory to restore not visible from GUI
We have a NT 4.0 client with TSM v 4.1.2.12 who cannot restore a particular directory from the GUI. The directory is not even visible from the tree, whereas other directories placed at the same level are visible and can be restored normally. What is strange is that files and subdirs within this directory have been backed up (we see activity and entries in the DB) and we can see files and subdirs using the command line (query backup command). Can this be due to illegal characters in the directory name, so that it is not recognized by the GUI. Server is AIX with TSM 4.1 Thanks in advance. Gilles Danan
