3.5 BACKUP AND RECOVERY REQUIREMENTS
Define the method of backup and recovery for the network and systems management systems. These systems can be incorporated in the management domain or a single system can backup each if there is enough bandwidth and I/O throughput. Listed here are some of the questions that need to be asked about system backups. Backup and restoration have a direct effect on how much disk space to purchase and whether an additional backup product needs to be included in the NMS design. Bandwidth and throughput on systems and networks need to be taken into account. In order to do an online backup of the NNM and OVO Oracle databases, the database must be placed in archive mode. Configuring the database for archiving produces a large number of archive logs and the database server places them in the configured directory. These archive logs can take up a lot of disk space as the systems get busy. When using the ovbackup script supplied with the NNM and OVO, there needs to be enough temporary disk space available to copy the information for backup.What organization is going to back up the systems and the data that is being collected?Will a backup product need to be purchased or will standard back up products be used?Will the organization backing up the systems want cost relief?Is there anything peculiar in backing up certain products?How much time will it take to back up the systems?How often do the systems need to be backed up?How is restoration tested?Where will offsite backup tapes be held?How fast can offsite backup tapes be retrieved?Is it faster to design a recovery scenario through HP Ignite/UX or Sun JumpStart and then restore only data? |
لطفا منتظر باشید ...
