Jump to content


  • Content count

  • Joined

  • Last visited

  • Days Won


Everything posted by jotrago

  1. It should be fine. I can't say I have personally upgraded directly from 7.6 to 10 but I have upgraded a variety of other combinations without issue. If you really want to be safe, create a test backup set in 7.6, migrate it to a test 10 installation and see if you can restore. From the Upgrade Technote be aware that the Config files are incompatible and you will need to re-configure V10 manually.
  2. As you suspected upgrading from such an old version has a couple of caveats, but generally is still a fairly straightforward process. Firstly check out the Upgrade Technote, The Retrospect 10 Documentation section discusses upgrade procedures, and check the release notes for anything which may apply to your environment. The key thing with the backupsets is that once you have brought them in to V10 they cannot be used in the old versions. Happy Upgrading!
  3. jotrago

    Fresh Install

    If you go for a clean install you can re-instate the backupsets by simply dragging and dropping the catalog files onto the Retrospect main window.
  4. jotrago

    "config file" to use after reinstall?

    Absolutely. With a bit of preparation Retrospect can be moved or recovered very quickly See my post here
  5. jotrago

    Need to reboot file server mid-backup

    Ah! OK Just a thought, I guess the Raid Groups are handled by the LSI CVard, and presented to Open Filer as 3 Disks, Since Openfiler is built on linux it probably then uses Logical Volume Manager to present the 3 raids as a single Logical Volume. As you discovered Windows will not recognise this. However you might get further, using an alternate Linux based system to boot. If you haven't already come across "Parted Magic" you might give it a go. It's a linux based rescue disk with the linux GParted Partition utility and just about every other Open Source Disk & FIle utility you can think of. I have had some success with it recognising MDADM & LVM objects, it has a bunch of copy / clone / image tools as well. Back to Retrospect. I suspect that if you reboot the server it may indeed break the connection, but you might get lucky. Retro DOES do File Level Single Instancing so it should skip stuff it already has. If you just reenable the incremental on your backup config and leave it pointing to the same BackupSet it should preserve that existing data and continue to add missing stuff on each run. By the sound of it the data on the SMB is not changing, so keep going till nothing more gets backed up.
  6. jotrago

    Need to reboot file server mid-backup

    A couple of thoughts. Transfer speed. How are you accessing the data on the SMB Server? Have you installed the new Linux Client which would be preferable and probably give better performance, or just mounting a share on the Retro Server which will not perform nearly as well? http://www.retrospect.com/en/support/kb/which-versions-of-linux-and-unix-does-the-client-support Why disable Incremental Backup? Retro is designed to do "Progressive" backups whereby it will backup everything it doesnt already have. To create a full backup you need only start with an empty BackupSet (or recycle an existing one) You can then run the backup as often as you like (rebooting the SMB in between) and Retro will effectively "Continue from where it left off" Keep going till no new data is backed up - Check the Session Conttents in the Backup Set to see what is backed up on each run The Snapshot will show you everything that was on the Client at the time of the backup
  7. Retrospect does not run conitnuously as a service, but runs on demand as a normal program. There is a Retrospect Launcher service that is responsible for monitoring the schedules and starting Retrospect when required. This service SHOULD be running all the time. Check that the Launcher service is running, if it is not the scheduled executions will not start until Retrospect is started manually, as you have described. There are also settings in the Configuration section to control what Retrospect does when scheduled executions start and when has finished all it's scheduled executions, stay running, shut down etc. You may want to adjust these to suit your situation. It is possible to have executions run without actually starting the Retrospect interface, whihc may create the impression that nothing is happening. Check your Services and Tasks (remember to select all users) to see what Retrospect is doing under the hood.
  8. jotrago

    Backing up client to NAS

    A couple of observations. 1. With GigE on a good day with the wind behind you you should be able to get up to 70MB/s total throughput. 2. Remember when backing up to a NAS target your data traverses the Backup ServerLAN Twice Client > Server & Server > NAS. Put them on separate NICs should help. 3. Depending on what NAS you have and how many drives it has, and what it's specs are, many smaller SMB/SOHO NAS typically perform at around 200MB/s so the NAS may be your bottle neck. 4. If your NAS has multiple Lan Ports, connect each directly to a separate NIC in your Retro Server, direct connection with a cable is fine, no switch needed. 5. Retrospect works it's own hard drives hard during backup. If the server only has one drive the following disk accesses will all compete. Placing these folders on separate physical drives can significantly improve performance. Retrospect Program Folder, Windows Temp Folder, BackupSet Catalog Folder, BackupSet Target Folder (This is on the NAS in your case so that is fine) 6. Retrospect only backs up one data stream per BackupSet, creating several backup sets will allow several clients to backup in parallel
  9. You are probably confusing Snapshots with Sessions. Every time Retro does a progessive Backup it takes a "Snapshot" of the volume it is backing up. THis Snapshot contains a list of all the files that were on the volume at the time. The Session show ONLY the files that were actually backed up during a given backup session. So your Session should show you the files you are expecting to see. A short study of the Intro Chapter of the Manual has a good explanation of how Retro works. And it is a little different to most conventional backup products, and is essential to understand to get the best from Retro. Welcome to Retrospect
  10. jotrago

    small files slow backup speed

    Your situation is always difficult for any backup application. With a large number of small files the overhead of scanning every file, recording its details updating snapshots & catalogs etc, ends up taking longer than the actual data transfer, especially if the files are relatively static. EG you spend hours scanning 2mill files to find the 200 that actually need backing up The real work is done by the client, so anything to improve performance there may help. Memory, CPU etc. Retrospect makes heavy use of the Windows Temp folder, it helps if this is on a separate drive from that being backed up (SSD would help here) Same on your server try and separate WIndows System / Temp folders, Catalogs, and Backupsets onto separate disk drives as these are all used intensively during backups. IF many of the files are static, try and move them into a separate folder, and back those up less frequently, reducing the number of files scanned daily. If the static files are also rarely if ever accessed, you might consider Retro's Archive feature to remove them altogether.
  11. If a user has lost some files that were present at some point in the past but have now disappeared, how do I restore every file there has ever been including those that may have been deleted along the way? As usual they are not sure when they were created, and they may have disappeared any time in the last 6 months. Session restores only files backed up in a session Snapshot Restore only restores files as of the time of the snapshot (IE: Excluding any files deleted before that time) Do I have to restore every snapshot for that client? Try Finding them - See Snapshot Confusion 1 & 2 I have restored about 10 Snapshots for a particular client to a spare folder. I eventually tripped over the Client Name Option in the More Choices Section of Find Files to restore. So I built a Find where Client Name matches the two client names that have existed for a particular user. It finds 4800 files. BUT I have already restored 14,000 plus files from individual snapshots for those same two clients. So presumably searching by client does not search the entire backup set, so what does it search?
  12. jotrago

    Snapshot Confusion 1

    You've hit the nail on the head there Lennart. The Snapshot shows what "Can Be Restored" as a result of any given backup That's a good way of thinking of it. Conversely the Session shows "What Was Backed Up" during any given backup.
  13. Docs imply that a snapshot is a "COMPLETE" listing of "ALL" the files on a volume at the time a backup runs. Is this true? I suspect it is, ONLY if the backup selects the ENTIRE volume What if only a certain selection of data is backed up. Does the snapshot list every file on the volume, or only those in the selection? (Whether they were actually backed up or not in the matching session) EG: If I backup C:\Users, will the snapshot show files in C:\ Windows even though they would never be backed up
  14. jotrago

    Snapshot Confusion 2

    For disk backup sets it shows which snapshots that will remain after an immediate grooming. For tape backup sets, I think it shows one snapshot per source. I had a suspicion this might be the case, thanks for the confirmation Lennart
  15. Properties of Backupset > Snapshots Tab shows some snapshots from the backupset, but not necessarily ALL the snapshots, ordered by Client Name, Volume & Date What are the criteria applied to decide what snapshots are shown? The ADD snapshot window shows some other snapshots from the backup set. Listed in Date Order across ALL clients. What are the criteria applied to decide what snapshots are shown? A column has a "number of files. What is this number? Number of Files in the Snapshot? Files that were backed up in the Matching Session? Selecting a snapshot in this window, sometimes the "Retrieve" button is active, sometimes not. Why would a snapshot NOT be retrievable? If I am trying to find all snapshots for a particular client it takes hours to trawl through this list finding them all. Worse the window is not wide enough to display the data, and is not re-sizable. It is the Client Name field that is truncated making difficult (and sometimes impossible to determine the client. {In what world do you make a window incapable of displaying the default data, and then NOT allow Column OR Windows re-sizing ?????????} How do I find all the Snapshots, NOT shown in the Main Window for a particular Client?
  16. jotrago

    Snapshot Confusion 2

    When it already exists in the "normal" list of snapshots. So this implies that the "ADD" snapshots list is the list of ALL Snapshots in the Backup Set, and the "Normal" list is a subset. That is what was not clear. I assumed that the ADD list was the snapshots NOT in the Main List.
  17. jotrago

    Snapshot Confusion 1

    Retro 9 Win User Guide "Snapshots Retrospect’s Snapshots make it easy to restore an entire volume or a selected file to its exact state as of a given date and time. A Snapshot is like a picture of the contents of a volume at a point in time. It contains a list of all of the files and folders on a volume and the sessions during which they were backed up." It seems that if you do a selected backup the Snapshot contains ALL the folders on the volume, but only the ones backed up have content. If you do a full volume restore, you get the data you backed up PLUS all the empty folders.
  18. It sounds like your Retrospect either crashed, or would not start for some reason. If you let Retro Exit when it has finished its work, then it is the RetroLauncher Service, which should be running permanently, that re-launches it when the next job is ready. Make sure the that the Launcher service is running by checking in your Services Control Panel If Retrospect crashes it makes an entry in the Assert.utx log which can be found in the (hidden) C:\Program Data\Retrospect folder on Win 7. You can open this file with Retrospect or Notepad Whilst the full content of the assert message only makes sense to a programmer, the header for each one can give some clues. And you can see whether it is an isolated incident or has been happening on a regular basis.
  19. I have fallen foul of Windows issues around removing & ejecting media. I also agree that it is important that windows is correctly informed of the ejection. I have found an excellent utility which helps tremendously with this issue, USB Safely Remove. Free trial and reasonably priced. Maybe worth a try. http://www.safelyremove.com/index.htm
  20. jotrago

    Restart Verify job

    Apologies, I just realised this is the Retro Professional forum so I guess that indicates you are using Pro, which only has a single execution unit, thus you can only run one job at a time. (in my defence I came straight to your post from an email notification and didn't notice which forum it was)
  21. jotrago

    Proactive backups not running

    Sounds like quite a setup. For Procative or Scripted backups to run they must be enabled, within their scheduled run times, and the source volume, and destination backupset must be available and not in use by any other Retro job or task. From your description you may have some overlapping in your setup. Perhaps try disabling (or even deleting) all your scripts and then run them manually (Run Now) one at a time to check their basic functionality. THen you can troubleshoot the scheduling.
  22. jotrago

    Restart Verify job

    OK if your search time is acceptable then that's fine. Re swapping the tapes. Having the two backup sets is what I expected and shoudl work to your advantage, You can have anly one operation per backupset at a time. Are you perhaps using Retrospect "Professional" it has only one execution unit (EU). ie can only run one job at a time, thus if you are running a Verify the Backup cannot run until the verify is finished or stopped, and the EU becomes free. Otherwise with the Server Editions with multiple execution units, your Backup job would start in a second EU, but the Verify job is keeping a lock on the drive, preventing the backup from using it. In which case I suspect the only alternative will be tory the Scheduling feature of teh Verify Job. (If that's available with V7) You can create a verify Script, set the option to only verify unverified backups, then set a Scheduled time during which the Verify is allowed to run. Hopefully it will stop at the end of it's sceduled run, allow you to do your backups, and then resume when the schedule starts again.
  23. jotrago

    Restart Verify job

    So with a standalone drive, you simply dont insert the next tape for your verify job. It will sit patiently "Awaiting Media" while you feed tapes for your Backup job. When that is finished insert the next tape for the verify job and it should continue. Assuming it takes around 4-6 hours to verify an LTO5 tape you would need to time things so that you give the verify job time to finish a tape before the backup is due to start. So you could end up with sequence something like this 08:00 start Verify insert first Tape 13:00; insert 2nd verify Tape; 17:00 Start Backup & insert Backup Tape; 07:00 Backup finished; remove backup tape, repeat THe process would then take about a month for you 40 tapes. That would seem to be a logical approach. However with Retrospect the bigger the saveset, the bigger the Catalog the longer it takes to search. Have you actually tried a search? Was the search time acceptable? Perhaps going forward create many archive backupsets based on a logical attribute of your archive jobs (Date, Customer, Subject etc). It would also be possible, (although a lengthy process) to re-organise your existing Archive set by using the Transfer BackupSet function to move backup sets to new tapes according to your new scheme.
  24. jotrago

    Restart Verify job

    Also on the Verify Job Configuration as I mentioned you set the option for "Verify backups not previously verified" And you can build a schedule so that the verify only runs outside your backup times. EG; Every day from 0600 to 1900 for verify and 1900 to 0600 for Backup