This community is for technical, feature, configuration and deployment questions.
For production deployment issues, please contact the TAC! We will not comment or assist with your TAC case in these forums.
Please see How to Ask the Community for Help for other best practices.
Q may seems silly but it's efforts reduction only subject :0)
Let's assume that i've migrated almost all nodes (PAN&MnT + NxPSN) from 1.4 to 2.2 successfully with backup&restore approach. At this point i have single node running both PAN&MnT role. Now i have to join to new deployment last node & promote it with primary Mnt&S-AN role. Q is do i need to restore this node from the conf&op backups made from previous 1.4 deployment before i'll promote it like mentioned?
My assumption is the node will be synchronized with conf&op data from ex-PAN&MnT node, & backup restore is not needed, m i right?
believing in power of community mind :0)
Solved! Go to Solution.
that's was i expected to hear. In fact i need to balance between customer's requirement to keep op-DB for as long time as possible (90 days :0) & optimal time for migration (i assume restoring op-DB will take considerable time per MnT - may be u have any ETAs for those?). & obviously it would be silly to repeat already made steps. As i understand now, if my only MnT on old deployment became these before migration started, i can have deltas op-DB deltas from backup&restore it from old MnT, but still no idea how to restore it on the primary MnT of new deployment w/o overriding previously restored data.
The restore will overwrite the existing data.
Please explore other means to keep data for longer terms; e.g. using an external syslog target to export the events to a reporting system.
hello Cisco TAC Engineer :0)
have u any idea about time to restore op-DB with 6GB size?