Re: too many filesystems to backup
Richard, Back in V1 of the product, the limitation of 20 operands on the command line was thought to be a good idea. Many (if not all) UNIX shells expand un-quoted wildcard characters with a list of files that match in the current directory. The limit of 20 operands was put in place to short-circuit a user who issued a command like: dsmc sel /home/* and accidentally got the wildcard expanded by the shell. In fact, the message you receive says something to that affect: ANS1102E Excessive number of command line arguments passed to the program! ANS1133W An expression might contain a wildcard not enclosed in quotes. You are correct in pointing out that in today's environment 20 operands is not very flexible. To that end, here is what I can tell you about the current product and welcome any suggestions. In TSM 4.2.2 and 5.1.5.2, we introduced the testflag NOOPERANDLIMIT. Coded on the command line as: dsmc sel -testflag=nooperandlimit This gives UNIX systems the ability pass in up to 450 operands (in 4.2.2); in 5.1.5.2 it is for all operating systems and the limit is 512. Having said this, you may encounter another one of the TSM backup-archive client's command-line parsing limits: only 2048 total bytes are allowed. If this is exceeded, you will see message: ANS1209E The input argument list exceeds the maximum length of 2048 characters. The customers for whom the NOOPERANDLIMIT (all of whom were running UNIX) was introduced have been satisfied with the new operand limit and there have not yet been any complaints about only accepting 2048 bytes. Questions to you: 1. Do you think TSM is being too cautious in trying to protect the wild-card expansion, i.e., would you rather see us just drop the testflag and let the client accept 512 (or more) operands. Is this worth the trade-off of stopping unwanted wild-card expansions? 2. Any thoughts about how many operands and bytes one really needs the command-line client to accept (if 512 operands / 2048 bytes is not sufficient). Thanks, Jim Smith J.P. (Jim) Smith TSM Client Development >I have an AIX system which has 65 filesystems in total and I want to >backup 27 filesystems out of these. Is there any other way apart from >specifying each one of them (there again we have limitaion of max 20 >objects in a single schedule/command). Anything more intelligent (???) >is welcome... The limit of 20 names on a command line is some developer's mighty poor concept of product usability, artificially handicapping the command in an environment which affords far more flexibility. You can get around this with the Unix 'xargs' command. I'd recommend getting familiar with it, as it can be very useful. Richard Sims, BU
Re: Sub-File Backup - 1 GB Limit
Subfilecachesize could be raised; please submit a requirement and let us know what types of cache sizes you need. The cache size is not bounded by the 32-bit differencing image limit. System objects and subfile processing would be very difficult. I would suggest pushing a requirement for incremental processing of system files, which are the files that get resent on every system object backup that are probably causing the majority of your woes. That would probably alleviate your problem and be a more applicable solution to other problems in this area. Thanks, Jim Thanks, Jim J.P. (Jim) Smith TSM Client Development [EMAIL PROTECTED] Hi Jim postings from development are always welcome. Beeing curious I (mis)use your readiness and ask you prior to opening a requirement: Are you limited with 32-bit addressing with SubFileCachesize with its maximum of 1 GB as well, or would it be simple for you to raise this limit significantly higher? The business case is ability to backup (almost) whole filesystems on small file servers over leased lines with limited throughput. And - any would it be troublesome to apply differencing technology for system objects backup? The business case is ability to backup enormous system objects from servers with microsoft systems over leased lines with limited throughput. best regards Juraj Salak, Asamer Holding > -Original Message- > From: Jim Smith [mailto:[EMAIL PROTECTED]] > Sent: Monday, January 06, 2003 10:00 PM > To: [EMAIL PROTECTED] > Subject: Re: Sub-File Backup - 1 GB Limit > > > Tim, > > Actually, two different behaviors based on two-different > problems. Files > that start less then 2 GB but grow > 2 GB will continue to use subfile > backup as long as the other requirements for the base file > (i.e., the file > on the client cache) is still valid. The limiting factor here is that > there is only 32-bit support in the differencing subsystem that we are > using. We chose 2 GB on the onset (instead of 4 GB) as the > limit to avoid > any possible boundary problems near the 32-bit addressing > limit and also > because this technology was aimed at the mobile market (read: > who is going > to have files on their laptops > 2 GB). I understand that there are > several shops that use this technology beyond the laptop environment. > Ultimately, the solution is to have a 64-bit subsystem in > place so that we > can go beyond 4 GB. I suggest a requirement to Tivoli if this is > important to your shop. > > The low-end limit (1024 bytes) was due to some strange behavior with > really small files, e.g., if a file started out at 5 k and then was > truncated to 8 bytes. The solution was to just send the > entire file if > the file fell below the 1k threshold. We can get away with resending > these small files because ... they are small files! It is > probably a wash > to resend or to try to correctly send a delta file in this case. > > Hope this helps. > > - Jim > > J.P. (Jim) Smith > TSM Client Development > [EMAIL PROTECTED] > > > Thanks Jim! > > I was confusing "size of base file falls < 1024" with 1 GB! > > So if a file starts at less than 2 GB but then grows bigger > than 2GB it > will > no longer be eligible? Similar if a file falls below 1024 bytes? > > Thanks again! > > Tim > > -Original Message- > From: Jim Smith [mailto:[EMAIL PROTECTED]] > Sent: January 3, 2003 4:36 PM > To: [EMAIL PROTECTED] > Subject: Re: Sub-File Backup - 1 GB Limit > > Tim, > > Actually, the subfile limit is 2 Gig; if a file size > 2 Gig > then TSM will > not bother to copy the base file to the client cache, so it > could not be a > candidate for subfile processing on a subsequent backup. > > Thanks, > Jim > > J.P. (Jim) Smith > TSM Client Development > [EMAIL PROTECTED] > > > Last August, Jim Smith wrote: > > > >Today the client code will send a new base file in these cases: > > > >- if the last time the detla was taken, the ratio of > delta:base is > .40 > >- digital signature of base is incorrect or doesn't match > signature on > >server > >- base entry on client cache is dirty, i.e., never committed on the > server > >- size of base file falls < 1024 > >- file is excluded from subfile backup processing, i..e, > exclude.subfile > >- file is encrypted by Windows efs > > > I just want to double check, does this mean that there is > still the 1GB > limit for subfile backup? Ie. If a file is > 1 GB, is it > ineligible for > subfile processing? > > Thanks, > > Tim Rushforth > City of Winnipeg >
Re: Sub-File Backup - 1 GB Limit
Len, I would open a requirement for the > 2 gig limit. Also, where do you need the limit to be? 4 gig ? higher ? The limits of the subfile cachesize have not changed. Is 1024 MB not sufficient ? If not, what would you like to have? Once again, if you need work in this area please open a requirement. If you do not code the cachesize in dsm.opt it takes the default value of 10 MB. Thanks, Jim J.P. (Jim) Smith TSM Client Development [EMAIL PROTECTED] In article <[EMAIL PROTECTED]>, Jim Smith <[EMAIL PROTECTED]> says: > >Tim, > >Actually, the subfile limit is 2 Gig; if a file size > 2 Gig then TSM will >not bother to copy the base file to the client cache, so it could not be a >candidate for subfile processing on a subsequent backup. > >Thanks, >Jim > >J.P. (Jim) Smith >TSM Client Development >[EMAIL PROTECTED] Hello Jim We are a big user of the sub file feature and this explains some of our long ru nning backups. Any chance that TSM Client Development will increase the 2gig limit. Also in the early doc it said that the client subfile client cache size had a limit of 1024meg(SUBFILECACHESIZE). Is this still the limit for SUBFILECACHESIZE? And is the SUBFILECACHESIZE statement still required in the dsm.opt file? Thanks len boyle - Leonard Boyle [EMAIL PROTECTED] SAS Institute Inc. ussas4hs@ibmmail Room RB448 [EMAIL PROTECTED] 1 SAS Campus Drive (919) 531-6241 Cary NC 27513
Re: Sub-File Backup - 1 GB Limit
Tim, Actually, two different behaviors based on two-different problems. Files that start less then 2 GB but grow > 2 GB will continue to use subfile backup as long as the other requirements for the base file (i.e., the file on the client cache) is still valid. The limiting factor here is that there is only 32-bit support in the differencing subsystem that we are using. We chose 2 GB on the onset (instead of 4 GB) as the limit to avoid any possible boundary problems near the 32-bit addressing limit and also because this technology was aimed at the mobile market (read: who is going to have files on their laptops > 2 GB). I understand that there are several shops that use this technology beyond the laptop environment. Ultimately, the solution is to have a 64-bit subsystem in place so that we can go beyond 4 GB. I suggest a requirement to Tivoli if this is important to your shop. The low-end limit (1024 bytes) was due to some strange behavior with really small files, e.g., if a file started out at 5 k and then was truncated to 8 bytes. The solution was to just send the entire file if the file fell below the 1k threshold. We can get away with resending these small files because ... they are small files! It is probably a wash to resend or to try to correctly send a delta file in this case. Hope this helps. - Jim J.P. (Jim) Smith TSM Client Development [EMAIL PROTECTED] Thanks Jim! I was confusing "size of base file falls < 1024" with 1 GB! So if a file starts at less than 2 GB but then grows bigger than 2GB it will no longer be eligible? Similar if a file falls below 1024 bytes? Thanks again! Tim -Original Message----- From: Jim Smith [mailto:[EMAIL PROTECTED]] Sent: January 3, 2003 4:36 PM To: [EMAIL PROTECTED] Subject: Re: Sub-File Backup - 1 GB Limit Tim, Actually, the subfile limit is 2 Gig; if a file size > 2 Gig then TSM will not bother to copy the base file to the client cache, so it could not be a candidate for subfile processing on a subsequent backup. Thanks, Jim J.P. (Jim) Smith TSM Client Development [EMAIL PROTECTED] Last August, Jim Smith wrote: >Today the client code will send a new base file in these cases: > >- if the last time the detla was taken, the ratio of delta:base is > .40 >- digital signature of base is incorrect or doesn't match signature on >server >- base entry on client cache is dirty, i.e., never committed on the server >- size of base file falls < 1024 >- file is excluded from subfile backup processing, i..e, exclude.subfile >- file is encrypted by Windows efs I just want to double check, does this mean that there is still the 1GB limit for subfile backup? Ie. If a file is > 1 GB, is it ineligible for subfile processing? Thanks, Tim Rushforth City of Winnipeg
Re: Sub-File Backup - 1 GB Limit
Tim, Actually, the subfile limit is 2 Gig; if a file size > 2 Gig then TSM will not bother to copy the base file to the client cache, so it could not be a candidate for subfile processing on a subsequent backup. Thanks, Jim J.P. (Jim) Smith TSM Client Development [EMAIL PROTECTED] Last August, Jim Smith wrote: >Today the client code will send a new base file in these cases: > >- if the last time the detla was taken, the ratio of delta:base is > .40 >- digital signature of base is incorrect or doesn't match signature on >server >- base entry on client cache is dirty, i.e., never committed on the server >- size of base file falls < 1024 >- file is excluded from subfile backup processing, i..e, exclude.subfile >- file is encrypted by Windows efs I just want to double check, does this mean that there is still the 1GB limit for subfile backup? Ie. If a file is > 1 GB, is it ineligible for subfile processing? Thanks, Tim Rushforth City of Winnipeg
Re: Question about Veritas Cluster and filespace name
All, The TSM Backup-Archive client has support for MSCS (Windows), HACMP (AIX) and NCS (NetWare) clustering solutions. If you are using a clustering solution on one of the Intel platforms other then these listed, you will have these naming issues after a fail-over. We are looking into something similiar to what Peter is suggesting, and that is a way to logically manage a set of data on the TSM server which is sent from different client nodes. This would be beneficial for clustering as well as have other applications. We are also pursuing adding support for some of these other clustering solutions. It doesn't hurt to open requirements to Tivoli if you have a particular cluster solution that you would like to see supported. Thanks, Jim Smith TSM client development In response to: >You know, there seems to be a similar issue with filespace naming with the new Netware cluster aware client. >We're awaiting a server upgrade to pursue it further. Seems as it the 'getservername' API call is at the heart of this. Yes, it seems TSM is not savey of any cluster soloutions except Microsoft's. If they (TSM) would only introduce a new option in the .opt file so one could override the servername if for some reason or another one should wish to do so. It would probably solve the naming problem in most cluster sitiations. Regards Peter J.P. (Jim) Smith TSM Client Development [EMAIL PROTECTED]
Re: Security question about number of bits used
TSM does use DES 56-bit encryption and it is currently not possible to change the method/strength. If you have additional requirements above and beyond DES 56-bit encryption, please open a requirement with Tivoli through your marketing rep. If you open a requirement can you please make sure to specify the following points: 1. encryption is for data encryption, authentication, secure communication, all of the above, etc. 2. if higher key strength is need, what is needed 3. if different algorithm is needed, e.g., AES, or if ability to plug-in different algorithm is needed 4. if user key management is needed This would help us understand what we need to do with our product set. Thanks, Jim Smith TSM development Hi all. It's posible to change the cypher method or the number of bits. I think TSM use DES 56 bits? Thanks. Estanislao Sanmartín Rejo [EMAIL PROTECTED]
Re: Encryption
Dwight, You are correct that compressed data would not encrypt well, since TSM uses a compression algorithm that works well with redundant data (and compression kills redundancy) - but, the TSM b/a client does in fact compress first and then encrypt the data to avoid this. So go ahead and use both encryption and compression if you would like. I don't have any performance data from development on the b/a client using encryption. What we did test in development was the b/a client vs. plain DES 56-bit encryption algorithms to make sure the client was not adding unnecessary overhead. DES is allot of number crunching, and it is by nature very CPU intensive and will slow the b/a client down noticeably. Thanks, Jim Smith TSM Client Development Been a while and I'd have to double check but... You might not want to use compression if you use encryption... I believe it encrypts first then tries to compress and encrypted data doesn't compress (much). Something to double check. Dwight -Original Message- From: J D Gable [mailto:josh.gable@;eds.com] Sent: Monday, October 21, 2002 4:13 PM To: [EMAIL PROTECTED] Subject: Encryption Does anybody have any evidence/research as to what kind of additional overhead encryption puts on a client when processing a backup (CPU, Memory, etc.)? I am running some tests myself, but the numbers are staggering (we're seeing up to a 300% increase in the backup time in some cases). I understand that it is largely based on the horsepower of the node, but I was wondering if anyone else is seeing the same, or if anyone knew a place I could get some additional info on encryption. Thanks in advance for your time, Josh
Re: TSM Encryption
Jim, I would recommend that you open a requirement against the product for stronger encryption. By the way, what are the HIPAA requirements as they relate to data encryption? Are these well documented? Thanks, Jim Smith TSM development >>> Hello Jim Follow up question, Can you ask if there is anyway for us to get clients that do stronger encryption, eg tripledes? If not, are there plans in the future to offer strong encryption? This relates to the HIPAA requirements that are coming. Thanks again. Jim Sporer At 10:32 AM 9/26/2002 -0700, you wrote: >Jim, > >The TSM Backup/Archive client uses 56-bit DES encryption. > >Thanks, >Jim Smith >TSM Development > > >>> >Does anyone know what level of encryption is done when using the INCLUDE >ENCRYPTION option in your dsm.opt file? Is it DES, triple DES or what? >Jim Sporer >[EMAIL PROTECTED]
Re: TSM Encryption
Jim, The TSM Backup/Archive client uses 56-bit DES encryption. Thanks, Jim Smith TSM Development >>> Does anyone know what level of encryption is done when using the INCLUDE ENCRYPTION option in your dsm.opt file? Is it DES, triple DES or what? Jim Sporer [EMAIL PROTECTED]
Re: Win2k system state restore
Dave, The TSM B-A client does have a facility to not replace the hardware dependent driver information during a system object restore. Let me explain: The traditional method backup/restore of the registry was for the backup product to export the registry files and backup the exported files. For restore, the backup product would simply then restore the files to a staging area and import the information back into the registry (the activation of the registry, if you will). This was a pretty simple exercises for a backup product. When Windows 2000 arrived Microsoft changed the procedure a bit and introduced the registry key: HKLM\SYSTEM\CurrentControlSet\Control\BackupRestore\KeysNotToRestore. The basic procedure now is the backup product restores the registry information to the staging area (as before) but now is required to move information from the current registry (these KeysNotToRestore) over the information that was just restored and then activate the registry. This is basically allowing information in the current registry to be preserved across a restore and reboot. Systems like Active Directory rely on this as they write information about the log reply into the current registry which would otherwise be overwritten by the restored copy of the registry and not available after the reboot. Another system which exploits this is the Plug & Play subsystem which describes the hardware dependent driver information about which you are inquiring. This subsystem preserves the information in the HKLM\SYSTEM\CurrentControlSet\Enum portion of the registry among other things. While TSM uses the procedures that Microsoft outlines regarding registry restoration, we found that by default the administrator doesn't have the proper permissions to write into Enum branch. This information is well documented in APAR IC34015. The APAR will be fixed in TSM 5.1.5; a simple work around involving using regedit to grant the proper permissions is documented in the APAR if you are using the TSM 4.2.2 client or TSM 5.1.0 client. Having said all this, I caution that Microsoft does not guarantee that you can always restore from hardware a to hardware b. If you are using Ntbackup.exe, then it would be safe for me to say that if your particular environment can be brought back by Ntbackup.exe then TSM should be able to do it as well. Hope this helps, Jim Smith TSM Development >>> Dear All, Does anybody know if there is any plan in future releases of the TSM client for W2K, to implement a facility to not replace the hardware dependent driver information during a system object restore. My reason for asking ; We have a requirement to fully restore a W2K server back to different hardware (ie. different RAID controller and/or different processor architecture) At present, our solution is to use NTBACKUP to backup the system state and TSM to backup the remainder. NTBACKUP is intelligent enough to not restore hardware dependent drivers back onto a platform that is different. I cannot get TSM to emulate this. The above solution is OK, but I am backing up the WINNT directory with TSM as flat files, then I am backing up the System Object with TSM and finally backing up the flat file generated by the NTBACKUP system state operation. It all seems a bit needless really. ( I know I could exlude WINNT but as yet I don't know of any way to exclude the systemobject). Any thoughts or knowledge of future client releases would be welcome. Thanks regards, -=Dave=- -- +44 (0)20 7608 7140 "I'll be Bach." - Johann Sebastian Schwarzenegger www.guardianit.com The information contained in this email is confidential and intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication is strictly prohibited. Guardian iT Group will accept no responsibility or liability in respect to this email other than to the addressee. If you have received this communication in error, please notify us immediately via email: [EMAIL PROTECTED] This e-mail has been scanned for all viruses by MessageLabs.
Re: Restoring MSCS cluster node
J.P. (Jim) Smith TSM Client Development [EMAIL PROTECTED] Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject:Restoring MSCS cluster node Hi. Has anyone got an idea how to perform "bare metal" restore of MSCS cluster node (win2k, winNT)? I have performed a lot of tries to do that. Sometimes it succeeds sometimes doesn't. According to the redbook sg24-6141 "Deploying the TSM client in a win2k env" I restored ALL system object including cluster db but cluster services were not running (of course) and restore failed. So I restored system objects except cluster db (first time it succeeded). If you know any better redbook than above or if you have any experience in it please HELP ME! -- --== KKus ==--
Re: Restoring MSCS cluster node
Hello Krzysztol, We are in the process of producing a white paper on this subject. I will try to summarize the basic points for you. I believe these points to be in-line with what Microsoft's native backup program Ntbackup.exe provide. I will use the term "backup product" to mean TSM B-A client or Ntbackup.exe to indicate the similarities in the procedures. The most basic scenario is that you have lost a node from the cluster and the cluster is still operational. In this case, the cluster database is not restored to the lost system but re-installed. If you follow the TSM Redbook procedures this means that after you have installed Windows + Service Packs from the install media you would install the cluster db, then restore the data (system data and system objects) from the backup product. If you need to restore the cluster database because you've lost all of the nodes in the cluster or there has been corruption introduced into the database, then you can restore the cluster database from the backup product. (If you have lost the entire node, then this would be in the context of a disaster recovery meaning you would restore the cluster as part of the system object backup; if you are only restoring the quorum disk, you can restore only the cluster database). This act of restoring the data from the backup product will place the cluster information into a staging area. At this point, MS provides a tool called clustrest.exe (part of the resource kit) which copies the restored data into the correct location and restarts the cluster. There is more detail on these scenarios in the upcoming paper. The first scenario I mentioned can be carried out on NT 4.0 or Windows 2000 since the backup product is not really involved in the restore of the cluster database. The other scenarios (restoring the cluster database from the backup product and using clusrest.exe) relies on an API available only in Windows 2000. (Microsoft does not offer this API for NT 4.0). One last note - it is not sufficient to simply backup/restore the Cluster hive in the registry as this does not guarantee consistency of the cluster database. The restores must use the Microsoft API. Let me know if you need any additional clarification. Thanks, Jim J.P. (Jim) Smith TSM Client Development > Hi. Has anyone got an idea how to perform "bare metal" restore of MSCS cluster node (win2k, winNT)? I have performed a lot of tries to do that. Sometimes it succeeds sometimes doesn't. According to the redbook sg24-6141 "Deploying the TSM client in a win2k env" I restored ALL system object including cluster db but cluster services were not running (of course) and restore failed. So I restored system objects except cluster db (first time it succeeded). If you know any better redbook than above or if you have any experience in it please HELP ME! -- --== KKus ==--
Re: Backing Up Dir's
Rikk, Are you observing this behavior? When NetWare is restoring files which do not have a supporting directory structure, a temporary directory entry (i.e., no trustee information) is created by Novell's backup API; when the directory entries do come from the server at a later time they are restored over the temporary directory entry; the end result is that the files and directories are restored fully and correctly regardless of their ordering from the server. If you are not seeing this behavior, I would suggest talking to the service organization. Thanks, Jim J.P. (Jim) Smith TSM Client Development >>> We currently backup 12 Netware servers nightly, I also now need to backup the directory structure as a seperate backup job. The reason for this is that in a DR when you do a complete restore of a Netware server if TSM attempts to restore a file before the dir for it has been restored it skips the file, so the idea is to backup the dir's seperatly then come DR to restore all the dir's then do a normal restore over it. What I need to know is how would I got about backing up just dirs to a seperate pool? Thanks in advance. ..Rikk > iTNET > Rikk Cahill > 3rd Line Server Support > [EMAIL PROTECTED] > Equitas London 0207-342-2358 > > Equitas Limited, 33 St Mary Axe, London EC3A 8LL, UK NOTICE: This message is intended only for use by the named addressee and may contain privileged and/or confidential information. If you are not the named addressee you should not disseminate, copy or take any action in reliance on it. If you have received this message in error please notify [EMAIL PROTECTED] and delete the message and any attachments accompanying it immediately. Equitas reserve the right to monitor and/or record emails, (including the contents thereof) sent and received via its network for any lawful business purpose to the extent permitted by applicable law Registered in England: Registered no. 3173352 Registered address above
Re: Please Explain!!" TSM and Windows 2000 Active Directory.
Tony, It is hard to get two people to agree on a precise definition for "bare metal restore" - I think I can generalize and say that it is a restore process that involves restoring backup data to a piece of undeveloped disk real estate, e.g., a disk that isn't formatted or is formatted with a different operating system, different flavor of an operating system ... etc. Some time ago it was the procedure that allowed you to boot from a floppy disk and execute the entire restore of the machine without using any install media. The TSM b-a client does not have a mechanism to restore a Windows 2000/XP machine in this manner. So, "we don't support bare metal restore" really should read "we don't have a native bare metal restore for Windows 2000/XP". What TSM does offer is a restore solution that can be used in the context of a disaster recovery, i.e., starting from an OS installation from media + installation of the TSM b-a client, you can restore your Windows 2000/XP systems to a state from a previous backup by restoring the data and the "system state" (MS term)/"system objects" (TSM term). This procedure is documented in the Redbook "Deploying the Tivoli Storage Manager Client in a Windows 2000 Environment (SG24-6141-00)". We do support this function and this procedure, i.e., take service calls and accept APARs for this function. Users have been successfully deploying this solution in their environments. Another area of confusion is "restore to different hardware" - which can mean anything from swapping identical disks out, upgrading to larger disks, to changing controllers. These procedures require the backup product to preserve some of the current hardware settings in the registry after the restore, i.e., merge the information in the active registry with the information in the registry that comes back during the restore. The TSM b-a client is designed to Microsoft's rules governing this registry merge (see APAR IC34015 which discusses granting the proper Administrator permissions for this to function correctly). Having said that, I must warn that even Microsoft doesn't give any guarantees when restoring to different hardware configurations. You may hear "we don't support that!" in the context of restoring to different hardware configurations for this reason. Customers have also had success doing this and our support organization generally tries to help out as much as they can with these situations. Hope this helps, Jim Smith TSM b-a client development Hello, Tim makes a very good point in the last sentence of the 1st paragraph. "It's tough talking to TSM support when doing Bare Metal Restores - I get the line - We don't support that!"... Now I know I have seen some TSM tech support people respond on this listserv; Could someone please define, once and for all, what TSM means by Bare Metal restore? I mean..if they "do" support the backup and restoring of the "guts of Win2K in AD" (i.e. System State/Objects) Why do they say "We don't support that!"? I have spoken with TSM tech support over phone and they say that they can backup and restore the AD...However, the one answer I got over the phone was that they(TSM), will not say we support BMR is because they do not want to get caught up in supporting M.S.'s OS. So please can some one define Bare Metal Restore? Thanks -Original Message- From: Rushforth, Tim [mailto:[EMAIL PROTECTED]] Sent: Friday, July 05, 2002 9:21 PM To: [EMAIL PROTECTED] Subject: Re: "Please HELP !!" TSM and Windows 2000 Active Directory. I've just done some bare metal restore tests with 5.11 client on w2k dc in a test environment. 2 DC's in AD domain, native mode, integrated DNS, both servers Global Catalog servers. All fsmo's on dc1, I restored dc2. The restore worked fine except for TSM. Failed to start one of the services after the restore - said a file was missing. (TSM was installed via Group Policy). Had to play around a bit to uninstall TSM then reinstall then things seemed to work fine. I've run into something similar with a 4.1 client and DC restores. It's tough talking to TSM support when doing Bare Metal Restores - I get the line - We don't support that! I've done multiple member server restore tests with 5.11 and never ran into this problem but ran into it 2 times on dc restores. I also tried a retrieve combined with MS system state restore. This seemed to work better (here no problems with tsm but there were a couple weird ad messages). But the resulting system seemed to be fine. All of my restores were to exact same h/w. You just have to be sure to be backing up the system state (DOMAIN ALL-LOCAL will do it). For a DC I would recommend running MS Backup of System State as insurance. Tim Rushforth City of Winnipeg -
Re: Backup a W2K Domain Controller?
Tony, Some clarification: the restore of the Active Directory has two distinct pieces. The backup product puts the files (db, logs, etc.) back into the proper location and then the system, upon reboot, replays the logs and synchronizes the AD with the organization. This synchronization is by default "non-authoritative", i.e., what is restored gets synchronized by "catching-up" to the rest of the organization. Some of the cases that you list imply an "authoritative restore", i.e., the rest of the organization needs to synch-up to what has been restored. Microsoft does not give backup vendors the ability to mark the AD restore as authoritative. To do this, you will need to use the tool "ntdsutil.exe" which is shipped with Windows 2000 servers. This allows you to mark an object, container, section or entire AD as authoritative. Generally, the procedure is: 1. restore the system following the procedures in the Redbook (see my previous post) 2. reboot into Directory Services Restore Mode 3. use ntdsutil.exe to mark the restore as authoritative 4. reboot again. Since ntdsutil.exe is Microsoft's tool, you might need to have MS support stand by TSM support until any issues are resolved. Thanks, Jim Smith TSM b-a client development Given the Examples of backup reasons below: Has any one every had a AD corruption that that used TSM to recover from after the GC's have already replicated that corrupted data out? If so, did TSM support stand by them all the way until the issue was resolved?? We are sort of leery about using TSM so the simple reason that they always say "We do not support BMR" and on a DC with AD this is critical. Any help would be great "1.) Botched Schema update 2.) Accidental deletion of OU (or any other object) 3.) Database corruption (AD Corruption) 4.) System State. 5.) Accidentally deletion of a DNS zone 6.) Some DC's are also File/Print servers, DHCP, etc. *** Some of these scenarios would require an authoritative restore or a complete rebuild of the Active Directory, as some changes are replicated immediately." -Original Message- From: Jon Adams [mailto:[EMAIL PROTECTED]] Sent: Thursday, July 11, 2002 1:09 AM To: [EMAIL PROTECTED] Subject: Re: Backup a W2K Domain Controller? Thank you Jim. I will add this to the followong reasons I just learned a few moments ago: "Botched" Schema update Accidental deletion of OU (or any other object) Database corruption System State Accidentally deletion of a DNS zone Some DC's are also File/Print servers, DHCP, etc. Some of these scenarios would require an authoritative restore or a complete rebuild of the Active Directory, as some changes are replicated immediately. ...and as you mentioned Jim, time to synch. verses restore. -Original Message- From: Jim Smith [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 10, 2002 5:57 PM To: [EMAIL PROTECTED] Subject: Re: Backup a W2K Domain Controller? Jon, I'm sure there are a number of pros and cons and I'll let others chime in ... one advantage of having a backup of the Active Directory on a given DC is time to recovery. While you can bring an active directory back by simply installing it and letting it synchronize to "catch-up" to the rest of the organization, this synchronization can take quite a long time depending on the size of the directory. In this case, a backup product can give you a point-in-time copy of the active directory such that the synchronization process only has to "catch-up" from a time in the recent past. The time to restore from a tape can be much quicker then doing a synchronization from ground-zero. - Jim J.P. (Jim) Smith TSM Client Development Here's an interesting question: why would you want to backup a DC, especially where you have a DC (W2K) or two in every remote site of the WAN? Why/what would you ever restore that you wouldn't get from the other domain controllers if one or even a few are down? I ask this because my theory is "when in doubt, backup it up". At a couple hundred dollars a license it seems a reasonable assurance policy (depending on the budget, of course). Another theory applies here as well, "backup everything, exclude only as needed, even if that client options set gets pretty big". Jon R. Adams IT IPS BST Infrastructure Premera Blue Cross Mountlake Terrace, WA 425-670-5770 [EMAIL PROTECTED]
Re: Backup a W2K Domain Controller?
Jon, I'm sure there are a number of pros and cons and I'll let others chime in ... one advantage of having a backup of the Active Directory on a given DC is time to recovery. While you can bring an active directory back by simply installing it and letting it synchronize to "catch-up" to the rest of the organization, this synchronization can take quite a long time depending on the size of the directory. In this case, a backup product can give you a point-in-time copy of the active directory such that the synchronization process only has to "catch-up" from a time in the recent past. The time to restore from a tape can be much quicker then doing a synchronization from ground-zero. - Jim J.P. (Jim) Smith TSM Client Development Here's an interesting question: why would you want to backup a DC, especially where you have a DC (W2K) or two in every remote site of the WAN? Why/what would you ever restore that you wouldn't get from the other domain controllers if one or even a few are down? I ask this because my theory is "when in doubt, backup it up". At a couple hundred dollars a license it seems a reasonable assurance policy (depending on the budget, of course). Another theory applies here as well, "backup everything, exclude only as needed, even if that client options set gets pretty big". Jon R. Adams IT IPS BST Infrastructure Premera Blue Cross Mountlake Terrace, WA 425-670-5770 [EMAIL PROTECTED]
Re: Exclusions added to dsm.opt
Joe, It is doubtful that you will have any problems with restore; the reason why most of these files are excluded is that they are held exclusively and you will not be able to backup the files in the first place. Exceptions to this are things like the temporary internet files which are excluded because they are somebody's temporary work area and are not needed - these are innocuous also and it will not hurt if they are restored. Newer versions of the TSM b-a client (4.2.2, 5.1.0) automatically exclude most of these files, so they are no longer needed in dsm.opt (we're trying to make sure any of the recommended exclude lists that are documented reflect this). Try to issue a Q INCLEXCL from the command-line client and you will see several exclude statements which have a Source File of Operating System. We get these values from the registry key: HKLM\SYSTEM\CurrentControlSet\Control\BackupRestore\FilesNotToBackup Microsoft uses this key to communicate exclude lists to backup products. Thanks, Jim Smith TSM client development I found the section in the manual that covers the recommended Windows system files to exclude (see below). I changed the dsm.opt files to reflect this list. My question is: If I attempt a full restore will these files that got backed up (prior to me excluding them) restore and risk corrupting windows as the manual suggests? If so, how do I address this? exclude "*:\microsoft uam volume\*" exclude "*:\microsoft uam volume\...\*" exclude "*:\...\ea data. sf" exclude "*:\...\pagefile.sys" exclude "*:\...\ibmbio.com" exclude "*:\ibmdos.com" exclude "*:\msdos.sys" exclude "*:io.sys" exclude.dir *:\recycled exclude.dir *:\recycler exclude.dir *:\...\system32\wins exclude.dir *:\...\system32\LServer exclude.dir *:\...\system32\dhcp exclude.dir *:\...\system32\config exclude.dir "*:\system volume information" exclude *:\...\system32\perflib*.dat exclude.dir "*:\...\temporary internet files" exclude "*:\documents and settings\...\ntuser.dat.LOG" exclude "*:\documents and settings\...\ntuser.dat" exclude "*:\documents and settings\...\usrclass.dat.LOG" exclude "*:\documents and settings\...\usrclass.dat" Thanks in advance - Joe McAllister Grundfos Pumps Corp.
Re: Error Backup Unix Client: TCP/IP received rc 25 trying to accept connection from server
Anja, This is a cosmetic error and is addressed in APAR IC32436 "TCP/IP RECEIVED RC 25 TRYING TO ACCEPT CONNECTION FROM SERVER". There is a good explanation in the APAR of the error. Thanks, J.P. (Jim) Smith TSM Development Hi all, I want to backup an Unix Client with our TSM Scheduler, but i get always this Error Message in the tsmerror.log at the Client. TCP/IP received rc 25 trying to accept connection from server We have TSM version 4.1.3 and the Client has Version 4.2.1 Can anybody please help me??? Thank you, Anja! Anja Frey Gm|nder ErsatzKasse GEK Abteilung EDV Gottlieb Daimler Str.19 73529 Schwdbisch Gm|nd Tel.: 07171/801-647 Fax.: 07171/801-706 E-Mail: [EMAIL PROTECTED] Internet: http://www.gek.de
Re: W2K Active Directory backup and edb000*.log files accumulating
Alex, This is being addressed in APAR IC33389 - TSM ACTIVE DIRECTORY BACKUP NOT TRUNCATING LOGS Thanks J.P. (Jim) Smith TSM Development I'm backing up a W2K Domain Controller with the 4.2.1.30 client to a 4.2.1.15 server. This includes the "domain systemobject", i.e. Active Directory. Recently I found a huge bunch of old transaction log files in the NTDS directory: edb1.log to edb0003e.log 10MB each. Each one was created when TSM backed up ADS. After 60 daily backups, I got of 600MB of these. When I run ntbackup.exe to make a systemstate backup these log files get erased, only the last one remained. But when I make the backup with TSM, the log files stay and accumulate. I cannot believe that this behaviour of TSM works as designed, because I would have to delete the older logfiles manually after some time or use a postschedulecmd to delete edb0*.log, which I would consider not a clean solution. I have not found a dsm.opt option to change the client's behaviour, and I have tried two other clients (4.2.1.20 and .32) which had similar behaviour. Does anybody know what's up with that issue? I assume everybody who is backing up Active Directory via the "domain systemobject" on a Domain Controller has this problem. But with today's gigabytes of disk space you may have not taken notice of that yet. Tschau Alex
Re: Backing up Active Directory on Win2000
Julie, To add to Tim's comments. The TSM B/A client processes all system objects which are active on the machine; there are now a total of eleven of these system objects (added the WMI db support in TSM 5.1.0) of which only a subset will be valid on a given machine. This subset depends both on the flavor of Windows 2000 installed (e.g., Pro vs. Server vs. Adv. Server ...) and which Windows components are installed (e.g., Active Directory is available with the W2k server edition but only active if it is installed). You can expand the System Object container in the Windows B/A GUI to see which system objects are active. Also, you can issue the command SHOW SYSTEMOBJECT (not documented) and see which objects are active: statrc system object --- - OK COM+ Database n/a 4312Certificate Server Database OK Event Log ... OK WMI Database >From this you can see that the COM+, Event Log and WMI Database are active but Cert. Server is not .. (I only showed partial output). As Tim mentions, the QUERY SYSTEMOBJECT shows you what is actually backed-up to the TSM server. Hope this helps, Jim Smith TSM Development ... >From the Backup/Archive Command line clinet (dsmc), enter q systemobject. It should show you the last backup date of all system objects. tsm> q systemobject Size Backup DateMgmt Class A/I File ----- --- 7,750 05/17/2002 00:04:27DEFAULT A SYSTEM OBJECT\SERVER1\compdb 717,644 05/17/2002 00:04:28DEFAULT A SYSTEM OBJECT\SERVER1\EVENTLOG 140,726,199 05/17/2002 00:04:34DEFAULT A SYSTEM OBJECT\SERVER1\SYSFILES 21,533,875 05/17/2002 00:11:37DEFAULT A SYSTEM OBJECT\SERVER1\SYSVOL 94,404,688 05/17/2002 00:14:20DEFAULT A SYSTEM OBJECT\SERVER1\NTDS 4,318,790 05/17/2002 00:14:32DEFAULT A SYSTEM OBJECT\SERVER1\REGISTRY 20,883 05/17/2002 00:14:34DEFAULT A SYSTEM OBJECT\SERVER1\RSM -Original Message- From: Julie Phinney [mailto:[EMAIL PROTECTED]] Sent: Friday, May 17, 2002 2:57 PM To: [EMAIL PROTECTED] Subject: Re: Backing up Active Directory on Win2000 Thanks, Tim, What's a Q systemobject? That command doesn't seem to produce anything, do I have it wrong? Thanks, Julie "Rushforth, Tim" <[EMAIL PROTECTED] To: [EMAIL PROTECTED] IPEG.MB.CA> cc: Sent by: "ADSM: Subject: Re: Backing up Active Directory on Win2000 Dist Stor Manager" <[EMAIL PROTECTED] DU> 05/16/2002 05:48 PM Please respond to "ADSM: Dist Stor Manager" Incremental backup process all of the system ojbects on our Windows 2000 Domain Controllers. I've done full restores with many client versions including 4.2.1.20 and 4.12.12. The default is to include system objects with DOMAIN ALL-LOCAL. What is your domain statement? Have you done a q systemobject from the b/a command line? Tim Rushforth City of Winnipeg -Original Message- From: Julie Phinney [mailto:[EMAIL PROTECTED]] Sent: Thursday, May 16, 2002 4:11 PM To: [EMAIL PROTECTED] Subject: Backing up Active Directory on Win2000 Hi all, I'm not familiar with Active Directory on Win2000 but I've been told by one of our Win2000 guys : There is a System Object selection list that includes the following items to backup using TSM: Active Directory, COM+ DB, Event Log, Registry, RSM, System Files, System Volume But it appears like only the following System Objects are currently being selected for backup: Event Log Registry RSM I'm wondering if by default, incremental backup does not back up all of the System Objects? Do I need to specify something in the DSM.OPT file or in a client optionset to get it to do all the system objects in Active Directory? Thanks, Julie Phinney
TSM FLASH: UNIX BACKUP-ARCHIVE CLIENT V4.2.2
Problem Description: The TSM 4.2.2 UNIX backup-archive clients may produce error messages similar to the following when performing incremental backup of files with hard links: ANS1228E Sending of object '' failed ANS4018E Error processing '': file name too long where is the name of the file that failed to back up. It is important to note that file names experiencing this problem are NOT too long. Message ANE4018E (same text as ANS4018E above) may also be logged to the TSM server. This problem affects files that have hard links. For affected files, the problem occurs only during incremental backup. SELECTIVE backup of these files works correctly. For files that have hard links, both the link and the original file may be affected by this problem: If the original file does not have a backup version on the TSM server, then the original file will experience the problem. If the hard link does not have a backup version on the TSM server, then the hard link will experience the problem. Files with hard links where the file already has a backup version (regardless of whether the link has a backup version) are unaffected. Hard links where the link already has a backup version (regardless of whether the original file has a backup version) are unaffected. Files that have no hard links are unaffected. Client APAR IC33645 has been opened to address this problem. The version 4.2.2 UNIX clients have been removed from the FTP download site. They will soon be replaced with newer client code that fixes this problem. Circumvention: Use SELECTIVE backup to back up those files that are affected by this problem. They can be identified by reviewing the ANS1228E and ANS4018E messages in the dsmerror.log file. The backup-archive GUI may also be used to back up these files. From the GUI, be sure to select the "Always backup" option (located in the drop-down list to the left of the "Help" button). Alternatively, customers who were running an earlier 4.2.x version of the client can remove 4.2.2 and reinstall the earlier version. Customers who upgraded from version 4.1.x or below can not back off, and must use the circumvention described above. We plan on having a fix available soon, so this circumvention is viewed as being very short-term. Users Affected: All TSM 4.2.2 UNIX backup-archive clients. Recommendation: Apply fixing code when available. We anticipate that the fix will be delivered on or before the end of May 2002. This statement was prepared by TSM Backup-Archive client development and system test
Re: TSM 422 client gone from ftp server?
The problem is reported in IC33645 and is only a problem with the TSM 4.2.2 backup/archive client; it has been addressed in TSM 5.1.0. We are working to provide more information about the specifics of the problem. Thanks, Jim J.P. (Jim) Smith TSM Client Development Well, that certainly explains that problem. Does anyone have a word if this problem is fixed in 5.1? I had plenty of people reporting that problem with Linux after upgrading to 4.2.2. Big whoops! thanks, bob On Fri, May 17, 2002 at 10:43:06AM -0500, Andrew Carlson wrote: > I am not privy to why it is not out there, but the AIX 4.2.2 client has > big problems. About 1/3 of all the files it backed up were rejected for > filenme too long. I suspect that is why it is gone. > > > Andy Carlson|\ _,,,---,,_ > Senior Technical Specialist ZZZzz /,`.-'`'-. ;-;;,_ > BJC Health Care|,4- ) )-,_. ,\ ( `'-' > St. Louis, Missouri '---''(_/--' `-'\_) > Cat Pics: http://andyc.dyndns.org/animal.html > > > On Thu, 16 May 2002, Bob Booth - UIUC wrote: > > > Does anyone know why or where the TSM 4.2.2 clients for some platforms are > > now missing from the IBM ftp server? 422 and LATEST are no longer out there > > for AIX, Solaris .. Among others.. > > > > Whats up? > > > > thanks, > > > > bob > >
Re: TSM 422 client gone from ftp server?
Bob, We have determined that there is a problem with the 4.2.2 UNIX backup-archive clients and they have been pulled from the ftp server. We are working to correct the problem. Expect to see a flash from IBM Tivoli shortly. Thanks, J.P. (Jim) Smith TSM Development Has someone reported this? I have not heard anything about UNIX clients at 4.2.2 having problems.. The Windows client still has the 422 directory and LATEST link. IBM/Tivoli? bob On Thu, May 16, 2002 at 04:24:14PM -0400, David Longo wrote: > Perhaps because there seems to be some problems with some of the > 4.2.2. stuff? > > David Longo > > >>> [EMAIL PROTECTED] 05/16/02 03:59PM >>> > I went out there earlier today myself and found what you found too. I'm > curious too. > > Dave Pearson > > > -Original Message- > > From: Bob Booth - UIUC [SMTP:[EMAIL PROTECTED]] > > Sent: Thursday, May 16, 2002 12:37 PM > > To: [EMAIL PROTECTED] > > Subject: TSM 422 client gone from ftp server? > > > > Does anyone know why or where the TSM 4.2.2 clients for some platforms are > > now missing from the IBM ftp server? 422 and LATEST are no longer out > > there > > for AIX, Solaris .. Among others.. > > > > Whats up? > > > > thanks, > > > > bob > > > > "MMS " made the following > annotations on 05/16/02 16:39:37 > -- > 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. > > ==
Re: Netware - NDS - Restoring NDS in case of extreme loss
David, You are correct - NDS not backed-up by default. Question for you - should it be? Some options: 1. backup NDS by default on every server that has a replica stored - this would mean redundant backups and also, as you have pointed out, walking the NDS from all these machines will be a performance concern. At least you would have the NDS backed-up out of the box and could turn off (via DOMAIN) this behavior where it wasn't wanted. 2. backup NDS by default on server with master replica of root partition ( or some other intelligent way of choosing a candidate server). Same as above, maybe this is not the "best" choice in your environment, but it is at least "a" choice and will mean that the NDS is backed-up by a machine by default.. Once again, could change behaviors through DOMAIN option. The scenario we are trying to avoid is having the NetWare admin discover that the NDS is not backed-up by default when it is time for a disaster recovery. I am interested in any ideas you or any other user would have about the TSM NetWare B-A client's default behavior when it comes to the NDS. Thanks, Jim Smith TSM development Yes, you can backup the NDS, but it is not backed up by default! Look in manual uder DOMAIN statement, you have to explicitly specify it. Then look at file Ntwback.htm loaded with yoyu Netware client install under ...Tivoli/Tsm/Client directory. If you have objects spread out over several machines, then I would do the NDS backup from the machien with least data/least busy. The backup of NDS "walks" the tree and gets from all machines. NOTE: License objects cannot be backed up! There is expalnation in documentation. Haven't tried a restore yet. David B. Longo System Administrator Health First, Inc. 3300 Fiske Blvd. Rockledge, FL 32955-4305 PH 321.434.5536 Pager 321.634.8230 Fax:321.434.5525 [EMAIL PROTECTED] >>> [EMAIL PROTECTED] 05/02/02 03:19PM >>> I've been asked by our NDS expert, if TSM backs up the netware hidden directory. Apparently it doesn't as I've watched TSM backup the NDS and it backups the individual NDS objects. Has anyone had to do a complete restore of a netware box, including NDS? Did it work, what steps did you take as the backup/archive manual for netware is lacking this kind of information "MMS " made the following annotations on 05/02/02 16:16:14 -- 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. ==
Re: Netware - NDS - Restoring NDS in case of extreme loss
Hello, Please refer to the "Tivoli Storage Manager for NetWare Backup-Archive Client Installation and User's Guide" Version 5 Release 1 which is available at the Tivoli web site. There is a chapter called "Tivoli Storage Manager NetWare Backup and Recovery Guide" which documents how to recover machines and NDS considerations (this was formally published as a separate white paper). Even if you are running the TSM V4 Netware B-A client, the information will still apply. I assume that the "hidden" directory you are talking about is the directory where the NetWare server physically stores the logical NDS information for which that server is responsible. The B-A client does not explicitly backup/restore this directory, but instead relies on using the NetWare backup API via the NDS target-service agent (TSANDS.NLM) to backup/restore NDS objects. Even if this directory were visible to a backup product, I don't think that you would be guaranteed any level consistency during a backup operation. Hope this helps, Jim Smith TSM development I've been asked by our NDS expert, if TSM backs up the netware hidden directory. Apparently it doesn't as I've watched TSM backup the NDS and it backups the individual NDS objects. Has anyone had to do a complete restore of a netware box, including NDS? Did it work, what steps did you take as the backup/archive manual for netware is lacking this kind of information
Re: Novell NetWare include/exclude for print queues
Steve, The "NetWare Backup and Recovery Guide" has a section concerning print queues and suggested include/excludes for NetWare 4.x; I don't think that the print queue handling has changed in NetWare 5.x so this information should be valid for NetWare 5.x as well (somebody please correct me if this assumption is not correct). J.P. (Jim) Smith Tivoli Storage Manager - Software Developmen >> in response to Our admins want to make sure that the definitions & rights of all print queues on our NW servers are backed up, but we obviously don't want to backup the actual print jobs. Can anyone provide a good set of include/exclude statements to accomplish this? Thanks. Steve Schaub Haworth, Inc email: [EMAIL PROTECTED]
Re: TSM Support for Windows Me
Andy, Is it true that we only started supporting Windows ME in 4.1.2.x; or was it 4.1.2 ??? Thanks, Jim J.P. (Jim) Smith Tivoli Storage Manager - Software Development e-mail: [EMAIL PROTECTED] tel: (408) 256-7618 Andy Raibeck <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 04/23/2001 06:43:09 Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: Re: TSM Support for Windows Me Apparently the web page is not up to date. As of TSM 4.1.2.x, we do support Windows Me (it's mentioned in the READ1STC.TXT file that accompanies the client. So if you install 4.1.2.12 or 4.1.2.14, you can back up Windows Me. Regards, Andy Andy Raibeck IBM Tivoli Systems Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] "The only dumb question is the one that goes unasked." Dave Canan <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 04/22/2001 08:43:52 PM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: TSM Support for Windows Me Can someone from Tivoli Support comment on the support for TSM and Windows Me? I realize that it is not on the supported page for Windows platforms, but how different is Windows Me from Windows 9x? Has anyone actually tried the TSM Windows client with this platform? I have a customer who has several machines with it and wants to know whether or not it will work. Any comments are welcome. Thanks. Money is not the root of all evil - full backups are.
Re: NDS ba/rest guide?
Jie, This guide is shipped with the TSM NetWare client. J.P. (Jim) Smith Tivoli Storage Manager - Software Development >> >>Hi, >> There used to be a netware NDS backup/restore guide from adsm ftp >>site. But I could not find it anymore. Does anybody know if there is a new >>version for TSM and where I can find it? Thanks.>> >> >>Jie
Re: Excluding parts of a NDS tree B/U
Merle, Sorry I took so long in reply: have you tried coding this statement in dsm.opt: exclude "dir:*License ID*" This worked for me: 02/06/2001 13:01:35 ANS1115W File '.[Root].O=tivoli.NLS:Publisher=Novell+NLS:Product=NetWare 5 Conn SCL+NLS:Version=510.NLS:License ID=SN:300589192' excluded by Include/Exclude list 02/06/2001 13:01:35 ANS1115W File '.[Root].O=tivoli.NLS:Publisher=Novell+NLS:Product=NetWare 5 Server+NLS:Version=510.NLS:License ID=SN:300589192' excluded by Include/Exclude list - Jim In response to: If you can find out how to exclude the Netware 5.1 license objects (they always return an error) I'd appreciate knowing how. I've tried several different syntaxes, including cutting the line from dsmerror.log with no success.
Re: Domain option not effective in TSM cluster environment
I believe what you are seeing is the fact that the GUI is designed to display all of the local files systems, regardless of the DOMAIN statement specified. This is normal behaviour and can be demonstrated in non-clustered environments. For example, you could have two local drives, C: and E:, and have a domain specification DOMAIN C:. The GUI is still going to display both C: and E: as local drives; the incremental backups, however, will honor the DOMAIN statement. Thanks, Jim J.P. (Jim) Smith Tivoli Storage Manager - Software Development TSM Mail-ID <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 01/28/2001 14:49:21 Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: Re: Domain option not effective in TSM cluster environment Thanx for the help. After some more testing, it appears that the problem is in the GUI. When I did a show options, the proper domains were listed. The client command-line backups up the proper domains when tested. So, it appears that the GUI and the ESS have issues. Scheduled backups work fine as well... We will avoid using the GUI for manual backups. Thanx! --- James Thompson <[EMAIL PROTECTED]> wrote: > From the client command line provide the output of > 'show options' it should > show the domain > that the client is using. > Also note that the domain statement is additive > unlike the include/exclude > statements. > So the lines > domain all-local > domain h: i: > > Is equivalent to > domain all-local h: i: > > James Thompson > > > - Original Message - > From: "TSM Mail-ID" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Friday, January 26, 2001 5:42 PM > Subject: Domain option not effective in TSM cluster > environment > > > > We're running TSM Server 3.7.2 and Client of > 3.7.x. > > We've installed 2 small NT 4.0 MSCS cluster > servers > > with shared disks (just external RAIDs). > Installed > > b/a client and scheduler services with no problem > and > > fail-over works. > > > > We just installed a big NT 4.0 MSCS server, with > the > > shared disks being part of an ESS (IBM Shark > system). > > When I install the b/a client on the local nodes > to > > back up the local disks, everything is fine. When > I > > configure the b/a client for the virtual nodes, it > > installs fine. But, when I edit the dsm.opt file > to > > limit the backup to the nodes shared disks only, > it > > appears to ignore the DOMAIN line and includes ALL > the > > shared disks: > > > > NODENAME HYDROGEN > > CLUSTERNODE YES > > DOMAIN H: I: > > > > Instead of limiting the backup to H: and I:, it > > includes all shared disks that it knows about, > such as > > J: K: R:, etc. > > > > In the two small MSCS clusters, TSM is working > fine > > with the above. In the big one, it isn't. All > > software is the same version, including OS. The > only > > difference is the that we're using an ESS for the > big > > one, so the sub-system drivers may be causing a > > problem. > > > > Has anyone run into this problem? If so how do we > fix > > it? > > > > I have tried everything in the DOMAIN statement, > eg. > > DOMAIN \\CLUS2\H$; DOMAIN "H:", etc. Nothing > appears > > to work. > > > > I've gotten around it, but it's ugly. I put an > > exclude/exclude.dir of the rest of the shared > drives > > in each node's dsm.opt file. Very annoying since > I > > shouldn't have to do this... > > > > Any help is appreciated... > > > > Thanx in advance! > > > > > > > ___ > > Do You Yahoo!? > > Get your free @yahoo.ca address at > http://mail.yahoo.ca > > ___ Do You Yahoo!? Get your free @yahoo.ca address at http://mail.yahoo.ca
Windows 2000 Client RedPiece available
The RedPiece "Deploying the Tivoli Storage Manager Client for Windows 2000" (SG24-6141-00) is now available at http://www.redbooks.ibm.com - Jim J.P. (Jim) Smith Tivoli Storage Manager - Software Development
Re: Excluding parts of a NDS tree B/U
Brain, Yes. Have you looked in the NetWare Backup and Recovery Guide (shipped with the client; ntwback.htm). This documents the procedure. - Jim Smith TSM Client developement >response to: Good morning everyone, Here is our configuration. TSM 3.7.3 on OS/390 2.9, Netware 5.1 server using TSM 3.7.2 client. My questions is this, can I use the DSM.OPT file to exclude certain parts of my NDS tree backup? We would like to exclude one object from the NDS tree backup and I am unsure if I can do this using the include/exclude list. Thanks for any help you can provide. Thanks, Brian Brian L. Nick Systems Technician - Storage Solutions Phoenix Home Life Mutual Ins. 100 Bright Meadow Blvd Enfield CT. 06082-1900 E-MAIL: [EMAIL PROTECTED] PHONE: (860)403-2281
Re: AW: TSM Client for NT 3.7.2.01
Are you you using NT or Windows 2000? First, I would add an include for the staging directory, ADSM.SYS, so that the registry and other system objects are processed correctly (this is important on Windows 2000): * this should be the last include/exclude statement, i.e., at the bottom of the list include *:\adsm.sys\...\* If you are running Windows 2000, I suggest looking into the registry for clues on which files to exclude. There is a key called HKLM\SYSTEM\CurrentControlSet\Control\BackupRestore\FilesNotToBackup which has a list of files that backup programs cannot process. Look for TSM client to be a bit more clever in the future in this area, i.e., automatically excluding FilesNotToBackup, automatically including staging directories, etc. Thanks, Jim Smith TSM Client Development --- Hello Do you find the the files that i excluded in dsm.opt correct for a normal File / Print Server?? exclude.file *:\pagefile.sys exclude.file *:\WINNT\system32\CPL.CFG exclude.file *:\...\SYSTEM32\CONFIG\default exclude.file *:\...\SYSTEM32\CONFIG\default.log exclude.file *:\...\SYSTEM32\CONFIG\sam exclude.file *:\...\SYSTEM32\CONFIG\sam.log exclude.file *:\...\SYSTEM32\CONFIG\security exclude.file *:\...\SYSTEM32\CONFIG\security.log exclude.file *:\...\SYSTEM32\CONFIG\software exclude.file *:\...\SYSTEM32\CONFIG\software.log exclude.file *:\...\SYSTEM32\CONFIG\system exclude.file *:\...\SYSTEM32\CONFIG\system.alt Thanks for the help Mauro Filippin -Ursprüngliche Nachricht- Von: Rushforth, Tim [mailto:[EMAIL PROTECTED]] Gesendet am: Donnerstag, 4. Januar 2001 18:15 An: [EMAIL PROTECTED] Betreff: Re: TSM Client for NT 3.7.2.01 Are these files being exluded from backup? Attempt to backup another user's ntuser.dat file from the GUI. Check the logs to see if the files are in use when your scheduled backups ran. Other than that, I am out of ideas! -Original Message- From: Filippin Mauro [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 04, 2001 11:05 AM To: [EMAIL PROTECTED] Subject: AW: TSM Client for NT 3.7.2.01 Yes, this is the same thing that i think but if i open the TSM Client i can find no NTUSER.dat File under the Profiles\username folders and also no under the ADSM.sys folder it sounds strange but is the true.. You will only see the user registry files under ADSM.sys if that user was logged on when the backup was run. If there are no directories there, you have nothing to worry about. Also if these files are not current you don't have to worry about them - they were from a prvious backup when the user was logged on. The "default" file is part of the system registry and should be copied to \winnt\system32\config along with the files in the adsm.sys\registry\...\MACHINE\ directory. This step has to be performed from another system (recovery system) since these files are used by NT. Tim Rushforth City of Winnipeg [EMAIL PROTECTED]
Re: Backing up Netware Partition
Mearl, The tsadosp.nlm is used to backup and restore the DOS partition on a NetWare server (I believe it was introduced by NetWare 5). The TSM client does not support the backup/restore of the DOS partition. Thanks, Jim Smith TSM Client Development I've noticed a tsadosp.nlm on our Netware server. I assume it is used for backing up the DOS partition. Is there anyway to use it with TSM (client 3.1 and 3.7)? - Mearl Danner Data Communications/Network Specialist Email: [EMAIL PROTECTED] Samford University
Re: Registry excluded by 4.1.2 client
Dave, This is correct. In TSM 4.1.2 client, we are using the hivelist from HKLM\SYSTEM\CurrentControlSet\Control\hivelist to get the list of registry keys that are needed to process during backup; the names in the staging directories are constructed from the data names + values located in this key. Hopefully, these new names can aid the user who is using the resource kit to selectively activate keys during restore. The upcoming redbook on Windows 2000 backup/recovery does walk through the include/exclude list and makes a new set of recommendations based on these changes. You are doing the absolutely safest thing, putting an include for the staging directory (c:\adsm.sys) at the end of the statements. (Note that these will also be included in the backup of the C: drive as well as the system objects; there is currently no way to avoid this). The redbook also adds several system files which are safe to exclude from normal incremental processing. We are continually trying to improve our include/exclude processing so that the users will not have to worry about the system files and the adsm staging directories. In the future, we plan on taking these additional steps with the client: 1. honor the FilesNotToBackup key. This key has a list, by MS component, of files that each component has determined to be volatile, e.g. pagefile.sys. You can see this list in HKLM\SYSTEM\CurrentControlSet\Control\BackupRestore\FilesNotToBackup. This would allow TSM to automatically reduce redundant backups, e.g., backing up c:\winnt\ntds as part of the C: backup and the Active Directory backup. 2. automatically exclude the staging directory from the C: backup (but including it in the system object backup). Also, the system objects would ignore any incl/excl statements (theoretically, the system objects must be processed as entire entities). This would alleviate users from accidently excluding important system files. We are open for any other suggestions to help automate in the include/exclude of system files. Thanks, Jim Smith TSM client development in response to: The 4.1.2 Windows client includes an exclude system32\config statement that prevents the registry backups from being sent to the server. TSM 4.1.2 now stores the registry files in a system32\config subdirectory of adsm.sys; all of the hkey_local_machine files are excluded from the backup. Current clients that are upgraded would continue to use their existing settings and thereby lose their registry backups in the process. I've added a include *:\adsm.sys\...\* to the bottom of my dsm.opt file. Dave
Re: Redbook for W2K - where are you ?
Tim, That requirement hasn't come up to my knowledge. I would suggest opening a requirement via marketing. Also, assuming that inactive/management class support is delivered for system objects, would that be sufficient for you archival needs? If not, can you please elaborate on how you would use such a function. Thanks, Jim Smith Windows 2000 Client Development In reply to: What about the ability to archive the system objects? Thanks, Tim Rushforth City of Winnipeg [EMAIL PROTECTED]
Re: Redbook for W2K - where are you ?
The residency you mention is in its final stages; you should be seeing the fruits early next year. In TSM 4.1.2, the client team focused on more automated backup and restore of the system objects, i.e., the new domain for backup, the ability to restore all of the system objects at once, etc. Our next focus will be to round out the support for system objects and try to provide inactive support, management class support, backupset support. I can't give you any firm commitments, but this is what appears to be what is needed next for the W2K system objects. While there is neither support for inactive or policy for system objects at this time, the redbook will cover a procedure to manually provide this support by scripting the renaming the SYSTEM OBJECT file space. Thanks, Jim Smith Windows 2000 Client Development team In reply to: Hello , does somebody know if there is some result from residency ST-0456 Deploying Tivoli Storage Manager for Windows 2000 ? I really appreciate some formal description of W2K server restore especialy in area of system objects and active directory. I expected possibility of restore inactive version of system objects in client 4.1.2 - unfortunately there is lack of ithis functionality . Is it planned ? Will be possible to use non-default management class for system objects ? Regards and happy christmas. Petr Prerost e-mail [EMAIL PROTECTED]
Re: Scheduled backup of Win2K System Objects
The rumor is true. Taken from the TSM 4.1.2 client readme file: - The SYSTEMOBJECTS domain has been added for Windows 2000 System Objects. This domain is included in domain ALL-LOCAL and will allow users to backup the Windows 2000 System Objects as part of a scheduled backup. All System Objects that are present on the particular system are backed up. Additionally, the commands BACKUP/QUERY/RESTORE SYSTEMOBJECTS have been added to the command-line client to backup/query/and restore all of the Windows 2000 System Objects. System Objects include Active Directory, Certificate Server Database, Cluster Database, COM+ database, Event Log, File System Replication, Registry, Removable Storage Manager Database, System and Boot Files, and the System Volume. Jim Smith TSM Client Development > >"This is probably a known issue but ADSM client does not backup Win2000 >System Objects using the Central Scheduler. Does anyone have a >recommendation for a fix or a workaround? We are using Client ver. >3.7.2.17 and Server 3.7.4.0. > >Thanks in advance for any help." Hello Paul The v412 windows client is rummered to have an improvement for this. This should be available from the ftp server soon as all the other tsm 4.1.2 client and server updates appear to be available. /len
