Pros: much simpler to manage a small number of things. If you don't have radically different retention policies or some regulating influence suggesting separation, a single domain sending information to a single pool hierarchy is perfectly fine.
Cons: none if the conditions above are met. In some cases, I like the idea of two domains: one for non-critical systems and one for critical. For the critical systems, build your pool hierarchy with a collocated tape pool for faster restores. Kelly J. Lipp Storage Solutions Specialists, Inc. PO Box 51313 Colorado Springs, CO 80949 [EMAIL PROTECTED] or [EMAIL PROTECTED] www.storsol.com or www.storserver.com (719)531-5926 Fax: (240)539-7175 -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Wholey, Joseph (TGA\MLOL) Sent: Wednesday, April 03, 2002 10:08 AM To: [EMAIL PROTECTED] Subject: domain ? Is there any reason why I wouldn't create one huge domain and have production, development and QA servers backing up to it? What are the pros and cons of 1 domain vs. many? Thanks in advance. Regards, Joe Wholey TGA Distributed Data Services Merrill Lynch Phone: 212-647-3018 Page: 888-637-7450 E-mail: [EMAIL PROTECTED]
