/* * These styles apply ONLY to the header and footer assets. */ * { padding: 0; margin: 0; box-sizing: border-box; } .super-nav { display: flex; justify-content: flex-end; align-items: center; margin: 0 auto; max-width: 1264px; padding-left: 40px; padding-right: 40px; height: 40px; text-align: right; } .super-nav a { color: #34427c; margin-right: 20px; padding: 10px; text-decoration: none; } .super-nav a:hover, .super-nav a:focus { background-color: #f7f9fa; } .footer { background: #f5f5f6; color: #555a62; font-size: 14px; line-height: 1.5; padding: 0; } .footer-image { background-image: url("/themes/kaseya/assets/images/footerImage.png"); height: 500px; background-repeat: no-repeat; background-size: cover; margin-top: -100px; } .footer-wrap { padding-left: 18px; padding-right: 18px; max-width: 1236px; margin: 0 auto; } .footer-main-content { background-color: #000; padding: 100px 0; } .footer .footer-col-title { color: #ffffff; font-weight: 700; font-size: 13px; padding-bottom: 10px; text-transform: uppercase; } .footer .footer-link { color: #9b9ca0; text-decoration: none; } .footer .footer-link:hover, .footer .footer-link:focus, .footer .footer-link:active { text-decoration: underline; } .footer-main-content .footer-link { padding-top: 10px; } .footer-row { display: flex; flex-wrap: wrap; justify-content: space-between; align-items: center; margin: -3px; } .footer-main-content-row { align-items: flex-start; } .footer-bottom-content { padding: 10px; align-items: center; } .footer-col { padding: 0 3px; display: flex; flex-direction: column; } .footer-col-copyRight { justify-content: flex-start; color: #9b9ca0; flex: 1; display: flex; } .footer-last-col { flex-direction: row; } .footer-last-col .footer-link { padding-right: 10px; text-transform: uppercase; } @media screen and (max-width: 768px) { .super-nav { padding-right: 0; } .footer-image { height: 250px; } .footer-main-content { padding: 40px 0; } .footer .footer-col-title { padding-top: 10px; } .footer-row:not(.footer-main-content-row) { display: block; } .footer-col:not(.footer-main-content-col) { width: 100%; text-align: center; padding: 10px 0; } .footer-main-content-col { width: 50%; } .footer-last-col { flex-direction: column; } .footer-last-col .footer-link { padding-bottom: 10px; } } /*# sourceMappingURL=styles.css.map */ Ask the Community Groups

Unitrends Cold Copy

Preparing disk media in an RXDA equipped appliance may return: "Failed: 1 drive was added; prepare media manually to use this configuration"

SUMMARY

Cold backup copies may fail with the message: "Failed: 1 drive was added; prepare media manually to use this configuration."

ISSUE

Customers may receive a cold copy failure result indicating "Failed: 1 drive was added; prepare media manually to use this configuration" In this case, when using an RXDA, the media will also fail manual preparation.

RESOLUTION

One of 2 processes are necessary to resolve this issue:

Use the Cold Copy Report from the reports tab. Run the report for an appropriate range and locate cold backups that contain the current serial number of drive (if the "serials" column is not displayed in your UI, use the hamburger icon at the right of the column names to enable it's view). Locate a recent cold copy containing the serial number you have and make note of the other serial numbers used in that same job. Locate those other physical devices and insert them all in your RXDA and then manually prepare the media. Note: this will erase all archives on that media and also erase historical record of those archives. You shoudl then be able to re-prepare the selected disk with a different set of alternate disks.

Override the media saftey check:

a) Ensure you are on release 10.1 or newer

b) Run the following command

bputil -p Archive SkipSerialCheck 1 /usr/bp/bpinit/master.ini

c) Insert the drives you would like to be part of a new set into your RXDA and prepare the drives normally

d) Run the following command to re-estabish the saftey check.

bputil -p Archive SkipSerialCheck 0 /usr/bp/bpinit/master.ini

CAUSE

The backup appliance knows which disk Serial Numbers have been used in prior archive sets. When a single disk from one older set is attempted to be used in a new archive set with different disks, a check is made that protects the user from accidentally erasing that older disk as part of the process of creating the new set.

The correct process is to load the old disk set using the original drive configuration and prepare that media, which will erase prior known configurations of that media. The alternative is to remove known prior disks sets using the UI feature if the original disks are not know. Some customers may not wish to perform these processes and wish the saftey check to be disabled to allow any combination of disks to be prepared even if that means the loss of ability to recover prior archives. 10.1 provides that manual setting option.