In this case AutoVault *IS NOT* an alternative - usage of server-to-server virtual volumes requires DRM license.
Zlatko Krastev IT Consultant Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: Re: Your advice wanted! Check out AutoVault from http://www.coderelief.com as a good alternative to DRM. Bill -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Steve Harris Sent: Thursday, June 27, 2002 7:05 PM To: [EMAIL PROTECTED] Subject: Re: Your advice wanted! There is a large retail operation here in Australia that backs up all its store servers without tape at each site. There is a TSM server at each site with local disk storage, copypools are defined across the network to a central site (probably one in each city). We briefly looked at something like that for some of our own sites, but the smaller sites are mainly netware only and they didn't want the hassle of an NT box just to do backups. Of course this requires DRM on each server, but if you buy enough licences I'm sure you'll get some sort of discount. Steve Harris AIX and TSM Admin, Queensland Health, Brisbane Australia. >>> [EMAIL PROTECTED] 28/06/2002 6:52:56 >>> Have in mind that due to lack of random access copypools you have to plan also reclamation there (of course if copypools is used at all). I would prefer to mirror primary diskpool volumes (of course DB&Log too) thus getting random access copies and still protected against HDD failure. Do not forget to schedule backups to file devclass copypools are using. Backup of volhistory&devconfig would help but even without them files from DB backups have .DBB extension and are easily recognizable. And they may go off-site if using Alex's idea for disks exchange (there is no hot-swapping for IDE but we know the cages for quick "cold"-swapping). Alex, you will not be able to send Shark's disks off-site because ESS LIC will complain but try to send the whole Shark off-site :) Zlatko Krastev IT Consultant Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: Re: Your advice wanted! Hi. I don't see much return on making those primary disk storagepools sequential, because once they get tape hardware, you can just "move data" or migrate the backup data off of the random diskpool volumes. In fact, it's more of a headache because you'll have to start reclaiming them and whatnot. Definitely stay with random access disk volumes in your primary diskpools. For copypool, I wonder. Since your installation is so small, I wonder if you can get some hotswap drive bays (do those exist for IDE?), buy 2 more IDE hard drives (they're fairly cheap, aren't they?), and start an offsite rotation of your copypool disks. That would be cute. And much cheaper than investing in a new tape infrastructure to begin with. Hmm... I wonder if I can do that with Shark disk. But your copypool would have to be sequential, so that would complicate matters. If you can figure out how to do sequential volumes and reclamation and whatnot on disk, I would use those two disks as copypool, with or without the extra 2 disks for offsite. Then if you have an application based corruption of your primary diskpool volumes, your copypool has a good chance of surviving that because it's more of an asynchronous "mirror" process. Synchronous mirroring would be more vulnerable to application based corruptions. Have you given any thought to how you're going to manage your dbbackups? It's a good thing to have them on some other machine or media. You could back up your database to disk and ftp it to another machine, or mount remote disk and back up to it, or half a dozen other variations. Good luck. Alex Paschal Storage Administrator Freightliner, LLC (503) 745-6850 phone/vmail -----Original Message----- From: Maria Waern [mailto:[EMAIL PROTECTED]] Sent: Wednesday, June 26, 2002 8:14 AM To: [EMAIL PROTECTED] Subject: Your advice wanted! As a TSM newbie I'd be grateful for some hints and tips - I'm not after instructions because I have those! A customer has a small office, 15 or 20 people with laptops (20 Gb HDDs mostly) and a new Windows 2000/TSM server that contains 4x 60Gb IDE disks. They have no tape robot. What is the best way to set up storage pools on the disks? Use sequential pools instead of standard disk storage pools to provide for easier future storage pool backup should they acquire some tape robot (although this seems highly unlikely at the present time)? Also how big should each storage volume on the disks be? Presumably it's not a good idea to make one large (approx 60 Gb) storage volume on each disk? It may not even be possible to do this for all I know! Also, what about having two of the disks set aside for copy storage pools? They only have one machine dedicated for TSM just now and no off-site backup. I said it was a small office! Anyway, I was thinking to have a primary pool on two of the disks and dedicate the other two for a copy storage pool. Like I said I don't need instructions, just your ideas! Maria ********************************************************************** 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. **********************************************************************
