home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!charon.amdahl.com!pacbell.com!sgiblab!zaphod.mps.ohio-state.edu!uwm.edu!linac!att!ucbvax!cmt.anl.gov!OSUDAR
- From: OSUDAR@cmt.anl.gov (John Osudar {708 252-7505})
- Newsgroups: comp.os.vms
- Subject: RE: ?Why does this backup go so slow?
- Message-ID: <921118112729.2520b496@cmt.anl.gov>
- Date: 18 Nov 92 17:27:29 GMT
- Sender: daemon@ucbvax.BERKELEY.EDU
- Distribution: world
- Organization: The Internet
- Lines: 22
-
- The idea of BACKUP doing disk I/O one allocation cluster at a time is really
- hilarious! Are there still people out there who are under the impression that
- disk I/O's must be done in units of the allocation cluster size?
-
- Since nobody else has asked...
- Are you running the "new" BACKUP (which began with VMS V5.2)?
- If you are, check the quotas on the account you're using to run BACKUP. Look
- at DEC's recommendations and guidelines. Setting the quotas properly is vital
- to BACKUP's performance improvements.
- How are the disks connected to their host(s)? Are they on two different
- cluster nodes on an Ethernet, on different controllers connected to one node,
- or both on the same controller?
- Was the source drive badly fragmented? Fragmentation really killed performance
- in the old BACKUP, and can do the same to the new BACKUP if quotas aren't set
- right. Even with decent quotas, bad fragmentation will affect performance.
- Was the BACKUP process running when the system was very busy?
- Which qualifiers did you use? For example, did you use /RECORD and are you
- including that time in the 4.5 hours? Did you do a /LOG?
-
- John
- osudar@cmt.anl.gov
-
-