Re: "reseting" 6.2 server : what are the steps to get the DB virgin again ?
I just did this shutdown TSM delete contents of db, active log and archive log directories, run dsmserv format. Regards Steve. On 22/02/2011 12:16 AM, PAC Brion Arnaud wrote: Hi All, I installed a TSM 6.2.0.0 server some times ago, where I'm now facing nasty IC71983 bug (slow Win2k8 system backup objects deletion). As this server is just a test instance that I would like to have emptied, and as I would like to avoid to install a maintenance level just in order to be able applying some eFix, I thought that it would be easier to "reset" the existing server, then to re-inject the previously extracted server scripts into it, using macros. Could anyone provide me a list of steps required to reset the DB on a TSM 6.2 server ? I do not want to change anything in the DB or LOGS layout, just have the volumes initialized ... I suppose that I should use the "dsmserv format" command, but would avoid to do mistakes in the brand new (at least for me) DB2 world Thanks in advance for your tips ! Cheers. Arnaud ** Corporate IT Systems& Datacenter Responsible Panalpina Management Ltd., Basle, Switzerland, CIT Department Viadukstrasse 42, P.O. Box 4002 Basel/CH Phone: +41 (61) 226 11 11, FAX: +41 (61) 226 17 01 Direct: +41 (61) 226 19 78 e-mail: arnaud.br...@panalpina.com **
Re: When is a TDP backup NOT a TDP backup
Hello Zoltan, It probably works but it is not officially supported. Thanks, Del "ADSM: Dist Stor Manager" wrote on 02/21/2011 01:05:16 PM: >> From: Zoltan Forray/AC/VCU >> To: ADSM-L@vm.marist.edu >> Date: 02/21/2011 01:20 PM >> Subject: When is a TDP backup NOT a TDP backup >> Sent by: "ADSM: Dist Stor Manager" >> >> I just got a strange call from a user. >> >> He wanted to know how his box is performing TDP backups of his SQLEXPRESS >> databases yet the SQL TDP is not installed? (I signed onto the box myself >> and inspected the "Program Files" directory) >> >> A check of the nodes filespaces does list SQLEXPRESS\meta and >> SQLEXPRESS\data filespaces. >> >> IIRC from earlier discussions here, SQLEXPRESS is NOT supported by the SQL >> TDP product, anyway? >> >> I am thoroughly confused! >> Zoltan Forray >> TSM Software & Hardware Administrator >> Virginia Commonwealth University >> UCC/Office of Technology Services >> zfor...@vcu.edu - 804-828-4807
When is a TDP backup NOT a TDP backup
I just got a strange call from a user. He wanted to know how his box is performing TDP backups of his SQLEXPRESS databases yet the SQL TDP is not installed? (I signed onto the box myself and inspected the "Program Files" directory) A check of the nodes filespaces does list SQLEXPRESS\meta and SQLEXPRESS\data filespaces. IIRC from earlier discussions here, SQLEXPRESS is NOT supported by the SQL TDP product, anyway? I am thoroughly confused! Zoltan Forray TSM Software & Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html
Re: RE : [ADSM-L] How many disk volumes are too many?
This is primarily for the disk LZ - backups come in (sequential and random write) and are then migrated to tape (sequential and random read) plus possible restores (sequential and random reads). Zoltan Forray TSM Software & Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html From: molin gregory To: ADSM-L@VM.MARIST.EDU Date: 02/21/2011 04:23 AM Subject: [ADSM-L] RE : [ADSM-L] How many disk volumes are too many? Sent by: "ADSM: Dist Stor Manager" Hello Zoltan, First is to know if this volumes are for sequential or random access. In our configuration, we have 3 100Go volumes for random access and more than 500 volumes of 20Go for sequential access. The first avantage off have many small volumes cause TSM using as many volumes is want. (maximun mount point for the devclass) The second, is to be able to reclaim very quickly such volumes. In our case, we reclaim with a threshold=40. Cordialement, Regards, Grégory De : ADSM: Dist Stor Manager [ADSM-L@VM.MARIST.EDU] de la part de Zoltan Forray/AC/VCU [zfor...@vcu.edu] Date d'envoi : jeudi 17 février 2011 19:15 À : ADSM-L@VM.MARIST.EDU Objet : [ADSM-L] How many disk volumes are too many? I am aware of the TSM design that says the more disk volumes you have, the more it will spread out the I/O for better performance. I also realize a lot of this doesn't really apply what with RAID-5, EMC SAN, multi-terabyte storage, etc. So, at what point does having lots of smaller volumes (for a disk LZ), not give you any more benefit, I/O wise? I have a 5.3TB SAN space on my new 6.2.2.0 server. Originally, I started formatting 200GB volumes then moved to 300GB, up to 25-volumes. Now I am adding another 5.3TB space and was wondering if I should continue with 300GB or jump to 500GB? Simultaneous sessions should not be an issue since most of these backups are Domino TDP and therefore single thread. I don't think there is a peak of more than 60-simultaneous sessions. The TSM server is a Dell T710 with 48GB RAM and 15K internal disk for the DB & Logs. Your thoughts? Zoltan Forray TSM Software & Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html "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. "
"reseting" 6.2 server : what are the steps to get the DB virgin again ?
Hi All, I installed a TSM 6.2.0.0 server some times ago, where I'm now facing nasty IC71983 bug (slow Win2k8 system backup objects deletion). As this server is just a test instance that I would like to have emptied, and as I would like to avoid to install a maintenance level just in order to be able applying some eFix, I thought that it would be easier to "reset" the existing server, then to re-inject the previously extracted server scripts into it, using macros. Could anyone provide me a list of steps required to reset the DB on a TSM 6.2 server ? I do not want to change anything in the DB or LOGS layout, just have the volumes initialized ... I suppose that I should use the "dsmserv format" command, but would avoid to do mistakes in the brand new (at least for me) DB2 world Thanks in advance for your tips ! Cheers. Arnaud ** Corporate IT Systems & Datacenter Responsible Panalpina Management Ltd., Basle, Switzerland, CIT Department Viadukstrasse 42, P.O. Box 4002 Basel/CH Phone: +41 (61) 226 11 11, FAX: +41 (61) 226 17 01 Direct: +41 (61) 226 19 78 e-mail: arnaud.br...@panalpina.com **
RE : [ADSM-L] How many disk volumes are too many?
Hello Zoltan, First is to know if this volumes are for sequential or random access. In our configuration, we have 3 100Go volumes for random access and more than 500 volumes of 20Go for sequential access. The first avantage off have many small volumes cause TSM using as many volumes is want. (maximun mount point for the devclass) The second, is to be able to reclaim very quickly such volumes. In our case, we reclaim with a threshold=40. Cordialement, Regards, Grégory De : ADSM: Dist Stor Manager [ADSM-L@VM.MARIST.EDU] de la part de Zoltan Forray/AC/VCU [zfor...@vcu.edu] Date d'envoi : jeudi 17 février 2011 19:15 À : ADSM-L@VM.MARIST.EDU Objet : [ADSM-L] How many disk volumes are too many? I am aware of the TSM design that says the more disk volumes you have, the more it will spread out the I/O for better performance. I also realize a lot of this doesn't really apply what with RAID-5, EMC SAN, multi-terabyte storage, etc. So, at what point does having lots of smaller volumes (for a disk LZ), not give you any more benefit, I/O wise? I have a 5.3TB SAN space on my new 6.2.2.0 server. Originally, I started formatting 200GB volumes then moved to 300GB, up to 25-volumes. Now I am adding another 5.3TB space and was wondering if I should continue with 300GB or jump to 500GB? Simultaneous sessions should not be an issue since most of these backups are Domino TDP and therefore single thread. I don't think there is a peak of more than 60-simultaneous sessions. The TSM server is a Dell T710 with 48GB RAM and 15K internal disk for the DB & Logs. Your thoughts? Zoltan Forray TSM Software & Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html "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. "
