Mark,
I have two objections to backupsets. The first is that API data is not
covered. The second is that you are not supposed to make new backups for a
node whilst the backupset is being created - this could cause horrendous
scheduling difficulties in my environment.
Is this second restriction a real issue or is it not a concern in practice?
Regards
Steve Harris
AIX and TSM Admin
Queensland Health, Brisbane Australia
>>> stapleto AT BERBEE DOT COM 01/04/2003 14:21:37 >>>
>On Mon, 31 Mar 2003 07:16 pm, it was written:
>>You could try running monthly incrementals under a
>>different nodename (ie: create another dsm.opt file
>>eg: dsmmthly.opt) to your TSM (same or even dedicated)
>>server.
BTW, running monthly incrementals will not facilitate your long-term
storage nearly as nicely as an archive will.
The original poster commented that he could not run archives and backups
off the same client; I'd be interested in seeing what is going on with
his TSM environment.
From: Steven Pemberton [mailto:stevep AT IBK.COM DOT AU]
>Have you considered creating a monthly BackupSet tape for
>each of your file servers?
>
>BackupSets have several advantages over a "full archive"
>for monthly retention:
>
>1/ The file server doesn't need to send any additional data
>for the "monthly" retention. There is no need for a
>"special" monthly backup. The backupset is
>created from existing incremental backup data already in the
>TSM server.
>
>2/ The BackupSet contents are indexed on the backupset tapes,
>and not in the TSM database. Therefore your database doesn't
>need to grow as you retain the monthly backupsets.
As big a fan of backupsets as I am, I feel the need to point out the
disadvantage of backupsets: you can't browse through them if you don't
the name of a desired file or its directory location. You can run Q
BACKUPSETCONTENTS, but then you'll have to grep through a *very* long
output.
--
Mark Stapleton (mark.stapleton AT berbee DOT com)
**********************************************************************
This e-mail, including any attachments sent with it, is confidential
and for the sole use of the intended recipient(s). This confidentiality
is not waived or lost if you receive it and you are not the intended
recipient(s), or if it is transmitted/ received in error.
Any unauthorised use, alteration, disclosure, distribution or review
of this e-mail is prohibited. It may be subject to a statutory duty of
confidentiality if it relates to health service matters.
If you are not the intended recipient(s), or if you have received this
e-mail in error, you are asked to immediately notify the sender by
telephone or by return e-mail. You should also delete this e-mail
message and destroy any hard copies produced.
**********************************************************************
|
