I am in the process of replacing another backup solution (CAM by STK). It
had a lot of problems and we out grew it. Anyway, the network wasn't really
a big issue. Most of the 100+ servers have ATM cards and the ATM network is
used only for backups. The CAM system was more of a bottleneck than the
network. I know that will change. We are still growing and I am sure *SM
on OS390 will have more resourses available for backups in the off hours
than was available to the old system.
I look at the SELECTIVE backup and see that this would be the vehicle to
mirror the present schedule that is in place, weekly (weekend) fulls and
daily incrementals (for most stuff).
The GENERATE BACKUPSET looks interesting, but I don't think it is the
same as a SELECTIVE in updating the versioning of the backups. It seems to
be more of a point in time snapshot without the network overhead.
THe COLLOCATION looks good except I have to maintain a current offsite
copy of most of the servers. I thought it would be nice to COLLOCATE all
the smaller servers by OS (I have to deal with NT, AIX, SUN, and NETWARE).
BUt I don't think I could really do that unless I started cutting up my disk
storage into many different pools. Which leads to all kinds of
inefficiency. So I will COLLOCATE only the real BIG servers. I will be
using really big tape for this, 9840s.
I have learned a lot from this little dialog. I have enjoyed it. If
anyone has more to say on this, GREAT! I am all ears.
Thanks
Matt
-----Original Message-----
From: Serge Gaudet/EIG [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, October 31, 2000 1:43 PM
To: [EMAIL PROTECTED]
Subject: Re: how is a weekly FULL bkup scheduled?
I am of the opinion the "selective" makes sense to backup files that are in
an area normally excluded by the incremental process (via your
include-exclude definitions). Have you ever considered Collocation? At
least for your most critical server? Just a suggestion. Furthermore, a
server executed/generated archive or backupset would probably be better.
(avoiding the bottleneck... the network - hence executable during the day
as opposed to smack in the middle of the backup window). I would just
perform incrementals otherwise.
What can I say: Everywhere I went, network was always the primary issue.
I quickly learned the cost of using it, and learned to become effective
considering the constraint.
Serge Gaudet
Consultant, CMI
Tim Melly
<Tim.Melly.B@ To: [EMAIL PROTECTED]
BAYER.COM> cc:
Sent by: Subject: Re: how is a weekly
FULL bkup scheduled?
"ADSM: Dist
Stor Manager"
<[EMAIL PROTECTED]
RIST.EDU>
31/10/2000
12:59 PM
Please
respond to
"ADSM: Dist
Stor Manager"
We recently had a "minor" Data Center fire and I had to restore several
Novell
volumes. The Novell servers had been incrementally backed up for two years,
the
restoration times were horrendous (12 GB in 18 hours). The tapepool was 270
DLT
tapes and almost all of the tapes were mounted during the restore. We've
since
implemented every other weekend "selective/full" backups of our Novell
servers.
There are situations were "selective" backups make sense.
FYI *SMs, the Novell client does not always restore the file with the "long
filename". We had a significant amount of files which we restored to the
DOS
file name not the "long filename". We had to manually move the files to the
correct location when that location could be determined. Tivoli is looking
into
the issue.
Regards, Tim Melly
"[EMAIL PROTECTED]/P=Internet/A= /C=us" on 10/31/2000
12:00:55 PM
Please respond to "[EMAIL PROTECTED]/P=Internet/A= /C=us" @
X400
To: "[EMAIL PROTECTED]/P=Internet/A= /C=us" @ X400
cc:
Subject: Re: how is a weekly FULL bkup scheduled?
Why is this so strange? I need the data for many servers for a months
worth
of data. I have to be able to restore to any date they (user) says. We
keep the tapes offsite and exercise our DR plan yearly. I will be
restoring
whole servers. Not a file here and there. I would think a full backup and
a year of incrementals could get a little ugly.
Matt
-----Original Message-----
From: Serge Gaudet/EIG [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, October 31, 2000 11:00 AM
To: [EMAIL PROTECTED]
Subject: Re: how is a weekly FULL bkup scheduled?
It's gotta be a tape stress test in progress..... or a validation of the
reclamation process....
I don't know anyone in their right mind who would want to do such a
thing...
...but then again, it could be just to satisfy a paranoid ex-arcserv like
client user!
Serge Gaudet, CMI
"Couldn't help the wise crack - Have a great day"
Larry Way
<Larry.Way@TR To: [EMAIL PROTECTED]
W.COM> cc:
Sent by: Subject: Re: how is a weekly
FULL bkup scheduled?
"ADSM: Dist
Stor Manager"
<[EMAIL PROTECTED]
RIST.EDU>
31/10/2000
10:49 AM
Please
respond to
"ADSM: Dist
Stor Manager"
My question to you is why would you want to ?
>>> [EMAIL PROTECTED] 10/31/00 07:37AM >>>
Check "selective" backups.
"[EMAIL PROTECTED]/P=Internet/A= /C=us" on 10/31/2000
10:32:55 AM
Please respond to "[EMAIL PROTECTED]/P=Internet/A= /C=us" @
X400
To: "[EMAIL PROTECTED]/P=Internet/A= /C=us" @ X400
cc:
Subject: how is a weekly FULL bkup scheduled?
Hello,
I am trying to figure out how to set up a scheduled job that will
do
a Full backup every weekend of a client. I will be running daily
incrementals and will have the POLICY set to keep 4 copies of the backup.
I
just don't see how to get the client to do a full backup after the intial
has been done. What am I missing?
Matt
