TDP DOMINO for E-mail missing backup
We are experiencing missing backup for TDP DOMINO on Lotus notes E-mail. Does anyone had similar experiences/fixes? We are running DOMINO 6.5.5, TDP for DOMINO 5.3.0.0 and with NT 2000 operating system. Thanks. Frank Tsao [EMAIL PROTECTED] PAX 25803, 626-302-5803 FAX 626-302-7131
LAN free TSM set up in Gresham environment
We are in the process of doing proof of concept of LAN free under Gresham environment. I like to know for whoever uses this type of structure how many LAN free client do you have? Also, I like to find out are you using TSM domain or management class to control the client? How many domain do you have for LAN free client? Thanks. Frank Tsao [EMAIL PROTECTED] PAX 25803, 626-302-5803 FAX 626-302-7131
Re: TSM 5.3.3 loaddb and audit problem
Richard, Is there any way can minimize the fragmentation? For example, like how much maximum reduction size should have before the database reach a point of no response. Frank Tsao [EMAIL PROTECTED] PAX 25803, 626-302-5803 FAX 626-302-7131 Richard Sims [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 05/17/2006 05:09 AM Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject Re: TSM 5.3.3 loaddb and audit problem Hi, Kelly - I was appalled when I first saw TSM manuals blithely enticing customers to reorganize their TSM databases as though it were some kind of risk-free, trivial undertaking. Nowhere in the documentation for this procedure are there the strong advisories which should be there regarding the prolonged unavailability which your site's data recovery facility will experience during the procedure, full perspective on why it might ever be warranted, the risks involved, what messages to expect, how to know whether or not the operation has succeeded, or what to do in case of a problem. Conspicuously missing is any mention that the utilities involved are not mainstream TSM software, but rather salvage utilities - which get little developer attention or testing (as is evident in the frightening APARs I've read on these utilities). To my experienced eye, this was an extraordinarily irresponsible thing for IBM to do, and a recipe for disaster. TSM novices in particular will see this in the manual, think it harmless because IBM offers it, and launch right into it. Unfortunately, the disaster potential has been borne out by customers writing to ADSM-L for help upon discovering the hard way that their TSM database is no longer viable after the operation. (And we don't know how many more customers have suffered silently.) It is high risk stuff, and almost always unwarranted, as customers are typically trying it expecting it to be some panacea for their system. Without an understanding of databases in general and the TSM db specifically, a customer is wandering through an unfamiliar house in the dark in such an undertaking, where the risk of getting hurt is high. The fact is that IBM *DOES NOT* have suitable software for its TSM customers to use to reorganize the TSM database. Salvage utilities, by their nature, are VERY physical in their orientation and operation, with no customer-meaningful feedback during execution and no customer-oriented assurance summary at conclusion. (I speak from experience in having run these utilities - and having seen no enduring performance or space benefit.) And, again, these utilities are not part of the main product and, as tributary software, receive little developmental attention. Such software is wholly unsuitable for this purported usage. And the encouraging but unadvising documentation only makes the situation worse. I can't imagine who, at what level in IBM, thought it was a good idea to suggest that salvage utilities be promoted as a means for accomplishing vaguely described goals. It boggles my mind that IBM would encourage their enterprise customers to blindly risk their corporate recovery vehicles, to no well-defined end. I simply do not understand how a technical organization could have decided upon such an ill-conceived and irresponsible course of action. I strongly believe that all documentation for the use of these utilities for TSM db reorganization should be removed from the TSM manuals. If at some time in the future, IBM can provide a true, customer-suitable TSM database reorganization function - AND a full rationale for engaging in such an undertaking - then such may be reintroduced to the documentation set. Thankfully, we have this forum to try to keep customers from getting into trouble when someone suggests actions which we experienced technicians know are just plain bad. To all the novice customers: Get the whole story on a major procedure before considering undertaking it. Richard Sims On May 17, 2006, at 7:08 AM, Kelly Lipp wrote: Richard, I could not agree more on your stance regarding Dump/Load. However, I'm in Holland teaching a Level 2 class and have been surprised to learn that a lot of my students perform this action as a matter of course on their servers. The objective is to reduce the size of aged TSM databases. In TSM 5.3 we have new functionality to determine if a db reorg would reclaim a significant amount of space. Then the Dump/load is executed to get this space. Do you suppose this new command is encouraging us to do something that is high risk? Alternatives? I guess they've decided the risk is worth the potential gain. I personally have not experience the problem so have not attempted this solution.
How do TSM decide need to copy tape
I had an interesting situation: A volume in primary pool had a read error. I used q vol f=d and found the last date of data written is around January. Since then, I had several good backup on this tape. However, I found on March 26, it had requested to make copy of this tape. Since this tape is in error condition, the copy failed. Do I have good data on the copy tape? How do TSM decide need to copy tape? How reliable I can trust the last read or written date? Thanks for your help. Frank Tsao [EMAIL PROTECTED] PAX 25803, 626-302-5803 FAX 626-302-7131
Control of data flow in collocation group environment
Can I have the control of the data flow in the collocation group set up environment? For example, I like to have collocation group A moving their data through migration to storage pool A. If the answer is yes, where is the control? I do not find in the def collocgroup or def stg help menu. Thanks for the response. Frank Tsao [EMAIL PROTECTED] PAX 25803, 626-302-5803 FAX 626-302-7131
Re: How to find out all drives in NT2000 using command line? Thanks
I had talked to several people and found that dumpcfg utility would
generate the data I am looking for.
Thanks for all your help and effort.
Frank Tsao
[EMAIL PROTECTED]
PAX 25803, 626-302-5803
FAX 626-302-7131
Andrew Raibeck
[EMAIL PROTECTED]
OMTo
Sent by: ADSM: ADSM-L@VM.MARIST.EDU
Dist Stor cc
Manager
[EMAIL PROTECTED] Subject
.EDU Re: How to find out all drives in
NT2000 using command line? Thanks
04/25/2005 09:16
AM
Please respond to
ADSM: Dist Stor
Manager
[EMAIL PROTECTED]
.EDU
Hi Frank,
There is no command that I can think of that does this; you'd have to write
a program or script to do it. Here are sample script and C++ program (they
both do the same thing). If these are useful, tailor as you wish.
Regards,
Andy
WMI SCRIPT
' ListDrives.vbs
' Invoke by running
'
'cscript ListDrives.vbs
'
' from an OS command prompt.
strComputer = .
set objWMIService = GetObject(winmgmts: _
{impersonationLevel=impersonate}!\\ _
strComputer \root\cimv2)
set disks = objWMIService.ExecQuery (select * from Win32_LogicalDisk)
for each objDisk in disks
select case objDisk.DriveType
case 0
' I would not normally expect to see this.
Wscript.Echo objDisk.DeviceID Unknown
case 1
Wscript.Echo objDisk.DeviceID Invalid root path
case 2
Wscript.Echo objDisk.DeviceID Removable
case 3
Wscript.Echo objDisk.DeviceID Fixed
case 4
Wscript.Echo objDisk.DeviceID Remote
case 5
Wscript.Echo objDisk.DeviceID CD-ROM
case 6
Wscript.Echo objDisk.DeviceID RAM disk
case Else
' I would not normally expect to see this.
Wscript.Echo objDisk.DeviceID ??
end select
next
C++ PROGRAM
/*
ListDrive.cpp
Compiled with Visual Studio .Net 2003 from an OS prompt as follows:
cl /GX /Zi /O1 ListDrives.cpp /link /debug
*/
#include windows.h
#include cstdio
#include cmath
#include iostream
using namespace std;
int main()
{
char driveLetter[] = *:\\;
DWORD drives= GetLogicalDrives();
DWORD bit = 0;
if (!drives)
{
cout ERROR: GetLogicalDrives() failed with rc
GetLastError() endl;
return -1;
}
for (int i = 0, bit = 1; i != 26; i++, bit *= 2)
{
if (drives bit)
{
cout char('A' + i) : ;
driveLetter[0] = 'A' + i;
switch (GetDriveType(driveLetter))
{
case DRIVE_UNKNOWN:
// I would not normally expect to see this.
cout Unknown;
break;
case DRIVE_NO_ROOT_DIR:
cout Invalid root path;
break;
case DRIVE_REMOVABLE:
cout Removable;
break;
case DRIVE_FIXED:
cout Fixed;
break;
case DRIVE_REMOTE:
cout Remote;
break;
case DRIVE_CDROM:
cout CD-ROM;
break;
case DRIVE_RAMDISK:
cout RAM disk;
break;
default:
// I would not normally expect to see this.
cout ??;
break;
} // switch (...)
cout endl;
} // if (drives bit)
} // for (...)
cout endl;
return 0;
}
Regards,
Andy
Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED]
Internet e-mail: [EMAIL PROTECTED]
The only dumb question is the one that goes unasked.
The command line is your friend.
Good enough is the enemy of excellence.
ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 2005-04-22
14:05:23:
Frank Tsao
[EMAIL PROTECTED]
PAX 25803, 626-302-5803
FAX 626-302-7131[attachment ListDrives.cpp deleted by Frank
Tsao/SCE/EIX]
Attachment ListDrives.vbs contains a potentially harmful file type
extension and was removed in accordance with IBM IT content security
practices.
Re: How to find out all drives in NT2000 using command line? Thanks
Thanks, Richards. It is close but that is not what I am looking for. I want to find drive letter installed on a NT2000 system. For example, issue find_drive_of_all_systems will return results as C: E: F: J: K: Frank Tsao [EMAIL PROTECTED] PAX 25803, 626-302-5803 FAX 626-302-7131 Richard Sims [EMAIL PROTECTED] Sent by: ADSM:To Dist Stor ADSM-L@VM.MARIST.EDU Manager cc [EMAIL PROTECTED] .EDU Subject Re: How to find out all drives in NT2000 using command line? Thanks 04/24/2005 04:27 AM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] .EDU Frank - You may find the DevCon utility useful for Windows command line work: http://support.microsoft.com/kb/q311272/ and www.robvanderwoude.com/devcon.html Richard Sims
How to find out all drives in NT2000 using command line? Thanks
Frank Tsao [EMAIL PROTECTED] PAX 25803, 626-302-5803 FAX 626-302-7131
STK drives go off line after upgraded to TSM 5.2.3
We are running 5.2.1 and suffered core dump every ten days. So, I upgraded the system to 5.2.3. Now we had a problem STK drives 9940B, one by one goes off-line until there is no drive is on line. We are running AIX 5.2-ML3, STK 7.0.0.2 EDT 6.4 with SAN switch connected between P60 and STK Silo. Any clues or similar experience. Thanks. Frank Tsao [EMAIL PROTECTED] PAX 25803, 626-302-5803 FAX 626-302-7131
Re: Node very very slow for incremental backup
What is your AIX version? If it is AIX 5.1 it should be at ML4. Frank Tsao [EMAIL PROTECTED] PAX 25803, 626-302-5803 FAX 626-302-7131 Dave Canan [EMAIL PROTECTED]To: [EMAIL PROTECTED] L.NET cc: Sent by: ADSM: Subject: Re: Node very very slow for incremental backup Dist Stor Manager [EMAIL PROTECTED] .EDU 06/03/2003 12:21 PM Please respond to ADSM: Dist Stor Manager I would not change the TCPWINDOWSIZE for this client - 63 is what we recommend for this platform. The trace you sent indicates a large percentage of time being spent (97%) in the process dirs category. This category represents the amount of time spent inspecting directories and files before any backups occur. Journaling in this case definitely would help reduce the maount of time for the backup. Additional questions: 1. Are there any deep directory structures that have recently been introduced on the system? 2. Have there recently been any new applications added to the box that have added substantially to the number of files on the box? Look into journaling - it will definitely help. At 08:43 PM 6/3/2003 +0200, you wrote: You may want to change your TCPWindowSize from 63 to 1024 - Original Message - From: David Rigaudiere [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, May 26, 2003 3:36 PM Subject: Node very very slow for incremental backup Hi *SMers, I have a probleme whit a node. Client 4.2.1.15 WinNT Server 5.1.6.3 AIX This node is very very slow to backups. 14H for less 6GB !! (1H is a normal backup time) The sysadmins said no change on this node I can't find where is the probleme, the node spent a lot of time to browse files and directories. A performance analyse when node is backuping does not show a bottleneck (memory, CPU, I/O ...) I tested a selective or big restore, without problem. (Data transfer rate: 10,000 to 12,000 KB/sec) Maybee I must install journal based backup but yesterday it worked perfectly without it... you're my only hope, do you have an idea ? dsm.opt : = TCPWindowSize63 TCPBuffSize 31 TCPNodelay YES SubDir YES Compression YES CompressAlways NO SchedModePolling * (behind Firewall) It is a session report : Total number of objects inspected: 192,386 Total number of objects backed up:2,221 Total number of objects updated: 8 Total number of objects rebound: 0 Total number of objects deleted: 0 Total number of objects expired:523 Total number of objects failed: 0 Total number of bytes transferred: 5.89 GB Data transfer time:1,416.29 sec Network data transfer rate:4,362.30 KB/sec Aggregate data transfer rate:119.69 KB/sec Objects compressed by: 15% Elapsed processing time:14:20:17 and a trace report : Section TotalTime(sec)Average Time(msec)Frequency used == Client Setup 0.344344.0 1 Process Dirs 50292.881 2250.6 22346 Solve Tree 0.000 0.0 0 Compute 2.677 0.0 304175 Transaction 46.145 0.0 938009 BeginTxn Verb0.047 0.1508 File I/O 164.261 0.7 241799 Compression372.440 2.3 164443 Encryption 0.000 0.0 0 Delta0.000 0.0 0 Data Verb0.297 8.3 36 Confirm Verb 0.297 8.3 36 EndTxn Verb541.249 1065.5508 Client Cleanup 2.735 2735.0 1 -- David Rigaudiere -+- Administration TSM -+- Paris -+- 40, rue de Courcelles -+- 4e itage -+- [EMAIL PROTECTED] -+- 01.5621.7802 --- This message (including any attachments) is confidential and may be privileged. If you have received it by mistake please notify the sender by return e-mail and delete this message from your system. Any unauthorised use or dissemination of this message in whole or in part is strictly prohibited. Please note that e-mails are susceptible to change. ABN AMRO Bank N.V. (including its group companies) shall not be liable for the improper or incomplete
Re: Version 4.2.1.7
We will need 4.2.1.7 because it fixes license registration problem. In 4.2.1.6, you can only register a license file once. So, total of license could register is 66. We would have problems when the clients exceed 66. And the noncompliant message would flood our activity log. Frank Tsao [EMAIL PROTECTED] PAX 25803, 626-302-5803 FAX 626-302-7131 Wouter V wouter-v@EASTo: [EMAIL PROTECTED] YNET.BE cc: Sent by: Subject: Re: Version 4.2.1.7 ADSM: Dist Stor Manager [EMAIL PROTECTED] RIST.EDU 11/15/2001 08:35 AM Please respond to ADSM: Dist Stor Manager What problems did you have on 4.2.1.6 (because I'm also using this level and don't have a problem). Regards, Wouter. -Oorspronkelijk bericht- Van: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]Namens Rafael Mendez Verzonden: donderdag 15 november 2001 16:36 Aan: [EMAIL PROTECTED] Onderwerp: Version 4.2.1.7 Hi all, Does anyone have installed the 4.2.1.7 patch for TSM server? We are planning to install this patch but we want to know if the problems on 4.2.1.6 version are fixed. Any comments? TIA Rafael Mindez Prosol Ingenierma Madrid-Spain -- Obtin gratis tu cuenta de correo en StarMedia Email. !Regmstrate hoy mismo!. http://www.starmedia.com/email --
Re: TSM Bare Restore AIX Different Arch
We had used SYSBACK to perform three functions in addition to TSM: Copy rootvg to a SYSBACK server on a monthly basis. Total of 200+ systems. Cut a tape remotely for all systems on a semiannual basis. Create a network boot option and refreshed all the bootp servers and boot client roles on a quarterly basis. You can see SYSBACK features in the following URL: http://sysback.services.ibm.com/sysback.nsf/en/features Frank Tsao [EMAIL PROTECTED] PAX 25803, 626-302-5803 FAX 626-302-7131 Kauffman, Tom To: [EMAIL PROTECTED] KauffmanT@NIcc: BCO.COM Subject: Re: TSM Bare Restore AIX Different Arch Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] RIST.EDU 08/22/2001 08:50 AM Please respond to ADSM: Dist Stor Manager Dave, we use much the same approach as your current one, with similar problems on the mksysb. We try to run a mksysb at least monthly, or after maintenance is applied to AIX. The difference is that our mksysb tapes go off-site after we cut them. Is there any reason you can't do this? If you really can't off-site the mksysb tapes, I'd seriously look at setting up one system as a network install master with just AIX and TSM on it. Back when we had the SP frames this was our Control Workstation. It had one current mksysb image file, for the TSM server. Get this box up, network install the TSM server, use TSM to restore the filesystem of current (weekly, in our case) mksysb images for the other systems, and network install them. You still have the problem of getting an off-site non-tsm backup of this system though -- unless your D/R window is long enough to allow building the TSM server with a 'vanilla' AIX image, followed by restoring the filesystem of images, followed by re-booting the TSM server again from the archived image. Tom Kauffman NIBCO, Inc -Original Message- From: Dave Z [mailto:[EMAIL PROTECTED]] Sent: Wednesday, August 22, 2001 9:42 AM To: [EMAIL PROTECTED] Subject: TSM Bare Restore AIX Different Arch Folks, I apologize if this is a FAQ (I cannot find a complete documented procedure) :0( Currently, we use the following procedure to restore systems: 1) Restore the OS using the cloaner method as published by IBM: a) Boot off of the AIX installation media b) Restore system from tape (mksysb) (This allows you to recover the OS to dissimilar hardware) 2) Reconstruct the network (including the TSM backup network). 3) Restore all application data (and system data if needed) via TSM. This methodology does not support a true DR test as our mksysb tapes are not cut regularly or vaulted. Unfortunately we do not have a solution that allows us to cut bootable AIX tapes on a regular basis. (Not all of the systems have local tape drives. The procedure can not be automated. etc.) In the future we must restore all RS/6000s with only our vaulted installation media (OS and TSM) as well as our vaulted TSM tapes. Due to this we must develop procedures for a total bare metal restore of an RS/6000 using only the OS installation media, TSM backup tapes, and any relevant TSM disaster recovery reports. We would like to develop a procedure that details the recovery of a generic RS/6000 using only installation media, TSM backup, and disaster recovery reports. Ideas/Things to consider: We can not assume that we will recover systems to identical hardware. As such we can not simply install a base OS and restore. What system files (/etc/passwd, /etc/hosts, etc...) are relevant to the recovery of the system. What system files should not be recovered? (I.e. kernel, driver specific, etc.) Can anyone help with any existing procedures or point me in the proper direction? Thanks! DaveZ
