Re: Client not using all available drives
maybe to put colocation to off ? goran. - Original Message - From: Thomas Rupp, Vorarlberger Illwerke AG [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, February 25, 2004 7:30 PM Subject: Client not using all available drives Hi ADSM gurus, I have to backup a big fileserver with where our Outlook mail-archives are stored as well. I have created a management class to backup this *.pst files directly to tape whereas all other files go to disk. Now I see that the client starts 3 sessions but only uses 1 drive - 2 are available. MAXNUMMP is set to 2. Server is 4.2.2.8 (I know ;-) ) What do I have to change to make it use 2 drives? Node Name: BRVFS2V2 Platform: WinNT Client OS Level: 5.00 Client Version: Version 5, Release 1, Level 5.0 Policy Domain Name: STANDARD Last Access Date/Time: 02/25/04 19:13:34 Days Since Last Access: 1 Password Set Date/Time: 01/03/03 14:40:47 Days Since Password Set: 418 Invalid Sign-on Count: 0 Locked?: No Contact: Fileserver virt. Knoten 2 Compression: Client Archive Delete Allowed?: Yes Backup Delete Allowed?: Yes Registration Date/Time: 01/03/03 14:40:47 Registering Administrator: ADMINLB Last Communication Method Used: Tcp/Ip Bytes Received Last Session: 2,949 Bytes Sent Last Session: 776.49 M Duration of Last Session: 944.56 Pct. Idle Wait Last Session: 57.48 Pct. Comm. Wait Last Session: 13.16 Pct. Media Wait Last Session: 19.57 Optionset: WINDOWS URL: Node Type: Client Password Expiration Period: Keep Mount Point?: No Maximum Mount Points Allowed: 2 Auto Filespace Rename : No Kind regards Thomas Rupp
AW: Full W2K Server restore
just as Kenny, not. We have got, however, minor problems with network driver and vga driver, network card could be helped by simply reconfiguring some parameters like full duplex, vga driver worked only in vga/svga modes but driver update helped. While dubious, not a real problem. No other problems so far, especially not with AD. regards Juraj -Ursprüngliche Nachricht- Von: Bill Boyer [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 25. Februar 2004 19:29 An: [EMAIL PROTECTED] Betreff: Re: Full W2K Server restore Did you have to boot into AD Recovery mode (F8) before doing the system object restore?? -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Salak Juraj Sent: Wednesday, February 25, 2004 1:21 PM To: [EMAIL PROTECTED] Subject: AW: Full W2K Server restore I can fully second to Kenny, very same experiences with restore and later swap to VMWARE here. Juraj Salak -Urspr|ngliche Nachricht- Von: Barnes, Kenny [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 25. Februar 2004 17:20 An: [EMAIL PROTECTED] Betreff: Re: Full W2K Server restore We have been able to restore AD to the same hardware by restoring the c:\* and then restoring all system objects with out rebooting. Once both have been restored, then reboot. Restoring to different hardware is another story. Client version 5.1.5. We are starting to use VMware and run a DC with no primary roles and backup the OS as a file and restore the file from TSM. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Magalie Siaud Sent: Tuesday, December 23, 2003 7:09 PM To: [EMAIL PROTECTED] Subject: Full W2K Server restore Hi all. We are using TSM 5.1.6 to backup w2k nodes. These nodes are W2K server Domain controllers. We are testing full restores on other kind hardwre. We have been working on the Bare Metal restore Redbook. Our procedure was to: 1- Bring a new machine with different hardware, same IP, same nodename 5Ip could be different), with W2K server and TSM client 5.16 pre-installed, 2- Restore the whole machine on the new one, except systemobjects, 3- Reboot the new server, in AD reconstruction mode, 4- Restore the systemobjects, 5- Reboot. Unfortunately, we are not able to restore the systemobjects in the 4th step. TSm don't even allow us to do it. Object ID problem?? Anyone has been able to test a full restore for w2k servers using different hardware, even same hardware? The problem using different hardware versus same hardware should be HAL compatibility slice, shouldn't it? This is solved when using Ntbackup (merge some registry entries related to hardware specifications). Therefore we are trying to get rid of it too with TSM... Magalie Siaud. -- Note: The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer... Thank you. --
ClientOptionSet Question
Hi @ll, when i change something in a client option set on the server, do i need to restart the scheduler so the changes will take effect??? thx in advandce Bernd Wiedmann
Strange RETRIEVE behaviour
Hi All, I've noticed some strange behaviour with RETRIEVE, which I haven't been able to explain yet. I've made an ARCHIVE with: dsmc archive -archmc=xyz *.txt -v2archive -filesonly -subdir=no -descr=XYZ This archive was made from the directory /volume/a. When I do a dsmc retrieve * /temp/ -filesonly -descr=XYZ when still in /volume/a, all files are retrieved. When I do the same when switched to /volume/b (different filesystem) nothing is retrieved. Has anyone got a clue to why this isn't working? I want to be able to retieve files from any location, regarding what the orginal path was (hence the -v2archive with the archive operation). I've tried this with the TSM 5.2.2 client on both Linux and Windows, with the same effect. Also I tried with TSM Server 5.2.2.1 on Linux and Windows, but that also didn't make any difference. Richard.
Re: Returning a Reclaimed Offsite Copypool Volume to the Library Scratch Pool?
OTOH, can I do a Checkin with Status=Private, Update the volume to readwrite and simply have TSM use it before requesting a new tape from the Scratch Pool? Yes and when you update your volume to ReadW it will go to your scratch pool but it wont necessarily be used before other scratch tapes. //Henrik Mike Bantz [EMAIL PROTECTED]To: [EMAIL PROTECTED] .COMcc: (bcc: Henrik Wahlstedt) Sent by: Subject: Re: Returning a Reclaimed Offsite Copypool Volume to the Library Scratch Pool? ADSM: Dist Stor Manager [EMAIL PROTECTED] RIST.EDU 2004-02-26 00:22 Please respond to ADSM: Dist Stor Manager Try to update the access of those volumes to onsite retrieve: move drm TSM023 tostate=onsiteretr (if it's a DRM volume) Or just update the volume to readwrite instead of offsite. Then try checking them in as scratch. HTH, Mike Bantz -Original Message- From: Dwight McCann [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 25, 2004 12:39 PM To: [EMAIL PROTECTED] Subject: Returning a Reclaimed Offsite Copypool Volume to the Library Scratch Pool? I am running TSM 5.1.8.3 on W2K. I have several tape volumes that I have reclaimed from Offsite Copypool storage. When I attempt to do a CHECKIN to return them to the Scratchpool TSM does not allow it: tsm: DATAPLUS_SERVER1q vol tsm023 Volume Name Storage Device Estimated Pct Volume Pool Name Class Name Capacity Util Status (MB) --- -- - - TSM023 COPYPOOLLTO2 0.0 0.0 Empty tsm: DATAPLUS_SERVER1q vol tsm023 f=d Volume Name: TSM023 Storage Pool Name: COPYPOOL Device Class Name: LTO2 Estimated Capacity (MB): 0.0 Pct Util: 0.0 Volume Status: Empty Access: Offsite Pct. Reclaimable Space: 0.0 Scratch Volume?: Yes In Error State?: No Number of Writable Sides: 1 Number of Times Mounted: 14 Write Pass Number: 1 Approx. Date Last Written: 10/09/2003 06:47:24 Approx. Date Last Read: 09/27/2003 06:35:55 Date Became Pending: Number of Write Errors: 0 Number of Read Errors: 0 Volume Location: Last Update by (administrator): DWIGHT Last Update Date/Time: 12/16/2003 12:11:14 tsm: DATAPLUS_SERVER1checkin libv lb1.1.0.5 tsm023 status=scratch ANR8443E CHECKIN LIBVOLUME: Volume TSM023 in library LB1.1.0.5 cannot be assigned a status of SCRATCH. ANS8001I Return code 12. The explanation of ANR84423E says that it is not allowed because there might be data on the tape, but TSM clearly knows that there is no data on the tape. In the Admin Guide it says that volumes defined in a Storage Pool cannot be checked as Scratch. Is the correct way to get this volume back into the Scratch Pool to delete it from the storage pool and then do the Checkin? This tape was originally moved to the COPYPOOL from SCRATCH. Neither the message nor the message explanation gives the explicit reason that this volume cannot be made scratch. OTOH, can I do a Checkin with Status=Private, Update the volume to readwrite and simply have TSM use it before requesting a new tape from the Scratch Pool? -- Dwight McCann Computer and Network Technologist, UCSB Info Systems Computing [EMAIL PROTECTED], [EMAIL PROTECTED] http://borg.isc.ucsb.edu/dmm/ - office: 805-893-3113 --- The information contained in this message may be CONFIDENTIAL and is intended for the addressee only. Any unauthorised use, dissemination of the information or copying of this message is prohibited. If you are not the addressee, please notify the sender immediately by return e-mail and delete this message. Thank you.
Incremental backups
Hi, Currently i am the new administrator of TSM in my organization. I have a request for backing up a windows 2000 server (backup domain C and D) and i must be able to restore data up to two years ago. Please find below the solution i am going to implement for the above request and let me know: 1.Every day i will run incremental (progressive) backup with the following Backup Copy Group: (keep incremental backup for one year) VEREXISTS=NOLIMIT VERDELETED=NOLIMIT RETEXTRA=365 RETONLY=31 2. At the end of the year (30/12/2004) i will perform an archive and keep it for 730 days. 3. What about backing up the system state of a windows 2000 server? Is it ok to perform dsmc backup systemstate or is better to use NTBackup utility and save the backup file on the disk and then backup that file with TSM. I would appreciate to have your comments on the above issues. Thanks for your time Nicolas Savva Privileged/Confidential information may be contained in this message and may be subject to legal privilege. Access to this e-mail by anyone other than the intended recipient is unauthorised. If you are not the intended recipient (or responsible for delivery of the message to such person), you may not use, copy, distribute or deliver to anyone this message (or any part of its contents) or take any action in reliance on it. In such case, you should destroy this message, and notify us immediately. If you have received this email in error, please notify us immediately by e-mail or telephone and delete the e-mail from any computer. If you or your employer does not consent to internet e-mail messages of this kind, please notify us immediately. All reasonable precautions have been taken to ensure no viruses are present in this e-mail. As we cannot accept responsibility for any loss or damage arising from the use of this e-mail or attachments we recommend that you subject these to your virus checking procedures prior to use. The views, opinions, conclusions and other information expressed in this electronic mail are not given or endorsed by Laiki Group unless otherwise indicated by an authorised representative independent of this message.
AW: ClientOptionSet Question
yes Juraj -Ursprüngliche Nachricht- Von: Bernd Wiedmann [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 26. Februar 2004 09:18 An: [EMAIL PROTECTED] Betreff: ClientOptionSet Question Hi @ll, when i change something in a client option set on the server, do i need to restart the scheduler so the changes will take effect??? thx in advandce Bernd Wiedmann
Re: Strange RETRIEVE behaviour
How do you mean? Richard. goran [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 26-02-2004 09:54 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Re: Strange RETRIEVE behaviour yes there is ... but to /volume/a !!! :-) - Original Message - From: Richard van Denzel [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, February 26, 2004 9:20 AM Subject: Strange RETRIEVE behaviour Hi All, I've noticed some strange behaviour with RETRIEVE, which I haven't been able to explain yet. I've made an ARCHIVE with: dsmc archive -archmc=xyz *.txt -v2archive -filesonly -subdir=no -descr=XYZ This archive was made from the directory /volume/a. When I do a dsmc retrieve * /temp/ -filesonly -descr=XYZ when still in /volume/a, all files are retrieved. When I do the same when switched to /volume/b (different filesystem) nothing is retrieved. Has anyone got a clue to why this isn't working? I want to be able to retieve files from any location, regarding what the orginal path was (hence the -v2archive with the archive operation). I've tried this with the TSM 5.2.2 client on both Linux and Windows, with the same effect. Also I tried with TSM Server 5.2.2.1 on Linux and Windows, but that also didn't make any difference. Richard.
AW: Incremental backups
Hello, While you are basically on the right way, the exact answer cannot be given now, as it depends upon: - do you have to be able to restore any version which existed during last 2 years (a file changes each day and the user wants to restore the version from february 26.th 2002) If yes, is i true for files which has been deleted some day during last 2 years or not? - or you only have to be able to restore a (last version of) a file even 2 years after it has been deleted - or do you have to be able to restore exact state of certain, listed qualifying dates, like 1.st of each month? - are you sure you need to restore 2 yeras old system state? Usually it makes little sense. Depending on how many files change daily the first requirement can be expensive in terms of TSM database and ST pool space. In addition to setting verexist etc. do no forget to limit backups to once per day maximum, otherwise subsequent backups during one day could generate more file version during one day thus causing the oldest you still need to expire. This can be set in management classes copy frequency=1. I would personaly go for incremental backup only, no archives, setting verexist etc. to 730 (depending on your exact requirements). Except your requirements is this ony with qualifying dates (above). One extra point which can be easily overseen: when setting parameters for deleted files do not forget that files renamed or moved to another location or files in renamed directories are by TSM handled just like pair of (deleted file + a new file). For Backup of System state, both ways will work, on AD controllers (very important servers) I used to use both in paralell (a bit of paranoia, i know) but swapped now to backup systemstate + VMWARE backup of whole operating system (just another kind of paranoia). While not an exact answer, hope it helped a bit regards juraj -Ursprüngliche Nachricht- Von: Nicolas Savva [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 26. Februar 2004 09:43 An: [EMAIL PROTECTED] Betreff: Incremental backups Hi, Currently i am the new administrator of TSM in my organization. I have a request for backing up a windows 2000 server (backup domain C and D) and i must be able to restore data up to two years ago. Please find below the solution i am going to implement for the above request and let me know: 1.Every day i will run incremental (progressive) backup with the following Backup Copy Group: (keep incremental backup for one year) VEREXISTS=NOLIMIT VERDELETED=NOLIMIT RETEXTRA=365 RETONLY=31 2. At the end of the year (30/12/2004) i will perform an archive and keep it for 730 days. 3. What about backing up the system state of a windows 2000 server? Is it ok to perform dsmc backup systemstate or is better to use NTBackup utility and save the backup file on the disk and then backup that file with TSM. I would appreciate to have your comments on the above issues. Thanks for your time Nicolas Savva Privileged/Confidential information may be contained in this message and may be subject to legal privilege. Access to this e-mail by anyone other than the intended recipient is unauthorised. If you are not the intended recipient (or responsible for delivery of the message to such person), you may not use, copy, distribute or deliver to anyone this message (or any part of its contents) or take any action in reliance on it. In such case, you should destroy this message, and notify us immediately. If you have received this email in error, please notify us immediately by e-mail or telephone and delete the e-mail from any computer. If you or your employer does not consent to internet e-mail messages of this kind, please notify us immediately. All reasonable precautions have been taken to ensure no viruses are present in this e-mail. As we cannot accept responsibility for any loss or damage arising from the use of this e-mail or attachments we recommend that you subject these to your virus checking procedures prior to use. The views, opinions, conclusions and other information expressed in this electronic mail are not given or endorsed by Laiki Group unless otherwise indicated by an authorised representative independent of this message.
License expiration not made after 30 days inactivity ...
Hi *SM'ers Could anybody explain following behaviour, on a TSM 5.1.6.2 server, AIX 4.3 hosted. Running following query : select * from license_details shows me several nodes having last access_date 30 days, like this one : MGSYSLAN PAC2K060 2003-10-27 FALSE From what I read in this list, a license should normally be freed after 30 days of node inactivity, what is not happening in my case. Any thoughts or comments on this ? Arnaud Brion *** Panalpina Management Ltd., Basle, Switzerland, CIT Department Viadukstrasse 42, P.O. Box 4002 Basel/CH Phone: +41 (61) 226 11 11, FAX: +41 (61) 226 17 01 Direct: +41 (61) 226 19 78 e-mail: [EMAIL PROTECTED] ***
Re: Windows open file problem
For the cache location, is drive D:\ is on the same disk with TSM Client? You should change the cache location to different partition on different disk... TSM Open File Support restrictions: - 1. Microsoft Windows Server 2003. -- Currently OFS is only supported on Windows 2000 and Windows XP. The current version of OFS support in TSM v5.2.0 does not support Windows Server 2003. The TSM OFS feature uses its own TSM snapshot technology (TSM LVSA). Windows Server 2003 has native snapshot support via the Shadow Copy services, which may prevent the operation of, or negatively interact with the TSM LVSA. IBM is currently working on removing this restriction so that OFS will be supported on Windows Server 2003. 2. Machines with a single drive. -- OFS uses the TSM LVSA to create a snapshot of a volume that is being backed up. The TSM LVSA requires the use of a local drive, other than the one that is being backed up, to contain a cache file. This means the location of this cache can not be on the same drive that is being backed up. Therefore a machine with only a single drive can not take advantage of this OFS feature. IBM is currently working on removing this restriction. 3. Microsoft Terminal Services. -- There is known limitation in Microsoft Terminal Services server on Windows 2000 that prevents the OFS feature from working over a Microsoft Terminal Services session. The following errors are recorded to the dsmerror.log during the snapshot creation process: ANS1327E The snapshot operation for 'D:' failed. Error code: 673. ANS1375E The snapshot operation failed. ANS1376E Unable to perform operation using a point-in-time copy of the filesystem. The backup/archive operation will continue without snapshot support. To get around this limitation the TSM Remote Web GUI can be used to perform the backup operation. This limitation does not effect TSM Scheduled backups which run locally nor will it effect any Restore operations. The Microsoft Terminal Services limitation can be seen outside of the TSM Client by logging on to a Terminal Service session and creating a new volume. Using the Windows Disk Management tool under Administrative Tools create and format a new volume. The volume is created successfully, but the new volume will not be seen in Windows Explorer or the Windows Command Prompt unless the user logs off of the current Terminal Service session and re-establishes a new Terminal Service session. This limitation is not seen with the Remote Desktop feature that is included with Windows XP. Other known OFS issues - 1. Machines with multiple drives. --- If the OFS feature is selected at Install time (default is not selected) then the install and setup will place the cache file location (SNAPSHOTCACHELOCATION option) on the System drive. This will enable OFS backup for all drives other than the System drive. The backup of the System drive will detect the cache file on this drive and will place the error message below in the dsmerror.log and will then fail-over to non-OFS backup for the System drive. ANS1327E The snapshot operation for 'C:' failed. Error code: 659. ANS1228E Sending of object '\\machinename\c$' failed ANS1381E The snapshot cache location cannot be located on the same volume that is being backed up. TSM indicates a failure for the System drive backup since the snapshot could not occur. This may be a misleading message because the fail-over to non-OFS will be the same backup support that would be done if the new OFS feature was not installed. To prevent these error messages use the following option in the TSM client options file (dsm.opt) to disable OFS on the System drive (example shown is where C: is the System drive): include.fs C: fileleveltype=dynamic 2. File system IO activity. The TSM snapshot feature will wait for a file system to be idle for a given period to help ensure a consistent point-in-time view of the filesystem. This is controlled through the SNAPSHOTFSIDLEWAIT and SNAPSHOTFSIDLERETRIES options. Given that NTFS flushes I/O in bursts, there should be idle time adequate to take a snapshot between NTFS filesystem cache flushes. TSM also requests a filesystem flush before a snapshot is taken to further increase the chance of a consistent filesystem snapshot. TSM uses a SNAPSHOTFSIDLEWAIT default value of 5 seconds and a SNAPSHOTFSIDLERETRIES default value of 10. This requires that a period of 5 seconds must pass without write activity (read activity is ignored) on a volume before a snapshot can occur. If write activity is detected, TSM will retry again up to 10 times. The values are conservatively set to maximize the chances of a consistent point-in-time state of the
Re: ClientOptionSet Question
One more question about ClientOptionSet on the server. How do you 'delete or dissociate' this option from node definition on server without deleting it from server? I used it for a while and now I don't need anymore. 'dsm.opt' will have it instead. Thanks. Gus [EMAIL PROTECTED] 2/26/2004 9:51:03 AM We don't. -Original Message- From: Salak Juraj [mailto:[EMAIL PROTECTED] Sent: February 26, 2004 2:52 AM To: [EMAIL PROTECTED] Subject: AW: ClientOptionSet Question yes Juraj -Ursprüngliche Nachricht- Von: Bernd Wiedmann [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 26. Februar 2004 09:18 An: [EMAIL PROTECTED] Betreff: ClientOptionSet Question Hi @ll, when i change something in a client option set on the server, do i need to restart the scheduler so the changes will take effect??? thx in advandce Bernd Wiedmann
Re: Things I could just as soon never ever ever see again.
... Database backup encountered an unusually vigorous expiration session, ... You're not getting any younger, so relieve stress by adding a Duration to your Expire Inventory, and perhaps a DBBackuptrigger. Richard Sims still only 39...?
Restartable Restores - How To Restart?
Hello all, Hows does one restart a restartable restore? I have been restoring massive amounts of data recently and I noticed there are three of these restores pending. Server Version: 5.1.5 OS: AIX 5.1 Thanks, Rob
TDP for Domino for Linux on s390
Hi All, Does anyone know if such an animal exists? This would be the Domino TDP agent to run on Linux in an LPAR on a z/Series Mainframe running SuSE V8, SP3. All of the code that I can find on the FTP sites is for Linux on X86. Thanks, Steve Roder University at Buffalo ([EMAIL PROTECTED] | (716)645-3564)
Migrating to new tape drives.
Good day everyone, I am preparing to upgrade our L700 jukebox to SDLT320 from DLT7000. All 360 tapes will have to be removed from the L700 jukebox. Then the L700 jukebox will be upgraded and new media added. I have connected an ATL7100 jukebox to the TSM server and have made it available to TSM. This is how I plan on doing the migration. Plan was to checkout all media from the L700 and checkin to the ATL7100 the perform a move data to the diskpools and let the data migrate to the new tapes. I have started testing and come across the following: 1) Incompatible barcodes, I'll be ordering barcodes that can be read by the ATL7100. 2) I performed a checkout libvol from the L700 and a checkin libvol on the ATL7100, works but the TSM server asks for the volume to be mounted in the L700 whenever I try to perform a move data command. I am figuring it is storagepool association. How can I move all the tapes out of the L700 and associate them to the ATL7100 ? PS. Even under the best conditions DLT7000 written tapes are only about 30% - 40% compatible with SDLT320 drives. This was told to me by a Storagetek engineer. Duane Ochs Enterprise Computing Quad/Graphics Sussex, Wisconsin 414-566-2375 phone 414-917-0736 beeper [EMAIL PROTECTED] www.QG.com
ANR9999D imexp.c(4574)
Hi, During expiration we get the following message: ANRD imexp.c(4574): ThreadId71 Backup Entry for object 0.43293636 could not be found in Expiration Processing. Show object doesn't give anything back and delete object is failing also. We know what file space and node it is concerning. We tried to delete the file space (systemobject) but that doesn't work either. Anyone knows a good (clean and fast) way to get rid of this object (without auditing the database)? Regard, Karel
Re: ClientOptionSet Question
We don't. -Original Message- From: Salak Juraj [mailto:[EMAIL PROTECTED] Sent: February 26, 2004 2:52 AM To: [EMAIL PROTECTED] Subject: AW: ClientOptionSet Question yes Juraj -Ursprüngliche Nachricht- Von: Bernd Wiedmann [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 26. Februar 2004 09:18 An: [EMAIL PROTECTED] Betreff: ClientOptionSet Question Hi @ll, when i change something in a client option set on the server, do i need to restart the scheduler so the changes will take effect??? thx in advandce Bernd Wiedmann
Backing up files that may have virus
I have a TSM Client V5.1.6 (NW6) whom I backup incrementally on a nightly basis with my MVS OS/390 2.10, TSM Server 5.1.7. I received a call from the administrator of this (client)server that he may have a virus on his server and would I retain his backup from 3 nights ago which may be the last good backup pre-virus. Here are my questions I hope someone who has gone through this before may help me with. 1. The MC for this client is our default of 3 incremental backups, 1 active and 2 inactive. I'm pretty sure I will have to rebind all of this nodes files for a specific length of time in order to keep the last good backup for awhile. Does anyone know if there is an alternative to this? He has not specified a time-length but I'm assuming it may take at least 3 months to find out if he does have a virus, what files it may have affected. (This is my guess , I don't even know for sure what type of data he keeps on his server). 2. What are the possibilities of him restoring the virus accidentally down the line. For example, he may have a file that only gets changed once a year. What if 6 months from now he restores this file because it is the last active version and it is infected with the virus. Would this put the virus back on his system? Is there anyway I can avoid this from happening? Does this make sense or am I being a paranoia? I'll take any helpful opinions or advice I can get. Thank you in advance! Shannon Bach Madison Gas Electric Co. Operations Analyst - Data Center Services e-mail [EMAIL PROTECTED]
Re: ANR9999D imexp.c(4574)
Hmm, I had a similar thing recently, where I could not delete a systemobject filespace because of problems with code release 4.2.4 handling a partial object. However there were changes in the way partial objects are dealt with in 5.1, and I now at 5.1.8 I have been able to successfully delete the systemobject filespace. Maybe this is what you are seeing. Karel Bos [EMAIL PROTECTED] omTo Sent by: ADSM: [EMAIL PROTECTED] Dist Stor cc Manager [EMAIL PROTECTED] Subject .edu ANRD imexp.c(4574) 26/02/2004 14:44 Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] .edu Hi, During expiration we get the following message: ANRD imexp.c(4574): ThreadId71 Backup Entry for object 0.43293636 could not be found in Expiration Processing. Show object doesn't give anything back and delete object is failing also. We know what file space and node it is concerning. We tried to delete the file space (systemobject) but that doesn't work either. Anyone knows a good (clean and fast) way to get rid of this object (without auditing the database)? Regard, Karel ** The information in this E-Mail is confidential and may be legally privileged. It may not represent the views of Scottish and Southern Energy Group. It is intended solely for the addressees. Access to this E-Mail by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Any unauthorised recipient should advise the sender immediately of the error in transmission. Scottish Hydro-Electric, Southern Electric, SWALEC and S+S are trading names of the Scottish and Southern Energy Group. **
Re: TDP for Domino for Linux on s390
Hi Steve, It exists and it is available from the Passport Advantage site. IBM Tivoli Storage Manager v5.2.2 for Mail (Data Protection for Lotus Domino v5.2.2) UNIX Users. Eduardo ADSM: Dist Stor Manager [EMAIL PROTECTED] wrote on 02/26/2004 06:20:05 AM: Hi All, Does anyone know if such an animal exists? This would be the Domino TDP agent to run on Linux in an LPAR on a z/Series Mainframe running SuSE V8, SP3. All of the code that I can find on the FTP sites is for Linux on X86. Thanks, Steve Roder University at Buffalo ([EMAIL PROTECTED] | (716)645-3564)
Things I could just as soon never ever ever see again.
Ever ever. As long as I live. This turned out OK, but still bash-2.04# cd /usr/tivoli/tsm/server/bin/ bash-2.04# dsmserv extend log /export/dat03/emergency-log 2000 ANR7800I DSMSERV generated at 14:00:40 on Mar 14 2003. [...] ANR0900I Processing options file dsmserv.opt. ANR7811I Direct I/O will be used for all eligible disk files. ANR4726I The Async I/O support module has been loaded. ANR7805E Volume /dev/rtsmdblv12a is in use by another server. ANR7805E Volume /dev/rtsmdblv12b is in use by another server. ANR0259E Unable to read complete restart/checkpoint information from any database or recovery log volume. bash-2.04# Shudder. I had an out-of-recovery-log condition, slew my server, formatted a volume, set about extending the log, and evidently restarted a smidge before all the tentacles were removed. I stared at this for about 10 seconds, heart palpitating, took a deep breath, and ran it again. And it worked. Database backup encountered an unusually vigorous expiration session, kablooey. My log use usually climbs into the 30-50% at that phase of the day, but today it was deleting almost everything it came across, almost a million objects the last time I'd looked at it. What fun! - Allen S. Rout - Ever Ever.
AW: Restartable Restores - How To Restart?
A) on server: QUERY RESTORE B) on dsmc client: help 1b.lxix) Restart Restore The restart restore command displays a list of your restartable restore sessions in the server database. You can select zero or more restartable restore sessions that you want to restart. The restarted restore uses the same options you used in the failed restore. The restarted restore continues from the point at which the restore previously failed. To cancel restartable restore sessions, use the cancel restore command. Use the restart restore command when: * Restartable restore sessions lock the file space at the server so that files cannot be moved off the server's sequential volumes. * You cannot back up files affected by the restartable restore. Options from the failed session supersede new or changed options for the restarted session. Supported Clients This command is valid for all Windows clients. Syntax -RESTArt Restore--+--+--- '- options-' Parameters options See the client processing options topics for more information. Examples Task Restart a restore. Command: restart restore Press enter to continue, 'q' to return to help menu 'u' to scroll up, or 'd' to scroll down: Task Restart a restore. Command: restart restore ** End of help section; press enter to return to help menu. Press 'u' to scroll up. ** -Ursprüngliche Nachricht- Von: Rob Hefty [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 26. Februar 2004 14:47 An: [EMAIL PROTECTED] Betreff: Restartable Restores - How To Restart? Hello all, Hows does one restart a restartable restore? I have been restoring massive amounts of data recently and I noticed there are three of these restores pending. Server Version: 5.1.5 OS: AIX 5.1 Thanks, Rob
AW: ClientOptionSet Question
consequently, I must be wrong :-) -Ursprüngliche Nachricht- Von: Rushforth, Tim [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 26. Februar 2004 15:51 An: [EMAIL PROTECTED] Betreff: Re: ClientOptionSet Question We don't. -Original Message- From: Salak Juraj [mailto:[EMAIL PROTECTED] Sent: February 26, 2004 2:52 AM To: [EMAIL PROTECTED] Subject: AW: ClientOptionSet Question yes Juraj -Ursprüngliche Nachricht- Von: Bernd Wiedmann [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 26. Februar 2004 09:18 An: [EMAIL PROTECTED] Betreff: ClientOptionSet Question Hi @ll, when i change something in a client option set on the server, do i need to restart the scheduler so the changes will take effect??? thx in advandce Bernd Wiedmann
Re: Restartable Restores - How To Restart?
Use the restart restore command Alexei Kojenov TSM Client Development (408) 256-7009 [EMAIL PROTECTED] Rob Hefty [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 02/26/2004 05:47 AM Please respond to ADSM: Dist Stor Manager To [EMAIL PROTECTED] cc Subject Restartable Restores - How To Restart? Hello all, Hows does one restart a restartable restore? I have been restoring massive amounts of data recently and I noticed there are three of these restores pending. Server Version: 5.1.5 OS: AIX 5.1 Thanks, Rob
Re: Incremental backups
Nicolas wrote: 3. What about backing up the system state of a windows 2000 server? Is it ok to perform dsmc backup systemstate or is better to use NTBackup utility and save the backup file on the disk and then backup that file with TSM. I use ntbackup to backup up the systemstate because I found in earlier versions of TSM (4.x) I had problems restoring with just the dsmc backup systemstate. We have a preschedule task that does an ntbackup of the systemstate prior to our incremental backups. Here is the syntax I use: ntbackup backup systemstate /f C:\Srvutils\Systemstate.bkf /m copy Louis G Louis Robertson Senior Systems Analyst BearingPoint [EMAIL PROTECTED] Cell (717) 903-1324 Fax (717) 213-6101 ** The information in this email is confidential and may be legally privileged. Access to this email by anyone other than the intended addressee is unauthorized. If you are not the intended recipient of this message, any review, disclosure, copying, distribution, retention, or any action taken or omitted to be taken in reliance on it is prohibited and may be unlawful. If you are not the intended recipient, please reply to or forward a copy of this message to the sender and delete the message, any attachments, and any copies thereof from your system. **
FW: Reference Memory Error ##Help## on TSM client 4.2.3
Has anyone experienced this problem when backing up system objects on Win2k Server SP4?? This error only appears on some servers and I can't seem to pin point out the problem since other servers are backing up fine. FYI (managedservices Schedule Webclient) is set in my dsm.opt. Platform: WinNT Client OS Level: 5.00 Client Version: Version 4, Release 2, Level 3.0 Error Windows POPUP Icon: Dsmcsvc.exe - Application Error The instruction at 0x77fcb032 referenced memory at 0x00 The memory could not be written This message seems to appear right after the local domain backup successfully and then tries to backup the system object. If I exclude the system object the client would backup successfully. Hangs at this entry below in the dsmsched.log: 02/25/2004 19:07:42 Preparing System Object - System and Boot FilesANS1898I * Processed72,500 files * 02/25/2004 19:07:46 ANS1898I * Processed73,000 files * 02/25/2004 19:07:50 ANS1898I * Processed73,500 files * From here on the scheduler would just hang there. Any help would be deeply appreciated. Thank you --- The information contained in this e-mail message, and any attachment thereto, is confidential and may not be disclosed without our express permission. If you are not the intended recipient or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that you have received this message in error and that any review, dissemination, distribution or copying of this message, or any attachment thereto, in whole or in part, is strictly prohibited. If you have received this message in error, please immediately notify us by telephone, fax or e-mail and delete the message and all of its attachments. Thank you. Every effort is made to keep our network free from viruses. You should, however, review this e-mail message, as well as any attachment thereto, for viruses. We take no responsibility and have no liability for any computer virus which may be transferred via this e-mail message.
Re: AIX HSM and NFS
We are experimenting with Space Management (HSM) and our AIX guy has some problems/questions. Is there anything special about referencing an HSM filespace via NFS? I have a fully functional HSM FS on an NFS server, - I have the normal entries in /etc/exports, - I have done the normal 'exportfs -a' command, - I have issued the normal mount command from the client mount hostname:/fsname /mnt, - I get message mount: 1831-010 server hostname not responding: RPC: 1832-019 Program not registered. Am I missing a step? Your AIX guy can't figure this out, Ted? Geez... An HSM file system is used via NFS the same way as any other file system. I have to wonder if NFS is running on the system where HSM and NFS are supposed to be. Your guy should know to run 'rpcinfo -p hostname' to see if NFS is registered in Portmap, expecting to get back lines like: 132 udp 2049 nfs 133 udp 2049 nfs 132 tcp 2049 nfs 133 tcp 2049 nfs And then do 'rpcinfo -u hostname nfs' to reflect off the NULLPROC of that RPC service which is called nfs, to test that it is responding. If no answer, then nfsd either didn't get started, or died. It should be accompanied by a suite of other pseudo-state daemons, which your AIX guy should be familiar with. If you do 'df -k' on the HSM file system, you see two mounts, right?...the JFS and FSM. And all the HSM dsm* commands show happiness? Using HSM over NFS requires a lot of TLC, else you can end up with some very ugly situations where all your NFS client systems can hang as HSM spends up to an hour or so reconciling a full FSM file system seeking to make space. See my various postings in the Archives. Good luck! Richard Sims, http://people.bu.edu/rbs
Re: Things I could just as soon never ever ever see again.
= On Thu, 26 Feb 2004 11:45:02 -0500, Richard Sims [EMAIL PROTECTED] said: ... Database backup encountered an unusually vigorous expiration session, ... You're not getting any younger, so relieve stress by adding a Duration to your Expire Inventory, and perhaps a DBBackuptrigger. In my current setup, I'm cancelling expiration at time [whatever] and am running daily fulls anyway. Most days the expiration doesn't generate nearly enough work to make for a lot of log; but this day it was plowing some fertile ground. Ahh, but it'll all be different soon. :) Big upgrades, new structure... -Allen S. Rout
Re: Backing up files that may have virus
This would appear to be a perfect situation for a Client Backup Set. See the chapter on them in the Administrator's Guide. There, in the very first paragraph it says, The process is also called _instant_archive_. Roger Deschner University of Illinois at Chicago [EMAIL PROTECTED] On Thu, 26 Feb 2004, Shannon Bach wrote: I have a TSM Client V5.1.6 (NW6) whom I backup incrementally on a nightly basis with my MVS OS/390 2.10, TSM Server 5.1.7. I received a call from the administrator of this (client)server that he may have a virus on his server and would I retain his backup from 3 nights ago which may be the last good backup pre-virus. Here are my questions I hope someone who has gone through this before may help me with. 1. The MC for this client is our default of 3 incremental backups, 1 active and 2 inactive. I'm pretty sure I will have to rebind all of this nodes files for a specific length of time in order to keep the last good backup for awhile. Does anyone know if there is an alternative to this? He has not specified a time-length but I'm assuming it may take at least 3 months to find out if he does have a virus, what files it may have affected. (This is my guess , I don't even know for sure what type of data he keeps on his server). 2. What are the possibilities of him restoring the virus accidentally down the line. For example, he may have a file that only gets changed once a year. What if 6 months from now he restores this file because it is the last active version and it is infected with the virus. Would this put the virus back on his system? Is there anyway I can avoid this from happening? Does this make sense or am I being a paranoia? I'll take any helpful opinions or advice I can get. Thank you in advance! Shannon Bach Madison Gas Electric Co. Operations Analyst - Data Center Services e-mail [EMAIL PROTECTED]
AIX HSM and NFS
Hi folks, First our environment: SERVER - TSM 5.1.1.6 on OS/390 2.10 CLIENT - TSM 5.1.5.0 on AIX 4.3 We are experimenting with Space Management (HSM) and our AIX guy has some problems/questions. Is there anything special about referencing an HSM filespace via NFS? I have a fully functional HSM FS on an NFS server, - I have the normal entries in /etc/exports, - I have done the normal 'exportfs -a' command, - I have issued the normal mount command from the client mount hostname:/fsname /mnt, - I get message mount: 1831-010 server hostname not responding: RPC: 1832-019 Program not registered. Am I missing a step? Thanks in advance, Ted Spendlove ATK Thiokol Propulsion
Re: TDP for Domino for Linux on s390
Steve, tdp for domino v5.2 is supported on os/390 at the function level of v5.1.5 on os/390 v2 release 10 configured with Unix services. I did not see linux support, except for tdp for domino v5.2 on linux x86. you can go to http://www.ibmlink.ibm.com you will need to register for this site and need an ibm customer #. Once registered you can acces the announcement for tsm v5.2., announcement letter 203-095. Regards, Paul Steve Roder wrote: Hi All, Does anyone know if such an animal exists? This would be the Domino TDP agent to run on Linux in an LPAR on a z/Series Mainframe running SuSE V8, SP3. All of the code that I can find on the FTP sites is for Linux on X86. Thanks, Steve Roder University at Buffalo ([EMAIL PROTECTED] | (716)645-3564) begin:vcard n:Bergh;Paul tel;work:518-928-9413 x-mozilla-html:FALSE org:Northwood Information Solutions version:2.1 email;internet:[EMAIL PROTECTED] title:President - Consultant adr;quoted-printable:;;3672 Galway Road=0D=0A;Ballston Spa;New York;12020; note;quoted-printable:IBM Business Partner=0D=0ACertified for Tivoli Storage Manager=0D=0ASales and Installation Services fn:Paul Bergh end:vcard
Re: TSM Storage Agent 5.2.0 in AIX 4.3.3 ???
On Wed, 25 Feb 2004 13:47:49 -0400 Juan Jose Reale [EMAIL PROTECTED] wrote: Hello everyone... I know that the TSM Server 5.2.1.3 will run on Server AIX 5.2, but as we have other server AIX 4.3.3, I need to know if the TSM Storage Agent 5.2.1.3 will also run on other server AIX 4.3.3 ? ? Wouldn't it be a good idea to upgrade the OS on these boxes. 4.3.3 is EOL, and at least tivoli decided not to support 5.2 on 4.3.3 since 4.3.3 would be EOL soon anyway. Thank you. -- Met vriendelijke groeten, Remco Post SARA - Reken- en Netwerkdiensten http://www.sara.nl High Performance Computing Tel. +31 20 592 8008Fax. +31 20 668 3167 I really didn't foresee the Internet. But then, neither did the computer industry. Not that that tells us very much of course - the computer industry didn't even foresee that the century was going to end. -- Douglas Adams
Re: Backing up files that may have virus
Some old fashion ways would be to A) export the backups for that file space, then you could import with relative dates down the road... B) rename the filespace BUT the inactive versions would still expire based on retain extra versions so that might not buy you much... but you could rename the file space, allow the actual filespace to continue to backup and not run expiration until you completed an export of the ~renamed~ filespace (us this if the export might run for days...) just a couple of thoughts... Dwight E. Cook Systems Management Integration Professional, Advanced Integrated Storage Management TSM Administration (918) 925-8045 Shannon Bach [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent by: ADSM: cc: Dist StorSubject: Backing up files that may have virus Manager [EMAIL PROTECTED] .EDU 02/26/2004 09:24 AM Please respond to ADSM: Dist Stor Manager I have a TSM Client V5.1.6 (NW6) whom I backup incrementally on a nightly basis with my MVS OS/390 2.10, TSM Server 5.1.7. I received a call from the administrator of this (client)server that he may have a virus on his server and would I retain his backup from 3 nights ago which may be the last good backup pre-virus. Here are my questions I hope someone who has gone through this before may help me with. 1. The MC for this client is our default of 3 incremental backups, 1 active and 2 inactive. I'm pretty sure I will have to rebind all of this nodes files for a specific length of time in order to keep the last good backup for awhile. Does anyone know if there is an alternative to this? He has not specified a time-length but I'm assuming it may take at least 3 months to find out if he does have a virus, what files it may have affected. (This is my guess , I don't even know for sure what type of data he keeps on his server). 2. What are the possibilities of him restoring the virus accidentally down the line. For example, he may have a file that only gets changed once a year. What if 6 months from now he restores this file because it is the last active version and it is infected with the virus. Would this put the virus back on his system? Is there anyway I can avoid this from happening? Does this make sense or am I being a paranoia? I'll take any helpful opinions or advice I can get. Thank you in advance! Shannon Bach Madison Gas Electric Co. Operations Analyst - Data Center Services e-mail [EMAIL PROTECTED] inline: graycol.gifinline: ecblank.gifinline: pic03532.gif
TSM Space Management (HSM) on zOS
I have just been in contact with a VAR that remarkets TSM. The staffer there is telling me that you can license and run Space Management on any server except for zSeries or S/390. Now, we are running Space Management (HSM) on TSM 5.1.1.6 server on OS/390 servicing AIX clients of various versions. Are we doing something unsupported? Anyone else out there running HSM on a OS/390 or z/OS server? We have a 5.1.7.2 server under OS/390 2.10 supporting an AIX space management client. The function is clearly supported, since the syntax for the 'register license' command includes specific provisions for licensing space management. I took a quick look at the 5.2.2.2 documentation and found that the 'register license' command still provides for space management licensing at that release level.
Re: Strange RETRIEVE behaviour
I've noticed some strange behaviour with RETRIEVE, which I haven't been able to explain yet. I've made an ARCHIVE with: dsmc archive -archmc=xyz *.txt -v2archive -filesonly -subdir=no -descr=XYZ This archive was made from the directory /volume/a. When I do a dsmc retrieve * /temp/ -filesonly -descr=XYZ when still in /volume/a, all files are retrieved. When I do the same when switched to /volume/b (different filesystem) nothing is retrieved. ... Observe the syntax of the Retrieve command: sourcefilespec Specifies the path and file name that you want to retrieve. Use wildcard characters to specify a group of files or all the files in a directory. In the absence of an explicit path specification your request is relative to your current location: via the lone asterisk you are requesting all files in the current directory. You can observe the same thing at the Unix prompt by entering the rudimentary command 'echo *'. To retrieve your files from whatever directory location you happen to be sitting in at the moment, you need to be explicit as to their origin. Richard Sims http://people.bu.edu/rbs
