Policies - Business Continuity: Global System Administration

	Site Guide \| Contact Us *Thinking inside the box...*
	Business Continuity / Disaster Recovery / High Availability Data Center Automation / Audit Assessment / Security Assessment


	Home About TriParadigm Triparadigm Officers Privacy Policies Affiliations Contact Us News Press Releases Publications Events Solutions Business Continuity Planning Audit Response Audit Compliance Audit Readiness Security Assessment Enterprise Solutions Architecture & Design Integrated Automation Products VLPAR Orwell Disaster Recovery System P³ AMMS - Automated Microcode Management System P³ CMDB - Configuration Management Data Base P³ ADGS - Automated Document Generation System P³ ACMS - Automated Content Management System P³ APMS - Automated Patch Management System Product Demonstrations Services Business Continuity Planning and Implementation Disaster Recovery Planning and Implementation High Availability Planning and Implementation Virtualization Planning and Implementation Technical Project Planning and Implementation System Architecture Design and Integration Support Business Continuity Technical Support Disaster Recovery Technical Support High Availability Technical Support Virtualization Technical Support Microcode Technical Support Automated Documentation Technical Support vLPAR Technical Support Documentation Methdologies Articles Books Rules and Regulations Recommendations


	Current Location TriParadigm Business Continuity Methdology

JFS Log Logical Volume Name Policies

Each volume group that contains file systems will require at least one JFS log. The name of the JFS Log shall be an enterprise wide unique value.

Policies

Guidelines
Standards
Procedures

Digg this page

Post to del.icio.us

Slashdot it!