EMC Avamar Shutdown Procedure Guide
Uploaded by
UNETIEMC Avamar Shutdown Procedure Guide
Uploaded by
UNETICommon questions
Powered by AIAfter the backup scheduler is suspended, the shutdown sequence proceeds with the termination of hfs integrity maintenance, dtlt, EMS, MCS, gsan, and axionfs services sequentially. This order likely prevents data corruption and ensures that maintenance tasks, backups, and other processes complete safely, maintaining data integrity and ensuring no conflicts occur during the active shutdown phase .
Saving and exiting the configuration file before stopping and starting MCS services reflects a best practice to commit configuration changes securely. This ensures that once the services are restarted, they operate with the latest settings, minimizing downtime and reducing the risk of operational errors and configuration mismatches .
When using the 'mapall' command for NTP settings in EMC Avamar multi-node environments, considerations include ensuring that all nodes are synchronized properly without causing network strain or inconsistencies. It is also essential to understand the current configuration and dependencies of each node to prevent disruptions. Testing configurations in a staged environment prior to executing in live systems may also be beneficial .
The maintenance windows scheduler status being 'enabled' during the initial system status check implies that automated maintenance operations may still be active, potentially affecting the shutdown process by requiring them to be paused or completed to prevent data loss or corruption. Ensuring it is disabled or managed properly is crucial for a seamless shutdown process .
The repeated broadcast messages during the EMC Avamar physical server shutdown serve to notify all connected users of the impending downtime, ensuring that any critical operations can be completed or paused appropriately. This communication helps prevent data loss and ensures users and administrators can safely finish or interrupt their current tasks before the system goes into maintenance mode .
Assessing the status of EMS before confirming a shutdown is important to ensure that all essential monitoring and environmental services are terminated safely, preventing potential loss of environmental data and ensuring a smooth restart without lingering issues. Options available include shutting down the local instance of EMS or leaving it up based on operational requirements .
Disabling the backup scheduler prior to shutting down services is crucial to preserving the EMC Avamar backup system's integrity. It prevents new backup jobs from initiating, ensuring that system resources aren't strained and enabling existing processes to complete smoothly. This orderly cessation minimizes the risk of data corruption and resource conflicts during the shutdown .
The initial step in the EMC Avamar shutdown procedure is to log in as the root user and switch to the admin account using 'su – admin'. This step is important because it grants the necessary permissions to execute subsequent commands essential for checking system status and initiating the shutdown sequence, thus ensuring a controlled and orderly shutdown process .
To define a new SMTP server for EMC Avamar, the '/usr/local/avamar/var/mc/server_data/prefs/mcserver.xml' file should be edited. The '<entry key="smtpHost" value="mail"/>' and '<entry key="admin_mail_sender_address" value=""/>' entries within the file must be updated with the new SMTP server and sender address information, respectively .
Running the 'asktime' command is necessary when modifying NTP settings in a multi-node EMC Avamar system to synchronize the time settings across all nodes, preventing inconsistencies that could affect backup and system operations. Cautions include ensuring no reboots or system halts are needed and consulting the manual for using the 'mapall' command to propagate changes correctly across nodes .
