Verifying EXPORT NODE is successful with Q OCC - LOGICAL SPACE OCCUPIED (MB) differences?
Hi Team, I’ve performed an EXPORT NODE operation from a source TSM server (Windows 5.4.3.2) to a target server (AIX 5.5.1.1) over TCP/IP with the TOSERVER option. All appears to have completed successfully, the processes on both TSM Servers report SUCCESS with no errors. However, being of a cautious nature (particularly with others’ data) I’m doing some additional verification, and it’s a comparison of the `Q OCC` output on the two servers that I want to double-check as there's something which has me a little concerned. On the source server (i.e. that from which I issued the EXPORT NODE) the relevant exported filespace looks like this: tsm: CENTSM02q occ CENCONMGR02_CONT /ICM/RMDB/1/CSXMGMT Node Name Type Filespace FSID StorageNumber of Physical Logical Name Pool Name Files Space Space Occupied Occupied (MB) (MB) -- -- - -- - - - NODENAME Bkup FILESPACE 5 LTOCONTC 85,299 16,119.97 16,119.97 On the target server it looks like this: tsm: ARCTSM01q occ CENCONMGR02_CONT /ICM/RMDB/1/CSXMGMT ANR2017I Administrator DAVID.MCCLELLAND issued command: QUERY OCCUPANCY CENCONMGR02_CONT /ICM/RMDB/1/CSXMGMT Node Name Type Filespace FSID StorageNumber of Physical Logical Name Pool Name Files Space Space Occupied Occupied (MB) (MB) -- -- - -- - - - NODENAME Bkup FILESPACE 2 CONT_DISK85,299 16,098.71 16,098.71 Apols if this doesn't come out clearly when converted to plain text, but in summary the NUMBER OF FILES reported is identical (85,299) between source and target, and the PHYSICAL SPACE OCCUPIED (MB) is not - which is down to empty space in aggregates on the source. However, what I want to double check is why the LOGICAL SPACE OCCUPIED (MB) isn't the same - I'd have expected that these would have identical. There's a 20MB difference between the source and target, with less on the target. The variables that I can immediately think of are different TSM Server code and platform, and the storage media (LTO2 on source, DISK on target). Any ideas? I'm certainly happy that the number of files adds up and that the EXPORT/IMPORT NODE commands completed apparently successfully, but I'd like to be able to explain the difference in LOGICAL SPACE OCCUPIED, or understand if this figure is indeed definitive or subject to rounding etc. Thanks Rgds, David Mc London, UK No virus found in this outgoing message. Checked by AVG. Version: 7.5.524 / Virus Database: 270.12.0/2068 - Release Date: 19/04/2009 20:04
Re: Verifying EXPORT NODE is successful with Q OCC - LOGICAL SPACE OCCUPIED (MB) differences?
David - The Admin Ref manual description of the Physical and Logical Space report element from Query OCCupancy is superficial, leading the customer to believe that the Logical value is just the amount of space occupied by client files. According to info I've seen, logical space also includes headers housing control information for each file, such as magic numbers, CRC info, segment numbering, server ID, etc. The size of the header info can vary as TSM evolves, and so may differ across TSM releases. The header size can be seen in the output of the SHow INVObject command for a given ObjectID. Richard Sims http://people.bu.edu/rbs
syntax problem | preschedulecmd
hi all, i'm trying to execute backup from with preschedulecmd from windows client like - powershell 'B:\Laptop Backup\system_backups\scripts\sys_backup2.ps1' wzpwebstream1 but i'm having problems how to put it into -preschedulecmd as an option of course, errors are something like ANR2020E UPDATE SCHEDULE: Invalid parameter - B:\LAPTOP ANR2020E UPDATE SCHEDULE: Invalid parameter - . etc.. above mentioned line works flawlesly from cmd prompt on client, i guess the problem is where to put all the 's and s and 's and more 's , right ? thanks for help! // PS: the script executes ntbackup as scheduled task (via wmi) on any remote machine and stores *.bkf localy ready for archiving
Object size query
I would like to query the DB for any stored objects 1GB. The output will help improve our incl/excl specifications. The only table/column I see is CONTENTS/FILE_SIZE. My select works, but obviously it's an intense scan. Is CONTENTS the only place? Please suggest the best approach.
Re: Object size query
On Apr 21, 2009, at 18:09 , Mark Devine wrote: I would like to query the DB for any stored objects 1GB. The output will help improve our incl/excl specifications. The only table/column I see is CONTENTS/FILE_SIZE. My select works, but obviously it's an intense scan. Is CONTENTS the only place? Please suggest the best approach. contents and backups, and yes, you don't want to run queries against those -- Met vriendelijke groeten, Remco Post r.p...@plcs.nl +31 6 248 21 622
Re: syntax problem | preschedulecmd
The whole presched command needs to be quoted as one item. Converting from Laptop Backup to the short name should save the single quotes. If powershell will honor the single quotes, you can use them to quote the powershell arguments instead, and then then double quotes are available for the whole string passed to preschedulecmd. [RC] -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of goc Sent: Tuesday, April 21, 2009 6:50 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] syntax problem | preschedulecmd hi all, i'm trying to execute backup from with preschedulecmd from windows client like - powershell 'B:\Laptop Backup\system_backups\scripts\sys_backup2.ps1' wzpwebstream1 but i'm having problems how to put it into -preschedulecmd as an option of course, errors are something like ANR2020E UPDATE SCHEDULE: Invalid parameter - B:\LAPTOP ANR2020E UPDATE SCHEDULE: Invalid parameter - . etc.. above mentioned line works flawlesly from cmd prompt on client, i guess the problem is where to put all the 's and s and 's and more 's , right ? thanks for help! // PS: the script executes ntbackup as scheduled task (via wmi) on any remote machine and stores *.bkf localy ready for archiving DISCLAIMER: This message is intended for the sole use of the addressee, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not the addressee you are hereby notified that you may not use, copy, disclose, or distribute to anyone the message or any information contained in the message. If you have received this message in error, please immediately advise the sender by reply email and delete this message.
Re: Object size query
You can produce an allied report by scanning your dsmaccnt.log to report on large adds (Archive or Backup operations) over a long period of time, by dividing quantity of data sent to the TSM server by the number of objects, allowing you to identify nodes and users (but not filespaces) involved in biggies. This alone may be sufficient for your needs; or you might use it to perform a more limited Select on formidable tables. Richard Sims
Re: Object size query
Not really an answer, set max file size of primary pool to 1GB and force it to a next large file pool. Check what files ends up in the large file pool. -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Richard Sims Sent: Tuesday, April 21, 2009 10:43 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: Object size query You can produce an allied report by scanning your dsmaccnt.log to report on large adds (Archive or Backup operations) over a long period of time, by dividing quantity of data sent to the TSM server by the number of objects, allowing you to identify nodes and users (but not filespaces) involved in biggies. This alone may be sufficient for your needs; or you might use it to perform a more limited Select on formidable tables. Richard Sims
Re: Object size query
Upgrade to version 6, and just run your SQL without fear. :) -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Mark Devine Sent: Tuesday, April 21, 2009 10:10 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Object size query I would like to query the DB for any stored objects 1GB. The output will help improve our incl/excl specifications. The only table/column I see is CONTENTS/FILE_SIZE. My select works, but obviously it's an intense scan. Is CONTENTS the only place? Please suggest the best approach.
Green issue: How to avoid leaving clients on all night
We're getting requests from a number of people who have their desktop computers (mix of Macs and Windows XP/Vista) backed up to TSM, for a way to avoid leaving them on all night. The issue is simple energy conservation. Even with the monitor off, and the disk drives spun down, a live PC still consumes quite a bit of electricity. If you put it into either Hibernate or Standby mode, the TSM Scheduler cannot run the backup. We had thought of setting a POSTSCHEDULECOMMAND of shutdown, but that has a severe problem. What if you were working late, because of an urgent project, and backup ran. Your computer would then shut down without saving what you were working on, and precisely because it was urgent enough for you to be working on it late, this would be very valuable work that would be lost. Has anybody figured out a way around this basic problem? Roger Deschner University of Illinois at Chicago rog...@uic.edu Research is what I'm doing when I don't know what I'm doing. = -- Wernher von Braun =
Re: Green issue: How to avoid leaving clients on all night
Why not just give them a warning/mandate that if they are working late, they need to go out under services and disable the TSM client scheduler until they are done working, then start the scheduler before leaving. -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Roger Deschner Sent: Tuesday, April 21, 2009 7:55 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Green issue: How to avoid leaving clients on all night We're getting requests from a number of people who have their desktop computers (mix of Macs and Windows XP/Vista) backed up to TSM, for a way to avoid leaving them on all night. The issue is simple energy conservation. Even with the monitor off, and the disk drives spun down, a live PC still consumes quite a bit of electricity. If you put it into either Hibernate or Standby mode, the TSM Scheduler cannot run the backup. We had thought of setting a POSTSCHEDULECOMMAND of shutdown, but that has a severe problem. What if you were working late, because of an urgent project, and backup ran. Your computer would then shut down without saving what you were working on, and precisely because it was urgent enough for you to be working on it late, this would be very valuable work that would be lost. Has anybody figured out a way around this basic problem? Roger Deschner University of Illinois at Chicago rog...@uic.edu Research is what I'm doing when I don't know what I'm doing. = -- Wernher von Braun =
Re: Green issue: How to avoid leaving clients on all night
Roger - A Macintosh can be scheduled to start up and/or shut down at chosen times on chosen days, through the Energy Saver system preference, and thus be alive for TSM client schedule activity. It's polite about this when someone happens to be using the computer. Richard Sims
Re: Green issue: How to avoid leaving clients on all night
Hi Roger I've not done it but There is a wake on lan function available. Send an appropriately crafted packet to the ethernet port and the machine will boot, if configured properly. If you use a schedule with a long window, then the backup will start as soon as the cad/scheduler is initialized after the boot. A preschedule command to simply wait for 5 minutes may be needed to make sure things are stable before you start really moving data. As to the shutdown part, you need to determine if any users are logged in, and only shutdown if none are. I'm reasonably sure you can do this from windows with vbscript/jscript and the WMI api. So, in short do-able, but there are some details to work out. A quick google search indicates there are a lot of people doing this for non-TSM reasons. Regards Steve. Steven Harris TSM Admin, Sydney Australia Roger Deschner rog...@uic.edu Sent by: ADSM:To Dist Stor ADSM-L@VM.MARIST.EDU Manager cc ads...@vm.marist .EDU Subject [ADSM-L] Green issue: How to avoid leaving clients on all night 22/04/2009 10:55 AM Please respond to ADSM: Dist Stor Manager ads...@vm.marist .EDU We're getting requests from a number of people who have their desktop computers (mix of Macs and Windows XP/Vista) backed up to TSM, for a way to avoid leaving them on all night. The issue is simple energy conservation. Even with the monitor off, and the disk drives spun down, a live PC still consumes quite a bit of electricity. If you put it into either Hibernate or Standby mode, the TSM Scheduler cannot run the backup. We had thought of setting a POSTSCHEDULECOMMAND of shutdown, but that has a severe problem. What if you were working late, because of an urgent project, and backup ran. Your computer would then shut down without saving what you were working on, and precisely because it was urgent enough for you to be working on it late, this would be very valuable work that would be lost. Has anybody figured out a way around this basic problem? Roger Deschner University of Illinois at Chicago rog...@uic.edu Research is what I'm doing when I don't know what I'm doing. = -- Wernher von Braun =
Re: Green issue: How to avoid leaving clients on all night
Roger Deschner wrote: We had thought of setting a POSTSCHEDULECOMMAND of shutdown, but that has a severe problem. What if you were working late, because of an urgent project, and backup ran. Your computer would then shut down without saving what you were working on, and precisely because it was urgent enough for you to be working on it late, this would be very valuable work that would be lost. What about a POSTSCHEDULECOMMAND that puts the computer into hibernate or standby mode instead of shutting it down? On the days someone is working late, they can just wake it back up. If this situation is the exception rather than the rule, you still come out ahead most of the time; most workstations would be suspended most nights. -- Hello World.David Bronder - Systems Admin Segmentation Fault ITS-SPA, Univ. of Iowa Core dumped, disk trashed, quota filled, soda warm. david-bron...@uiowa.edu
Re: Green issue: How to avoid leaving clients on all night
Well, you could try wrapping the shutdown program in a script with some intelligence behind it. I put a VBScript together fairly quickly on my XP workstation and it seems to work okay (see below). Notes: * I tested on XP only, so you'll need to test on other Windows OSes. * I use LocalSystem as the account for my scheduler service, in which case I had to use the Services applet to configure the account to allow interaction with my desktop. If I didn't do this, the Yes/No/Cancel prompt did not show up on my system. * When modifying the script or testing in your environment, if you want to stop a shutdown and the script isn't doing the trick, issue shutdown -a from a Windows OS prompt to stop the shutdown. * In general I would not normally expect the results of this script to otherwise have any bearing on the results of the scheduled operation that is reported to the TSM server. Therefore I recommend using POSTNSCHEDULECMD rather than POSTSCHEDULECMD. On my system, I put this in my options file: postnschedulecmd c:\my_vbscripts\shutitdown.vbs * Use a sane delay value that gives your users a chance to cancel the shutdown; for example, if they stepped away for a break. * Note that if the TSM client is unable to immediately update the server with the results of the scheduled event (for whatever reason, this is hypothetical) and it needs to retry, your shutdown script might shut the client down before the results can be reported back. As an alternative, you could define a separate schedule with ACTION=COMMAND to invoke the shutdown script; this schedule would run after the regular backup schedule. * This is provided as is, without warranty of any kind. Use at your own risk. You can modify it for your needs, but make sure you test it thoroughly before you deploy to avoid unexpected surprises from your users. '=== ' shutitdown.vbs ' Author: Andrew M. Raibeck ' stor...@us.ibm.com ' Tivoli Storage Manager client development ' IBM Corporation ' (c) Copyright by IBM Corporation 2009. All Rights Reserved. ' ' This code is provided on an as is basis without warranty of any ' kind. Use is at your own risk. Test thoroughly in your environment ' before deploying. ' ' Adjust delay to appropriate value in seconds. Consider possibility that ' user may have stepped away for a few minutes and might not be able to ' respond right away, so maybe something like delay = 1800 is more ' realistic. delay = 60 ' shutdown parameters: ' -s means shutdown ' -f means to force all running programs to close ' -t means to delay the shutdown by the specified number of seconds cmd = shutdown -s -f -t delay newline = Chr(13) Chr(10) msg = The computer will shut down in delay seconds. newline _ newline _ Press Yes to shut down now. newline _ Press No to stop the shut down. newline _ Press Cancel to shut down at the end of the countdown title = Daily shutdown prompt ' Issue the shutdown command. set objShell = Wscript.CreateObject(Wscript.Shell) objShell.Run cmd, 1, True ' vbDefaultButton2 used to make No the default, in case user ' accidentally presses ENTER without seeing the message. This ' is probably the safest. vbSystemModal will force the Msgbox ' dialog to appear on top of the shutdown dialog. confirmation = MsgBox(msg, _ vbYesNoCancel or vbDefaultButton2 or vbSystemModal, _ title) if confirmation = vbYes then ' Abort the current shutdown, then initiate a new instant shutdown. set objShell = Wscript.CreateObject(Wscript.Shell) objShell.Run shutdown -a, 2, True objShell.Run shutdown -s -f -t 0, 2, True elseif confirmation = vbNo then ' Abort the shutdown set objShell = Wscript.CreateObject(Wscript.Shell) objShell.Run shutdown -a, 2, True else ' Do nothing, just let the current shutdown command continue. end if '=== Andy Raibeck IBM Software Group Tivoli Storage Manager Client Product Development Level 3 Team Lead Internal Notes e-mail: Andrew Raibeck/Tucson/i...@ibmus Internet e-mail: stor...@us.ibm.com IBM Tivoli Storage Manager support web page: http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html The only dumb question is the one that goes unasked. The command line is your friend. Good enough is the enemy of excellence. ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 2009-04-21 20:55:05: [image removed] Green issue: How to avoid leaving clients on all night Roger Deschner to: ADSM-L 2009-04-21 20:55 Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU Please respond to ADSM: Dist Stor Manager We're getting requests from a number of people who have their desktop computers (mix of Macs and Windows XP/Vista) backed up to TSM, for a way to avoid leaving them on all night. The issue
Summary in TSM
Hi, I am able to get information for only 30 days from the below command .how to increase the days of information we need to get. Select * from summary Regards, Kiran. Disclaimer: This email message (including attachments if any) may contain privileged, proprietary, confidential information, which may be exempt from any kind of disclosure whatsoever and is intended solely for the use of addressee (s). If you are not the intended recipient, kindly inform us by return e-mail and also kindly disregard the contents of the e-mail, delete the original message and destroy any copies thereof immediately. You are notified that any dissemination, distribution or copying of this communication is strictly prohibited unless approved by the sender. DQ Entertainment (DQE) has taken every reasonable precaution to minimize the risk of transmission of computer viruses with this e-mail; DQE is not liable for any damage you may sustain as a result of any virus in this e-mail. DQE shall not be liable for the views expressed in the e-mail. DQE reserves the right to monitor and review the content of all messages sent to or from this e-mail address
