Jump to content

jotrago

Members
  • Content count

    146
  • Joined

  • Last visited

  • Days Won

    12

Everything posted by jotrago

  1. Retro1, so try this Reports > Backup Report Options > Report Layout = Performance Data Layout; Event Types = ProActive Backup Only; Event Dates ALL; or adjust to suit Show > Most Recent Successful Backups Including = Unchecked OK You should now get a list of your most recent successful backups with the Number of days Since they happened. You can now investigate any clients that are :- Missing altogether (No Backups) Excessive days since last good backup
  2. You need to enable the "Performance Data Format " Report Layout in the Backup Report Options, it is then the Second column in the report and you get the duration, backup Speed and volume of data for each volume. Cool!
  3. Work with the Backup Report a bit more, it takes a bit of getting your head around it. As you say it does not give a comprehensive history of ALL backups, it would get too big and unwieldy. Instead Retrospect tries to show you what you need to know. In general it will show you the last successful backup, and any errors. ESPECIALLY NOTICE THE "Elapsed Days" column. This indicates the number of days since the last backup and is conveniently highlighted in red. Play with the options button (top left corner). you can filter for several variations. EG create report for Pro-active Backup, for the last 7 days showing unsuccessful backups, with / without Client Offline Errors Retrospect 9 has a very useful "Dashboard" which has 5 Panes summarising key aspects of Retrospect operations including a pane titled "Not Backed Up in the Last 7 Days" http://www.retrospect.com/en/blog/2014/03/27/inside_dashboard You might also want to consider installing the Reports Watcher utility. This reads in the Backup log and generates a very handy HTML report which can be simply opened in a web browser, or you can have Reports watcher insert it into an intranet webserver folder to make it accessible more widely. This report includes and unsuccessful backup page. See http://forums.retrospect.com/index.php?/topic/151132-reports-watcher-gone/
  4. jotrago

    Remove client or folders from backset

    Unfortunately you cannot manually manipulate the contents of a backupset, nor would you want to. Retrospect implements a kind of Single Instance Storage whereby identical files are only stored once, and then referenced. If your retired client was one of several clients targeting the same backupset, it is entirely possible that some if its files may be referenced by other clients. If you keep your backups for a certain period or number and then groom your backup set, the files of your retired client will eventually be groomed out of the backup set. ANother approach would be to use the "Transfer Backups" functionality. Create a new script > Transfer Snapshots > Select you Backupset > Transfer Options - Check Selected Snapshots. You may need to click "Add Snapshots" to access all the snapshots in the backupset. No go through the list of snapshots and select all those EXCEPT the ones for your retired Client. Create New BackupSet to receive the snapshots Set options Run Script. This will now transfer all the selected snapshots, and their associated files to the New Backupset. Now Modify your normal backup Scripts to point to the Bew Backupset. This should achieve your objective, except that during the process you will need additional disk space of roughly the size of your backupset. Hope this helps
  5. jotrago

    off site clients

    Hi Lennart Of course there are backup and file synch products specifically designed to handle roaming laptops small remote sites etc. Druva is very impressive, and any number of Cloud Solutions, CrashPlan is impressive there combining the best of Cloud, Server, and Local Another approach might be to use WebDav with a NAS box, if you happen to have one. Most of the modern ones include some kind of backup/synch client, and they can connect on demand across the internet via Webdav. You could then backup the WebDav folder off the NAS to your Retrospect. Good Luck
  6. jotrago

    off site clients

    Hi Lennart. The clients have to be "Seen" by the Server when the ProActive backup does it's polling cycles, so that would require some sort of connectivity, VPN, SSLVPN etc. Depending on your VPN implementation you could perhaps arrange that the clients connect on a schedule of some sort to ensure they are available, or users would manually connect when convenient. I do know that if a laptop is configured for Proactive backup at the office, and it happens to be connected via VPN during the ProActive window then it will backup, I have had this happen by accident with one of my customers. A third possibility could be to use the User initiated manual backup, which requires setting up a backupset for the purpose. If combined with a "VPN on Demand" setting that would fire up the vpn when the users tries to connect, that could be another approach. Of course if they are in a ProActive Script, then any time they happen to be IN the office they would be backed up as well. Some VPN implementations allow rules to be setup to "Trigger" the VPN connection, eg when a certain IP Address is targeted, perhaps something like this could be incorporated.
  7. Probably not, Win 2012 support was introduced with Retrospect 8 for Windows. {but you never know ???} I suspect you may run into permissions issues. If you plan to continue using Retrospect going forward (and why wouldn't you!) I would suggest contacting your Retrospect Reseller / Distributor / or email Retrospect support, give them your current licenses, and explain you are moving from SBS to 2012, and ask them to quote you on a cross/up grade.
  8. jotrago

    Simple rotated, 2 disk backup

    Welcome to Retrospect. Retrospect is quite capable of doing what you need, but if you have come from other backup products, you will need to understand that Retrospect works rather differently from conventional backup products, and there are number of key principles you will need to get your head around. You will need to read the Manual or the Help (pretty much the same thing) for the relevant sections. Manual - Ch2 Getting Started - Overview 1. Retrospect does not do "Incremental" backups in the conventional sense, it uses a technology called "Progressive" backup, which is sort of incremental forever, or at least for an extended period (several months). Manual Ch3 Fundamentals - Progressive Backup 2. Snapshots, are records of the state of a client at a point in time, and are used in conjunction with Progressive backup to provide the ability to to effectively perform a "Full" recovery, from Progressive backups. Manual Ch3 Fundamentals - Snapshots 3. Pro-Active Backup is for your Laptops & Workstations, where their availability is unpredictable. You create Proactive backup scripts which implement backups of the form, for example. "Backup all the laptops whenever they are available, but not more than once every two days, ensuring that priority is given to the longest outstanding client" Manual Ch6 Automated Operations - Proactive Backup Scripts 4. BackupSets, are backup Target objects (Disks, file, tape) to which backup data is sent. A Key point is that you can specify multiple BackupSets (your two removable drives) for a particular Script, and Retrospect will do it's best to use which ever one is available at any time. Or you can specify one Backup Set and configure Multiple disks as Members of that Backup Set Manual Ch3 Fundamentals - Backup Sets and their Components 5. Retrospect knows how to handle USB and removable drives, for which you cannot predict in advance the drive letter under which they will mount. Retro uses the volume name. Manual Ch4 Hardware - Hard Disk Drives NB a USB External Drive is a HARD DISK to Retrospect NOT a Removable Drive ( a Removable drive is one where the drive stays connected but the media is removed eg: Floppy, CD, Rev, Jazz etc) 6. Retrospect can "Transfer" Snapshots or entire BackupSets from one place to another BackupSet. Thus a good plan is to perform your backups to a BackupSet on an ON-Site Disk (on the server / nas etc) and then Transfer the Most recent Snapshots to an "Offsite" BackupSet on your External Drives. This way your most recent backup is always available on site for a restore if required, AND it is safely stored off-site for disaster recovery. Manual Ch10 Management - Backup Strategies Manual Ch6 Automated Operations - Scripted Snapshot Transfer Hope this helps get you pointed in the right direction
  9. Yes browsing the catalog can be a time consuming process. Remember that a Retrospect Snapshot is always a representation of the state of the COMPLETE file system at any given point in time. so it is like browsing a Full Backup (Retrospect always takes a full Snapshot scan at the beginning of every backup, regardless of how little datat may actually be backed up in that session) You do, however, have a couple of choices in the method you use to restore a file :- User Restore In later versions user's can restore their own files (Let them do the waiting ) Restore Wizard Here you select the backupset, and Snapshot, then Retro constructs a Tree of the entire backup, which can be a lengthy process (hours) Then you have to browse the tree to find the file you want, which can also be a mission. Finding Files Useful if you are not sure what is needed. Quicker for large backup Sets, especially if you DO know the exact file you need You can search across multiple BackupSets. Find finds ALL instances of a particular file in the entire backup set and displays them all in the tree, with their dates so you can pick which version you need. Restore > Find Files - Choose Backup Set(s) - Retrospect OPENS the "Destination Selection" Window Browse a Session If you know exactly when the file of interest was backed up, you can go directly to the session and restore from there. Configure>Backupsets>Sessions Remember that Sessions contain ONLY the files that were actually backed up in a giveen session, so if it has not chaged for a while it may not be in the most recent session. BUT Sessions are much smaller, and should be quicker to scan. Catalog Performance Obviously Catalogs are busy things. In the Backup Set Properties DISABLE the compression feature, there's plenty of space on modern drives. Put Catalogs, Windows Temp Folders, and BackupSets on separate Drives / Spindles / Arrays / Luns. Retrospect Makes intensive use of these areas, and performance will suffer if they are all contending for the same resource.
  10. jotrago

    Hardware Sizing Backup Server

    Hi Tom, Interesting setup you have there. Lets do a few sums with what you have given us. Full Backup of 4TB in 24 Hours requires ~2.8 GB / min as you say. That's high but may be doable. Your File Server is 2.6 TB with ~1Mill files that means your average file size is around 2.4MB which is quite large. Maybe you are a Media house or similar whihc have larger file sizes. Thus the balance of your backups are ~1.4TB (Exchange, SQL, AD) In my experience a typical general purpose file server has an average file size of around 500KB. Typically the bigger the files the faster they backup (AND Retrospect 9 now has support for Block level incremental backups of files over 100MB in size) Is your Raid Backup Target Directly attached to the Backup Server (SCSI/SAS/FC)? or is it a NAS device. Retrospect can run multiple backups in parallel, up to 8 for Multi Server, provided each backup has a different destination backupset, (No Problem with Disk Backup) With some clever arranging you could have separate, parallel jobs for Exchange, SQL, AD, & File Server Data. If the File Server has separate volumes on separate disks/arrays/Luns/Volumes you could break that up into multiple jobs. With Three source servers running you may manage to flood a single GigE Nic, you might want to consider Multiple GigE Nics / Teaming / 10GigE (if your switch supports these) for the client side connections. If you backup Target Raid is a NAS then get that on a dedicated Teamed/Trunked/10GigE Dedicated Link. Given that most modern servers have multiple (up to 4) Nic Ports built in, I am also a fan of creating a separate Dedicated Backup LAN (DataCente Backup LAN) between the Backup Server, File Server, Exchange & SQL servers etc. Decent GigE Switches are so cheap this shoud be a no brainer, and Retrospect has elegant support for multiple nics. Modern Servers are so Powerful they can often sustain a GigE backup running on a dedicated Nic, during production time without affecting users, this can extend your backup windows. Retrospect can make good use of up to 2GB of RAM over and above the requirements of the OS, and anything else running on the Backup Server (hopefully not much) Remember that Retrospect writing to the Windows Temp File, Catalog File, and Backup Set Files are very intensive. These files should be on separate spindles / Luns / Arrays. Avoid Built in / On Board (Fake) raid contorllers. They are AWFUL. If you are buying new hardware anyway, fork out the $ for proper Hardware Raid Controllers. You wantt each of these 3 files systems to capable of 120MB/s Plus. Enable Checksum Verification and DISABLE verification during Backup. (This can Halve your backup time if you were doing full Verification) Then run separate Verify Jobs during the Day, without impacting the servers. Let me know if I can be of further help
  11. Excuse the dumb question but I cannot find a "Search Forum" function. The search box at the top of the page searches the whole Retrospect site. The Forum Help page talks about a Search and an Advanced Search where you can limit a search to a particular forum.. Maybe I am just blind but I can't see this Forum Search of which they speak. Since there is no general forum forum I'm posting this, inappropriately, here, for want of a better place.
  12. A forum without a search facilty!!!!!!
  13. I have a Windows site running Retro 8.5 with a couple of Mac Clients. We have the Macs Clients installed and configured (Mac 10.5 Client). I created a backup script for the Macs using the Default "Documents & Settings" Selector which appears to have some selectors for Mac Type User Data, expecting it to back up the User data & prefs The script runs, creates a snapshot, but no data is backed up. (Empty Sessions) I have further tested some variations of Mac Specific Selector items like :- "Mac OS9/OSX Path of Folder ends with :Users:, Matching case" and then run a check against my Mac clients. Nothing gets selected. If I use Universal selectors like Folder Name Contains "Users" then folders are selected on the Mac Clients. The docs don't seem to have any specific explanations of the Mac Selectors. Can anyone point me in the right direction While we are on the subject of Macs I have a site with an old Power Mac G5 PPC system which is still working fine. I have installed the latest PPC Mac client I could find (Retrospect Client for OSX 6.3.029 (for 10.5)) which seems to work OK. Is this the correct approach for sites with PPC Macs and Retro 8 or 9 for Windows Server? Thanks a mill
  14. jotrago

    Reports Watcher gone?

    Thanks Robin, Got them now. Just a point, the Watcher readme states that Reports watcher is fully documented in the User guide. I could not find any reference to it in either the 8 or 9 guides. It IS Documented in the 7.5 User Guide - here http://download.retrospect.com/docs/win/v7.5/Win_Retrospect_User_Guide-EN.pdf I am familiar with Watcher from earlier versions so it is not a problem for me. but newer users might get confused.
  15. I've just updated a Win8.2 to Win 8.5 and there no longer seems to be a Reports watcher? Has this been discontinued, and / or is there an alternative way to access a web report? I checked on a V9 site and also no RW.
  16. I have a bunch of laptops with clients automatically added to the "automatically added clients" group. These laptops turnover quite frequently so they are constantly being added and removed as clients. Pro-Active with Client Certificates & Using the Auto Added Group seemed like a perfect solution. I have a pro-active script backing these up. I only want to backup a folder on the C:\ drive eg: C:\MyData. I discovered it had not been implemented consistently and had variations like My Data MyData My-Data & My_Data. I created a selector to Include Windows Path starts with "C:\My" AND path contains "Data". This did the trick! I assumed that this would result in only the C:\Drive being scanned for data, but apparently not The backups run fine, they find the C:\MyData folder and it's variations. BUT they also waste time scanning every other drive they can find on each client where patently no folders will match "C:\My". (Some have additional drives configured, and various external drives are plugged in randomly) Is there a way to prevent Retro from scanning other drives WITHOUT Manually changing the Client Sources to Startup Volume or Manually creating a C:\ Volume for each Client on the console If there is a way to change the Client Sources setting from "Desktop" to "Startup Volume" I think that would meet my needs. I want to keep the system completely automatic so that all the customer has to do is install the client on a machine, the client is auto detected and added, and the correct folder will get backed up without any further configuration. Any tips greatly appreciated
  17. In the end I had to go to each client individually and set the Volumes to Startup Volume only. That was not too much of a pain with only a dozen clients. But this process has to be repeated fairly frequently as clients come and go, which is pain. It would have been a different story on a larger site with hundreds.
  18. Hmmmm Good thought. Yes there are two selectors, a generic Volume Name, and a Windows Drive Letter. I did a quick test, which didn't quite work. It appears that Retro Selects the drives/volumes it is going to work with based on the items resolved by the Sources. It then scans EVERY source applying the filters in the selector(s). It even did this when running the preview of a backup job, producing a separate window for each volume. So it finds the correct files on the correct drive, BUT if I select the whole Client as the Source, which by default, includes all items on the Desktop, ie ALL Drives, then Retro wastes time scanning all those extra drives AND building Snapshots for them. So it looks likes Selectors are only applied AFTER the Volumes are chosen
  19. Sorry I meant " If there is a way to change the DEFAULT Client Sources setting from "Desktop" to "Startup Volume" I think that would meet my needs.
  20. I want to ProActively backing up 15 laptops with Server 8.2 win. We want to backup some user data folders and keep that data for a reasonable period. We also need to backup Pop Email PST files, given that these can be large and change daily, but contain the full history, we want to put these in a separate Backupset with a short retention, probably only 2 or 3 backups, to conserve space. This will require two ProActive scripts to identify each data type and direct it to the appropriate backupsets. I tried setting up a test of this, with both scripts active continuously. One script ran successfully, the other doesn't seem to run at all. If both scripts are active at the same time, should Retrospect gracefully manage things?
  21. With a bit of help from support and some experimentation I found what is happening here. It stems from a natural assumption that turns out not to be true. Possibly it's a mistake a windows user might make, and a Mac user might not. Faced with a pre-defined parent Object of "Source Groups" what would you do if wanted to create a new group? I right click the parent object and select New Source Group on the assumption that New Source Group is a function of Source Groups. Not Necessary. You can right click ANYWHERE in the Volumes Database window, empty space, objects, whatever, and the menu has New Source Group. Selecting this will create a New Source Group CONTAINING THE CURRENTLY SELECTED OBJECT, be that a volume, client, folder, source group, whatever. So my instinctive action of always selecting the parent Source Groups Object, creates a new Source Group CONTAINING the Parent Source Group Object. THUS, all My Source Groups contained EVERY Source Group. SO What you SHOULD do is select the first object you intend to have as a member of your group, probably a client, THEN create the Group, and all will be well. You Live and learn!
  22. Update on this. After a bit if fiddling and restarting everything my test rig ran happily and the two scripts using the same client as source worked beautifully, separating the two types of data into the two backups sets. I then configured the production site using the same concept. but here it is slightly more complex. I have organised the users in to two Source Groups, "Office" & "Surveyors" to cater for different client availability patterns. I have created Four Proactive scripts, "Office-Data" and "Office-EMail", with a source of Office and Dest of the respective Data & Email BackupSets, likewise for "Surveyors" I have installed all the client software with certificates, and they have been recognised and added to the "Backup Clients" icon,and the"Automatically Added Clients" Source Group I am waiting for the customer to tell me who should be placed in the respective groups. All Clients are in AutoAddedGroup, I have copied an alias of one Client to the Office group The results were not quite what I was expecting Looking at the Sources in Proactive Backup Monitor, ALL the clients show up 4 times in the list under each of the four scripts, waiting to backup ASAP???? Since there are no Clients in Surveyors, and only one client in Office I was expecting to see only two items in the Sources, the Office Client for each of the two Office scripts. I conclude that with clients in the automatically added group, other groups are ignored. I tried to MOVE a client from Automatically added, to the Office group, but it only COPIED an alias, leaving the original behind in the AutoAdded group. What is going on here, can anyone explain? How would I achieve the objective explained above.
  23. Yep that can be a bit tricky. Referring to the documentation, ideally if you are going to run it in a TS Session you should INSTALL it in the TS Session. Make sure the Preferences are set to ALWAYS leave Retro Running Make sure that all users are made aware to NOT Logoff. Simply close the RDP session, leaving it running. See the Chapter "Management" in the user guide and topic "Terminal Services and Remote Desktop" There's some discussion here http://forums.retrospect.com/index.php?/topic/27442-best-practice-remote-administration-w2008-r2/ I have an old tech brief on the subject which is similar to the manual content
  24. I have a customer with 15 odd Win 7 Laptops being backed up by a Retro 8 Single Server. I can add clients by Address but not by Multicast Server & Client Firewalls are OFF. Do the clients respond with a name to the multicast requests, which might then require a DNS to resolve the IP Other than the necessary holes in firewalls as per KB ARticle 6326 are there any other specific requirements to be met in order for multicast discovery to work? Thanks
  25. jotrago

    Multiserver client/server compatibility between 7.7 and 8

    I suspect Retro 7.7 will not play nicely with some of the new features in 8. Especially the Instant Scan Technology. You may need to turn that off on the client. http://retrospect.force.com/articles/en_US/Retrospect_Article/General-SCSI-and-USB-Troubleshooting/?q=isa+usb&l=en_US&fs=Search&pn=1 See the above for advanced options with ISA. And probably some of the new Client features will not work, like on demand restore, but may not actually break anything
×