Re: TSM Server DB Backups
Our sequence: backup db backup disk to copy pool migration cartridge primary pool to copypool (in case some did not complete before migration) db backup expiration reclamation >>> [EMAIL PROTECTED] 07/18/2007 2:13 PM >>> Wouldn't you want to backup primary to copy before migration? That way you're doing that from disk. If you migrate then backup primary to copy, you're doing the copy from tape to tape, rather than from disk to tape. In addition, it gets your offsite copies created earlier in the cycle, so that you can hand them to your offsite storage vendor. What about this order? Backup Backup primary to copy Backup db Get copies & DB backup offsite Migration Expiration Reclamation Second DB backup if you've got time (perhaps to disk) Start all over again --- W. Curtis Preston Backup Blog @ www.backupcentral.com VP Data Protection, GlassHouse Technologies -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Mark Scott Sent: Wednesday, July 18, 2007 6:30 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM Server DB Backups I believe the best practise is Backup Migration Backup primary to copy Backup db Expiration Reclamation Start all over again :) Cheers -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Timothy Hughes Sent: Wednesday, 18 July 2007 9:14 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM Server DB Backups We actually backup ours after nightly backups complete and before migration. Is there a specific recommended order or is it up to each individual site and it's environment? Helder Garcia wrote: > You should backup db after migration and before expiration. > > On 7/17/07, Gregory Lynch <[EMAIL PROTECTED]> wrote: > >> >> Hello all, >> >> How many times a day should I be backing up the TSM DB and should it be >> after migration? >> >> >> Thanks >> >> Greg >> >> >> *** >> Gregory Lynch >> Lead Programmer Analyst >> IT Infrastructure/Systems Administration >> Stony Brook University Medical Center >> HSC Level 3, Room 121 ZIP 8037 >> Phone: 631-444-9783 >> [EMAIL PROTECTED] >> >> This e- mail message, including any attachments, >> is for the sole use of the intended recipient(s) and may >> contain confidential and privileged information. >> Any unauthorized review, use, disclosure or distribution is prohibited. >> If you are not the intended recipient, please contact the sender >> by e-mail and destroy all copies of the original. >> > > > > -- > Helder Garcia Bunnings Legal Disclaimer: 1) This email is confidential and may contain legally privileged information. If you are not the intended recipient, you must not disclose or use the information contained in it. If you have received this email in error, please notify us immediately by return email and delete the document. 2) All emails sent to and sent from Bunnings Group Limited. are scanned for content. Any material deemed to contain inappropriate subject matter will be reported to the email administrator of all parties concerned. The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain information that is confidential, privileged, and/or otherwise exempt from disclosure under applicable law. If this electronic message is from an attorney or someone in the Legal Department, it may also contain confidential attorney-client communications which may be privileged and protected from disclosure. If you are not the intended recipient, be advised that you have received this message in error and that any use, dissemination, forwarding, printing, or copying is strictly prohibited. Please notify the New York State Thruway Authority immediately by either responding to this e-mail or calling (518) 436-2700, and destroy all copies of this message and any attachments.
Re: TSM Server DB Backups
Wouldn't you want to backup primary to copy before migration? That way you're doing that from disk. If you migrate then backup primary to copy, you're doing the copy from tape to tape, rather than from disk to tape. In addition, it gets your offsite copies created earlier in the cycle, so that you can hand them to your offsite storage vendor. What about this order? Backup Backup primary to copy Backup db Get copies & DB backup offsite Migration Expiration Reclamation Second DB backup if you've got time (perhaps to disk) Start all over again --- W. Curtis Preston Backup Blog @ www.backupcentral.com VP Data Protection, GlassHouse Technologies -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Mark Scott Sent: Wednesday, July 18, 2007 6:30 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM Server DB Backups I believe the best practise is Backup Migration Backup primary to copy Backup db Expiration Reclamation Start all over again :) Cheers -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Timothy Hughes Sent: Wednesday, 18 July 2007 9:14 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM Server DB Backups We actually backup ours after nightly backups complete and before migration. Is there a specific recommended order or is it up to each individual site and it's environment? Helder Garcia wrote: > You should backup db after migration and before expiration. > > On 7/17/07, Gregory Lynch <[EMAIL PROTECTED]> wrote: > >> >> Hello all, >> >> How many times a day should I be backing up the TSM DB and should it be >> after migration? >> >> >> Thanks >> >> Greg >> >> >> *** >> Gregory Lynch >> Lead Programmer Analyst >> IT Infrastructure/Systems Administration >> Stony Brook University Medical Center >> HSC Level 3, Room 121 ZIP 8037 >> Phone: 631-444-9783 >> [EMAIL PROTECTED] >> >> This e- mail message, including any attachments, >> is for the sole use of the intended recipient(s) and may >> contain confidential and privileged information. >> Any unauthorized review, use, disclosure or distribution is prohibited. >> If you are not the intended recipient, please contact the sender >> by e-mail and destroy all copies of the original. >> > > > > -- > Helder Garcia Bunnings Legal Disclaimer: 1) This email is confidential and may contain legally privileged information. If you are not the intended recipient, you must not disclose or use the information contained in it. If you have received this email in error, please notify us immediately by return email and delete the document. 2) All emails sent to and sent from Bunnings Group Limited. are scanned for content. Any material deemed to contain inappropriate subject matter will be reported to the email administrator of all parties concerned.
Re: TSM Server DB Backups
I agree with Mark on this one, with the exception that I would do the drm processing after backing up the primary to the copypool, and then backup the db and then run a prepare. That way the copypool volumes show up as offsite and won't be marked as destroyed in case of a disaster. Cory Heikel Tivoli Systems Administrator Hershey Medical Center (717) 531-7972 >>> Mark Scott <[EMAIL PROTECTED]> 7/18/2007 9:29 AM >>> I believe the best practise is Backup Migration Backup primary to copy Backup db Expiration Reclamation Start all over again :) Cheers -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Timothy Hughes Sent: Wednesday, 18 July 2007 9:14 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM Server DB Backups We actually backup ours after nightly backups complete and before migration. Is there a specific recommended order or is it up to each individual site and it's environment? Helder Garcia wrote: > You should backup db after migration and before expiration. > > On 7/17/07, Gregory Lynch <[EMAIL PROTECTED]> wrote: > >> >> Hello all, >> >> How many times a day should I be backing up the TSM DB and should it be >> after migration? >> >> >> Thanks >> >> Greg >> >> >> *** >> Gregory Lynch >> Lead Programmer Analyst >> IT Infrastructure/Systems Administration >> Stony Brook University Medical Center >> HSC Level 3, Room 121 ZIP 8037 >> Phone: 631-444-9783 >> [EMAIL PROTECTED] >> >> This e- mail message, including any attachments, >> is for the sole use of the intended recipient(s) and may >> contain confidential and privileged information. >> Any unauthorized review, use, disclosure or distribution is prohibited. >> If you are not the intended recipient, please contact the sender >> by e-mail and destroy all copies of the original. >> > > > > -- > Helder Garcia Bunnings Legal Disclaimer: 1) This email is confidential and may contain legally privileged information. If you are not the intended recipient, you must not disclose or use the information contained in it. If you have received this email in error, please notify us immediately by return email and delete the document. 2) All emails sent to and sent from Bunnings Group Limited. are scanned for content. Any material deemed to contain inappropriate subject matter will be reported to the email administrator of all parties concerned.
Re: TSM Server DB Backups
As always, it depends . . . Our TSM DB is on raided enterprise disk (IBM DS8100 behind a SAN Volume control) as is our TSM LOGs. We run our logs in roll forward mode. The odds of losing both the DB and LOG except in a DR situation is small. If we have to restore the DB, we can roll forward using the logs. If we lose the logs, we can do a DB backups and have a clean restore point with the new logs. So DR is our main concern. Therefore, we backup DB right after our Backup STG to make offsite copies of the data. Our order is: Backup Backup Primary to copy Backup DB Move copy and DB offsite Migrate primary disk to primary tape Expiration Reclamation Start all over again We do backup stg before migration so 1) we can do the bulk of our copy pool creation disk to tape rather than tape to tape, 2) get data offsite as quickly as possible. David Ehresman University of Louisville >>> Mark Scott <[EMAIL PROTECTED]> 7/18/2007 9:29 AM >>> I believe the best practise is Backup Migration Backup primary to copy Backup db Expiration Reclamation Start all over again :) Cheers -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Timothy Hughes Sent: Wednesday, 18 July 2007 9:14 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM Server DB Backups We actually backup ours after nightly backups complete and before migration. Is there a specific recommended order or is it up to each individual site and it's environment? Helder Garcia wrote: > You should backup db after migration and before expiration. > > On 7/17/07, Gregory Lynch <[EMAIL PROTECTED]> wrote: > >> >> Hello all, >> >> How many times a day should I be backing up the TSM DB and should it be >> after migration? >> >> >> Thanks >> >> Greg >> >> >> *** >> Gregory Lynch >> Lead Programmer Analyst >> IT Infrastructure/Systems Administration >> Stony Brook University Medical Center >> HSC Level 3, Room 121 ZIP 8037 >> Phone: 631-444-9783 >> [EMAIL PROTECTED] >> >> This e- mail message, including any attachments, >> is for the sole use of the intended recipient(s) and may >> contain confidential and privileged information. >> Any unauthorized review, use, disclosure or distribution is prohibited. >> If you are not the intended recipient, please contact the sender >> by e-mail and destroy all copies of the original. >> > > > > -- > Helder Garcia Bunnings Legal Disclaimer: 1) This email is confidential and may contain legally privileged information. If you are not the intended recipient, you must not disclose or use the information contained in it. If you have received this email in error, please notify us immediately by return email and delete the document. 2) All emails sent to and sent from Bunnings Group Limited. are scanned for content. Any material deemed to contain inappropriate subject matter will be reported to the email administrator of all parties concerned.
Re: TSM Server DB Backups
I believe the best practise is Backup Migration Backup primary to copy Backup db Expiration Reclamation Start all over again :) Cheers -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Timothy Hughes Sent: Wednesday, 18 July 2007 9:14 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM Server DB Backups We actually backup ours after nightly backups complete and before migration. Is there a specific recommended order or is it up to each individual site and it's environment? Helder Garcia wrote: > You should backup db after migration and before expiration. > > On 7/17/07, Gregory Lynch <[EMAIL PROTECTED]> wrote: > >> >> Hello all, >> >> How many times a day should I be backing up the TSM DB and should it be >> after migration? >> >> >> Thanks >> >> Greg >> >> >> *** >> Gregory Lynch >> Lead Programmer Analyst >> IT Infrastructure/Systems Administration >> Stony Brook University Medical Center >> HSC Level 3, Room 121 ZIP 8037 >> Phone: 631-444-9783 >> [EMAIL PROTECTED] >> >> This e- mail message, including any attachments, >> is for the sole use of the intended recipient(s) and may >> contain confidential and privileged information. >> Any unauthorized review, use, disclosure or distribution is prohibited. >> If you are not the intended recipient, please contact the sender >> by e-mail and destroy all copies of the original. >> > > > > -- > Helder Garcia Bunnings Legal Disclaimer: 1) This email is confidential and may contain legally privileged information. If you are not the intended recipient, you must not disclose or use the information contained in it. If you have received this email in error, please notify us immediately by return email and delete the document. 2) All emails sent to and sent from Bunnings Group Limited. are scanned for content. Any material deemed to contain inappropriate subject matter will be reported to the email administrator of all parties concerned.
Re: TSM Server DB Backups
Hi, You plan your ITSM db backups depending on how much data you want to loose or time want to spent rerunning ran jobs (...). And things like re-use delays on storage pools should be also taken into account. After having to deal with a database restore to a point before the last reclamation run of our primary storage pools without having reuse delay set >0, we are a bit more carefull. Regards, Karel -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Timothy Hughes Sent: woensdag 18 juli 2007 15:14 To: ADSM-L@VM.MARIST.EDU Subject: Re: TSM Server DB Backups We actually backup ours after nightly backups complete and before migration. Is there a specific recommended order or is it up to each individual site and it's environment? Helder Garcia wrote: > You should backup db after migration and before expiration. > > On 7/17/07, Gregory Lynch <[EMAIL PROTECTED]> wrote: > >> >> Hello all, >> >> How many times a day should I be backing up the TSM DB and should it >> be after migration? >> >> >> Thanks >> >> Greg >> >> >> *** >> Gregory Lynch >> Lead Programmer Analyst >> IT Infrastructure/Systems Administration Stony Brook University >> Medical Center HSC Level 3, Room 121 ZIP 8037 >> Phone: 631-444-9783 >> [EMAIL PROTECTED] >> >> This e- mail message, including any attachments, is for the sole use >> of the intended recipient(s) and may contain confidential and >> privileged information. >> Any unauthorized review, use, disclosure or distribution is prohibited. >> If you are not the intended recipient, please contact the sender by >> e-mail and destroy all copies of the original. >> > > > > -- > Helder Garcia ÿþD i t b e r i c h t i s v e r t r o u w e l i j k e n k a n g e h e i m e i n f o r m a t i e b e v a t t e n e n k e l b e s t e m d v o o r d e g e a d r e s s e e r d e . I n d i e n d i t b e r i c h t n i e t v o o r u i s b e s t e m d , v e r z o e k e n w i j u d i t o n m i d d e l l i j k a a n o n s t e m e l d e n e n h e t b e r i c h t t e v e r n i e t i g e n . A a n g e z i e n d e i n t e g r i t e i t v a n h e t b e r i c h t n i e t v e i l i g g e s t e l d i s m i d d e l s v e r z e n d i n g v i a i n t e r n e t , k a n A t o s O r i g i n n i e t a a n s p r a k e l i j k w o r d e n g e h o u d e n v o o r d e i n h o u d d a a r v a n . H o e w e l w i j o n s i n s p a n n e n e e n v i r u s v r i j n e t w e r k t e h a n t e r e n , g e v e n w i j g e e n e n k e l e g a r a n t i e d a t d i t b e r i c h t v i r u s v r i j i s , n o c h a a n v a a r d e n w i j e n i g e a a n s p r a k e l i j k h e i d v o o r d e m o g e l i j k e a a n w e z i g h e i d v a n e e n v i r u s i n d i t b e r i c h t . O p a l o n z e r e c h t s v e r h o u d i n g e n , a a n b i e d i n g e n e n o v e r e e n k o m s t e n w a a r o n d e r A t o s O r i g i n g o e d e r e n e n / o f d i e n s t e n l e v e r t z i j n m e t u i t s l u i t i n g v a n a l l e a n d e r e v o o r w a a r d e n d e L e v e r i n g s v o o r w a a r d e n v a n A t o s O r i g i n v a n t o e p a s s i n g . D e z e w o r d e n u o p a a n v r a a g d i r e c t k o s t e l o o s t o e g e z o n d e n . T h i s e - m a i l a n d t h e d o c u m e n t s a t t a c h e d a r e c o n f i d e n t i a l a n d i n t e n d e d s o l e l y f o r t h e a d d r e s s e e ; i t m a y a l s o b e p r i v i l e g e d . I f y o u r e c e i v e t h i s e - m a i l i n e r r o r , p l e a s e n o t i f y t h e s e n d e r i m m e d i a t e l y a n d d e s t r o y i t . A s i t s i n t e g r i t y c a n n o t b e s e c u r e d o n t h e I n t e r n e t , t h e A t o s O r i g i n g r o u p l i a b i l i t y c a n n o t b e t r i g g e r e d f o r t h e m e s s a g e c o n t e n t . A l t h o u g h t h e s e n d e r e n d e a v o u r s t o m a i n t a i n a c o m p u t e r v i r u s - f r e e n e t w o r k , t h e s e n d e r d o e s n o t w a r r a n t t h a t t h i s t r a n s m i s s i o n i s v i r u s - f r e e a n d w i l l n o t b e l i a b l e f o r a n y d a m a g e s r e s u l t i n g f r o m a n y v i r u s t r a n s m i t t e d . O n a l l o f f e r s a n d a
Re: TSM Server DB Backups
We actually backup ours after nightly backups complete and before migration. Is there a specific recommended order or is it up to each individual site and it's environment? Helder Garcia wrote: You should backup db after migration and before expiration. On 7/17/07, Gregory Lynch <[EMAIL PROTECTED]> wrote: Hello all, How many times a day should I be backing up the TSM DB and should it be after migration? Thanks Greg *** Gregory Lynch Lead Programmer Analyst IT Infrastructure/Systems Administration Stony Brook University Medical Center HSC Level 3, Room 121 ZIP 8037 Phone: 631-444-9783 [EMAIL PROTECTED] This e- mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by e-mail and destroy all copies of the original. -- Helder Garcia
Re: TSM Server DB Backups
You should backup db after migration and before expiration. On 7/17/07, Gregory Lynch <[EMAIL PROTECTED]> wrote: Hello all, How many times a day should I be backing up the TSM DB and should it be after migration? Thanks Greg *** Gregory Lynch Lead Programmer Analyst IT Infrastructure/Systems Administration Stony Brook University Medical Center HSC Level 3, Room 121 ZIP 8037 Phone: 631-444-9783 [EMAIL PROTECTED] This e- mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by e-mail and destroy all copies of the original. -- Helder Garcia
Re: TSM Server DB Backups
Hi Greg, it really depends on how you are running your TSM environment. In a shared library environment. I try to back up the library manager as frequently as I can, just a few mb on sequential disk, takes a few seconds to back up and restore. An audit will be needed after restore anyway to align all library client, but that is really a quick task. On library clients and single-configurations such as branch offices I back up the database at least twice a day, once locally after client backups (housekeeping after that can easily be rerun without data loss) and once remotely after storage pool backups for DR if TSM in one location is lost. As always, YMMV depending on the data loss you can afford. Systems such as archive servers can be much more critical when using the archive/delete options, as these can not be rerun, more frequent dbbackups can be needed to reduce exposure of data. Regards, Markus -- Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese E-Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail oder von Teilen dieser Mail ist nicht gestattet. Wir haben alle verkehrsüblichen Maßnahmen unternommen, um das Risiko der Verbreitung virenbefallener Software oder E-Mails zu minimieren, dennoch raten wir Ihnen, Ihre eigenen Virenkontrollen auf alle Anhänge an dieser Nachricht durchzuführen. Wir schließen außer für den Fall von Vorsatz oder grober Fahrlässigkeit die Haftung für jeglichen Verlust oder Schäden durch virenbefallene Software oder E-Mails aus. Jede von der Bank versendete E-Mail ist sorgfältig erstellt worden, dennoch schließen wir die rechtliche Verbindlichkeit aus; sie kann nicht zu einer irgendwie gearteten Verpflichtung zu Lasten der Bank ausgelegt werden. __ This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorised copying, disclosure or distribution of the material in this e-mail or of parts hereof is strictly forbidden. We have taken precautions to minimize the risk of transmitting software viruses but nevertheless advise you to carry out your own virus checks on any attachment of this message. We accept no liability for loss or damage caused by software viruses except in case of gross negligence or willful behaviour. Any e-mail messages from the Bank are sent in good faith, but shall not be binding or construed as constituting any kind of obligation on the part of the Bank.
Re: TSM Server DB Backups
Hi
Preferably two copies. One on tape and one on disk
( o )
---
I,I ' ' I,I
"(("
))
With Best Regards,
Sandeep Jain
** Legal Disclaimer
*
"This email may contain confidential and privileged material for the sole
use of the intended recipient. Any unauthorized review, use or distribution
by others is strictly prohibited. If you have received the message in error,
please advise the sender by reply email and delete the message. Thank you."
*
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Gregory Lynch
Sent: Wednesday, July 18, 2007 2:06 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] TSM Server DB Backups
Hello all,
How many times a day should I be backing up the TSM DB and should it be
after migration?
Thanks
Greg
***
Gregory Lynch
Lead Programmer Analyst
IT Infrastructure/Systems Administration
Stony Brook University Medical Center
HSC Level 3, Room 121 ZIP 8037
Phone: 631-444-9783
[EMAIL PROTECTED]
This e- mail message, including any attachments,
is for the sole use of the intended recipient(s) and may
contain confidential and privileged information.
Any unauthorized review, use, disclosure or distribution is prohibited.
If you are not the intended recipient, please contact the sender
by e-mail and destroy all copies of the original.
DISCLAIMER The information contained in this e-mail is
intended only for the person or entity to whom it is addressed
and may contain confidential or privileged information.
If you are not the intended recipient, any dissemination,
use, review, distribution, printing or copying of information
in this e-mail is strictly prohibited, and you are requested
to contact the sender by reply e-mail and destroy all copies
of the original message.Thank you"
This email has been scanned for any virus
infection at the sending end.
