Thanks for correcting me Edward. Infact I had also been doing the same... just
missed it out altogether :)
Sadi
"Pugliese, Edward" wrote:
> You can still create DRM tapes. Just do the "backup stg diskpool copypool"
> prior to the migrate of diskpool to tapepool so the data is still in the
> diskpool. This way you are always copying from disk to tape. No need for
> tape to tape copy. This is applicable to all environments, not just one
> with one tape drive.
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
> Of MUHAMMAD SADAT ANWAR
> Sent: Thursday, April 27, 2006 1:24 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: [ADSM-L] Recommended policy for single drive scenario
>
> Dear mario,
> If you have 300GB of data to backup everyday, then you can insert your tape
> into the drive and schedule all the client backups accordingly to be backedup
> to that tape.
>
> Still if you want to keep one tape for everyday, then you need to take
> selective backups for everyday.
>
> I once had a configuration with one tape drive withthe following:
>
> I used normal configuation of all the policies as if i had a library. Keeping
> 9999 versions of data exists, and 9999 versions of data deleted. Retain extra
> and Retain Only versions as 32. This was done for my daily backups. I was
> taking incremental backups and was fine with the amount of data backedup
> daily.
>
> I was taking backups on diskpool in the night with schedules, and would
> migrate all the data to Primary tape pool.
>
> Effectively since you can not make DR tapes here, once your data is moved to
> Tape, you run prepare and then you backup the database onto separate tape.
> This set of tapes with DB backup and a floppy containing your plan file would
> also behave like a DR tapes set.
>
> Keep your DB expire, volume reuse delay to same as per your requirements that
> to which day you might need to revert in case of disaster. I would recommend
> that you keep these tapes and floppies into a fire proof and heat resistant
> vault at your location. You can not efffectively send these tapes to offsite
> since you would need these tapes daily.
>
> While you are backingup your data daily on a single tape or a set of tapes,
> reclaimation would arrive after 32 days. At this time you need some extra
> space to create migration pool on your hard disk. This would be a temporary
> pool that will hold your data in the process of reclaimation. You should set
> reclaimation to 100 percent in normal days and turn it on to for example 60
> when you think you need to perform reclaimation.
>
> Sadi
>
> ---- mariobehring AT yahoo DOT com wrote :
> > Hi Muhammad,
> >
> > There are about 20 or 30 clients. I guess that 100GB is available at the
> > server for use by the diskpool.
> >
> > I was thinking about trying to use TSM like smaller backup softwares like
> > ArcServe, using a tape for each day of the week (from Monday to Friday). I
> > know that the smart thing to do would be to have a second
> > drive.........I´ve already installed and configured TSM with automated tape
> > libraries.........but this customer is a small company and they will not
> > change anything on their environment..........so, it will be the operator´s
> > responsibility to change tapes everyday and to perform no reclamation
> > whatsoever.
> >
> > Any suggestions on how to configure a TSM policy for such scenario ?
> >
> > Thanks.
> >
> > Mario
> >
> >
> >
> > ----- Original Message ----
> > From: Muhammad Sadat Anwar <sadi AT SUPER.NET DOT PK>
> > To: ADSM-L AT VM.MARIST DOT EDU
> > Sent: Wednesday, April 26, 2006 3:18:01 PM
> > Subject: Re: Recommended policy for single drive scenario
> >
> > Mario,
> > 1- In the first place .. how many client nodes are there?
> > 2- How much space is there on your local hard disk for diskpool?
> >
> > 3- Your option of collocating the backups would eliminate if you run
> > scheduled backups directly to tape.
> > 3-Reclaimation would require quite alot of space again on your local
> > machine.
> > 4- If you are looking for DRM, it would be quite a time consuming and
> > manual work.
> >
> > These are just the basics, know that TSM is actually built to reduce
> > your pain of managing and taking backups if its utilized appropriately.
> > Giving it a hard time with reduced resources would turn your life miserable
> > abit.
> >
> > I suggest you go for atleast 2 tape drives (if you can't afford tape
> > library) for appropriate DR and Reclaimation.
> >
> > Sadi
> > Manager Systems IT
> > ABAMCO limited
> > Pakistan
> >
> >
> > Mario Behring wrote:
> >
> > > <!-- DIV {margin:0px} -->Hi list,
> > >
> > > The environment is TSM 5.3.2 running on a W2003 box connected with a
> > > single drive SCSI tape unit (SDLT3). The total amount of data to be
> > > backed up is about 300GB and the tapes are 400GB/800GB capacity.
> > >
> > > What is the recommended policy for such an environment?
> > > ...........considering that there is only one drive and that each tape
> > > has enough space to store the whole data.
> > >
> > > Please advise.
> > >
> > > Mario
> >
> >
>
> _____________________________________________________
> Sent via SUPERwebmail - Supernet web-based email service
> http://www.super.net.pk/mail
>
> "This e-mail and any attachments may contain confidential and privileged
> information. Any dissemination or use of the information by a person other
> than the intended recipient is unauthorized and may be illegal. If you are
> not the intended recipient, please notify the sender immediately by return
> e-mail, delete this e-mail and destroy any copies. Although this e-mail and
> any attachments are believed to be free of any virus or other defect that
> might affect any computer system into which it is received and opened, it is
> the responsibility of the recipient to ensure that it is virus free and no
> responsibility is accepted by the Board of Trade of the City of New York,
> Inc. or the New York Clearing Corporation for any loss or damage arising in
> any way from its use. Thank you."
>
|
