ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login
    1. Topics
    2. Tags
    3. restore
    Log in to post
    • All categories
    • OksanaO

      Enjoy Incredible Backup Window Flexibility and Speed

      Starwind
      • starwind backup nvme ssd restore • • Oksana
      1
      0
      Votes
      1
      Posts
      481
      Views

      No one has replied

    • DustinB3403D

      ShadowProtect SPX 6.3

      IT Discussion
      • shadowprotect restore logging spx • • DustinB3403
      1
      1
      Votes
      1
      Posts
      662
      Views

      No one has replied

    • AmbarishrhA

      Backup Restore Tests

      IT Discussion
      • backup restore • • Ambarishrh
      3
      1
      Votes
      3
      Posts
      984
      Views

      hobbit666H

      Urrrrr.....................😕

      a major thing on my #ToDoList

    • DustinB3403D

      Xen Orchestra working on File Level Restore capabilities

      IT Discussion
      • xen orchestra file level block level backups restore • • DustinB3403
      25
      6
      Votes
      25
      Posts
      3.6k
      Views

      DustinB3403D

      All I have to run is ./xo-update.sh

    • stacksofplatesS

      Red Hat ReaR

      IT Discussion
      • red hat rear linux backup restore • • stacksofplates
      6
      3
      Votes
      6
      Posts
      1.9k
      Views

      stacksofplatesS

      So I found a quirk, not sure if it's an actual bug. For incremental backups to work you have to use the NFS syntax (BACKUP_URL="nfs://<server>"). If you mount the share, and then write to the local mount it won't do incremental.

    • gjacobseG

      Create SQL History Database

      IT Discussion
      • server 2012 sql server sql server 2012 sql server management studio database backup restore • • gjacobse
      13
      1
      Votes
      13
      Posts
      2.6k
      Views

      gjacobseG

      In this case, it was a matter of the settings during the restore.

      Under GENERAL you had to select your source and destination as normal. Destination was changed so that it was the new History file. Under FILES you updated the DB and LOG files to reflect the new DB, otherwise you would over write the originals.

      This is where they borked it. They didn't mention FILES only going to OPTIONS, and there is where they mentioned updating the file names. The main discovery was that you need to uncheck LEAVE Source database in the restoring state.

      When I emailed them about removing the 'borked' databases I had created the called me back. I mentioned it to the fellow and we had a short discussion on the matter where he took notes and agreed that the directions were incorrect. When I got to the part about unchecking LEAVE Source database in the restoring state he mentioned that he uncheck Take tail-log backup before restore

      Hope this helps.

      0_1460118217976_2016-04-08 08_22_29-NTG - SSI-SQL01 - Connected.png

    • DustinB3403D

      Xen Orchestra Delta Restore

      IT Discussion
      • xen orchestra delta restore xenserver 6.5 • • DustinB3403
      30
      2
      Votes
      30
      Posts
      7.6k
      Views

      olivierO

      Happy to see it tested intensively 🙂

    • 1 / 1