Re: backing up just a few directories?
Hi, I tried putting a non-mount point in the domain line, but the client didn't like that. Recommendations? You can use the virtualmountpoint option on unix clients. Place the following option in dsm.sys: virtualmountpoint /etc and then define /etc as a domain in dsm.opt: domain /etc This will only backup your /etc directory. -- Viele Gruesse, Dirk Kastens Universitaet Osnabrueck, Rechenzentrum (Computer Center) Albrechtstr. 28, 49069 Osnabrueck, Germany Tel.: +49-541-969-2347, FAX: -2470
eVault vs. TSM
Has any one run into evault as a competitor to TSM? Can anyone share their experiences if you have worked with eVault in the past specifically as it relates to iSeries? Thanks
Re: backing up just a few directories?
For Dave: Try using the "virtualmountpoint". This allows just what you want. It telss tsm to treat the specified directory tree as if it were a real mountpoint. Good luck. Gary Lee Senior System Programmer Ball State University phone: 765-285-1310 -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Dave Mussulman Sent: Wednesday, July 18, 2007 1:07 PM To: ADSM-L@VM.MARIST.EDU Subject: backing up just a few directories? I have a few systems I'd like to add to TSM but only backup a few directory hierarchies. These aren't always mount points (for example, the /etc directory under the / mount point.) Does TSM really not have a way for me to define "just back up X" without worrying about anything else on that mount? I know I can do a exclude /.../* include /etc/.../* but then I get all the directories backed up all over /. I could append exclude.dirs for the larger hierarchies (/lib, /usr, etc.) but that seems awkward too. I feel like I'm going at this problem the wrong way, but I haven't found a right way. I tried putting a non-mount point in the domain line, but the client didn't like that. Recommendations? Thanks, Dave
Re: backing up just a few directories?
Take a look at the "virtual mountpoint" feature on the Backup Archive Client Installation and User's Guide. On 7/18/07, Dave Mussulman <[EMAIL PROTECTED]> wrote: I have a few systems I'd like to add to TSM but only backup a few directory hierarchies. These aren't always mount points (for example, the /etc directory under the / mount point.) Does TSM really not have a way for me to define "just back up X" without worrying about anything else on that mount? I know I can do a exclude /.../* include /etc/.../* but then I get all the directories backed up all over /. I could append exclude.dirs for the larger hierarchies (/lib, /usr, etc.) but that seems awkward too. I feel like I'm going at this problem the wrong way, but I haven't found a right way. I tried putting a non-mount point in the domain line, but the client didn't like that. Recommendations? Thanks, Dave -- Helder Garcia
Re: backing up just a few directories?
On Jul 18, 2007, at 1:06 PM, Dave Mussulman wrote: I have a few systems I'd like to add to TSM but only backup a few directory hierarchies. These aren't always mount points (for example, the /etc directory under the / mount point.) Does TSM really not have a way for me to define "just back up X" without worrying about anything else on that mount? I know I can do a exclude /.../* include /etc/.../* but then I get all the directories backed up all over /. I could append exclude.dirs for the larger hierarchies (/lib, /usr, etc.) but that seems awkward too. I feel like I'm going at this problem the wrong way, but I haven't found a right way. I tried putting a non-mount point in the domain line, but the client didn't like that. Recommendations? Get familiar with TSM facilities to be able to choose from the possibilities it provides. If you want to always backup up just /etc, then define that as a VIRTUALMountpoint and then code it on the DOMain statement. Then, / etc will become a TSM filespace. Another possibility: The dsmc Incremental command accepts a file system, directory, or file, so you could instead specify that as the OBJects value of a client schedule (OBJects="/etc/"). Richard Sims
Re: backing up just a few directories?
Specify the directories in the command line, e.g.: dsmc i /dir1/ /dir2/ /etc/ -subdir=yes etc. You can define a separate schedule for the machine and put the directories in the OBJECTS field of the schedule, e.g.: def schedule standard special objects="/dir1/ /dir2/ /etc/" options="-subdir=yes" Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Product Development Level 3 Team Lead Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] IBM Tivoli Storage Manager support web page: http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html The only dumb question is the one that goes unasked. The command line is your friend. "Good enough" is the enemy of excellence. "ADSM: Dist Stor Manager" wrote on 2007-07-18 10:06:49: > I have a few systems I'd like to add to TSM but only backup a few > directory hierarchies. These aren't always mount points (for example, > the /etc directory under the / mount point.) Does TSM really not have a > way for me to define "just back up X" without worrying about anything > else on that mount? I know I can do a > > exclude /.../* > include /etc/.../* > > but then I get all the directories backed up all over /. I could append > exclude.dirs for the larger hierarchies (/lib, /usr, etc.) but that > seems awkward too. I feel like I'm going at this problem the wrong way, > but I haven't found a right way. > > I tried putting a non-mount point in the domain line, but the client > didn't like that. Recommendations? > > Thanks, > Dave
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.
backing up just a few directories?
I have a few systems I'd like to add to TSM but only backup a few directory hierarchies. These aren't always mount points (for example, the /etc directory under the / mount point.) Does TSM really not have a way for me to define "just back up X" without worrying about anything else on that mount? I know I can do a exclude /.../* include /etc/.../* but then I get all the directories backed up all over /. I could append exclude.dirs for the larger hierarchies (/lib, /usr, etc.) but that seems awkward too. I feel like I'm going at this problem the wrong way, but I haven't found a right way. I tried putting a non-mount point in the domain line, but the client didn't like that. Recommendations? Thanks, Dave
Re: Checkout full, unchanging tape volumes
After a bit more thought, I believe I follow the problem through now. Our offsite copy tape pool supports multiple primary pools and IS subject to reclamation so presumably the full tapes in the primary (unchanging) pool will still be read on occasion to support reclamation on the offsite copy pool. Thanks for clearing my head Richard. Angus -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Richard Sims Sent: 18 July 2007 15:12 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Checkout full, unchanging tape volumes On Jul 18, 2007, at 8:40 AM, Angus Macdonald wrote: > So can I take it my suggestion won't work? Checking tapes out of a library will work to create empty cells in the library, but is problematic in that it is an "out of band" measure. TSM is enterprise software, with a rules set and regimen to assure that all pieces are consistent and aware of one another such that automated operations can work. It is implicit that investing in enterprise level software involves an equivalent commitment to enterprise hardware, with adequate capacity and performance - including all data being resident in managed libraries. By TSM conventions, tapes which leave a library are to be copy storage pool volumes marked as Offsite, where their life cycle can be tracked by automated facilities and be dealt with appropriately in all phases. For example, Reclamation will not sit in a stupor waiting for such a tape to be mounted, instead calling for mounts of the primary copy of the data, which is still in the library. As you can see from the Managing a Full Library topic in the Admin Guide, you have to go through gyrations to fabricate an alternate reality for primary storage pool volumes, including dealing with mount requests and allied handling of tapes which are outside the library. This is not something you really want to do. Richard Sims
Re: Checkout full, unchanging tape volumes
Thanks for that Richard. Reclamation should not be an issue because the content of a full tape in this pool never changes. Once full, the tapes just sit there taking up space. I've noticed in TSMManager that I have the option to checkout a tape to onsite storage so I may experiment with that. I agree that the real solution is more library capacity but in a cash-strapped environment with wildly differing budgets from year-to-year, it's neccessary to take a creative approach sometimes. Once you add in the fact that the system is *actually* managed by an external company that nevertheless has no in-house Tivoli skills you can start to appreciate the situation I find myself in all too often ;-) -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Richard Sims Sent: 18 July 2007 15:12 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Checkout full, unchanging tape volumes On Jul 18, 2007, at 8:40 AM, Angus Macdonald wrote: > So can I take it my suggestion won't work? Checking tapes out of a library will work to create empty cells in the library, but is problematic in that it is an "out of band" measure. TSM is enterprise software, with a rules set and regimen to assure that all pieces are consistent and aware of one another such that automated operations can work. It is implicit that investing in enterprise level software involves an equivalent commitment to enterprise hardware, with adequate capacity and performance - including all data being resident in managed libraries. By TSM conventions, tapes which leave a library are to be copy storage pool volumes marked as Offsite, where their life cycle can be tracked by automated facilities and be dealt with appropriately in all phases. For example, Reclamation will not sit in a stupor waiting for such a tape to be mounted, instead calling for mounts of the primary copy of the data, which is still in the library. As you can see from the Managing a Full Library topic in the Admin Guide, you have to go through gyrations to fabricate an alternate reality for primary storage pool volumes, including dealing with mount requests and allied handling of tapes which are outside the library. This is not something you really want to do. Richard Sims
Re: Checkout full, unchanging tape volumes
On Jul 18, 2007, at 8:40 AM, Angus Macdonald wrote: So can I take it my suggestion won't work? Checking tapes out of a library will work to create empty cells in the library, but is problematic in that it is an "out of band" measure. TSM is enterprise software, with a rules set and regimen to assure that all pieces are consistent and aware of one another such that automated operations can work. It is implicit that investing in enterprise level software involves an equivalent commitment to enterprise hardware, with adequate capacity and performance - including all data being resident in managed libraries. By TSM conventions, tapes which leave a library are to be copy storage pool volumes marked as Offsite, where their life cycle can be tracked by automated facilities and be dealt with appropriately in all phases. For example, Reclamation will not sit in a stupor waiting for such a tape to be mounted, instead calling for mounts of the primary copy of the data, which is still in the library. As you can see from the Managing a Full Library topic in the Admin Guide, you have to go through gyrations to fabricate an alternate reality for primary storage pool volumes, including dealing with mount requests and allied handling of tapes which are outside the library. This is not something you really want to do. Richard Sims
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 g r e e m e n t s u n d e r w h i c h A t o s O r i g i n s u p p l i e s g o o d s a n d / o r s e r v i c e s o f w h a t e v e r n a t u r e , t h e T e r m s o f D e l
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: Checkout full, unchanging tape volumes
So can I take it my suggestion won't work? -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Richard Sims Sent: 18 July 2007 12:58 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Checkout full, unchanging tape volumes On Jul 18, 2007, at 7:50 AM, Angus Macdonald wrote: > I support a TSM 5.3 installation with a 3582 library, which is > running out of local capacity. One of the tape pools is used > exclusively for a large body of files which receive regular > additions but are never changed or deleted. The tapes in the pool > are all full, apart from the one that is being currently written- > to. Is it safe to checkout some or all of the full tapes and store > them offsite, since their content will never change or expire? Angus - Your site needs to be more realistic about capacity needs, to avoid putting technicians (you) into a position of having to deal with capacity exhaustion. Try to make them fully aware of the situation. See topic "Managing a Full Library" in the Admin Guide for coping with it. Richard Simshttp://people.bu.edu/rbs
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: Checkout full, unchanging tape volumes
On Jul 18, 2007, at 7:50 AM, Angus Macdonald wrote: I support a TSM 5.3 installation with a 3582 library, which is running out of local capacity. One of the tape pools is used exclusively for a large body of files which receive regular additions but are never changed or deleted. The tapes in the pool are all full, apart from the one that is being currently written- to. Is it safe to checkout some or all of the full tapes and store them offsite, since their content will never change or expire? Angus - Your site needs to be more realistic about capacity needs, to avoid putting technicians (you) into a position of having to deal with capacity exhaustion. Try to make them fully aware of the situation. See topic "Managing a Full Library" in the Admin Guide for coping with it. Richard Simshttp://people.bu.edu/rbs
Checkout full, unchanging tape volumes
I support a TSM 5.3 installation with a 3582 library, which is running out of local capacity. One of the tape pools is used exclusively for a large body of files which receive regular additions but are never changed or deleted. The tapes in the pool are all full, apart from the one that is being currently written-to. Is it safe to checkout some or all of the full tapes and store them offsite, since their content will never change or expire? Thanks Angus
