Export Node
I need to export some nodes from one TSM server to another to balance the load. I tested the command 'export node1 filedata=all toserver=serverb mergfilespaces=yes' and got a data rate of about 16GB an hour. The 2nd run of the exact same command finished in 1/4 of the first run time and moved no data. (no changes to the data between runs) This indicates that there is a time savings for the incremental passes should the process end before completion. Has anyone used this method to move TBs of data between TSM servers while the nodes are active? I cannot stop backing up the node for the week it will take to move the data. Are there any other faster ways to move the data? Andy Huebner This e-mail (including any attachments) is confidential and may be legally privileged. If you are not an intended recipient or an authorized representative of an intended recipient, you are prohibited from using, copying or distributing the information in this e-mail or its attachments. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete all copies of this message and any attachments. Thank you.
export node
Hello, I am trying to export the obsolete nodes(filespace and all) so that I can free up some space on tsm server. The problem is I am low on scratch volumes where these nodes reside. Am I correct to think that I better have sufficient scratch volumes available before exporting the obsolete nodes as the scratch volumes will be used up or will more volumes be readily available to convert to scratch once I set the export nodes in motion? Thanks, Avy Wong Business Continuity Administrator Mohegan Sun 1 Mohegan Sun Blvd Uncasville, CT 06382 (860) 862-8164 cell (860) 961-6976 ** 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 copy 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. **
Export Node
Hi, we want to move from our OS/390 TSM server to a Solaris TSM server. What's the best practical way to get our "old" data to the new server? mfg / regards andreas rensch When all else fails, read the instructions.
Export node (Directly)
ServerA has a combination of primary storage pools, disk & tape library managed using migration, etc. It also has a segmented disk storage pool environment like AIXBKPOOL, NTBKPOOL, AIXARCHPOOL, NTARCHPOOL ServerB has only a single disk based storage pools such as ALLDISKPOOL. If on ServerA I entered: Export Node aixnode1 File=* Filedata=all Toserver=ServerB Would it place all the backup and archive data for aixnode1 in ALLDISKPOOL on ServerB?
EXPORT node toserver
I ran an export node toserver and it errored 1/3 of the way into 200gb of data. Are there any steps that need to be taken in order to restart this other than mergefilespace ? Will any of my archive data be duplicated on the target server ?
EXPORT NODE TOSERVER
Hi folks, I'm in the process of converting from TSM V5.1 on OS/390 to TSM V5.2 on Windows. The Admin Ref. For V5.2 lists the TOSserver= option for the EXPort Node command. This option is not listed in the V5.1 documentation. Just to be perverse, I tried the TOServer= option on the V5.1 server pointing to the V5.2 server and it seems to work but . . . Is this undocumented feature available, reliable, and supported at the V5.1 level? I'd really like to use it as one of the tools in the conversion plan. Thanks, Ted Spendlove ATK Thiokol
Restartable export node?
Hi, I'm migrating a TSM instance from AIX to Linux. I have a node that has a single filespace with about 5TB of data in it. Looking at the performance I'm getting I'd guess that the export node is going to take a week or two to complete - not good. And most likely I'll never get it to finish. So, is there anyway to restart a failed export node, or am I better of trying to scrounge up 5T of disk and restoring the data and then re-archiving it on the other end? Or, conversely, is there any way to export something at a finer granularity than filespace? If it makes a difference my TSM versions are... AIX : 5.1.6 Linux : 5.3.1.6 Thanks for any help or advice. Jason. -- Jason Lee DreamWorks Animation (818) 695-3782
Re: Export Node
Yes we here at Duke have mover over 14 TBs of data with this method And we were able to move about 1 TB per day with our environment. From: TSM Server: AIX 5.3 IBM, 7026-H80 4 GB memory 450 MHz CPU To: TSM Server: AIX 5.3 (P630) IBM, 7028-6C4 4 GB memory, 1.2 GHz CPU Have to make sure that your tape drives our available for the extra work. Justin -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Andy Huebner Sent: Thursday, May 11, 2006 3:41 PM To: ADSM-L@VM.MARIST.EDU Subject: Export Node I need to export some nodes from one TSM server to another to balance the load. I tested the command 'export node1 filedata=all toserver=serverb mergfilespaces=yes' and got a data rate of about 16GB an hour. The 2nd run of the exact same command finished in 1/4 of the first run time and moved no data. (no changes to the data between runs) This indicates that there is a time savings for the incremental passes should the process end before completion. Has anyone used this method to move TBs of data between TSM servers while the nodes are active? I cannot stop backing up the node for the week it will take to move the data. Are there any other faster ways to move the data? Andy Huebner This e-mail (including any attachments) is confidential and may be legally privileged. If you are not an intended recipient or an authorized representative of an intended recipient, you are prohibited from using, copying or distributing the information in this e-mail or its attachments. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete all copies of this message and any attachments. Thank you.
Re: Export Node
Hi Andy and all, Recently we did try to export some data from onsite production server to offsite server. We did a media export rather than server to server export due to network bandwidth and to save TSM resources on the onsite production server . Well, mine is just around 2TB and all goes into tape(s). On the offsite, I'll make sure there's a storage pool with enough tapes. I did a preview before importing it to estimate the quantity of tapes needed. Then import the node definition and lastly import the data into the storage pool. I'm on my way bring up the database (SAP R3 for Oracle). However I'm facing difficulties in doing so. The log file for TDP restore on the file level system no longer exist and therefore brtools can't be used to do the restore. We are looking for ways to bring up database. Anyone can share and help on this problem of mine? Thanks and Warmest Regards, Justin Case <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" 05/12/2006 04:27 AM Please respond to "ADSM: Dist Stor Manager" To ADSM-L@VM.MARIST.EDU cc Subject Re: [ADSM-L] Export Node Yes we here at Duke have mover over 14 TBs of data with this method And we were able to move about 1 TB per day with our environment. From: TSM Server: AIX 5.3 IBM, 7026-H80 4 GB memory 450 MHz CPU To: TSM Server: AIX 5.3 (P630) IBM, 7028-6C4 4 GB memory, 1.2 GHz CPU Have to make sure that your tape drives our available for the extra work. Justin -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Andy Huebner Sent: Thursday, May 11, 2006 3:41 PM To: ADSM-L@VM.MARIST.EDU Subject: Export Node I need to export some nodes from one TSM server to another to balance the load. I tested the command 'export node1 filedata=all toserver=serverb mergfilespaces=yes' and got a data rate of about 16GB an hour. The 2nd run of the exact same command finished in 1/4 of the first run time and moved no data. (no changes to the data between runs) This indicates that there is a time savings for the incremental passes should the process end before completion. Has anyone used this method to move TBs of data between TSM servers while the nodes are active? I cannot stop backing up the node for the week it will take to move the data. Are there any other faster ways to move the data? Andy Huebner This e-mail (including any attachments) is confidential and may be legally privileged. If you are not an intended recipient or an authorized representative of an intended recipient, you are prohibited from using, copying or distributing the information in this e-mail or its attachments. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete all copies of this message and any attachments. Thank you.
Re: export node
Yes - Original Message - From: [EMAIL PROTECTED] <[EMAIL PROTECTED]> To: ADSM-L@VM.MARIST.EDU Sent: Thu Apr 05 12:17:32 2007 Subject: export node Hello, I am trying to export the obsolete nodes(filespace and all) so that I can free up some space on tsm server. The problem is I am low on scratch volumes where these nodes reside. Am I correct to think that I better have sufficient scratch volumes available before exporting the obsolete nodes as the scratch volumes will be used up or will more volumes be readily available to convert to scratch once I set the export nodes in motion? Thanks, Avy Wong Business Continuity Administrator Mohegan Sun 1 Mohegan Sun Blvd Uncasville, CT 06382 (860) 862-8164 cell (860) 961-6976 ** 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 copy 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. **
Export node question
Hi I run each month a Disaster Recovery of some critical clients and take the data offsite. My question is after the process finished and the cartridge are checkout off the library with a copy of volhistory , devconfig and DBS I have a client who missed the scheduler and not backup . Can I a day after make a special export node with the option filedata=backupactive , checkout the volume. Can I do after atotal crash a restore first of my DBS with the volhistory ,devconfig , checkin the cartridges back of the DRM and secondly make an import node of my missed client with the parameter volumenames= X . My volhistory file is without the event of the export node which take place after the DRM process . T.I.A Regards Robert Ouzen E-mail: [EMAIL PROTECTED]
Re: Export Node
We moved from OS/390 to an AIX machine. We moved each client using server to server export. We had about 400 clients to move and It took us about 3 months to move all of the clients to the new machine. We would do one to several clients each day depending on the size of the clients. Jim Sporer At 11:38 AM 12/13/2001 +0100, you wrote: >Hi, > >we want to move from our OS/390 TSM server to a Solaris TSM server. What's >the best practical way to get our "old" data to the new server? > >mfg / regards > >andreas rensch > >When all else fails, read the instructions.
Re: Export Node
Hello Look in the RedBook ADSM Server-to-Server Implemantation and Operation SG24-5244-00. It explains the process very well -Original Message- From: Andreas Rensch [mailto:[EMAIL PROTECTED]] Sent: den 13 december 2001 11:38 To: [EMAIL PROTECTED] Subject: Export Node Hi, we want to move from our OS/390 TSM server to a Solaris TSM server. What's the best practical way to get our "old" data to the new server? mfg / regards andreas rensch When all else fails, read the instructions.
Re: Export Node
Hi
S/390 databases cannot be exported to a solaris machine.
Also, if your using Tivoli Storage Manager S/390 Edition version 4.1,
server-to-server isn't supported by Tivoli, and I don't know if it works at
all.
According to Tivoli, exporting a database is only supported on open systems
environments.
Using Server-To-Server communication won't export all of the TSM database.
When doing a S-S, nodes, domain and so on will be exported.
However, you cannot transport the devices, filespaces and file information.
Therefore, I wouldn't recommend this, and it is probably not supported by
Tivoli(if it works). If you cannot transport the devices, how will you be
able to transport file information? And if you cannot export file
information, you won't have transported the data, only the node names.
The best practice would be to use the Export command, exporting nodes,
filespaces and so on. However, this works theoretically, but I don't know
Tivolis position in this case.
Also, I don't know how you have connected you're storage devices. But if
you're using a Storagetek Powderhorn, it's ACSLS connected. Setting up this
in an open systems environment, is risky, concidering that your moving
production data. You wouldn't want to loose any of the data stored on the
tapes.
Perhaps this would work if you we're using Gresham EDT. I haven't tried
this, but, theoretically, it would probably work.
I don't know how many clients you have, but if they aren't that many,
wouldn't it be easier to move the clients to a new Solaris platforms. You
shouldn't move all at once, but perhaps migrate a couple at a time.
Best Regards
Daniel Sparrman
---
Daniel Sparrman
Exist i Stockholm AB
Bergkällavägen 31D
192 79 SOLLENTUNA
Växel: 08 - 754 98 00
Mobil: 070 - 399 27 51
Niklas Lundstrom
cc:
Sent by: "ADSM: Dist Stor Subject: Re: Export
Node
Manager" <[EMAIL PROTECTED]>
2001-12-20 16:18
Please respond to "ADSM: Dist
Stor Manager"
Hello
Look in the RedBook ADSM Server-to-Server Implemantation and Operation
SG24-5244-00.
It explains the process very well
-Original Message-
From: Andreas Rensch [mailto:[EMAIL PROTECTED]]
Sent: den 13 december 2001 11:38
To: [EMAIL PROTECTED]
Subject: Export Node
Hi,
we want to move from our OS/390 TSM server to a Solaris TSM server. What's
the best practical way to get our "old" data to the new server?
mfg / regards
andreas rensch
When all else fails, read the instructions.
EXPORT NODE problems
Folks, I'm still having enormous difficulty trying to EXPORT a DB2 node from a TSM 4.1.0.0 server on WinNT4 but seem to be getting nowhere fast. Client and server are physically on the same hardware. Every attempt to export seems to fail, on this occassion with a (probable) device I/O error: 24-04-2002 00:39:39 ANR8341I End-of-volume reached for 3590 volume 030460. 24-04-2002 00:39:39 ANR1362I Output volume 030460 closed (full). 24-04-2002 00:39:43 ANR8336I Verifying label of 3590 volume 030460 in drive 78F94901 (MT3.0.0.2). 24-04-2002 00:40:22 ANR8914I Drive 78F94901 (MT3.0.0.2) in library OS3494P3 needs to be cleaned. 24-04-2002 00:40:22 ANR8468I 3590 volume 030460 dismounted from drive 78F94901 (MT3.0.0.2) in library OS3494P3. 24-04-2002 00:43:56 ANR8337I 3590 volume 030449 mounted in drive 78F94901 (MT3.0.0.2). 24-04-2002 00:43:57 ANR0662E EXPORT NODE: Output error encountered in accessing data storage. 24-04-2002 00:43:57 ANR0569I Object not processed for DB2RSLTSBDC1001_DB2: type=Backup, file space=/SIGNPLUS, object=\NODE\ FULL_BACKUP.2002040305.2. 24-04-2002 00:44:03 ANR0794E EXPORT NODE: Processing terminated abnormally - error accessing data storage. 24-04-2002 00:44:03 ANR0626I EXPORT NODE: Copied 1 node definitions. 24-04-2002 00:44:03 ANR0568W Session 36 for admin 2031219 (Server) terminated - connection with client severed. 24-04-2002 00:44:03 ANR0627I EXPORT NODE: Copied 1 file space 0 archive files, 4 backup files, and 0 space managed files. 24-04-2002 00:44:03 ANR0656W EXPORT NODE: Skipped 0 archive files, 1 backup files, and 0 space managed files. 24-04-2002 00:44:03 ANR0630I EXPORT NODE: Copied 216964081 kilobytes of data. 24-04-2002 00:44:03 ANR0611I EXPORT NODE started by 2031219 as process 2 has ended. 24-04-2002 00:44:03 ANR0986I Process 2 for EXPORT NODE running in the BACKGROUND processed 6 items for a total of 222,171,219,- 015 bytes with a completion state of FAILURE at 00:44:03. 24-04-2002 00:44:32 ANR8468I 3590 volume 030449 dismounted from drive 78F94901 (MT3.0.0.2) in library OS3494P3. 24-04-2002 00:49:03 ANR8325I Dismounting volume 030469 - 5 minute mount retention expired. 24-04-2002 00:51:25 ANR8468I 3590 volume 030469 dismounted from drive 78F94920 (MT2.0.0.2) in library OS3494P3. There's plenty of available cartridges. Is this just a really ropey bit of code or do we have sudden and universal tape drive problems? Matt * internal.7-430-3213 * external. 020-7922-3213 * fax020-7922-3302 * e-mail[EMAIL PROTECTED] --- This e-mail is intended only for the above addressee. It may contain privileged information. If you are not the addressee you must not copy, distribute, disclose or use any of the information in it. If you have received it in error please delete it and immediately notify the sender. evolvebank.com is a division of Lloyds TSB Bank plc. Lloyds TSB Bank plc, 71 Lombard Street, London EC3P 3BS. Registered in England, number 2065. Telephone No: 020 7626 1500 Lloyds TSB Scotland plc, Henry Duncan House, 120 George Street, Edinburgh EH2 4LH. Registered in Scotland, number 95237. Telephone No: 0131 225 4555 Lloyds TSB Bank plc and Lloyds TSB Scotland plc are regulated by the Personal Investment Authority and represent only the Scottish Widows and Lloyds TSB Marketing Group for life assurance, pensions and investment business. Members of the UK Banking Ombudsman Scheme and signatories to the UK Banking Code. ---
Export node information.
Has anyone run an Export node for Exchange data ? For instance: I have a node that had the incorrect MC assigned in the opt file. My deletion process that runs on the TDP client deletes excess backups but keeps 1 per month for 18 months. I ran a q occupancy and found that there were 360 backup versions (1.6tb) for this one TDP for Exchange client, I was able to rebind the active files, but 348 copies are inactive and can not be modified. I called Tivoli and found that TDP for Exchange 1.1 went out of service on 3-31-2002. So no support, unless we extend our maintenance or get charged the hourly charge. My attempt at a solution: export node "client node" filedata=allactive Remove the tapes from the jukebox that the export completed to. Delete the filespaces associated to the client. Load the tapes back into the jukebox, then import the data. It should work... Right ? Duane Ochs Systems Administration Quad/Graphics Inc. 414.566.2375
Export node question
Hello I have an information question about the process export node (server to server) . When I run the command: export node X filedata=alltoserver=Y exportidentifier=X How the process export the files ? Active data first and then the inactive data ? or how ? I know that I can choose on the parameter filedata= …. the data I want to export but if I choose "ALL" what will be order? Best Regards Robert
SV: Export node (Directly)
Hi Larry, Because of you specify "Filedata=all" means that all your backups will be transferred to ServerB. About if the data will be saved to ALLDISKPOOL is depending on how your policy domain is setup on ServerB where node AIXNODE1 is belonging to. Thanks Christian -Ursprungligt meddelande- Från: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] För Larry Clark Skickat: den 27 september 2007 16:32 Till: ADSM-L@VM.MARIST.EDU Ämne: Export node (Directly) ServerA has a combination of primary storage pools, disk & tape library managed using migration, etc. It also has a segmented disk storage pool environment like AIXBKPOOL, NTBKPOOL, AIXARCHPOOL, NTARCHPOOL ServerB has only a single disk based storage pools such as ALLDISKPOOL. If on ServerA I entered: Export Node aixnode1 File=* Filedata=all Toserver=ServerB Would it place all the backup and archive data for aixnode1 in ALLDISKPOOL on ServerB?
Re: EXPORT node toserver
If you are using TSM Server version 5.5 export node will start from where it left off. You can use mergefilespace option also so it will not duplicate. Also issue following command on the source server ' q export ' to see the status of the export. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Ochs, Duane Sent: Thursday, July 03, 2008 10:17 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] EXPORT node toserver I ran an export node toserver and it errored 1/3 of the way into 200gb of data. Are there any steps that need to be taken in order to restart this other than mergefilespace ? Will any of my archive data be duplicated on the target server ?
Re: EXPORT node toserver
I'm using TSM 5.4.3 . -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Abid Ilias Sent: Thursday, July 03, 2008 10:25 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: EXPORT node toserver If you are using TSM Server version 5.5 export node will start from where it left off. You can use mergefilespace option also so it will not duplicate. Also issue following command on the source server ' q export ' to see the status of the export. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Ochs, Duane Sent: Thursday, July 03, 2008 10:17 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] EXPORT node toserver I ran an export node toserver and it errored 1/3 of the way into 200gb of data. Are there any steps that need to be taken in order to restart this other than mergefilespace ? Will any of my archive data be duplicated on the target server ?
Re: EXPORT node toserver
TSM has made a major change for the exporting the node between servers in version 5.5, where you restart the export node process that was suspended because or error. I think in your case mergefilespace=yes option will work so, the data doesn't get duplicated, but the entire process will start from the beginning (unfortunately). Abid -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Ochs, Duane Sent: Thursday, July 03, 2008 10:28 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] EXPORT node toserver I'm using TSM 5.4.3 . -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Abid Ilias Sent: Thursday, July 03, 2008 10:25 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: EXPORT node toserver If you are using TSM Server version 5.5 export node will start from where it left off. You can use mergefilespace option also so it will not duplicate. Also issue following command on the source server ' q export ' to see the status of the export. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Ochs, Duane Sent: Thursday, July 03, 2008 10:17 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] EXPORT node toserver I ran an export node toserver and it errored 1/3 of the way into 200gb of data. Are there any steps that need to be taken in order to restart this other than mergefilespace ? Will any of my archive data be duplicated on the target server ?
Backupsets and Export Node
TSM Server 5.2.0.0 running on the Windows platform. We have some issues at one of our offices. Here's what I've been able to decipher: There are several Netware,Linux and Windows nodes (12 total) that no longer exist and all hardware has been reused. They require one last "backup/archive" of these nodes that they want kept around for a couple of years. Of course, since these nodes no longer physically exist, my options are limited to backupsets and export node (I believe). Thrown into the mix, the IBM 3583 Tape Library is at capacity and an upgrade is pending but will take some time to get approved. (1). If I do generate backupsets for these nodes, can I then delete the filespace data to free up Tape Library space? (2). If I opt for export node, could I export the nodes, remove all references to the nodes and re-import to the same TSM server if I ever need to? Any other options out there? I've reads through the numerous posts on Backupsets and Export Node but none seem to address my concerns. Thank you Marco
Re: EXPORT NODE TOSERVER
On May 25, 2005, at 12:57 PM, Spendlove, Ted wrote: ...Is this undocumented feature available, reliable, and supported at the V5.1 level? ... The Readme files supplied with the maintenance levels describe new features added by those in-between-releases software updates. The TOServer option was introduced at the 5.1.5 level. Richard Sims
Re: EXPORT NODE TOSERVER
Thanks Richard, I had forgotten about the readme (APAR/PTF) write-ups. But, I guess the question is still open, since our OS390 TSM server is at V5.1.1.6 level. Ted Spendlove -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Richard Sims Sent: Wednesday, May 25, 2005 11:36 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: EXPORT NODE TOSERVER On May 25, 2005, at 12:57 PM, Spendlove, Ted wrote: > ...Is this undocumented feature available, reliable, and supported at > the > V5.1 level? ... The Readme files supplied with the maintenance levels describe new features added by those in-between-releases software updates. The TOServer option was introduced at the 5.1.5 level. Richard Sims
Re: EXPORT NODE TOSERVER
On May 25, 2005, at 2:06 PM, Spendlove, Ted wrote: Thanks Richard, I had forgotten about the readme (APAR/PTF) write-ups. But, I guess the question is still open, since our OS390 TSM server is at V5.1.1.6 level. Ted - I'd say, have a look at the Readme file that you have for that level. Beyond that, the simplest and most obvious method of verifying the voracity of a server command operand is to do a Help on that command: if the help info was updated with the software, as it should be, then the operand should be reflected therein. Richard Sims
Re: EXPORT NODE TOSERVER
Thanks again Richard. If it were Friday I could use that as an excuse, otherwise I guess it's just old age, that I didn't think of the HELP command either. Did it. Got it. It works. Thanks again, Ted Spendlove -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Richard Sims Sent: Wednesday, May 25, 2005 12:15 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: EXPORT NODE TOSERVER On May 25, 2005, at 2:06 PM, Spendlove, Ted wrote: > Thanks Richard, > > I had forgotten about the readme (APAR/PTF) write-ups. But, I guess > the question is still open, since our OS390 TSM server is at V5.1.1.6 > level. > Ted - I'd say, have a look at the Readme file that you have for that level. Beyond that, the simplest and most obvious method of verifying the voracity of a server command operand is to do a Help on that command: if the help info was updated with the software, as it should be, then the operand should be reflected therein. Richard Sims
Export node with TDP's ?
1. Does anyone know if export node works with the Exchange TDP? (Win2k3 with Exchange2k3) 2. Instead of running multiple Nodenames on our Cluster servers we are looking for ways of doing monthly backups and keep them for many years while still keeping our weekly backups for only 10 versions. Unfortunately it seems one cannot specify a ManagementClass on the commandline so we cannot use a different MC for this. Any other thoughts? Regards Louw Pretorius ___ Informasie Tegnologie Stellenbosch Universiteit There is only 10 kinds of people in the world: Those who understand binary and those who don't
Question about export node
Hi to all I want to export nodes from one server to another one don't have server to server connection , I have 19 nodes ( on 39 DLT cartridges) my output server is on SDLT cartridges , the amount of data is around 1 Tera. Can anybody give me an estimation of time to export and import those nodes. My two server are version 5.2.3.0 one Aix and second Windows. T.I.A Regards Robert Ouzen E-mail: [EMAIL PROTECTED]
Export Node Retention question
I have looked in the manual and through Mark's monthly FAQ but can not find this specific information. I am looking into the Export node to tape function to retain active and inactive backup files since backupsets only grab active files. Am I correct that a file deleted from the client is considered inactive by the server. And, although it can be restored at the client by selecting inactive files, it will not be picked up by a backupset? I am not concerned with retaining the client settings, only the data. How long can I keep an Export Node to tape for? Where is this set at, gen backupset has a retention setting. How does this differ from a backupset? I know one difference is that backupset can be retained for a specified period. Also, what controls the exported node data for expirations and retention files? Can I use it to restore individual files, all the info that I have read only shows a complete import option. Can it be used for databases, I know backupsets cannot. Server: W2K TSM 5.1.6.3 Client: W2K TSM 5.1.5.15 TDP 2.2.1 Thanks, Mark Bertrand
Export Node Mount Waits
TO *SMers - All, New to this so please bear with. ENVIRONMENT: TSM Server IBM RS6000 R50 2 Procs 1GB ram AIX 4.3.3 MNT_lev 004 TSM Server Version 3.7.2 Library IBM3575 - L12 2 drives - NOT XL No disk pools. All pools sequential to 3575. APPLICATION: Export node every weekend - active files for client node. (WHY? - Company Policy requires weekly full backups of this client to go off site.) This is in addition to daily incremental to the primary storage pool. Exports: 395,963 items 160,980,891,020 bytes. Copies active files from 71 sources tapes (2 storage pools) to 15 output tapes. Starts 0300 Saturday morning and runs until Sunday Afternoon. PROBLEM: Export node waits for retention timeout on source tape before unmounting it and mounting the next source tape. With a 5 minute mount retention this wastes almost 3.5 hours. Even with 1 minute retention wastes way over 1 hour. I have other thing that need to happen over the weekend that also need these drives. QUESTION: Is there a way around this? Is there a fix for it? Is there a better way to get a set of offsite tapes for the active files for the node without doing a selective backup to new storage pool? Please don't mention backup sets. Also, please don't tell me I need more drives. Upgrade request for them has been in the works, for more than 6 months along with upgrade to a L18. These systems are orphans, so to speak. Upper management does not like to spend money on them. Another story. Thanks to all, James D. Poehlman (Denny) AIX / Unix Systems Administrator Senior Technical Specialist Mid-Range Server Technology Team Black and Decker North American Power Tools - Information Systems [EMAIL PROTECTED] Voice 410-716-3039 Cell 410-375-5974
Deleted Client/Export Node
I have a TSM client node (WinNt 4.00, ADSM v3.1.0.3) that has been deinstalled. The node and file spaces have not been deleted from the TSM server (AIX 4.3.3, TSM 4.1.0.0) because they're afraid they might need the data some day. The occupancy for this node includes only backed up data; no archiving. Would "Export Node" be appropriate for moving this node out of the server and tape pool onto tape that I can send to the vault? Thank you, Maria
Re: Restartable export node?
"ADSM: Dist Stor Manager" wrote on 03/21/2006 02:00:35 PM: > I'm migrating a TSM instance from AIX to Linux. I have a node that > has a single filespace with about 5TB of data in it. Looking at the > performance I'm getting I'd guess that the export node is going to > take a week or two to complete - not good. And most likely I'll never > get it to finish. > > So, is there anyway to restart a failed export node, or am I better > of trying to scrounge up 5T of disk and restoring the data and then > re-archiving it on the other end? Or, conversely, is there any way to > export something at a finer granularity than filespace? An export cannot be restarted, and there is no finer granularity available than the filespace. You need to think about non-TSM ways to move the data from one server to another. -- Mark Stapleton ([EMAIL PROTECTED]) MR Backup and Recovery Management 262.790.3190 -- Electronic Privacy Notice. This e-mail, and any attachments, contains information that is, or may be, covered by electronic communications privacy laws, and is also confidential and proprietary in nature. If you are not the intended recipient, please be advised that you are legally prohibited from retaining, using, copying, distributing, or otherwise disclosing this information in any manner. Instead, please reply to the sender that you have received this communication in error, and then immediately delete it. Thank you in advance for your cooperation. ==
export node/server-crash
Today my server crashed when finishing off a successful export-node-operation. Server is 3.7.3.1 running on AIX 4.3.1.0. Back in som early adsm-server there was a problem writing the volume-history-information if the export node-command was too long (more than 256 characters?) This was fixed, and the limit is much higher now. But what is the current limit? The export-command that caused my crash today was 547 characters long. The command-column in the sql-table volhistory is 2001 characters long, and if the internal database-columns also should hold 2001 characters, then I'm on the rong track.. However, the failing operation seems to be the write the volumehistory-record: 001229-074843: ANR1361I Output volume EXP961 closed. 001229-074904: ANR0617I EXPORT NODE: Processing completed with status SUCCESS. 001229-074904: ANR0568W Session 51 for admin TOM (Server) terminated - connection with client 001229-074904: severed. 001229-074904: ANR0891I EXPORT NODE: Copied 3 optionset definitions. 001229-074904: ANR0626I EXPORT NODE: Copied 9 node definitions. 001229-074904: ANR0627I EXPORT NODE: Copied 30 file space 0 archive files, 530952 backup 001229-074904: files, and 0 space managed files. 001229-074904: ANR0630I EXPORT NODE: Copied 77117370 kilobytes of data. 001229-074904: ANR0611I EXPORT NODE started by TOM as process 1 has ended. 001229-074904: ANR4006I EXPORT NODE: Volume 1 written by process is EXP961. 001229-074907: ANR7834S Thread 52 (tid 34bc) terminating on signal 11 (Segmentation violation). 001229-074907: ANR7834S GPR 0: 0x0001, 1: 0x550e5e70, 2: 0xf0049e1c, 3: 0x550e6474 001229-074907: ANR7834S GPR 4: 0x0001, 5: 0x0226, 6: 0x69747461, 7: 0x300169ce 001229-074907: ANR7834S GPR 8: 0xd0299f20, 9: 0x6f0a0005, 10: 0x8000, 11: 0x7f7f7f7f 001229-074907: ANR7834S GPR 12: 0xf0044300, 13: 0x, 14: 0x, 15: 0x 001229-074907: ANR7834S GPR 16: 0x, 17: 0x, 18: 0x, 19: 0x 001229-074907: ANR7834S GPR 20: 0x, 21: 0x, 22: 0x, 23: 0x0001 001229-074907: ANR7834S GPR 24: 0x, 25: 0x, 26: 0x0223, 27: 0x550e5f18 001229-074907: ANR7834S GPR 28: 0x550e6720, 29: 0x0006, 30: 0x0001, 31: 0x69747461 001229-074907: ANR7834S IAR: 0xd0180db4 LR: 0x1007b150 CONTEXT: 0x550e5af0 001229-074907:0xD0180DB4 fwrite 001229-074907:0x1007B150 WriteRecord 001229-074907:0x1007E5FC icWriteVolumeHistory 001229-074907:0x1007E738 icRefreshHistoryFiles 001229-074907:0x104BDCB0 XiExport 001229-074907:0x1000CE00 StartThread 001229-074907:0xD011035C _pthread_body 001229-074907: ANR7833S Server thread 1 terminated in response to program abort. 001229-074907: ANR7833S Server thread 2 terminated in response to program abort. . . . Has anyone seen similar problems?
Re: EXPORT NODE problems
Hello Mathew, Clean your drive 78F94901 (MT3.0.0.2) in the library before proceeding for export node. The volume 030449 contains data from the particular node you want export. As the drive required to be cleaned, not able to read the data for the node from that volume, the export node process is being terminated abnormally. Go through the actlog message I pasted below from your input. 24-04-2002 00:39:43 ANR8336I Verifying label of 3590 volume 030460 in drive 78F94901 (MT3.0.0.2). 24-04-2002 00:40:22 ANR8914I Drive 78F94901 (MT3.0.0.2) in library OS3494P3 needs to be cleaned. 24-04-2002 00:43:56 ANR8337I 3590 volume 030449 mounted in drive 78F94901 (MT3.0.0.2). 24-04-2002 00:43:57 ANR0662E EXPORT NODE: Output error encountered in accessing data storage. 24-04-2002 00:43:57 ANR0569I Object not processed for DB2RSLTSBDC1001_DB2: type=Backup, file space=/SIGNPLUS, object=\NODE\ FULL_BACKUP.2002040305.2. Hope this works. Regards, Mahesh Prasad DCM Data Systems Limited New Delhi, India "Thomas, Matthew" cc: Sent by: "ADSM: Dist Subject: EXPORT NODE problems Stor Manager" <[EMAIL PROTECTED]> 04/24/2002 03:00 PM Please respond to "ADSM: Dist Stor Manager" Folks, I'm still having enormous difficulty trying to EXPORT a DB2 node from a TSM 4.1.0.0 server on WinNT4 but seem to be getting nowhere fast. Client and server are physically on the same hardware. Every attempt to export seems to fail, on this occassion with a (probable) device I/O error: 24-04-2002 00:39:39 ANR8341I End-of-volume reached for 3590 volume 030460. 24-04-2002 00:39:39 ANR1362I Output volume 030460 closed (full). 24-04-2002 00:39:43 ANR8336I Verifying label of 3590 volume 030460 in drive 78F94901 (MT3.0.0.2). 24-04-2002 00:40:22 ANR8914I Drive 78F94901 (MT3.0.0.2) in library OS3494P3 needs to be cleaned. 24-04-2002 00:40:22 ANR8468I 3590 volume 030460 dismounted from drive 78F94901 (MT3.0.0.2) in library OS3494P3. 24-04-2002 00:43:56 ANR8337I 3590 volume 030449 mounted in drive 78F94901 (MT3.0.0.2). 24-04-2002 00:43:57 ANR0662E EXPORT NODE: Output error encountered in accessing data storage. 24-04-2002 00:43:57 ANR0569I Object not processed for DB2RSLTSBDC1001_DB2: type=Backup, file space=/SIGNPLUS, object=\NODE\ FULL_BACKUP.2002040305.2. 24-04-2002 00:44:03 ANR0794E EXPORT NODE: Processing terminated abnormally - error accessing data storage. 24-04-2002 00:44:03 ANR0626I EXPORT NODE: Copied 1 node definitions. 24-04-2002 00:44:03 ANR0568W Session 36 for admin 2031219 (Server) terminated - connection with client severed. 24-04-2002 00:44:03 ANR0627I EXPORT NODE: Copied 1 file space 0 archive files, 4 backup files, and 0 space managed files. 24-04-2002 00:44:03 ANR0656W EXPORT NODE: Skipped 0 archive files, 1 backup files, and 0 space managed files. 24-04-2002 00:44:03 ANR0630I EXPORT NODE: Copied 216964081 kilobytes of data. 24-04-2002 00:44:03 ANR0611I EXPORT NODE started by 2031219 as process 2 has ended. 24-04-2002 00:44:03 ANR0986I Process 2 for EXPORT NODE running in the BACKGROUND processed 6 items for a total of 222,171,219,- 015 bytes with a completion state of FAILURE at 00:44:03. 24-04-2002 00:44:32 ANR8468I 3590 volume 030449 dismounted from drive 78F94901 (MT3.0.0.2) in library OS3494P3. 24-04-2002 00:49:03 ANR8325I Dismounting volume 030469 - 5 minute mount retention expired. 24-04-2002 00:51:25 ANR8468I 3590 volume 030469 dismounted from drive 78F94920 (MT2.0.0.2) in library OS3494P3. There's plenty of available cartridges. Is this just a really ropey bit of code or do we have sudden and universal tape drive problems? Matt * internal.7-430-3213 * external. 020-7922-3213 * fax020-7922-3302 * e-mail[EMAIL PROTECTED] --- This e-mail is intended only for the above addressee. It may contain privileged information. If you are not the addressee you must not copy, distribute, disclose or use any of the information in it. If you have received it in error please delete it and immediately notif
import/export node issue
we are trying to move data from the CX to the Centera via TSM import/export node utility. The performance so far has been only 1GB/hr. What are other ways that we can utilize TSM to migrate data instead of import/export node? We are thinking of setting the current storage pools to read only and perform a storage pool migration from the old storage pool to the new (Centera) storage pool. Any suggestions or ideas to accomplish this? Thanks, Kevin +-- |This was sent by ksmith...@gmail.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +--
Export Node in TSM...
Hi, I have two TSM 5.5.0 server instances with one client each. I have tried to export the client node using export to server directly option. It was successfully but I did not find any file spaces nor client node details in the target server. What's the procedure to retrieve/restore the export node data in the second server. 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
Export node +bad tape
Hi everybody, I have a question, i want to export the node on my new tsm with new TS3200. I have the old tsm (with lto3) the 2 tape driver was now down before finish move data to disk. I have always 9tape with data but if i do the export the export search data on tape but the tapedriver off the export node failed. (normal...) If i delete vol vol_name discarddata=yes in the 9 tape when i do the export the data can't be read on that tape and the export was successfull ? (i know all the data on this tape was lost) Regards, Mickael. +-- |This was sent by bobpatrick808...@yahoo.fr via Backup Central. |Forward SPAM to ab...@backupcentral.com. +--
Export node +bad tape
Hi everybody, Just a little up. Regards, Mickael. +-- |This was sent by bobpatrick808...@yahoo.fr via Backup Central. |Forward SPAM to ab...@backupcentral.com. +--
SV: Export node question
Doesn't matter what order it does? Because you can't work with the data in mean will on the target server, and TSM will send over all Meta Data first between the two servers. /Christian -Ursprungligt meddelande- Från: Robert Ouzen [mailto:rou...@univ.haifa.ac.il] Skickat: den 18 juli 2013 08:11 Till: ADSM-L@VM.MARIST.EDU Ämne: Export node question Hello I have an information question about the process export node (server to server) . When I run the command: export node X filedata=alltoserver=Y exportidentifier=X How the process export the files ? Active data first and then the inactive data ? or how ? I know that I can choose on the parameter filedata= .. the data I want to export but if I choose "ALL" what will be order? Best Regards Robert
Export node bad tape
Hi everybody, I try to export node from old server (5.5 lto3) to new serveur (6.3 lto6) but i have an error with a tape and the export node failed because of that, i have no copypool (because the 5.5 lto3 have one drive since 1month and the second server was new (interest of the export node)). Anyone have an idea to succefully the export node ? Regards, Mickael. +-- |This was sent by bobpatrick808...@yahoo.fr via Backup Central. |Forward SPAM to ab...@backupcentral.com. +--
Export node bad tape
Hi and thanks for reply Rick, The audit volume was in progress, i hope the audit was good. Happy new year to you and your family. Regars, Mickael. +-- |This was sent by bobpatrick808...@yahoo.fr via Backup Central. |Forward SPAM to ab...@backupcentral.com. +--
Export node bad tape
Hi Roger Deschner, thanks for reply That exactly what we try to do export node server1 to server2 but during the export we have an read error on tape and the export node failed. The LTO3 tape driver associated to the tsm server1 5.5 have one drive HS and the new tsm server 6.3 have a tape driver LTO6 associated, that for that we want to export the node to the new server. Happy new year to you and your family. Regards, Mickael. +-- |This was sent by bobpatrick808...@yahoo.fr via Backup Central. |Forward SPAM to ab...@backupcentral.com. +--
Re: SV: Export node (Directly)
Yes...Well the copygroups in the target server for both backups and archives would both have a destination of ALLDISKPOOL. - Original Message - From: "Christian Svensson" <[EMAIL PROTECTED]> To: Sent: Thursday, September 27, 2007 10:39 AM Subject: [ADSM-L] SV: Export node (Directly) Hi Larry, Because of you specify "Filedata=all" means that all your backups will be transferred to ServerB. About if the data will be saved to ALLDISKPOOL is depending on how your policy domain is setup on ServerB where node AIXNODE1 is belonging to. Thanks Christian -Ursprungligt meddelande- Från: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] För Larry Clark Skickat: den 27 september 2007 16:32 Till: ADSM-L@VM.MARIST.EDU Ämne: Export node (Directly) ServerA has a combination of primary storage pools, disk & tape library managed using migration, etc. It also has a segmented disk storage pool environment like AIXBKPOOL, NTBKPOOL, AIXARCHPOOL, NTARCHPOOL ServerB has only a single disk based storage pools such as ALLDISKPOOL. If on ServerA I entered: Export Node aixnode1 File=* Filedata=all Toserver=ServerB Would it place all the backup and archive data for aixnode1 in ALLDISKPOOL on ServerB?
Re: Backupsets and Export Node
(1). If I do generate backupsets for these nodes, can I then delete the filespace data to free up Tape Library space? >>Yes. But before you decide that is a good thing, think about what you would do, if someone ever wanted to retrieve a file off the tape. Deleting the filespace data means all the file entries are purged from the TSM db. You have no "inventory" of the data any more. I believe it is possible, although difficult, to retrieve a single file off a backupset tape. Better try it. 2). If I opt for export node, could I export the nodes, remove all references to the nodes and re-import to the same TSM server if I ever need to? >>Yes. In the case of EXPORT, all the TSM DB entries are removed as well. To access ANY of the data, you have to re-import the tape. >>Other issues. In both cases, where will your tapes be stored? And will you have an offsite copy of this data any more? When you delete the filespace from the primary pool, it is deleted from the copy pool, as well. So you will need to make and track TWO backupsets, or TWO EXPORT tapes. >>Possible options : If you decide on backupsets or export, use SELECT on the BACKUPS table to dump a list of the filenames/backup dates to a flat file. You can use that as a "table of contents" reference so that 6 months from now, if somebody wants to know if there was a particular file on the tape, you can find it. Another way: If your TSM DB size isn't currently a problem, and you just need to regain the storage space : 1) create a new storage pool called "OLDSTUFF". 2) run MOVE NODEDATA to move this client's data from the primary tape pool to the OLDSTUFF pool. 3) use MOVE MEDIA to eject the OLDSTUFF tape(s) from the library and store themt on a shelf. -This retains the inventory of the client in the TSM DB, you can view it any time with dsm -VIRTUALNODE or a SELECT on the TSM DB. -The client's copy pool data is still in the copypool, offsite, managed as usual. -The tapes are tracked in the normal way in the storage pool and copy pool, unlike backup sets and export tapes, which are tracked in volume history. - Your primary pool tapes will have space freed up, and go through recycle, so that you get space back in your library. If you decide to go to backup sets /export tapes later, you can still do that by just checking in the OLDSTUFF tapes. Wanda Prather "I/O, I/O, It's all about I/O" -(me) -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Marco Spagnuolo Sent: Tuesday, March 22, 2005 11:08 AM To: ADSM-L@VM.MARIST.EDU Subject: Backupsets and Export Node TSM Server 5.2.0.0 running on the Windows platform. We have some issues at one of our offices. Here's what I've been able to decipher: There are several Netware,Linux and Windows nodes (12 total) that no longer exist and all hardware has been reused. They require one last "backup/archive" of these nodes that they want kept around for a couple of years. Of course, since these nodes no longer physically exist, my options are limited to backupsets and export node (I believe). Thrown into the mix, the IBM 3583 Tape Library is at capacity and an upgrade is pending but will take some time to get approved. (1). If I do generate backupsets for these nodes, can I then delete the filespace data to free up Tape Library space? (2). If I opt for export node, could I export the nodes, remove all references to the nodes and re-import to the same TSM server if I ever need to? Any other options out there? I've reads through the numerous posts on Backupsets and Export Node but none seem to address my concerns. Thank you Marco
Re: Backupsets and Export Node
Just a quibble or two here... From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Prather, Wanda >>(1). If I do generate backupsets for these nodes, can I then >>delete the filespace data to free up Tape Library space? > >Yes. But before you decide that is a good thing, think >about what you >would do, if someone ever wanted to retrieve a file off the tape. >Deleting the filespace data means all the file entries are purged from >the TSM db. You have no "inventory" of the data any more. >I believe it is possible, although difficult, to retrieve a single file >off a backupset tape. Better try it. Yes, you can retrieve individual files from a backupset, but you have to know both the filename and the directory tree the file resides in to get it back >>2). If I opt for export node, could I export the nodes, remove all >>references to the nodes and re-import to the same TSM server if I ever >>need to? > >Yes. In the case of EXPORT, all the TSM DB entries are removed as >well. To access ANY of the data, you have to re-import the tape. That is incorrect. An export command does not move data, it copies it. All exported data will still exist after the export is complete. -- Mark Stapleton ([EMAIL PROTECTED]) Office 262.521.5627
Re: Backupsets and Export Node
Thanks for the info, Wanda. My comments below..
"Prather, Wanda" <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager"
22/03/2005 02:40 PM
Please respond to "ADSM: Dist Stor Manager"
To: ADSM-L@VM.MARIST.EDU
cc:
Subject: Re: Backupsets and Export Node
(1). If I do generate backupsets for these nodes, can I then delete the
filespace data to free up Tape Library space?
>>Yes. But before you decide that is a good thing, think about what you
would do, if someone ever wanted to retrieve a file off the tape.
Deleting the filespace data means all the file entries are purged from
the TSM db. You have no "inventory" of the data any more.
I believe it is possible, although difficult, to retrieve a single file
off a backupset tape. Better try it.
2). If I opt for export node, could I export the nodes, remove all
references to the nodes and re-import to the same TSM server if I ever
need to?
>>Yes. In the case of EXPORT, all the TSM DB entries are removed as
well. To access ANY of the data, you have to re-import the tape.
>>Other issues.
In both cases, where will your tapes be stored?
And will you have an offsite copy of this data any more? When you
delete the filespace from the primary pool, it is deleted from the copy
pool, as well. So you will need to make and track TWO backupsets, or
TWO EXPORT tapes.
I was thinking of having these tapes stored at our offsite location
regardless
of which method I was going to use. Would I still need 2 copies in each
case?
>>Possible options :
If you decide on backupsets or export, use SELECT on the BACKUPS table
to dump a list of the filenames/backup dates to a flat file. You can
use that as a "table of contents" reference so that 6 months from now,
if somebody wants to know if there was a particular file on the tape,
you can find it.
Another way:
If your TSM DB size isn't currently a problem, and you just need to
regain the storage space :
1) create a new storage pool called "OLDSTUFF".
2) run MOVE NODEDATA to move this client's data from the primary tape
pool to the OLDSTUFF pool.
3) use MOVE MEDIA to eject the OLDSTUFF tape(s) from the library and
store themt on a shelf.
-This retains the inventory of the client in the TSM DB, you can view it
any time with dsm -VIRTUALNODE or a SELECT on the TSM DB.
-The client's copy pool data is still in the copypool, offsite, managed
as usual.
-The tapes are tracked in the normal way in the storage pool and copy
pool, unlike backup sets and export tapes, which are tracked in volume
history.
- Your primary pool tapes will have space freed up, and go through
recycle, so that you get space back in your library.
If you decide to go to backup sets /export tapes later, you can still do
that by just checking in the OLDSTUFF tapes.
Wanda Prather
"I/O, I/O, It's all about I/O" -(me)
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Marco Spagnuolo
Sent: Tuesday, March 22, 2005 11:08 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Backupsets and Export Node
TSM Server 5.2.0.0 running on the Windows platform.
We have some issues at one of our offices. Here's what I've been able
to
decipher:
There are several Netware,Linux and Windows nodes (12 total) that no
longer exist and all hardware has been reused. They require one last
"backup/archive" of these nodes that they want kept around for a couple
of
years. Of course, since these nodes no longer physically exist, my
options are limited to backupsets and export node (I believe). Thrown
into the mix, the IBM 3583 Tape Library is at capacity and an upgrade is
pending but will take some time to get approved.
(1). If I do generate backupsets for these nodes, can I then delete the
filespace data to free up Tape Library space?
(2). If I opt for export node, could I export the nodes, remove all
references to the nodes and re-import to the same TSM server if I ever
need to?
Any other options out there?
I've reads through the numerous posts on Backupsets and Export Node but
none seem to address my concerns.
Thank you
Marco
Re: Backupsets and Export Node
I was thinking of having these tapes stored at our offsite location
regardless
of which method I was going to use. Would I still need 2 copies in each
case?
Yes.
Once you've exported the data and then deleted the filespaces from your
TSM server, your ONLY copy of the data is on that EXPORT (or backupset)
tape.
What if it's your OFFSITE location that burns down/blows up/ or is hit
by a tornado?
What if the courier truck smashes up on the way to the offsite location?
etc.
YOU ARE NEVER SAFE with only 1 copy of the data on magnetic media.
Period.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Marco Spagnuolo
Sent: Tuesday, March 22, 2005 4:02 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Backupsets and Export Node
Thanks for the info, Wanda. My comments below..
"Prather, Wanda" <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager"
22/03/2005 02:40 PM
Please respond to "ADSM: Dist Stor Manager"
To: ADSM-L@VM.MARIST.EDU
cc:
Subject:Re: Backupsets and Export Node
(1). If I do generate backupsets for these nodes, can I then delete the
filespace data to free up Tape Library space?
>>Yes. But before you decide that is a good thing, think about what you
would do, if someone ever wanted to retrieve a file off the tape.
Deleting the filespace data means all the file entries are purged from
the TSM db. You have no "inventory" of the data any more.
I believe it is possible, although difficult, to retrieve a single file
off a backupset tape. Better try it.
2). If I opt for export node, could I export the nodes, remove all
references to the nodes and re-import to the same TSM server if I ever
need to?
>>Yes. In the case of EXPORT, all the TSM DB entries are removed as
well. To access ANY of the data, you have to re-import the tape.
>>Other issues.
In both cases, where will your tapes be stored?
And will you have an offsite copy of this data any more? When you
delete the filespace from the primary pool, it is deleted from the copy
pool, as well. So you will need to make and track TWO backupsets, or
TWO EXPORT tapes.
I was thinking of having these tapes stored at our offsite location
regardless
of which method I was going to use. Would I still need 2 copies in each
case?
>>Possible options :
If you decide on backupsets or export, use SELECT on the BACKUPS table
to dump a list of the filenames/backup dates to a flat file. You can
use that as a "table of contents" reference so that 6 months from now,
if somebody wants to know if there was a particular file on the tape,
you can find it.
Another way:
If your TSM DB size isn't currently a problem, and you just need to
regain the storage space :
1) create a new storage pool called "OLDSTUFF".
2) run MOVE NODEDATA to move this client's data from the primary tape
pool to the OLDSTUFF pool.
3) use MOVE MEDIA to eject the OLDSTUFF tape(s) from the library and
store themt on a shelf.
-This retains the inventory of the client in the TSM DB, you can view it
any time with dsm -VIRTUALNODE or a SELECT on the TSM DB.
-The client's copy pool data is still in the copypool, offsite, managed
as usual.
-The tapes are tracked in the normal way in the storage pool and copy
pool, unlike backup sets and export tapes, which are tracked in volume
history.
- Your primary pool tapes will have space freed up, and go through
recycle, so that you get space back in your library.
If you decide to go to backup sets /export tapes later, you can still do
that by just checking in the OLDSTUFF tapes.
Wanda Prather
"I/O, I/O, It's all about I/O" -(me)
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Marco Spagnuolo
Sent: Tuesday, March 22, 2005 11:08 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Backupsets and Export Node
TSM Server 5.2.0.0 running on the Windows platform.
We have some issues at one of our offices. Here's what I've been able
to
decipher:
There are several Netware,Linux and Windows nodes (12 total) that no
longer exist and all hardware has been reused. They require one last
"backup/archive" of these nodes that they want kept around for a couple
of
years. Of course, since these nodes no longer physically exist, my
options are limited to backupsets and export node (I believe). Thrown
into the mix, the IBM 3583 Tape Library is at capacity and an upgrade is
pending but will take some time to get approved.
(1). If I do generate backupsets for these nodes, can I then delete the
filespace data to free up Tape Library space?
(2). If I opt for export node, could I export the nodes, remove all
references to the nodes and re-import to the same TSM server if I ever
need to?
Any other options out there?
I've reads through the numerous posts on Backupsets and Export Node but
none seem to address my concerns.
Thank you
Marco
Re: Backupsets and Export Node
Thanks Mark, I worded that very badly. What I was trying to convey: Once Marco does the EXPORT (which is a copy) and then deletes the filespaces from the TSM server, there is NO inventory of the data anywhere. You must re-IMPORT at least one entire filespace, in order to find out what is on the export tape, or to restore a file. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Stapleton, Mark Sent: Tuesday, March 22, 2005 3:26 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Backupsets and Export Node Just a quibble or two here... From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Prather, Wanda >>(1). If I do generate backupsets for these nodes, can I then >>delete the filespace data to free up Tape Library space? > >Yes. But before you decide that is a good thing, think >about what you >would do, if someone ever wanted to retrieve a file off the tape. >Deleting the filespace data means all the file entries are purged from >the TSM db. You have no "inventory" of the data any more. >I believe it is possible, although difficult, to retrieve a single file >off a backupset tape. Better try it. Yes, you can retrieve individual files from a backupset, but you have to know both the filename and the directory tree the file resides in to get it back >>2). If I opt for export node, could I export the nodes, remove all >>references to the nodes and re-import to the same TSM server if I ever >>need to? > >Yes. In the case of EXPORT, all the TSM DB entries are removed as >well. To access ANY of the data, you have to re-import the tape. That is incorrect. An export command does not move data, it copies it. All exported data will still exist after the export is complete. -- Mark Stapleton ([EMAIL PROTECTED]) Office 262.521.5627
EXPORT NODE directly to server
Hello Everyone! I was trying to export data from our mainframe server: b390.highmark.com to our new AIX server TSMPROD. I received the following message. Did anyone ever experience this issue? How can I test communication between the 2 servers without trying an export? Thanks! 05/25/2005 09:12:47 ANR2017I Administrator LIDZR8V issued command: EXPORT NODE pgsp007 filedata=archive toserver=tsmprod previewimport=- yes (SESSION: 739) 05/25/2005 09:12:47 ANR0984I Process 40 for EXPORT NODE started in the BACKGROUND at 09:12:47. (SESSION: 739, PROCESS: 40) 05/25/2005 09:12:47 ANR0609I EXPORT NODE started as process 40. (SESSION: 739, PROCESS: 40) 05/25/2005 09:12:47 ANR0609I EXPORT NODE started as process 40. (SESSION: 739, PROCESS: 40) 05/25/2005 09:12:47 ANR0402I Session 740 started for administrator LIDZR8V (Server) (Memory IPC). (SESSION: 739, PROCESS: 40) 05/25/2005 09:12:48 ANRD SMXI(587): ThreadId<1197> Could not open session with TSMPROD. Callchain follows: pkShowCallChain+2E2 <- outDiagf+27E <- smXiSetupServer2ServerExport+832 <- XiExport+220 <- pkThreadHead+4FA (SESSION: 739, PROCESS: 40) 05/25/2005 09:12:48 ANR0781E EXPORT NODE: Process aborted - server sign on failed. (SESSION: 739, PROCESS: 40) 05/25/2005 09:12:48 ANR0985I Process 40 for EXPORT NODE running in the BACKGROUND completed with completion state FAILURE at 09:12:48. (SESSION: 739, PROCESS: 40) TSMPROD: Q STAT output Server Name: TSMPROD Server host name or IP address: 157.154.47.18 Server TCP/IP port number: 1500 Server URL: Crossdefine: On Server Password Set: Yes Server Installation Date/Time: 06/23/04 09:32:54 Server Restart Date/Time: 04/17/05 18:43:00 Authentication: On Password Expiration Period: 9,999 Day(s) Invalid Sign-on Attempt Limit: 0 Minimum Password Length: 0 WEB Admin Authentication Time-out (minutes): 0 Registration: Closed Subfile Backup: No Availability: Enabled Accounting: Off Activity Log Retention Period: 15 Day(s) Activity Summary Retention Period: 30 Day(s) License Audit Period: 15 Day(s) Last License Audit: 05/16/05 18:45:53 Server License Compliance: Valid Central Scheduler: Active Maximum Sessions: 300 Maximum Scheduled Sessions: 270 Event Record Retention Period: 15 Day(s) Client Action Duration: 5 Day(s) Schedule Randomization Percentage: 25 Query Schedule Period: 6 Hour(s) Maximum Command Retries: Client Retry Period: Client Scheduling Modes: Any Log Mode: Normal Database Backup Trigger: Not Defined BufPoolSize: 419,432 K Active Receivers: CONSOLE ACTLOG FILE Configuration manager?: Off Refresh interval: 60 Last refresh date/time: Context Messaging: Off Server-free Status: Not Supported Server-free Batch Size: Table of Contents (TOC) Load Retention: 120 Minute(s) Machine Globally Unique ID: 3a.c7.e8.06.63.cc.11.d8.91.3 d.08.6 3.c0.a8.0b.03 Archive Retention Protection: Off TSMPROD defintion on our mainframe b390.highmark.com server Server Name: TSMPROD Comm. Method: TCPIP High-level Address: tsmprod Low-level Address: 1500 Description: TSM Production Server Allow Replacement: No Node Name: Last Access Date/Time: 05/25/2005 09:12:48 Days Since Last Access: <1 Locked?: No Compression: No Archive Delete Allowed?: (?) URL: http://tsmprod:1580 Registration Date/Time
Re: Export node with TDP's ?
Archive the data, rather than backing it up. You can specify an ARCHMC when you do so. -- Mark Stapleton ([EMAIL PROTECTED]) IBM Certified Advanced Deployment Professional Tivoli Storage Management Solutions 2005 IBM Certified Advanced Technical Expert (CATE) AIX Office 262.521.5627 >-Original Message- >From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On >Behalf Of Pretorius Louw <[EMAIL PROTECTED]> >Sent: Wednesday, June 29, 2005 7:10 AM >To: ADSM-L@VM.MARIST.EDU >Subject: Export node with TDP's ? > >1. Does anyone know if export node works with the Exchange >TDP? (Win2k3 >with Exchange2k3) > >2. Instead of running multiple Nodenames on our Cluster servers we are >looking for ways of doing monthly backups and keep them for many years >while still keeping our weekly backups for only 10 versions. >Unfortunately it seems one cannot specify a ManagementClass on the >commandline so we cannot use a different MC for this. Any other >thoughts? > >Regards > >Louw Pretorius > >___ > >Informasie Tegnologie > >Stellenbosch Universiteit > > > >There is only 10 kinds of people in the world: Those who understand >binary and those who don't > > >
Re: Export node with TDP's ?
Del has suggested in the past that instead of using different nodenames for the daily and monthly backups, to run the monthly backups using the COPY type of backup. "TDPEXCC BACKUP * COPY ..." and then in your dsm.opt file use an include for the COPY objects to a management class with the correct retentions. You would have a script file for your daily backups, and then one for your monthly backups...or you could put logic in the script to decide when to run the FULL and when to run the COPY. Also, ARCHIVE is not a function of the TDP agent. Bill Boyer "Some days you're the bug, some days you're the windshield" - ?? -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Stapleton, Mark Sent: Wednesday, June 29, 2005 8:16 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: Export node with TDP's ? Archive the data, rather than backing it up. You can specify an ARCHMC when you do so. -- Mark Stapleton ([EMAIL PROTECTED]) IBM Certified Advanced Deployment Professional Tivoli Storage Management Solutions 2005 IBM Certified Advanced Technical Expert (CATE) AIX Office 262.521.5627 >-Original Message- >From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf >Of Pretorius Louw <[EMAIL PROTECTED]> >Sent: Wednesday, June 29, 2005 7:10 AM >To: ADSM-L@VM.MARIST.EDU >Subject: Export node with TDP's ? > >1. Does anyone know if export node works with the Exchange TDP? >(Win2k3 with Exchange2k3) > >2. Instead of running multiple Nodenames on our Cluster servers we are >looking for ways of doing monthly backups and keep them for many years >while still keeping our weekly backups for only 10 versions. >Unfortunately it seems one cannot specify a ManagementClass on the >commandline so we cannot use a different MC for this. Any other >thoughts? > >Regards > >Louw Pretorius > >___ > >Informasie Tegnologie > >Stellenbosch Universiteit > > > >There is only 10 kinds of people in the world: Those who understand >binary and those who don't > > >
Re: Export node with TDP's ?
Pretorius, > 1. Does anyone know if export node works with the Exchange TDP? (Win2k3 > with Exchange2k3) This should work, make sure you export all filespaces for the node. Each TSM filespace contains data for one and only one Exchange storage group. > 2. Instead of running multiple Nodenames on our Cluster servers we are > looking for ways of doing monthly backups and keep them for many years > while still keeping our weekly backups for only 10 versions. > Unfortunately it seems one cannot specify a ManagementClass on the > commandline so we cannot use a different MC for this. Any other > thoughts? If this is for Data Protection for Exchange, this can be done by using a "COPY"-type backup and binding the "COPY"-type backups to a different management class using the INCLUDE statement. See the User's Guide for more information on that. If this is for "file"-level backups... did you look into the archive function to accomplish long term retention?
Re: Question about export node
One important factor will be the distribution of the data across the cartridges. If it is very intermixed the export time will be significantly longer than it would be if the data were collocated, for example. Matt. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Robert Ouzen Sent: Thursday, August 19, 2004 9:48 AM To: [EMAIL PROTECTED] Subject: Question about export node Hi to all I want to export nodes from one server to another one don't have server to server connection , I have 19 nodes ( on 39 DLT cartridges) my output server is on SDLT cartridges , the amount of data is around 1 Tera. Can anybody give me an estimation of time to export and import those nodes. My two server are version 5.2.3.0 one Aix and second Windows. T.I.A Regards Robert Ouzen E-mail: [EMAIL PROTECTED] ___ Disclaimer Notice __ This message and any attachments are confidential and should only be read by those to whom they are addressed. If you are not the intended recipient, please contact us, delete the message from your computer and destroy any copies. Any distribution or copying without our prior permission is prohibited. Internet communications are not always secure and therefore Powergen Retail Limited does not accept legal responsibility for this message. The recipient is responsible for verifying its authenticity before acting on the contents. Any views or opinions presented are solely those of the author and do not necessarily represent those of Powergen Retail Limited. Registered addresses: Powergen Retail Limited, Westwood Way, Westwood Business Park, Coventry, CV4 8LG. Registered in England and Wales No: 3407430 Telephone +44 (0) 2476 42 4000 Fax +44 (0) 2476 42 5432
Re: Export Node Retention question
that is the beauty of export tapes as long as the tape is OK and as long as you have a server version that can read the export tape (probably created on an earlier version) and all the other things that go along with media type and devices to read it you can keep it forever! I keep sample export tape sets so when I upgrade TSM I'll be able to see if I can still import what I had exported earlier. I went up to 5.2 and could still import as far back as 3.7 (or was it 4.1) ??? anyway, I got paranoid and called back in all my long term data and imported it and re-exported it to new media on the new 5.2 server. Dwight E. Cook Systems Management Integration Professional, Advanced Integrated Storage Management TSM Administration (918) 925-8045 Mark Bertrand <[EMAIL PROTECTED] UNWIRED.COM> To Sent by: "ADSM: [EMAIL PROTECTED] Dist Stor cc Manager" <[EMAIL PROTECTED] Subject .EDU> Export Node Retention question 09/02/2004 11:13 AM Please respond to "ADSM: Dist Stor Manager" I have looked in the manual and through Mark's monthly FAQ but can not find this specific information. I am looking into the Export node to tape function to retain active and inactive backup files since backupsets only grab active files. Am I correct that a file deleted from the client is considered inactive by the server. And, although it can be restored at the client by selecting inactive files, it will not be picked up by a backupset? I am not concerned with retaining the client settings, only the data. How long can I keep an Export Node to tape for? Where is this set at, gen backupset has a retention setting. How does this differ from a backupset? I know one difference is that backupset can be retained for a specified period. Also, what controls the exported node data for expirations and retention files? Can I use it to restore individual files, all the info that I have read only shows a complete import option. Can it be used for databases, I know backupsets cannot. Server: W2K TSM 5.1.6.3 Client: W2K TSM 5.1.5.15 TDP 2.2.1 Thanks, Mark Bertrand <><><>
Re: Export Node Retention question
More stuff: When you do an import, you import the whole node, or at least a whole filespace. Can't get any more granular than filespace. You are essentially reloading everything back into the TSM server DB and storage pools. Then you start the regular B/A client and restore whatever files you want to the client. So it's a 2-step process with IMPORT, where with a BACKUPSET you can restore directly from the backupset tape. Things that are on EITHER an EXPORT or BACKUPSET tape are not governed by expiration rules. Whatever is on the tape, stays on the tape. When you IMPORT a filespace, the data is back in the TSM DB and the inactive file copies (if you included the inactive data in the export) are again governed by expiration rules. Look at HELP IMPORT NODE, the DATES= parm. It controls whether the imported inactive files start to expire immediately or not. EXPORT/IMPORT works on filespaces, so can be used for application data bases backed up by TSM for Oracle, SQL, etc. Wanda Prather "I/O, I/O, It's all about I/O" -(me) -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Dwight Cook Sent: Thursday, September 02, 2004 2:04 PM To: [EMAIL PROTECTED] Subject: Re: Export Node Retention question that is the beauty of export tapes as long as the tape is OK and as long as you have a server version that can read the export tape (probably created on an earlier version) and all the other things that go along with media type and devices to read it you can keep it forever! I keep sample export tape sets so when I upgrade TSM I'll be able to see if I can still import what I had exported earlier. I went up to 5.2 and could still import as far back as 3.7 (or was it 4.1) ??? anyway, I got paranoid and called back in all my long term data and imported it and re-exported it to new media on the new 5.2 server. Dwight E. Cook Systems Management Integration Professional, Advanced Integrated Storage Management TSM Administration (918) 925-8045 Mark Bertrand <[EMAIL PROTECTED] UNWIRED.COM> To Sent by: "ADSM: [EMAIL PROTECTED] Dist Stor cc Manager" <[EMAIL PROTECTED] Subject .EDU> Export Node Retention question 09/02/2004 11:13 AM Please respond to "ADSM: Dist Stor Manager" I have looked in the manual and through Mark's monthly FAQ but can not find this specific information. I am looking into the Export node to tape function to retain active and inactive backup files since backupsets only grab active files. Am I correct that a file deleted from the client is considered inactive by the server. And, although it can be restored at the client by selecting inactive files, it will not be picked up by a backupset? I am not concerned with retaining the client settings, only the data. How long can I keep an Export Node to tape for? Where is this set at, gen backupset has a retention setting. How does this differ from a backupset? I know one difference is that backupset can be retained for a specified period. Also, what controls the exported node data for expirations and retention files? Can I use it to restore individual files, all the info that I have read only shows a complete import option. Can it be used for databases, I know backupsets cannot. Server: W2K TSM 5.1.6.3 Client: W2K TSM 5.1.5.15 TDP 2.2.1 Thanks, Mark Bertrand
Re: Export Node Retention question
Great thanks Dwight, how about the databases? How does the exports work with live databases. Databases that I am now backing up with TDP? Thanks, Mark Bertrand -Original Message- From: Dwight Cook [mailto:[EMAIL PROTECTED] Sent: Thursday, September 02, 2004 1:04 PM To: [EMAIL PROTECTED] Subject: Re: Export Node Retention question that is the beauty of export tapes as long as the tape is OK and as long as you have a server version that can read the export tape (probably created on an earlier version) and all the other things that go along with media type and devices to read it you can keep it forever! I keep sample export tape sets so when I upgrade TSM I'll be able to see if I can still import what I had exported earlier. I went up to 5.2 and could still import as far back as 3.7 (or was it 4.1) ??? anyway, I got paranoid and called back in all my long term data and imported it and re-exported it to new media on the new 5.2 server. Dwight E. Cook Systems Management Integration Professional, Advanced Integrated Storage Management TSM Administration (918) 925-8045 Mark Bertrand <[EMAIL PROTECTED] UNWIRED.COM> To Sent by: "ADSM: [EMAIL PROTECTED] Dist Stor cc Manager" <[EMAIL PROTECTED] Subject .EDU> Export Node Retention question 09/02/2004 11:13 AM Please respond to "ADSM: Dist Stor Manager" I have looked in the manual and through Mark's monthly FAQ but can not find this specific information. I am looking into the Export node to tape function to retain active and inactive backup files since backupsets only grab active files. Am I correct that a file deleted from the client is considered inactive by the server. And, although it can be restored at the client by selecting inactive files, it will not be picked up by a backupset? I am not concerned with retaining the client settings, only the data. How long can I keep an Export Node to tape for? Where is this set at, gen backupset has a retention setting. How does this differ from a backupset? I know one difference is that backupset can be retained for a specified period. Also, what controls the exported node data for expirations and retention files? Can I use it to restore individual files, all the info that I have read only shows a complete import option. Can it be used for databases, I know backupsets cannot. Server: W2K TSM 5.1.6.3 Client: W2K TSM 5.1.5.15 TDP 2.2.1 Thanks, Mark Bertrand
Re: Export Node Retention question
Thanks Wanda, I am going to start using this feature immediately. Mark -Original Message- From: Prather, Wanda [mailto:[EMAIL PROTECTED] Sent: Thursday, September 02, 2004 1:27 PM To: [EMAIL PROTECTED] Subject: [spam] Re: Export Node Retention question More stuff: When you do an import, you import the whole node, or at least a whole filespace. Can't get any more granular than filespace. You are essentially reloading everything back into the TSM server DB and storage pools. Then you start the regular B/A client and restore whatever files you want to the client. So it's a 2-step process with IMPORT, where with a BACKUPSET you can restore directly from the backupset tape. Things that are on EITHER an EXPORT or BACKUPSET tape are not governed by expiration rules. Whatever is on the tape, stays on the tape. When you IMPORT a filespace, the data is back in the TSM DB and the inactive file copies (if you included the inactive data in the export) are again governed by expiration rules. Look at HELP IMPORT NODE, the DATES= parm. It controls whether the imported inactive files start to expire immediately or not. EXPORT/IMPORT works on filespaces, so can be used for application data bases backed up by TSM for Oracle, SQL, etc. Wanda Prather "I/O, I/O, It's all about I/O" -(me) -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Dwight Cook Sent: Thursday, September 02, 2004 2:04 PM To: [EMAIL PROTECTED] Subject: Re: Export Node Retention question that is the beauty of export tapes as long as the tape is OK and as long as you have a server version that can read the export tape (probably created on an earlier version) and all the other things that go along with media type and devices to read it you can keep it forever! I keep sample export tape sets so when I upgrade TSM I'll be able to see if I can still import what I had exported earlier. I went up to 5.2 and could still import as far back as 3.7 (or was it 4.1) ??? anyway, I got paranoid and called back in all my long term data and imported it and re-exported it to new media on the new 5.2 server. Dwight E. Cook Systems Management Integration Professional, Advanced Integrated Storage Management TSM Administration (918) 925-8045 Mark Bertrand <[EMAIL PROTECTED] UNWIRED.COM> To Sent by: "ADSM: [EMAIL PROTECTED] Dist Stor cc Manager" <[EMAIL PROTECTED] Subject .EDU> Export Node Retention question 09/02/2004 11:13 AM Please respond to "ADSM: Dist Stor Manager" I have looked in the manual and through Mark's monthly FAQ but can not find this specific information. I am looking into the Export node to tape function to retain active and inactive backup files since backupsets only grab active files. Am I correct that a file deleted from the client is considered inactive by the server. And, although it can be restored at the client by selecting inactive files, it will not be picked up by a backupset? I am not concerned with retaining the client settings, only the data. How long can I keep an Export Node to tape for? Where is this set at, gen backupset has a retention setting. How does this differ from a backupset? I know one difference is that backupset can be retained for a specified period. Also, what controls the exported node data for expirations and retention files? Can I use it to restore individual files, all the info that I have read only shows a complete import option. Can it be used for databases, I know backupsets cannot. Server: W2K TSM 5.1.6.3 Client: W2K TSM 5.1.5.15 TDP 2.2.1 Thanks, Mark Bertrand
Re: Export Node Retention question
Mark, One caveat about using EXPORT for TDP data: I don't remember the beginning of this thread, if you said WHY you are trying to do export/import of TDP data, or which TDP it is. Your need to be conscious of how the TDP works, and where you are going with the data, to decide whether this is going to work for you. For example, The TDP for Oracle works through the Oracle RMAN catalog. Other TDP's work other ways. You have to take into account what is expected when you do the restore. For example, if you used EXPORT to take the TSM TDP filespace to a DR site, and IMPORTed the data back to your TSM server at the DR site, that would not be sufficient to enable you to restore. You would also need to have a valid RMAN catalog for the TDP to connect to. Et. cetera. Plan, plan, plan. Test, test, test. Wanda Prather "I/O, I/O, It's all about I/O" -(me) . -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Mark Bertrand Sent: Thursday, September 02, 2004 3:10 PM To: [EMAIL PROTECTED] Subject: Re: Export Node Retention question Thanks Wanda, I am going to start using this feature immediately. Mark -Original Message- From: Prather, Wanda [mailto:[EMAIL PROTECTED] Sent: Thursday, September 02, 2004 1:27 PM To: [EMAIL PROTECTED] Subject: [spam] Re: Export Node Retention question More stuff: When you do an import, you import the whole node, or at least a whole filespace. Can't get any more granular than filespace. You are essentially reloading everything back into the TSM server DB and storage pools. Then you start the regular B/A client and restore whatever files you want to the client. So it's a 2-step process with IMPORT, where with a BACKUPSET you can restore directly from the backupset tape. Things that are on EITHER an EXPORT or BACKUPSET tape are not governed by expiration rules. Whatever is on the tape, stays on the tape. When you IMPORT a filespace, the data is back in the TSM DB and the inactive file copies (if you included the inactive data in the export) are again governed by expiration rules. Look at HELP IMPORT NODE, the DATES= parm. It controls whether the imported inactive files start to expire immediately or not. EXPORT/IMPORT works on filespaces, so can be used for application data bases backed up by TSM for Oracle, SQL, etc. Wanda Prather "I/O, I/O, It's all about I/O" -(me) -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Dwight Cook Sent: Thursday, September 02, 2004 2:04 PM To: [EMAIL PROTECTED] Subject: Re: Export Node Retention question that is the beauty of export tapes as long as the tape is OK and as long as you have a server version that can read the export tape (probably created on an earlier version) and all the other things that go along with media type and devices to read it you can keep it forever! I keep sample export tape sets so when I upgrade TSM I'll be able to see if I can still import what I had exported earlier. I went up to 5.2 and could still import as far back as 3.7 (or was it 4.1) ??? anyway, I got paranoid and called back in all my long term data and imported it and re-exported it to new media on the new 5.2 server. Dwight E. Cook Systems Management Integration Professional, Advanced Integrated Storage Management TSM Administration (918) 925-8045 Mark Bertrand <[EMAIL PROTECTED] UNWIRED.COM> To Sent by: "ADSM: [EMAIL PROTECTED] Dist Stor cc Manager" <[EMAIL PROTECTED] Subject .EDU> Export Node Retention question 09/02/2004 11:13 AM Please respond to "ADSM: Dist Stor Manager" I have looked in the manual and through Mark's monthly FAQ but can not find this specific information. I am looking into the Export node to tape function to retain active and inactive backup files since backupsets only grab active files. Am I correct that a file deleted from the client is considered inactive by the server. And, although it can be restored at the client by selecting inactive files, it will not be picked up by a backupset? I am not concerned with retaining the client settings, only the data. How long can I keep an Export Node to tape for? Where is this set at, gen backupset has a retention setting. How does this differ from a backupset? I know one difference is that backupset can be retained for a specified period. Also, what controls the exported node data for expirations and retention files? Can I use it to restore individual files, all the info that I have read only shows a complete impo
Re: Export Node Mount Waits
You can set mount retention to 0. I don't know of any reason not to, in a robotic library. -Original Message- From: Poehlman, James [mailto:[EMAIL PROTECTED]] Sent: Monday, April 02, 2001 12:52 PM To: [EMAIL PROTECTED] Subject: Export Node Mount Waits TO *SMers - All, New to this so please bear with. ENVIRONMENT: TSM Server IBM RS6000 R50 2 Procs 1GB ram AIX 4.3.3 MNT_lev 004 TSM Server Version 3.7.2 Library IBM3575 - L12 2 drives - NOT XL No disk pools. All pools sequential to 3575. APPLICATION: Export node every weekend - active files for client node. (WHY? - Company Policy requires weekly full backups of this client to go off site.) This is in addition to daily incremental to the primary storage pool. Exports: 395,963 items 160,980,891,020 bytes. Copies active files from 71 sources tapes (2 storage pools) to 15 output tapes. Starts 0300 Saturday morning and runs until Sunday Afternoon. PROBLEM: Export node waits for retention timeout on source tape before unmounting it and mounting the next source tape. With a 5 minute mount retention this wastes almost 3.5 hours. Even with 1 minute retention wastes way over 1 hour. I have other thing that need to happen over the weekend that also need these drives. QUESTION: Is there a way around this? Is there a fix for it? Is there a better way to get a set of offsite tapes for the active files for the node without doing a selective backup to new storage pool? Please don't mention backup sets. Also, please don't tell me I need more drives. Upgrade request for them has been in the works, for more than 6 months along with upgrade to a L18. These systems are orphans, so to speak. Upper management does not like to spend money on them. Another story. Thanks to all, James D. Poehlman (Denny) AIX / Unix Systems Administrator Senior Technical Specialist Mid-Range Server Technology Team Black and Decker North American Power Tools - Information Systems [EMAIL PROTECTED] Voice 410-716-3039 Cell 410-375-5974
Re: Export Node Mount Waits
James: Why don't you run a selective backup of this client to a specific tapeppool every weekend. Or run an archive every weekend to a specific tapepool where the media will be easily managed. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Poehlman, James Sent: Monday, April 02, 2001 12:52 PM To: [EMAIL PROTECTED] Subject: Export Node Mount Waits TO *SMers - All, New to this so please bear with. ENVIRONMENT: TSM Server IBM RS6000 R50 2 Procs 1GB ram AIX 4.3.3 MNT_lev 004 TSM Server Version 3.7.2 Library IBM3575 - L12 2 drives - NOT XL No disk pools. All pools sequential to 3575. APPLICATION: Export node every weekend - active files for client node. (WHY? - Company Policy requires weekly full backups of this client to go off site.) This is in addition to daily incremental to the primary storage pool. Exports: 395,963 items 160,980,891,020 bytes. Copies active files from 71 sources tapes (2 storage pools) to 15 output tapes. Starts 0300 Saturday morning and runs until Sunday Afternoon. PROBLEM: Export node waits for retention timeout on source tape before unmounting it and mounting the next source tape. With a 5 minute mount retention this wastes almost 3.5 hours. Even with 1 minute retention wastes way over 1 hour. I have other thing that need to happen over the weekend that also need these drives. QUESTION: Is there a way around this? Is there a fix for it? Is there a better way to get a set of offsite tapes for the active files for the node without doing a selective backup to new storage pool? Please don't mention backup sets. Also, please don't tell me I need more drives. Upgrade request for them has been in the works, for more than 6 months along with upgrade to a L18. These systems are orphans, so to speak. Upper management does not like to spend money on them. Another story. Thanks to all, James D. Poehlman (Denny) AIX / Unix Systems Administrator Senior Technical Specialist Mid-Range Server Technology Team Black and Decker North American Power Tools - Information Systems [EMAIL PROTECTED] Voice 410-716-3039 Cell 410-375-5974
Re: Export Node Mount Waits
Hi James, If I understand well, every week, you backup 160 GB of data to new tapes that are taken offsite ? Have you tried to use backup STG. This command only put offsite the new files. Say you have 1% of new files, you only have to offsite some GB and not some hundred GBs. You do not need to purchase DRM to do this, there are plenty of scripts that can helps you. On your backup site, do you have a TSM server w/ a 3575 lib ? If yes, that's is the solution, you only move "week" data. Else, sometime, you will need to reclaim your offsite tapes and regenerates a full set of unfragmented-copy-tapes. I did this for a 8 TB site and only a few tapes (and DLT) are moved offsite every day. As mentionned in the list, set the retention to 0. or scan IDLE drives an manually dismount tapes from a admin sched. Hope this helps Rv - Original Message - From: "Poehlman, James" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, April 02, 2001 6:51 PM Subject: Export Node Mount Waits > TO *SMers - All, > New to this so please bear with. > > ENVIRONMENT: > TSM Server IBM RS6000 R50 2 Procs 1GB ram > AIX 4.3.3 MNT_lev 004 > TSM Server Version 3.7.2 > Library IBM3575 - L12 2 drives - NOT XL > No disk pools. > All pools sequential to 3575. > > APPLICATION: > Export node every weekend - active files for client node. > (WHY? - Company Policy requires weekly full backups of this > client to go off site.) > This is in addition to daily incremental to the primary storage pool. > Exports: > 395,963 items > 160,980,891,020 bytes. > Copies active files from 71 sources tapes (2 storage pools) to 15 output > tapes. > Starts 0300 Saturday morning and runs until Sunday Afternoon. > > PROBLEM: > Export node waits for retention timeout on source tape before > unmounting it and mounting the next source tape. With a 5 minute > mount retention this wastes almost 3.5 hours. Even with 1 minute > retention wastes way over 1 hour. I have other thing that need to > happen over the weekend that also need these drives. > > QUESTION: > Is there a way around this? Is there a fix for it? > Is there a better way to get a set of offsite tapes for > the active files for the node without doing a selective > backup to new storage pool? > Please don't mention backup sets. Also, please don't tell > me I need more drives. Upgrade request for them has been in the > works, for more than 6 months along with upgrade to a L18. > These systems are orphans, so to speak. Upper management does > not like to spend money on them. Another story. > > Thanks to all, > > James D. Poehlman (Denny) > AIX / Unix Systems Administrator > Senior Technical Specialist > Mid-Range Server Technology Team > Black and Decker > North American Power Tools - Information Systems > [EMAIL PROTECTED] > Voice 410-716-3039 > Cell 410-375-5974 >
Re: Deleted Client/Export Node
Yes, I think you can do it this way, the other way is to generate backupset to tape or CD for this node. Hi Tom -Original Message- From: Maria Ragan [mailto:[EMAIL PROTECTED]] Sent: Tuesday, August 07, 2001 8:14 PM To: [EMAIL PROTECTED] Subject: Deleted Client/Export Node I have a TSM client node (WinNt 4.00, ADSM v3.1.0.3) that has been deinstalled. The node and file spaces have not been deleted from the TSM server (AIX 4.3.3, TSM 4.1.0.0) because they're afraid they might need the data some day. The occupancy for this node includes only backed up data; no archiving. Would "Export Node" be appropriate for moving this node out of the server and tape pool onto tape that I can send to the vault? Thank you, Maria --- Odchozí zpráva neobsahuje viry. Zkontrolováno antivirovým systémem AVG (http://www.grisoft.cz). Verze: 6.0.268 / Virová báze: 140 - datum vydání: 7.8.2001
export node toserver, extremely slow
Hi! Both source ant target-servers are 5.3.2.0, running on the same P650 machine, AIX 5.3.0.0 I only get around 35-50 KB/s, and that is useless... When exporting to tape from the target-server, the export runs at 20-30 MB/s, and about the same when importing from the tape to the source-server. I did a lot of noe-movement between the servers a couple of years ago, and this was probably at TSM-level 5.2.2.5. Has anyone else seen this behavior, any ideas what to look for that could cause the export toserver to be this slow ? Tom
Export Node and OS Migrations
Hi *, We are currently in the middle of migrating our Novell file servers to Windows 2003. We will be doing a copy of all our Novell file server data to our Windows 2003 machines and then eventually deleting the Novell machine in the future. In the meantime, we will be running low on slots in our library because we will for a short time have the duplicate copies before we cut off our Novell servers.. If I do an export of our Novell data to get the data out of TSM and the library, it will free up our onsite slot issue, but what will happen to the reclamation for that server for my offsite tapes ? Rich
Re: Export Node Mount Waits
On Mon, 2 Apr 2001, Prather, Wanda wrote: > You can set mount retention to 0. > I don't know of any reason not to, in a robotic library. I know of a reason. A bad TSM version (3.7.x) In observing my 3.7.x system with mountret=0, I have found during TAPEPOOL migration WITH Collocation that multiple clusters going to the same tape will cause the tape to be dismounted and then remounted. This also occurs with migration from diskpool to tapepool. In my opinion its a bug or B.A.D. (broken as designed) It wasn't this way with 3.1.2.20 !!! I am told its fixed back to the old behaviour in 3.7.4 + beyond. I have only found it working in 4.3.x Sigh. ... joe.f.
EXPORT NODE with a CLOPTSET
I'm having some surprising things happen when doing an EXPORT NODE directly to another server, on a node that has a CLOPTSET defined. Both servers are TSM 5.5 on AIX. I exported a node from one server to another, which has a cloptset defined, and the cloptset exists on both source and target servers. I exported with REPLACEDEFS=NO (the default), yet QUERY PROCESS shows: ANR1358I Export Identifier: ROGER1 ANR0648I Have copied the following: 1 Optionsets 1 Nodes 3 Filespaces 18402 Backup Files 5562788 Bytes (0 errors have been detected) ...so it appears that it copied the cloptset, replacing the existing one of the same name that was already on the target server. I hope they were identical before the export, because it appears they are now! How can I guard against this? It appears that REPLACEDEFS=NO is ineffective for cloptsets. Roger Deschner University of Illinois at Chicago rog...@uic.edu ==I have not lost my mind -- it is backed up on tape somewhere.=
export node writing to spacemgpool
I am seeing surprising behavior from a process exporting a node directly to another server. Most of the exported files are being written to an HSM disk pool and HSM tape pool, but some to the primary disk and tape poosl. All the filespaces being exported are dong this. I see this by running 'q occ ' on the target server. The same command on the source server does not show any files in an HSM pool. The node being exported is running Windows 5.0.2 and TSM version 5.5.2.6. It is not running HSM, to my knowledge. The source TSM server is at Linux version 5.5.2.1. The target TSM server is at Linux version 5.5.4.1. What circumstances could be causing this? I am baffled. The primary disk pool is not hitting HighMig, and it wouldn't migrate to SPACEMGPOOL if it were. Thank you, Keith Arbogast
Re: Export Node in TSM...
What exactly was the 'export node' command you issued to export the definitions and data between servers? And what exactly did the TSM Server activity log report regarding the completion status and statistics of that export process? //David Mc London, UK On 3 Jun 2010, at 08:47, M KIRAN KUMAR wrote: Hi, I have two TSM 5.5.0 server instances with one client each. I have tried to export the client node using export to server directly option. It was successfully but I did not find any file spaces nor client node details in the target server. What's the procedure to retrieve/restore the export node data in the second server. 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
Re: Export Node in TSM...
Export node node1 filedata=all toserver=2(server2 name) I am testing in a test environment before actually implementing in production servers. NR0986I Process 12 for EXPORT NODE running in the AMBACKGROUND processed 5 items for a total of 1,914,957 bytes with a completion state of SUCCESS at 11:25:46 AM. Regards, Kiran. -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of ADSM-L Sent: Thursday, June 03, 2010 1:23 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Export Node in TSM... What exactly was the 'export node' command you issued to export the definitions and data between servers? And what exactly did the TSM Server activity log report regarding the completion status and statistics of that export process? //David Mc London, UK On 3 Jun 2010, at 08:47, M KIRAN KUMAR wrote: > Hi, > > > > I have two TSM 5.5.0 server instances with one client each. I have > tried to > export the client node using export to server directly option. > > > > It was successfully but I did not find any file spaces nor client node > details in the target server. > > > > What's the procedure to retrieve/restore the export node data in the > second > server. > > > > 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 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
Re: Export Node in TSM...
On Jun 3, 2010, at 4:43 AM, M KIRAN KUMAR wrote: > Export node node1 filedata=all toserver=2(server2 name) > > I am testing in a test environment before actually implementing in > production servers. > > NR0986I Process 12 for EXPORT NODE running in the > AMBACKGROUND processed 5 items for a total of 1,914,957 > > bytes with a completion state of SUCCESS at 11:25:46 > AM. That's one of the messages, in the set of ANR0626I, ANR0627I, ANR0630I, ANR0986I. Review the others for more perspective, and whether that test environment had any real data to transfer. Perform a Query OCCupancy on the node to see if it has substantive data. Prior to doing the actual export, it is good practice to perform the export with Preview=Yes and review the resulting ANR messages to see what will result when the export is run. Richard Sims
Re: Export Node in TSM...
Yes I performed test archival and executed export node. Can u tell me if we export a node directly to a server will that exported node be visible in the client node list with file spaces on the target server for data retrivals? Regards, Kiran. -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Richard Sims Sent: Thursday, June 03, 2010 4:49 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Export Node in TSM... On Jun 3, 2010, at 4:43 AM, M KIRAN KUMAR wrote: > Export node node1 filedata=all toserver=2(server2 name) > > I am testing in a test environment before actually implementing in > production servers. > > NR0986I Process 12 for EXPORT NODE running in the > AMBACKGROUND processed 5 items for a total of 1,914,957 > > bytes with a completion state of SUCCESS at 11:25:46 > AM. That's one of the messages, in the set of ANR0626I, ANR0627I, ANR0630I, ANR0986I. Review the others for more perspective, and whether that test environment had any real data to transfer. Perform a Query OCCupancy on the node to see if it has substantive data. Prior to doing the actual export, it is good practice to perform the export with Preview=Yes and review the resulting ANR messages to see what will result when the export is run. Richard Sims 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
Re: Export Node in TSM...
On Jun 3, 2010, at 10:59 PM, M KIRAN KUMAR wrote: > Can u tell me if we export a node directly to a server will that exported > node be visible in the client node list with file spaces on the target > server for data retrivals? Providing that the export-import was successful, the target server should then contain all the information which the source server transferred. Check the Activity Log for evidence of what actually occurred. You need to be mindful of the possibility of pre-existing nodes and filespaces on the target server which have the same names as in the data being imported: the Admin Guide manual describes the handling of that situation. Richard Simshttp://people.bu.edu/rbs/
export node with copy stgpool......
Hi, When exporting client node to another server, do the destination server import copy pool also??? Regards Krishnababu 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
TSM EXPORT NODE TO NODE
Good Morning All, We have exchange data on an old TSM server that we are trying to decommission. What I need to do is, export the exchange data that still exists on the old TSM server to our new TSM server that was just built approximately 6 months ago. So my question is, can I export the node from the old TSM server to the new TSM server, even though, the new TSM server already has that node name registered. In other words, the node exists on both servers, but the domain are different. If I start the export command will it export the data from the old TSM server to the same node which already exists on the new TSM server. I appreciate the help Ricky M. Plair Storage Engineer HealthPlan Services Office: 813 289 1000 Ext 2273 Mobile: 757 232 7258 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ CONFIDENTIALITY NOTICE: This email message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information and/or Protected Health Information (PHI) subject to protection under the law, including the Health Insurance Portability and Accountability Act of 1996, as amended (HIPAA). If you are not the intended recipient or the person responsible for delivering the email to the intended recipient, be advised that you have received this email in error and that any use, disclosure, distribution, forwarding, printing, or copying of this email is strictly prohibited. If you have received this email in error, please notify the sender immediately and destroy all copies of the original message.
Export node and management classes
Hi All I can't seem to find a definitive answer on this one, so thought I'd ask the wider group. I have some nodes i'd like to export from one instance to another. The nodes use 3-4 different managemant classes and also some archive data with 7 year retention. If I have a target domain with all the correct management classes, all named the same, and create the node name on this domain, will everything get rebound correctly? i.e. will my archive data still be intact and maintain the same retention? Thanks Steven
Export node to new server
My goal is to relocate all backup data for a node currently on a TSM 5.5.2 server to a TSM 6.2.4 server. There are no archive or space managed data in the system. First time I've had to try this, so looking to the experts for comment. Looks like a fairly simple process: Define the node on the target server with appropriate schedules, policy, etc. Have the node manager modify the DSM.OPT file to specify the new server. Let scheduled backups run. On source TSM: EXPORT NODE FILEDATA=BACKUP DEVCLASS= On target TSM: IMPORT NODE FILEDATA=BACKUP DEVCLASS= DATES=ABSOLUTE MERGEFILESPACES=YES VOL= An important parameter MERGEFILESPACES=YES to bring in the old data into the identical filespaces. Harold Vandeventer Systems Programmer State of Kansas - Office of Information Technology Services harold.vandeven...@ks.gov (785) 296-0631 [Confidentiality notice:] *** This e-mail message, including attachments, if any, is intended for the person or entity to which it is addressed and may contain confidential or privileged information. Any unauthorized review, use, or disclosure is prohibited. If you are not the intended recipient, please contact the sender and destroy the original message, including all copies, Thank you. ***
Re: Export node bad tape
Mickael, Have you tried to run an audit on the tape volume that is having the issue? audit volume fix=yes -Rick Adamson -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of mik Sent: Friday, January 03, 2014 8:15 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Export node bad tape Hi everybody, I try to export node from old server (5.5 lto3) to new serveur (6.3 lto6) but i have an error with a tape and the export node failed because of that, i have no copypool (because the 5.5 lto3 have one drive since 1month and the second server was new (interest of the export node)). Anyone have an idea to succefully the export node ? Regards, Mickael. +-- |This was sent by bobpatrick808...@yahoo.fr via Backup Central. |Forward SPAM to ab...@backupcentral.com. +--
Re: Export node bad tape
Try exporting the node directly from one server to the other via the network. Getting the two servers to talk to each other over the net is not difficult. V5 talks to V6 OK. BTW just finished an upgrade of our largest TSM server (300GB database) from V5 to V6, and it went very well. I have concluded that upgrading a TSM server from V5 to V6 is much better, faster, and easier than moving the nodes via export or having them do new backups. I wish I had known this two years ago, because I could have saved a lot of work. The upgrade process is long and complicated, taking us 49 hours, but it works and then you're done. We now have a v6.2.5 TSM server with the "Server Installation Date/Time" in 1999. Roger Deschner University of Illinois at Chicago rog...@uic.edu ==I have not lost my mind -- it is backed up on tape somewhere.= On Fri, 3 Jan 2014, mik wrote: >Hi and thanks for reply Rick, > >The audit volume was in progress, i hope the audit was good. > >Happy new year to you and your family. > >Regars, Mickael. > >+-- >|This was sent by bobpatrick808...@yahoo.fr via Backup Central. >|Forward SPAM to ab...@backupcentral.com. >+-- >
EXPORT NODE to SERVER question/issue....
I am now on my fourth attempt to do an EXPORT NODE to SERVER, from my zOS TSM server (5.1.6.4) to our AIX TSM server (5.1.6.2). The reason I am on my fourth attempt is that it seems to quit/drop-dead/whatever for no apparent reason I can fathom. The last attempt, while the final status said "SUCCESSFULL", further digging for an error message found one that said "INCOMPLETE" (not sure why a previous "failure" still registers as "successfull" but I am not concerned about this, right now). Eventhough each attempt seems to move some data, nothing seems to appear on the receiving end. My question(s): 1. Where is the stuff being imported/exported going if it doesn't seem to appear on the other end ? 2. If it actually does send some files across and I run the EXPORT again, does it just skip the files previously sent ? 3. What if an *EXACT* copy of the file(s) I am export/importing already exists on the receiving end ? Does it ignore it ?
Export node to second TSM instance
Anyone run into issues exporting nodes from one TSM server to a second instance of TSM running on the same physical server? Will this data pass though the network? Thanks Kevin
Re: EXPORT NODE directly to server
Joni, You could use "PING SERVER TSMPROD" command from your mainframe server TSM command prompt to test communication. Regards, Samiran Das -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Joni Moyer Sent: Wednesday, May 25, 2005 9:18 AM To: ADSM-L@VM.MARIST.EDU Subject: EXPORT NODE directly to server Hello Everyone! I was trying to export data from our mainframe server: b390.highmark.com to our new AIX server TSMPROD. I received the following message. Did anyone ever experience this issue? How can I test communication between the 2 servers without trying an export? Thanks! 05/25/2005 09:12:47 ANR2017I Administrator LIDZR8V issued command: EXPORT NODE pgsp007 filedata=archive toserver=tsmprod previewimport=- yes (SESSION: 739) 05/25/2005 09:12:47 ANR0984I Process 40 for EXPORT NODE started in the BACKGROUND at 09:12:47. (SESSION: 739, PROCESS: 40) 05/25/2005 09:12:47 ANR0609I EXPORT NODE started as process 40. (SESSION: 739, PROCESS: 40) 05/25/2005 09:12:47 ANR0609I EXPORT NODE started as process 40. (SESSION: 739, PROCESS: 40) 05/25/2005 09:12:47 ANR0402I Session 740 started for administrator LIDZR8V (Server) (Memory IPC). (SESSION: 739, PROCESS: 40) 05/25/2005 09:12:48 ANRD SMXI(587): ThreadId<1197> Could not open session with TSMPROD. Callchain follows: pkShowCallChain+2E2 <- outDiagf+27E <- smXiSetupServer2ServerExport+832 <- XiExport+220 <- pkThreadHead+4FA (SESSION: 739, PROCESS: 40) 05/25/2005 09:12:48 ANR0781E EXPORT NODE: Process aborted - server sign on failed. (SESSION: 739, PROCESS: 40) 05/25/2005 09:12:48 ANR0985I Process 40 for EXPORT NODE running in the BACKGROUND completed with completion state FAILURE at 09:12:48. (SESSION: 739, PROCESS: 40) TSMPROD: Q STAT output Server Name: TSMPROD Server host name or IP address: 157.154.47.18 Server TCP/IP port number: 1500 Server URL: Crossdefine: On Server Password Set: Yes Server Installation Date/Time: 06/23/04 09:32:54 Server Restart Date/Time: 04/17/05 18:43:00 Authentication: On Password Expiration Period: 9,999 Day(s) Invalid Sign-on Attempt Limit: 0 Minimum Password Length: 0 WEB Admin Authentication Time-out (minutes): 0 Registration: Closed Subfile Backup: No Availability: Enabled Accounting: Off Activity Log Retention Period: 15 Day(s) Activity Summary Retention Period: 30 Day(s) License Audit Period: 15 Day(s) Last License Audit: 05/16/05 18:45:53 Server License Compliance: Valid Central Scheduler: Active Maximum Sessions: 300 Maximum Scheduled Sessions: 270 Event Record Retention Period: 15 Day(s) Client Action Duration: 5 Day(s) Schedule Randomization Percentage: 25 Query Schedule Period: 6 Hour(s) Maximum Command Retries: Client Retry Period: Client Scheduling Modes: Any Log Mode: Normal Database Backup Trigger: Not Defined BufPoolSize: 419,432 K Active Receivers: CONSOLE ACTLOG FILE Configuration manager?: Off Refresh interval: 60 Last refresh date/time: Context Messaging: Off Server-free Status: Not Supported Server-free Batch Size: Table of Contents (TOC) Load Retention: 120 Minute(s) Machine Globally Unique ID: 3a.c7.e8.06.63.cc.11.d8.91.3 d.08.6 3.c0.a8.0b.03 Archive Retention Protection: Off TSMPROD defintion on our mainframe b390.highmark.com server Server Name: TSMPROD Comm. Method: TCPIP High-level Address: tsmprod Low-level Address: 1500 Description: TSM Production Server Allow Replacement: No Node Name:
Re: EXPORT NODE directly to server
On May 25, 2005, at 9:17 AM, Joni Moyer wrote: ...How can I test communication between the 2 servers without trying an export?... The PING SERVER command is provided for that purpose. The command uses the user ID and password of the administrative ID that issued the command. If the administrator is not defined on the server being pinged, the ping fails even if the server may be running. Outside of TSM you can use the OS ping command to test TCP/IP connectivity. Richard Sims
Re: EXPORT NODE directly to server
Hello Samiran,
I entered the command from the TSM mainframe's dsmadmc command line and I
received the following:
tsm: ADSM>ping server tsmprod
ANR1705W Ping for server 'TSMPROD' was not able to establish a connection.
I'm not quite sure what needs to be setup in order for this export to work?
I just thought each server had to be defined to the other. Am I missing
something else? Thanks!
Joni Moyer
Highmark
Storage Systems
Work:(717)302-6603
Fax:(717)302-5974
[EMAIL PROTECTED]
"Das, Samiran
(IDS ECCS)"
<[EMAIL PROTECTED] To
OM> ADSM-L@VM.MARIST.EDU
Sent by: "ADSM:cc
Dist Stor
Manager" Subject
<[EMAIL PROTECTED] Re: EXPORT NODE directly to server
.EDU>
05/25/2005 09:31
AM
Please respond to
"ADSM: Dist Stor
Manager"
<[EMAIL PROTECTED]
.EDU>
Joni,
You could use "PING SERVER TSMPROD" command from your mainframe server
TSM command prompt to test communication.
Regards, Samiran Das
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Joni Moyer
Sent: Wednesday, May 25, 2005 9:18 AM
To: ADSM-L@VM.MARIST.EDU
Subject: EXPORT NODE directly to server
Hello Everyone! I was trying to export data from our mainframe server:
b390.highmark.com to our new AIX server TSMPROD. I received the
following message. Did anyone ever experience this issue? How can I
test communication between the 2 servers without trying an export?
Thanks!
05/25/2005 09:12:47 ANR2017I Administrator LIDZR8V issued command:
EXPORT
NODE
pgsp007 filedata=archive toserver=tsmprod
previewimport=-
yes (SESSION: 739)
05/25/2005 09:12:47 ANR0984I Process 40 for EXPORT NODE started in the
BACKGROUND at 09:12:47. (SESSION: 739, PROCESS:
40)
05/25/2005 09:12:47 ANR0609I EXPORT NODE started as process 40.
(SESSION:
739,
PROCESS: 40)
05/25/2005 09:12:47 ANR0609I EXPORT NODE started as process 40.
(SESSION:
739,
PROCESS: 40)
05/25/2005 09:12:47 ANR0402I Session 740 started for administrator
LIDZR8V
(Server) (Memory IPC). (SESSION: 739, PROCESS:
40)
05/25/2005 09:12:48 ANRD SMXI(587): ThreadId<1197> Could not open
session
with TSMPROD. Callchain follows:
pkShowCallChain+2E2 <-
outDiagf+27E <- smXiSetupServer2ServerExport+832
<-
XiExport+220 <- pkThreadHead+4FA (SESSION: 739,
PROCESS:
40)
05/25/2005 09:12:48 ANR0781E EXPORT NODE: Process aborted - server
sign
on
failed. (SESSION: 739, PROCESS: 40)
05/25/2005 09:12:48 ANR0985I Process 40 for EXPORT NODE running in the
BACKGROUND completed with completion state
FAILURE at
09:12:48. (SESSION: 739, PROCESS: 40)
TSMPROD: Q STAT output
Server Name: TSMPROD
Server host name or IP address: 157.154.47.18
Server TCP/IP port number: 1500
Server URL:
Crossdefine: On
Server Password Set: Yes
Server Installation Date/Time: 06/23/04 09:32:54
Server Restart Date/Time: 04/17/05 18:43:00
Authentication: On
Password Expiration Period: 9,999 Day(s)
Invalid Sign-on Attempt Limit: 0
Minimum Password Length: 0
WEB Admin Authentication Time-out (minutes): 0
Registration: Closed
Subfile Backup: No
Availability: Enabled
Accounting: Off
Activity Log Retention Period: 15 Day(s)
Activity Summary Retention Period: 30 Day(s)
License Audit Period: 15 Day(s)
Last License Audit: 05/16/05 18:45:53
Server License Compliance: Valid
Central Scheduler: Active
Maximum Sessions: 300
Maximum Scheduled Sessions: 270
Event Record Retention Period: 15 Day(s)
Client Action Duration: 5 Day(s)
Schedule Randomization Percentage: 25
Query Schedule Period: 6 Hour(s)
Maximum Command Retries: Client
Re: EXPORT NODE directly to server
Hello Richard! I am a little confused about using the ping server command. I have 2 AIX servers defined to each other and I can run the ping server command to each and it does see a response, but I have defined TSMPROD to b390.highmark.com and vice versa. I am using the same admin id and password on both and they reside on the same network. Results from OS ping: Pinging b390.highmark.com [157.154.93.185] with 32 bytes of data: Reply from 157.154.93.185: bytes=32 time<10ms TTL=61 Reply from 157.154.93.185: bytes=32 time<10ms TTL=61 Reply from 157.154.93.185: bytes=32 time<10ms TTL=61 Reply from 157.154.93.185: bytes=32 time<10ms TTL=61 Ping statistics for 157.154.93.185: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms C:\Documents and Settings\lidzr8v> C:\Documents and Settings\lidzr8v>ping tsmprod Pinging chrs144.highmark.com [157.154.47.18] with 32 bytes of data: Reply from 157.154.47.18: bytes=32 time<10ms TTL=252 Reply from 157.154.47.18: bytes=32 time<10ms TTL=252 Reply from 157.154.47.18: bytes=32 time<10ms TTL=252 Reply from 157.154.47.18: bytes=32 time<10ms TTL=252 Ping statistics for 157.154.47.18: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms Results of ping for adsm on TSMPROD tsm: TSMPROD>ping server adsm ANR1706I Ping for server 'ADSM' was able to establish a connection. Results of ping for tsmprod from adsm tsm: ADSM>ping server tsmprod ANR1705W Ping for server 'TSMPROD' was not able to establish a connection. Any ideas? Thanks! Joni Moyer Highmark Storage Systems Work:(717)302-6603 Fax:(717)302-5974 [EMAIL PROTECTED] "Richard Sims" <[EMAIL PROTECTED]> Sent by: "ADSM:To Dist Stor ADSM-L@VM.MARIST.EDU Manager" cc <[EMAIL PROTECTED] .EDU> Subject Re: EXPORT NODE directly to server 05/25/2005 09:39 AM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED] .EDU> On May 25, 2005, at 9:17 AM, Joni Moyer wrote: > ...How can I test > communication between the 2 servers without trying an export?... The PING SERVER command is provided for that purpose. The command uses the user ID and password of the administrative ID that issued the command. If the administrator is not defined on the server being pinged, the ping fails even if the server may be running. Outside of TSM you can use the OS ping command to test TCP/IP connectivity. Richard Sims
Re: EXPORT NODE directly to server
Hi Joni,
Please make the following changes and issue "ping server tsmprod"
command to see the result.
At Mainframe tsm server:
1. update server tsmprod hla=157.154.47.18
Regards, Samiran Das
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Joni Moyer
Sent: Wednesday, May 25, 2005 10:10 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: EXPORT NODE directly to server
Hello Richard!
I am a little confused about using the ping server command. I have 2
AIX servers defined to each other and I can run the ping server command
to each and it does see a response, but I have defined TSMPROD to
b390.highmark.com and vice versa. I am using the same admin id and
password on both and they reside on the same network.
Results from OS ping:
Pinging b390.highmark.com [157.154.93.185] with 32 bytes of data:
Reply from 157.154.93.185: bytes=32 time<10ms TTL=61
Reply from 157.154.93.185: bytes=32 time<10ms TTL=61
Reply from 157.154.93.185: bytes=32 time<10ms TTL=61
Reply from 157.154.93.185: bytes=32 time<10ms TTL=61
Ping statistics for 157.154.93.185:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate
round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
C:\Documents and Settings\lidzr8v>
C:\Documents and Settings\lidzr8v>ping tsmprod
Pinging chrs144.highmark.com [157.154.47.18] with 32 bytes of data:
Reply from 157.154.47.18: bytes=32 time<10ms TTL=252
Reply from 157.154.47.18: bytes=32 time<10ms TTL=252
Reply from 157.154.47.18: bytes=32 time<10ms TTL=252
Reply from 157.154.47.18: bytes=32 time<10ms TTL=252
Ping statistics for 157.154.47.18:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate
round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
Results of ping for adsm on TSMPROD
tsm: TSMPROD>ping server adsm
ANR1706I Ping for server 'ADSM' was able to establish a connection.
Results of ping for tsmprod from adsm
tsm: ADSM>ping server tsmprod
ANR1705W Ping for server 'TSMPROD' was not able to establish a
connection.
Any ideas? Thanks!
Joni Moyer
Highmark
Storage Systems
Work:(717)302-6603
Fax:(717)302-5974
[EMAIL PROTECTED]
"Richard Sims"
<[EMAIL PROTECTED]>
Sent by: "ADSM:
To
Dist Stor ADSM-L@VM.MARIST.EDU
Manager"
cc
<[EMAIL PROTECTED]
.EDU>
Subject
Re: EXPORT NODE directly to
server
05/25/2005 09:39
AM
Please respond to
"ADSM: Dist Stor
Manager"
<[EMAIL PROTECTED]
.EDU>
On May 25, 2005, at 9:17 AM, Joni Moyer wrote:
> ...How can I test
> communication between the 2 servers without trying an export?...
The PING SERVER command is provided for that purpose. The command uses
the user ID and password of the administrative ID that issued the
command. If the administrator is not defined on the server being pinged,
the ping fails even if the server may be running.
Outside of TSM you can use the OS ping command to test TCP/IP
connectivity.
Richard Sims
If you are not an intended recipient of this e-mail, please notify the sender,
delete it and do not read, act upon, print, disclose, copy, retain or
redistribute it. Click here for important additional terms relating to this
e-mail. http://www.ml.com/email_terms/
Re: EXPORT NODE directly to server
Thank you so very much! I guess I cannot put dns names within the hla and
will have to stick with the ip address. Thank you again!
Joni Moyer
Highmark
Storage Systems
Work:(717)302-6603
Fax:(717)302-5974
[EMAIL PROTECTED]
"Das, Samiran
(IDS ECCS)"
<[EMAIL PROTECTED] To
OM> ADSM-L@VM.MARIST.EDU
Sent by: "ADSM:cc
Dist Stor
Manager" Subject
<[EMAIL PROTECTED] Re: EXPORT NODE directly to server
.EDU>
05/25/2005 10:18
AM
Please respond to
"ADSM: Dist Stor
Manager"
<[EMAIL PROTECTED]
.EDU>
Hi Joni,
Please make the following changes and issue "ping server tsmprod"
command to see the result.
At Mainframe tsm server:
1. update server tsmprod hla=157.154.47.18
Regards, Samiran Das
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Joni Moyer
Sent: Wednesday, May 25, 2005 10:10 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: EXPORT NODE directly to server
Hello Richard!
I am a little confused about using the ping server command. I have 2
AIX servers defined to each other and I can run the ping server command
to each and it does see a response, but I have defined TSMPROD to
b390.highmark.com and vice versa. I am using the same admin id and
password on both and they reside on the same network.
Results from OS ping:
Pinging b390.highmark.com [157.154.93.185] with 32 bytes of data:
Reply from 157.154.93.185: bytes=32 time<10ms TTL=61
Reply from 157.154.93.185: bytes=32 time<10ms TTL=61
Reply from 157.154.93.185: bytes=32 time<10ms TTL=61
Reply from 157.154.93.185: bytes=32 time<10ms TTL=61
Ping statistics for 157.154.93.185:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate
round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
C:\Documents and Settings\lidzr8v>
C:\Documents and Settings\lidzr8v>ping tsmprod
Pinging chrs144.highmark.com [157.154.47.18] with 32 bytes of data:
Reply from 157.154.47.18: bytes=32 time<10ms TTL=252
Reply from 157.154.47.18: bytes=32 time<10ms TTL=252
Reply from 157.154.47.18: bytes=32 time<10ms TTL=252
Reply from 157.154.47.18: bytes=32 time<10ms TTL=252
Ping statistics for 157.154.47.18:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate
round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
Results of ping for adsm on TSMPROD
tsm: TSMPROD>ping server adsm
ANR1706I Ping for server 'ADSM' was able to establish a connection.
Results of ping for tsmprod from adsm
tsm: ADSM>ping server tsmprod
ANR1705W Ping for server 'TSMPROD' was not able to establish a
connection.
Any ideas? Thanks!
Joni Moyer
Highmark
Storage Systems
Work:(717)302-6603
Fax:(717)302-5974
[EMAIL PROTECTED]
"Richard Sims"
<[EMAIL PROTECTED]>
Sent by: "ADSM:
To
Dist Stor ADSM-L@VM.MARIST.EDU
Manager"
cc
<[EMAIL PROTECTED]
.EDU>
Subject
Re: EXPORT NODE directly to
server
05/25/2005 09:39
AM
Please respond to
"ADSM: Dist Stor
Manager"
<[EMAIL PROTECTED]
.EDU>
On May 25, 2005, at 9:17 AM, Joni Moyer wrote:
> ...How can I test
> communication between the 2 servers without trying an export?...
The PING SERVER command is provided for that purpose. The command uses
the user ID and password of the administrative ID that issued the
command. If the administrator is not defined on the server being pinged,
the ping fails even if the server may be running.
Outside of TSM you can use the OS ping command to test TCP/IP
connectivity.
Richard Sims
If you are not an intended recipient of this e-mail, please notify the
sender, delete it and do not read, act upon, print, disclose, copy, retain
or redistribute it. Click here for important additional terms relating to
this e-mail. http://www.ml.com/email_terms/
Export Node - Usage to fake Archiving
Would this "Export Node" be something that could replace the Archiving command?. I understand that I have to keep track of the backups, and tapes myself. Maybe its still easier then letting DRM keep track of them and it will reduce the space used on the server right?? (Find the archiving somewhat tricky to set up, but I'm a newbie :-)) ) Or am totaly out in the blue here?? Henrik Hansson Nomafa AB Web; www.nomafa.com Mail; [EMAIL PROTECTED] "Cook, Dwight E" To: [EMAIL PROTECTED] <[EMAIL PROTECTED]cc: M> Subject: Re: Export DB - Usage Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED] RIST.EDU> 2000-08-01 21:14 Please respond to "ADSM: Dist Stor Manager" I'm doing that... Lots of different situations... If they say the data is REALLY REALLY REALLY important I leave it in the tsm server, have it in an isolated storage pool with a copypool copy of it AND I export the node, twice, and give the end user one of the copies. If it is REALLY important (like IRS data) I keep it in the server and have an isolated primary and copy pool with it (and run periodic audits on the volumes) If they stand there picking their nose and say "Duh, we better keep this around forever 'cause duh..." I just export the node, print the summary info from the tsm server's activity log showing ALL THE VOLUMES AND THEIR SEQUENCE, check the tapes out of the atl and stick the tapes in a rack with the paper work in a folder at the end... and when I export the client, I only export ACTIVE data... GOD I LOVE TSM :-) Dwight > -- > From: Siciliano, Gerald > (Moody's)[SMTP:[EMAIL PROTECTED]] > Reply To: ADSM: Dist Stor Manager > Sent: Tuesday, August 01, 2000 1:42 PM > To: [EMAIL PROTECTED] > Subject: Export DB - Usage > > Has anyone ever used 'export node' as long term storage for node data? > > I have about 24 nodes that are being retained for 10yrs, the data has not > been accessed since the backups were initially done. These nodes > represent > about 30% of my TSM server database. To reclaim the space in the DB can > the > 'export node' command be used for this purpose? > > This is just a thought I had, any suggestions? > > > Thanks, > Jerry Siciliano >
Re: export node toserver, extremely slow
Tom - To factors which come to mind are: - Lack of collocation can make for a lot of tape repositioning, which, depending upon your tape technology, can be painful. - I know from experience, watching reclamations, that tapes which have been sitting unused for long periods of time (years) can be more difficult to read than recently written tapes. If you are using node or filespace collocation, I would try doing Move Data on one or more of the feeder volumes involved, and see if that process is sluggish, which means an issue with the old storage pool tape. Once on a fresh tape, I would expect the export to move faster, with no tape read struggling. If you have a disk storage pool in you hierarchy, you might try moving data there, to eliminate the tape factor in seeing where the slowdown is. Beyond that, you would need to engage in problem isolation Richard Sims
export node toserver= , slow.. on AIX
Hi! This is probaly not an itsm-issue, but anyway..: both tsm-servers, 5.3.4, running on the same P650, AIX5.3-box. Shared memory is used (lo0), but performance is useless. (about 140KB/sek on average, 70KB in, 70KB out) This used to work fine on our old S7A, the numbers where usually 100MB/s and up. Has anyone running TSM on AIX seen similar behavior?
Re: Export Node and OS Migrations
An EXPORT is just a copy. You have your data on an export tape, but nothing else happens. To get the data "out of TSM", you need to 1) EXPORT the data 2) DELETE the filespaces for the nodes you have exported. When you delete the filespace, it deletes the data from the primary tape AND the offsite tape. Reclamation proceeds as normal. If your data is collocated, or your NOVELL data is in a separate storage pool, look at the MOVE MEDIA command. It's a way to eject the tapes (solving your slot problem), and tell TSM you are storing them outside the library. You could just leave them that way until you are ready to completely destroy the NOVELL data. From: ADSM: Dist Stor Manager on behalf of Richard Mochnaczewski Sent: Tue 6/19/2007 3:03 PM To: ADSM-L@VM.MARIST.EDU Subject: Export Node and OS Migrations Hi *, We are currently in the middle of migrating our Novell file servers to Windows 2003. We will be doing a copy of all our Novell file server data to our Windows 2003 machines and then eventually deleting the Novell machine in the future. In the meantime, we will be running low on slots in our library because we will for a short time have the duplicate copies before we cut off our Novell servers.. If I do an export of our Novell data to get the data out of TSM and the library, it will free up our onsite slot issue, but what will happen to the reclamation for that server for my offsite tapes ? Rich
Re: export node writing to spacemgpool
You've got management class(es)/backup copy group(s) on the source server that do not match in some respect the management class(es)/backup copy group(s) on the target server. (And remember the old gotcha, directories are bound to the mgmt class with the highest RETONLY setting) -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Keith Arbogast Sent: Monday, April 12, 2010 11:40 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] export node writing to spacemgpool I am seeing surprising behavior from a process exporting a node directly to another server. Most of the exported files are being written to an HSM disk pool and HSM tape pool, but some to the primary disk and tape poosl. All the filespaces being exported are dong this. I see this by running 'q occ ' on the target server. The same command on the source server does not show any files in an HSM pool. The node being exported is running Windows 5.0.2 and TSM version 5.5.2.6. It is not running HSM, to my knowledge. The source TSM server is at Linux version 5.5.2.1. The target TSM server is at Linux version 5.5.4.1. What circumstances could be causing this? I am baffled. The primary disk pool is not hitting HighMig, and it wouldn't migrate to SPACEMGPOOL if it were. Thank you, Keith Arbogast
Re: export node writing to spacemgpool
Wanda, Thank you for your reply. It got me on the right track to find the problem. Best wishes, Keith
Re: export node with copy stgpool......
Hi Krishbababu The export/import is of primary data, which gets placed into a primary storage pool on the receiving server. Should you choose to run a backup stg on that, the new server TSM database will not yet have a copy and create one. So import your data and run a backup stg on it to get your copy pool. Regards Steve Steven Harris TSM Admin Canberra Australia On 22/06/2011 4:38 PM, Krishnababu wrote: Hi, When exporting client node to another server, do the destination server import copy pool also??? Regards Krishnababu 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
Re: TSM EXPORT NODE TO NODE
Hello Ricky, You can do an export node with a mergefilespace=yes option, but I've found that to be problematic when replicating application data. You could rename the node on the source server first, before exporting, then the node will import with a different name and will not have any disruption to the existing data. Hope that helps __ Matthew McGeary Technical Specialist - Operations PotashCorp T: (306) 933-8921 www.potashcorp.com From: "Plair, Ricky" To: ADSM-L@VM.MARIST.EDU Date: 03/03/2015 09:57 AM Subject: [ADSM-L] TSM EXPORT NODE TO NODE Sent by:"ADSM: Dist Stor Manager" Good Morning All, We have exchange data on an old TSM server that we are trying to decommission. What I need to do is, export the exchange data that still exists on the old TSM server to our new TSM server that was just built approximately 6 months ago. So my question is, can I export the node from the old TSM server to the new TSM server, even though, the new TSM server already has that node name registered. In other words, the node exists on both servers, but the domain are different. If I start the export command will it export the data from the old TSM server to the same node which already exists on the new TSM server. I appreciate the help Ricky M. Plair Storage Engineer HealthPlan Services Office: 813 289 1000 Ext 2273 Mobile: 757 232 7258 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ CONFIDENTIALITY NOTICE: This email message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information and/or Protected Health Information (PHI) subject to protection under the law, including the Health Insurance Portability and Accountability Act of 1996, as amended (HIPAA). If you are not the intended recipient or the person responsible for delivering the email to the intended recipient, be advised that you have received this email in error and that any use, disclosure, distribution, forwarding, printing, or copying of this email is strictly prohibited. If you have received this email in error, please notify the sender immediately and destroy all copies of the original message.
Re: Export node and management classes
Yes. -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Steven Langdale Sent: Wednesday, February 15, 2012 6:24 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Export node and management classes Hi All I can't seem to find a definitive answer on this one, so thought I'd ask the wider group. I have some nodes i'd like to export from one instance to another. The nodes use 3-4 different managemant classes and also some archive data with 7 year retention. If I have a target domain with all the correct management classes, all named the same, and create the node name on this domain, will everything get rebound correctly? i.e. will my archive data still be intact and maintain the same retention? Thanks Steven
Re: Export node to new server
Better if you do that in reverse order, unless the clients are trivial in size. If you let the client scheduled backup run, it will do a full, which for many clients can be painful. If you get the export done first, all the existing data will be represented in the new server DB, and the client's scheduled backup to the new server will be incremental. If there is a time lag between the time you do the first export and the time you get the clients dsm.opt file pointing to the new server, you can do an incremental export to catch up - add the FROMDATE=today-blah fromtime=xx:yy:zz to the EXPORT command. Also IMHO it's easier to do what you suggest using server-to-server export than using media. Then it's just one step. Wanda -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Vandeventer, Harold [BS] Sent: Thursday, August 23, 2012 4:19 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Export node to new server My goal is to relocate all backup data for a node currently on a TSM 5.5.2 server to a TSM 6.2.4 server. There are no archive or space managed data in the system. First time I've had to try this, so looking to the experts for comment. Looks like a fairly simple process: Define the node on the target server with appropriate schedules, policy, etc. Have the node manager modify the DSM.OPT file to specify the new server. Let scheduled backups run. On source TSM: EXPORT NODE FILEDATA=BACKUP DEVCLASS= On target TSM: IMPORT NODE FILEDATA=BACKUP DEVCLASS= DATES=ABSOLUTE MERGEFILESPACES=YES VOL= An important parameter MERGEFILESPACES=YES to bring in the old data into the identical filespaces. Harold Vandeventer Systems Programmer State of Kansas - Office of Information Technology Services harold.vandeven...@ks.gov (785) 296-0631 [Confidentiality notice:] *** This e-mail message, including attachments, if any, is intended for the person or entity to which it is addressed and may contain confidential or privileged information. Any unauthorized review, use, or disclosure is prohibited. If you are not the intended recipient, please contact the sender and destroy the original message, including all copies, Thank you. ***
Re: Export node to new server
Do you have any information on doing "server-to-server export"? Is there a TSM name for it? Thanks Grant On 24/08/12 09:31, Prather, Wanda wrote: Better if you do that in reverse order, unless the clients are trivial in size. If you let the client scheduled backup run, it will do a full, which for many clients can be painful. If you get the export done first, all the existing data will be represented in the new server DB, and the client's scheduled backup to the new server will be incremental. If there is a time lag between the time you do the first export and the time you get the clients dsm.opt file pointing to the new server, you can do an incremental export to catch up - add the FROMDATE=today-blah fromtime=xx:yy:zz to the EXPORT command. Also IMHO it's easier to do what you suggest using server-to-server export than using media. Then it's just one step. Wanda -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Vandeventer, Harold [BS] Sent: Thursday, August 23, 2012 4:19 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Export node to new server My goal is to relocate all backup data for a node currently on a TSM 5.5.2 server to a TSM 6.2.4 server. There are no archive or space managed data in the system. First time I've had to try this, so looking to the experts for comment. Looks like a fairly simple process: Define the node on the target server with appropriate schedules, policy, etc. Have the node manager modify the DSM.OPT file to specify the new server. Let scheduled backups run. On source TSM: EXPORT NODE FILEDATA=BACKUP DEVCLASS= On target TSM: IMPORT NODE FILEDATA=BACKUP DEVCLASS= DATES=ABSOLUTE MERGEFILESPACES=YES VOL= An important parameter MERGEFILESPACES=YES to bring in the old data into the identical filespaces. Harold Vandeventer Systems Programmer State of Kansas - Office of Information Technology Services harold.vandeven...@ks.gov (785) 296-0631 [Confidentiality notice:] *** This e-mail message, including attachments, if any, is intended for the person or entity to which it is addressed and may contain confidential or privileged information. Any unauthorized review, use, or disclosure is prohibited. If you are not the intended recipient, please contact the sender and destroy the original message, including all copies, Thank you. ***
Re: Export node to new server
Thanks Wanda... the nodes are not trivial, unfortunately. We've never had a need for server-server comms; a lot can be done there it appears. I see a description in the Admin Guide for "Preparing to export to another server for immediate import." That includes a DEFINE SERVER to establish the name of the "target server or the originating server". I'm confused by the two syntax's of DEFINE SERVER. Do I follow the "virtual volumes" setup process? Then, define the node manually on the target; some changes in contact, Policy Domain names and other items easy to define manually, but don't need to be exported/imported. Then: 1: Lock the node. 2: EXPORT NODE TOSERVER= FILEDATA=BACKUP EXPORTIDENTIFIER=. 3: monitor that, but have the node manager edit the DSM.OPT. 4: unlock node when done. 5: delete filespaces/node on source after everyone is comfortable it all worked. Again, thanks for helping out, I'm jumping into server-server for the first time. Harold Vandeventer Systems Programmer State of Kansas - Office of Information Technology Services harold.vandeven...@ks.gov (785) 296-0631 -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Prather, Wanda Sent: Thursday, August 23, 2012 6:32 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Export node to new server Better if you do that in reverse order, unless the clients are trivial in size. If you let the client scheduled backup run, it will do a full, which for many clients can be painful. If you get the export done first, all the existing data will be represented in the new server DB, and the client's scheduled backup to the new server will be incremental. If there is a time lag between the time you do the first export and the time you get the clients dsm.opt file pointing to the new server, you can do an incremental export to catch up - add the FROMDATE=today-blah fromtime=xx:yy:zz to the EXPORT command. Also IMHO it's easier to do what you suggest using server-to-server export than using media. Then it's just one step. Wanda -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Vandeventer, Harold [BS] Sent: Thursday, August 23, 2012 4:19 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Export node to new server My goal is to relocate all backup data for a node currently on a TSM 5.5.2 server to a TSM 6.2.4 server. There are no archive or space managed data in the system. First time I've had to try this, so looking to the experts for comment. Looks like a fairly simple process: Define the node on the target server with appropriate schedules, policy, etc. Have the node manager modify the DSM.OPT file to specify the new server. Let scheduled backups run. On source TSM: EXPORT NODE FILEDATA=BACKUP DEVCLASS= On target TSM: IMPORT NODE FILEDATA=BACKUP DEVCLASS= DATES=ABSOLUTE MERGEFILESPACES=YES VOL= An important parameter MERGEFILESPACES=YES to bring in the old data into the identical filespaces. Harold Vandeventer Systems Programmer State of Kansas - Office of Information Technology Services harold.vandeven...@ks.gov (785) 296-0631 [Confidentiality notice:] *** This e-mail message, including attachments, if any, is intended for the person or entity to which it is addressed and may contain confidential or privileged information. Any unauthorized review, use, or disclosure is prohibited. If you are not the intended recipient, please contact the sender and destroy the original message, including all copies, Thank you. ***
Re: Export node to new server
Hi Harold, I would recommend you check of server-to-server communication between server is supported configuration in terms of TSM version. because if you have an issue during the migration and it is not supported config, IBM will refuse support ... Regards Chavdar On Fri, Aug 24, 2012 at 7:03 PM, Vandeventer, Harold [BS] wrote: > Thanks Wanda... the nodes are not trivial, unfortunately. > > We've never had a need for server-server comms; a lot can be done there it > appears. > > I see a description in the Admin Guide for "Preparing to export to another > server for immediate import." That includes a DEFINE SERVER to establish the > name of the "target server or the originating server". > > I'm confused by the two syntax's of DEFINE SERVER. > > Do I follow the "virtual volumes" setup process? > > Then, define the node manually on the target; some changes in contact, Policy > Domain names and other items easy to define manually, but don't need to > be exported/imported. > > Then: > 1: Lock the node. > 2: EXPORT NODE TOSERVER= FILEDATA=BACKUP > EXPORTIDENTIFIER=. > 3: monitor that, but have the node manager edit the DSM.OPT. > 4: unlock node when done. > 5: delete filespaces/node on source after everyone is comfortable it all > worked. > > Again, thanks for helping out, I'm jumping into server-server for the first > time. > > > Harold Vandeventer > Systems Programmer > State of Kansas - Office of Information Technology Services > harold.vandeven...@ks.gov > (785) 296-0631 > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of > Prather, Wanda > Sent: Thursday, August 23, 2012 6:32 PM > To: ADSM-L@VM.MARIST.EDU > Subject: Re: [ADSM-L] Export node to new server > > Better if you do that in reverse order, unless the clients are trivial in > size. > If you let the client scheduled backup run, it will do a full, which for many > clients can be painful. > > If you get the export done first, all the existing data will be represented > in the new server DB, and the client's scheduled backup to the new server > will be incremental. > > If there is a time lag between the time you do the first export and the time > you get the clients dsm.opt file pointing to the new server, you can do an > incremental export to catch up - add the FROMDATE=today-blah > fromtime=xx:yy:zz to the EXPORT command. > > Also IMHO it's easier to do what you suggest using server-to-server export > than using media. Then it's just one step. > > Wanda > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of > Vandeventer, Harold [BS] > Sent: Thursday, August 23, 2012 4:19 PM > To: ADSM-L@VM.MARIST.EDU > Subject: [ADSM-L] Export node to new server > > My goal is to relocate all backup data for a node currently on a TSM 5.5.2 > server to a TSM 6.2.4 server. > > There are no archive or space managed data in the system. > > First time I've had to try this, so looking to the experts for comment. > > Looks like a fairly simple process: > Define the node on the target server with appropriate schedules, policy, etc. > Have the node manager modify the DSM.OPT file to specify the new server. > Let scheduled backups run. > > On source TSM: EXPORT NODE FILEDATA=BACKUP DEVCLASS= > > On target TSM: IMPORT NODE FILEDATA=BACKUP DEVCLASS= > DATES=ABSOLUTE MERGEFILESPACES=YES VOL= > > An important parameter MERGEFILESPACES=YES to bring in the old data into the > identical filespaces. > > > > Harold Vandeventer > Systems Programmer > State of Kansas - Office of Information Technology Services > harold.vandeven...@ks.gov > (785) 296-0631 > > > [Confidentiality notice:] > *** > This e-mail message, including attachments, if any, is intended for the > person or entity to which it is addressed and may contain confidential or > privileged information. Any unauthorized review, use, or disclosure is > prohibited. If you are not the intended recipient, please contact the sender > and destroy the original message, including all copies, Thank you. > ***
Re: Export node to new server
>>Do I follow the "virtual volumes" setup process? No, use the "enterprise configuration" form. You won't be creating any virtual volumes. When you export client data, it will land in the appropriate domain/mgmt. class, and get put into the storage hierarchy of the target server. Woe be unto you if you have domains/mgmt. classes with the same names, but different retention rules, when you start the export/import. >>Then, define the node manually on the target; Not necessary, it will get created with the import. Then: >>1: Lock the node. Not really necessary. >>2: EXPORT NODE TOSERVER= FILEDATA=BACKUP >>EXPORTIDENTIFIER= Suggest adding MERGE =YES as standard practice. Wanda
