Ask the Community
Groups
Alert: File Level Recovery Issues - Connect IT Community | Kaseya
<main> <article class="userContent"> <h2 data-id="summary"><strong>SUMMARY</strong></h2> <p>Information about resolving FLR issues</p> <h2 data-id="issue"><strong>ISSUE</strong></h2> <p></p> <p>When creating a<strong> File Level Recovery</strong>:</p> <blockquote class="blockquote"> <p>Failed to map disk - PHDVB-554/468 - There are no more loopback devices available for the disk(s) in the backup.</p> </blockquote> <p> </p> <p>When deleting a <strong>File Level Recovery</strong>:</p> <blockquote class="blockquote"> <p>Device or resource busy - PHDVB-1231 - One or more partitions/disks for this backup is currently being accessed.</p> </blockquote> <p> </p> <blockquote class="blockquote"> <p>Configuration returned failure, see logs for more info - PHDVB-559 - The configuration subsystem is currently performing another operation associated with FLR. The failed operation should be retried.</p> </blockquote> <p> </p> <p><strong>File Level Recovery object/share not created:</strong></p> <blockquote class="blockquote"> <p>Failed to map disk 129 for ubuntu-12.04+lvm-disk.”</p> </blockquote> <p>This error can occur if more file recovery sessions were created than the appliance can handle. Restarting the appliance will usually resolve this issue.</p> <p> </p> <p>When a second <strong>iSCSI</strong> or <strong>CIFS</strong> <strong>FLR object</strong> is created for the same backup using a different user name:</p> <blockquote class="blockquote"> <p>Error encountered with FLR share</p> <p>'iqn.2014-01.com.phdvirtual:phdvb_flr_420a2d3a-45ce-3f80-d898-ce39665d78e8_1390227052_iscsi':</p> <p>Export</p> <p>'iqn.2014-01.com.phdvirtual:phdvb_flr_420a2d3a-45ce-3f80-d898-ce39665d78e8_1390227052_iscsi'</p> <p>already exists with a different username</p> </blockquote> <p> <br>When trying to remove an FLR object while a partition is still is use:</p> <p><img alt="User-added image" src="https://us.v-cdn.net/6032361/uploads/migrated/B0NW3ISJT952/eid-ka01w000000tcsw-feoid-00n40000002yvfa-refid-0em40000000mjk9." class="embedImage-img importedEmbed-img"></img></p> </article> </main>