Re: draining a diskpool when using a DD and no copypool
"ADSM: Dist Stor Manager" wrote on 03/24/2011 04:08:28 PM: > Couldn't you create a copypool into the same DD device class? If you had > 2 pools in the same DD > And this *shouldn't* cost anything > except for the I/O of TSM creating the local copypool. Have been thinking about this. We are counting on getting rid of the I/O to the copy pool, as well as the db meta-data associated to it. So I don't think this is where we want to go. > We had a compression card failure in 2007 that caused corrupt data to be > saved to disk (different vendor) The 2-pool model saved us that day. > Ever since then, I've been hesitant on the one-pool model, although I > haven't heard of any data corruption issues lately. It's also not just one pool, but one disk system. With tape you loose individual pieces of media. A hdwr or os bug could loose all your backups, and that's kind of scary. In stead of two pools (primary and copy) I've been thinking of DD snapshots. The problem with snapshots is that they are over the entire DD filesystem, and, that there is no way to revert the entire filesystem back to a snapshot (you can only copy stuff out of a snap). A snapshot might be useful for a TSM database backup, but not for a filepool of all your backups. Rick - The information contained in this message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately, and delete the original message.
Re: Ang: Re: Tsm v6 migration question
Hello Daniel, You say : ' That's not really something new to TSM v6'. DB2 is now the DBMS for TSM, and if DB2 improve database, DB2 has system requirement who was not the same in previous version My experience: The installer has set up the solution on our site has not implemented the recommendations related to DB2. TSM crash after two months. Best Regards Cordialement, Grégory Molin Tel : 0141628162 gregory.mo...@afnor.org -Message d'origine- De : ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] De la part de Daniel Sparrman Envoyé : jeudi 24 mars 2011 10:17 À : ADSM-L@VM.MARIST.EDU Objet : [ADSM-L] Ang: Re: Tsm v6 migration question That's not really something new to TSM v6. For performance reasons, it has always been recommended to separate database and log on different spindles. As with v6, at least for larger implementations, the same rule of thumb applies: Try separating your DB paths on at least 4 different arrays/spindles, preferably 8 or more. Too many will not increase performance, rather reduce it. Put your active log / log mirror on spindles of it's own, as well as your archivelog / failover paths. Watch out for sharing archivelog with something else (like storage) since the database backup trigger will look at the % used on the filesystem. So putting storagepools and then your archivelog in the same filesystem probably isnt the best of ideas. Best Regards Daniel Sparrman -"ADSM: Dist Stor Manager" skrev: - Till: ADSM-L@VM.MARIST.EDU Från: molin gregory Sänt av: "ADSM: Dist Stor Manager" Datum: 03/24/2011 11:06 Ärende: Re: Tsm v6 migration question Hello Gary, Effectively, the database grows between 10 and 20 %. (more if new features, like dedup, are intalled) But, the most important with the 6.x is the architecture of database files. You have to reserve one disk for the database, on for the actlog and one other for the archlog. Having this disks on the same axe may result poor efficientie Cordialement, Grégory Molin Tel : 0141628162 gregory.mo...@afnor.org -Message d'origine- De : ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] De la part de Lee, Gary D. Envoyé : mercredi 23 mars 2011 18:44 À : ADSM-L@VM.MARIST.EDU Objet : [ADSM-L] Tsm v6 migration question We are preparing to migrate our tsm v5,5,4 system to 6.2.2. Are there any rules of thumb for relating db size in v5.5.4 with what we will need under v6? I assume it will be somewhat larger being a truly relational structure. Thanks for any help. Gary Lee Senior System Programmer Ball State University phone: 765-285-1310 "ATTENTION. Ce message et les pièces jointes sont confidentiels et établis à l'attention exclusive de leur destinataire (aux adresses spécifiques auxquelles il a été adressé). Si vous n'êtes pas le destinataire de ce message, vous devez immédiatement en avertir l'expéditeur et supprimer ce message et les pièces jointes de votre système. This message and any attachments are confidential and intended to be received only by the addressee. If you are not the intended recipient, please notify immediately the sender by reply and delete the message and any attachments from your system. " "ATTENTION. Ce message et les pièces jointes sont confidentiels et établis à l'attention exclusive de leur destinataire (aux adresses spécifiques auxquelles il a été adressé). Si vous n'êtes pas le destinataire de ce message, vous devez immédiatement en avertir l'expéditeur et supprimer ce message et les pièces jointes de votre système. This message and any attachments are confidential and intended to be received only by the addressee. If you are not the intended recipient, please notify immediately the sender by reply and delete the message and any attachments from your system. "
Ang: Re: Ang: Re: Tsm v6 migration question
Hi Gregory My comment was to this previous comment: "But, the most important with the 6.x is the architecture of database files. You have to reserve one disk for the database, on for the actlog and one other for the archlog. Having this disks on the same axe may result poor efficientie" What I ment was that it has never been recommended to share the same array / spindle / filesystem between logs and database. If you go back to the TSM v5.5 performance guide, you'll will notice the recommendation to separate log and DB on separate spindles / filesystems / arrays. As for DB2, yes, DB2 is new for v6, but the performance setup isnt. My guess is that if your setup crashed after 2 months, whoever implemented your solution probably shared filesystemspace between the database and some other part of TSM, such as archivelog or log. Since a) the database can now grow "of it's own" I wouldnt place it with something else since you might run out of space b) I wouldnt share archivelog space with something else either since it also "grows of it's own". I cant imagine that your TSM implementation crashed just because the person who implemented it placed the database on a single filesystem. This is technically possible, but not something I would recommend due to performance issues. Best Regards Daniel Sparrman -"ADSM: Dist Stor Manager" skrev: - Till: ADSM-L@VM.MARIST.EDU Från: molin gregory Sänt av: "ADSM: Dist Stor Manager" Datum: 03/25/2011 14:47 Ärende: Re: Ang: Re: Tsm v6 migration question Hello Daniel, You say : ' That's not really something new to TSM v6'. DB2 is now the DBMS for TSM, and if DB2 improve database, DB2 has system requirement who was not the same in previous version My experience: The installer has set up the solution on our site has not implemented the recommendations related to DB2. TSM crash after two months. Best Regards Cordialement, Grégory Molin Tel : 0141628162 gregory.mo...@afnor.org -Message d'origine- De : ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] De la part de Daniel Sparrman Envoyé : jeudi 24 mars 2011 10:17 À : ADSM-L@VM.MARIST.EDU Objet : [ADSM-L] Ang: Re: Tsm v6 migration question That's not really something new to TSM v6. For performance reasons, it has always been recommended to separate database and log on different spindles. As with v6, at least for larger implementations, the same rule of thumb applies: Try separating your DB paths on at least 4 different arrays/spindles, preferably 8 or more. Too many will not increase performance, rather reduce it. Put your active log / log mirror on spindles of it's own, as well as your archivelog / failover paths. Watch out for sharing archivelog with something else (like storage) since the database backup trigger will look at the % used on the filesystem. So putting storagepools and then your archivelog in the same filesystem probably isnt the best of ideas. Best Regards Daniel Sparrman -"ADSM: Dist Stor Manager" skrev: - Till: ADSM-L@VM.MARIST.EDU Från: molin gregory Sänt av: "ADSM: Dist Stor Manager" Datum: 03/24/2011 11:06 Ärende: Re: Tsm v6 migration question Hello Gary, Effectively, the database grows between 10 and 20 %. (more if new features, like dedup, are intalled) But, the most important with the 6.x is the architecture of database files. You have to reserve one disk for the database, on for the actlog and one other for the archlog. Having this disks on the same axe may result poor efficientie Cordialement, Grégory Molin Tel : 0141628162 gregory.mo...@afnor.org -Message d'origine- De : ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] De la part de Lee, Gary D. Envoyé : mercredi 23 mars 2011 18:44 À : ADSM-L@VM.MARIST.EDU Objet : [ADSM-L] Tsm v6 migration question We are preparing to migrate our tsm v5,5,4 system to 6.2.2. Are there any rules of thumb for relating db size in v5.5.4 with what we will need under v6? I assume it will be somewhat larger being a truly relational structure. Thanks for any help. Gary Lee Senior System Programmer Ball State University phone: 765-285-1310 "ATTENTION. Ce message et les pièces jointes sont confidentiels et établis à l'attention exclusive de leur destinataire (aux adresses spécifiques auxquelles il a été adressé). Si vous n'êtes pas le destinataire de ce message, vous devez immédiatement en avertir l'expéditeur et supprimer ce message et les pièces jointes de votre système. This message and any attachments are confidential and intended to be received only by the addressee. If you are not the intended recipient, please notify immediately the sender by reply and delete the message and any attachments from your system. " "ATTENTION. Ce message et les pièces jointes sont confidentiels et établis à l'attention exclusive de leur destinataire (aux adresses spécifiques auxquelles il a été adressé). Si vous n'êtes pas le destinataire de ce message, vous devez immédiatem
TSM for DB password expiration
Has anyone had problems with TSM for DB (Oracle), aka TDPO, and password expiration? We are running TSM for DB v5.5.1.0 with TSM api 6.2.2.0 on AIX 5.3 to a TSM server at 6.2.2.0 also on AIX 5.3. We are running with password generate. Last night we got two ANR0425W password has expired messages for node DBFINTEST. I assume I got two messages because the rman command is using two channels, thus two concurrent TSM sessions. At that point the password should have been set to something new and life should go on. Instead, subsequent sessions for that node got the "ANS0282E Password file is not available.", ie password is incorrect, message. Any thoughts on what might be going wrong? David Ehresman
Ang: TSM for DB password expiration
Hi David Correct me if I'm wrong, but when the nodes password has expired, passwordaccess generate will not set a new password for the client. You'll have to set a new password for the node, and then use tdpoconf to update the stored password on the client machine. Best Regards Daniel Sparrman -"ADSM: Dist Stor Manager" skrev: - Till: ADSM-L@VM.MARIST.EDU Från: David E Ehresman Sänt av: "ADSM: Dist Stor Manager" Datum: 03/25/2011 15:41 Ärende: TSM for DB password expiration Has anyone had problems with TSM for DB (Oracle), aka TDPO, and password expiration? We are running TSM for DB v5.5.1.0 with TSM api 6.2.2.0 on AIX 5.3 to a TSM server at 6.2.2.0 also on AIX 5.3. We are running with password generate. Last night we got two ANR0425W password has expired messages for node DBFINTEST. I assume I got two messages because the rman command is using two channels, thus two concurrent TSM sessions. At that point the password should have been set to something new and life should go on. Instead, subsequent sessions for that node got the "ANS0282E Password file is not available.", ie password is incorrect, message. Any thoughts on what might be going wrong? David Ehresman
Re: Ang: TSM for DB password expiration
Are you saying that "password generate" does not work for TSM for DB? >>> Daniel Sparrman 3/25/2011 9:52 AM >>> Hi David Correct me if I'm wrong, but when the nodes password has expired, passwordaccess generate will not set a new password for the client. You'll have to set a new password for the node, and then use tdpoconf to update the stored password on the client machine. Best Regards Daniel Sparrman -"ADSM: Dist Stor Manager" skrev: - Till: ADSM-L@VM.MARIST.EDU Från: David E Ehresman Sänt av: "ADSM: Dist Stor Manager" Datum: 03/25/2011 15:41 Ärende: TSM for DB password expiration Has anyone had problems with TSM for DB (Oracle), aka TDPO, and password expiration? We are running TSM for DB v5.5.1.0 with TSM api 6.2.2.0 on AIX 5.3 to a TSM server at 6.2.2.0 also on AIX 5.3. We are running with password generate. Last night we got two ANR0425W password has expired messages for node DBFINTEST. I assume I got two messages because the rman command is using two channels, thus two concurrent TSM sessions. At that point the password should have been set to something new and life should go on. Instead, subsequent sessions for that node got the "ANS0282E Password file is not available.", ie password is incorrect, message. Any thoughts on what might be going wrong? David Ehresman
Re: Ang: TSM for DB password expiration
For the Oracle TDP on AIX you have to set the passwordaccess option to prompt, as the TDP will NOT update the password. The best option here is to set the password expiration to 0 on both the node, and the admin owner (if you have it) of the node. However, what Daniel said is correct unless you run "update node server-oracle passexp=0" AND "update admin server-oracle passexp=0", then it will just keep on using the same password. See Ya' Howard Coles Jr., RHCE, CNE, CDE John 3:16! -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Daniel Sparrman Sent: Friday, March 25, 2011 8:52 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Ang: TSM for DB password expiration Hi David Correct me if I'm wrong, but when the nodes password has expired, passwordaccess generate will not set a new password for the client. You'll have to set a new password for the node, and then use tdpoconf to update the stored password on the client machine. Best Regards Daniel Sparrman -"ADSM: Dist Stor Manager" skrev: - Till: ADSM-L@VM.MARIST.EDU Från: David E Ehresman Sänt av: "ADSM: Dist Stor Manager" Datum: 03/25/2011 15:41 Ärende: TSM for DB password expiration Has anyone had problems with TSM for DB (Oracle), aka TDPO, and password expiration? We are running TSM for DB v5.5.1.0 with TSM api 6.2.2.0 on AIX 5.3 to a TSM server at 6.2.2.0 also on AIX 5.3. We are running with password generate. Last night we got two ANR0425W password has expired messages for node DBFINTEST. I assume I got two messages because the rman command is using two channels, thus two concurrent TSM sessions. At that point the password should have been set to something new and life should go on. Instead, subsequent sessions for that node got the "ANS0282E Password file is not available.", ie password is incorrect, message. Any thoughts on what might be going wrong? David Ehresman
Re: Ang: TSM for DB password expiration
And is Oracle TDP on Linux different than on AIX? Does password generate on linux? David >>> Howard Coles 3/25/2011 11:21 AM >>> For the Oracle TDP on AIX you have to set the passwordaccess option to prompt, as the TDP will NOT update the password. The best option here is to set the password expiration to 0 on both the node, and the admin owner (if you have it) of the node. However, what Daniel said is correct unless you run "update node server-oracle passexp=0" AND "update admin server-oracle passexp=0", then it will just keep on using the same password. See Ya' Howard Coles Jr., RHCE, CNE, CDE John 3:16! -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Daniel Sparrman Sent: Friday, March 25, 2011 8:52 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Ang: TSM for DB password expiration Hi David Correct me if I'm wrong, but when the nodes password has expired, passwordaccess generate will not set a new password for the client. You'll have to set a new password for the node, and then use tdpoconf to update the stored password on the client machine. Best Regards Daniel Sparrman -"ADSM: Dist Stor Manager" skrev: - Till: ADSM-L@VM.MARIST.EDU Från: David E Ehresman Sänt av: "ADSM: Dist Stor Manager" Datum: 03/25/2011 15:41 Ärende: TSM for DB password expiration Has anyone had problems with TSM for DB (Oracle), aka TDPO, and password expiration? We are running TSM for DB v5.5.1.0 with TSM api 6.2.2.0 on AIX 5.3 to a TSM server at 6.2.2.0 also on AIX 5.3. We are running with password generate. Last night we got two ANR0425W password has expired messages for node DBFINTEST. I assume I got two messages because the rman command is using two channels, thus two concurrent TSM sessions. At that point the password should have been set to something new and life should go on. Instead, subsequent sessions for that node got the "ANS0282E Password file is not available.", ie password is incorrect, message. Any thoughts on what might be going wrong? David Ehresman
Re: Ang: TSM for DB password expiration
No, it's not different, Oracle TDP works the same on Linux and AIX. The only TDP I'm not sure of is the Windows version, but if I remember correctly it doesn't reset the password either. See Ya' Howard Coles Jr., RHCE, CNE, CDE John 3:16! -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of David E Ehresman Sent: Friday, March 25, 2011 10:34 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Ang: TSM for DB password expiration And is Oracle TDP on Linux different than on AIX? Does password generate on linux? David >>> Howard Coles 3/25/2011 11:21 AM >>> For the Oracle TDP on AIX you have to set the passwordaccess option to prompt, as the TDP will NOT update the password. The best option here is to set the password expiration to 0 on both the node, and the admin owner (if you have it) of the node. However, what Daniel said is correct unless you run "update node server-oracle passexp=0" AND "update admin server-oracle passexp=0", then it will just keep on using the same password. See Ya' Howard Coles Jr., RHCE, CNE, CDE John 3:16! -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Daniel Sparrman Sent: Friday, March 25, 2011 8:52 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Ang: TSM for DB password expiration Hi David Correct me if I'm wrong, but when the nodes password has expired, passwordaccess generate will not set a new password for the client. You'll have to set a new password for the node, and then use tdpoconf to update the stored password on the client machine. Best Regards Daniel Sparrman -"ADSM: Dist Stor Manager" skrev: - Till: ADSM-L@VM.MARIST.EDU Från: David E Ehresman Sänt av: "ADSM: Dist Stor Manager" Datum: 03/25/2011 15:41 Ärende: TSM for DB password expiration Has anyone had problems with TSM for DB (Oracle), aka TDPO, and password expiration? We are running TSM for DB v5.5.1.0 with TSM api 6.2.2.0 on AIX 5.3 to a TSM server at 6.2.2.0 also on AIX 5.3. We are running with password generate. Last night we got two ANR0425W password has expired messages for node DBFINTEST. I assume I got two messages because the rman command is using two channels, thus two concurrent TSM sessions. At that point the password should have been set to something new and life should go on. Instead, subsequent sessions for that node got the "ANS0282E Password file is not available.", ie password is incorrect, message. Any thoughts on what might be going wrong? David Ehresman
Re: Ang: TSM for DB password expiration
Hi, since TDP for Oracle version 5.5.1 on Unix systems 'passsordaccess=generate' may be used. The TSM API is then taking care about password issues. best regards, Rainer > -Original Message- > From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf > Of Howard Coles > Sent: Friday, March 25, 2011 5:11 PM > To: ADSM-L@VM.MARIST.EDU > Subject: Re: [ADSM-L] Ang: TSM for DB password expiration > > No, it's not different, Oracle TDP works the same on Linux and AIX. > The only TDP I'm not sure of is the Windows version, but if I remember > correctly it doesn't reset the password either. > > > See Ya' > Howard Coles Jr., RHCE, CNE, CDE > John 3:16! > > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf > Of David E Ehresman > Sent: Friday, March 25, 2011 10:34 AM > To: ADSM-L@VM.MARIST.EDU > Subject: Re: [ADSM-L] Ang: TSM for DB password expiration > > And is Oracle TDP on Linux different than on AIX? Does password > generate on linux? > > David > > >>> Howard Coles 3/25/2011 11:21 AM > >>> > For the Oracle TDP on AIX you have to set the passwordaccess option to > prompt, as the TDP will NOT update the password. The best option here > is to set the password expiration to 0 on both the node, and the admin > owner (if you have it) of the node. > > However, what Daniel said is correct unless you run "update node > server-oracle passexp=0" AND "update admin server-oracle passexp=0", > then it will just keep on using the same password. > > > See Ya' > Howard Coles Jr., RHCE, CNE, CDE > John 3:16! > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf > Of Daniel Sparrman > Sent: Friday, March 25, 2011 8:52 AM > To: ADSM-L@VM.MARIST.EDU > Subject: [ADSM-L] Ang: TSM for DB password expiration > > Hi David > > Correct me if I'm wrong, but when the nodes password has expired, > passwordaccess generate will not set a new password for the client. > You'll have to set a new password for the node, and then use tdpoconf > to update the stored password on the client machine. > > Best Regards > > Daniel Sparrman > -"ADSM: Dist Stor Manager" skrev: - > > Till: ADSM-L@VM.MARIST.EDU > Från: David E Ehresman > Sänt av: "ADSM: Dist Stor Manager" > Datum: 03/25/2011 15:41 > Ärende: TSM for DB password expiration > > Has anyone had problems with TSM for DB (Oracle), aka TDPO, and > password > expiration? > > We are running TSM for DB v5.5.1.0 with TSM api 6.2.2.0 on AIX 5.3 to > a > TSM server at 6.2.2.0 also on AIX 5.3. We are running with password > generate. Last night we got two ANR0425W password has expired > messages > for node DBFINTEST. I assume I got two messages because the rman > command > is using two channels, thus two concurrent TSM sessions. At that > point > the password should have been set to something new and life should go > on. Instead, subsequent sessions for that node got the "ANS0282E > Password file is not available.", ie password is incorrect, message. > > Any thoughts on what might be going wrong? > > David Ehresman
Re: Ang: TSM for DB password expiration
Hi, As I know, from TDP for DB (Oracle) v.5.4.? option passwordaccess generate is fully supported. Try to check that TSM.PWD owned by Oracle user. If not - TDP can't change password. Password must be changed automatically and immediately after ANR0425W message. Efim 2011/3/25 Howard Coles : > No, it's not different, Oracle TDP works the same on Linux and AIX. The only > TDP I'm not sure of is the Windows version, but if I remember correctly it > doesn't reset the password either. > > > See Ya' > Howard Coles Jr., RHCE, CNE, CDE > John 3:16! > > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of > David E Ehresman > Sent: Friday, March 25, 2011 10:34 AM > To: ADSM-L@VM.MARIST.EDU > Subject: Re: [ADSM-L] Ang: TSM for DB password expiration > > And is Oracle TDP on Linux different than on AIX? Does password generate on > linux? > > David > Howard Coles 3/25/2011 11:21 AM >>> > For the Oracle TDP on AIX you have to set the passwordaccess option to > prompt, as the TDP will NOT update the password. The best option here is to > set the password expiration to 0 on both the node, and the admin owner (if > you have it) of the node. > > However, what Daniel said is correct unless you run "update node > server-oracle passexp=0" AND "update admin server-oracle passexp=0", then it > will just keep on using the same password. > > > See Ya' > Howard Coles Jr., RHCE, CNE, CDE > John 3:16! > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of > Daniel Sparrman > Sent: Friday, March 25, 2011 8:52 AM > To: ADSM-L@VM.MARIST.EDU > Subject: [ADSM-L] Ang: TSM for DB password expiration > > Hi David > > Correct me if I'm wrong, but when the nodes password has expired, > passwordaccess generate will not set a new password for the client. You'll > have to set a new password for the node, and then use tdpoconf to update the > stored password on the client machine. > > Best Regards > > Daniel Sparrman > -"ADSM: Dist Stor Manager" skrev: - > > Till: ADSM-L@VM.MARIST.EDU > Från: David E Ehresman > Sänt av: "ADSM: Dist Stor Manager" > Datum: 03/25/2011 15:41 > Ärende: TSM for DB password expiration > > Has anyone had problems with TSM for DB (Oracle), aka TDPO, and password > expiration? > > We are running TSM for DB v5.5.1.0 with TSM api 6.2.2.0 on AIX 5.3 to a > TSM server at 6.2.2.0 also on AIX 5.3. We are running with password > generate. Last night we got two ANR0425W password has expired messages > for node DBFINTEST. I assume I got two messages because the rman command > is using two channels, thus two concurrent TSM sessions. At that point > the password should have been set to something new and life should go > on. Instead, subsequent sessions for that node got the "ANS0282E > Password file is not available.", ie password is incorrect, message. > > Any thoughts on what might be going wrong? > > David Ehresman > -- Efim
[no subject]
We are seeing activity log messages like the following: ANE4987E (Session: 326356, Node: STMEDIA) Error processing '\\stmedia\c$\Windows\System32\SMI\Store\Machine\SCHEMA.DAT.LOG1': the object is in use by another process for a number of Windows 2008 client systems with 6.2.1.0 client code. Is this going to compromise our ability to recover these systems?
TSM Parallel restores question
I'm looking into methods for HSM for my company. One of the requirements I have is that restores must use the maximum speed we can achieve. I have looked at several TSM pages, but couldn't find something that explicitly explains how parallel restores (the NQR option) are going to be performed. My specific question is: Do all copies have to go over the server or can they go over different paths? For example: 2 files (F1,F2) are to be restored to two different primary systems (P1,P2) from 2 different secondary storage systems (S1,S2). Does TSM support a physical connection like the one shown bellow in a) or does it have to be a connection such as the one shown in b) a) P1 <- F1 -- S1 P2 <- F2 -- S2 b) P1 <--F1---\/---F1 S1 - Server -- P2 <--F2---/\---F2 S2 +-- |This was sent by andres...@gmail.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +--
Re: TSM Parallel restores question
HSM and backup-restore are very different concepts with equally different handling and, usually, architecture. While backup/restore is essentially serialized, HSM is on demand parallelized via independent processes. Define your objectives and then seek a storage architecture to fit the needs. Richard Sims On Mar 25, 2011, at 4:26 PM, andresms5 wrote: > I'm looking into methods for HSM for my company. > > One of the requirements I have is that restores must use the maximum speed we > can achieve. > > I have looked at several TSM pages, but couldn't find something that > explicitly explains how parallel restores (the NQR option) are going to be > performed. > > My specific question is: Do all copies have to go over the server or can they > go over different paths? > > For example: > 2 files (F1,F2) are to be restored to two different primary systems (P1,P2) > from 2 different secondary storage systems (S1,S2). Does TSM support a > physical connection like the one shown bellow in a) or does it have to be a > connection such as the one shown in b) > a) > P1 <- F1 -- S1 > P2 <- F2 -- S2 > > b) > P1 <--F1---\/---F1 S1 >- Server -- > P2 <--F2---/\---F2 S2 > > +-- > |This was sent by andres...@gmail.com via Backup Central. > |Forward SPAM to ab...@backupcentral.com. > +--
