Jump to content

vsharapov

Members
  • Content count

    7
  • Joined

  • Last visited

Community Reputation

0 Neutral

About vsharapov

  • Rank
    Newbie
  1. vsharapov

    Backup drives are full

    I did rebuild it, started for a second and task finished with no errors and nothing done. I tried this before start topic here and unfortunatelly it didnt help.
  2. vsharapov

    Backup drives are full

    I was wonder as I thought that grooming on its own should clean, or at least it will add data only that is new and update previous. At this point you explained alot! Appreciate it. The last thing are how to prevent retrospect to crash, as it crashes engine and keeps restarting. Should I just wipe backups, uninstall Retrospect and reinstall from scratch?
  3. vsharapov

    Backup drives are full

    5GB was just an example, it does usually different amounts, from 100 to 300+ - GB Thanks a lot for your explanation! What would be your recommendation for media sets in terms of grooming policy? Is it better always to keep fixed amount of backups or not to groom at all and rely only on Grooming script that will create? Regards
  4. vsharapov

    Backup drives are full

    On destination volumes there is only backup files, catalog are stored on host. Speaking about the onsite backup: Source is the external drive that hold main data (4.6TB) , script is "backup" Same for offsite backup. Sorry if Im slow a bit. as what I understood I have to create a script " Groom" include drives that are full and it should groom out big amount of data? And one more thing - is retrospect shouldnt takeoff data that is older? or kinda update backups ? Lets say main data got 100 new files in total 5GB per week, so the main chunk should grow only with this 5GB? correct? I mean if I have 4645GB + 5 GB = 4650GB , so how then data overfilling drive? Appreciate your assistance, sorry for grammar. Regards
  5. vsharapov

    Backup drives are full

    Im not running it manually or by script, the only way how grooming is work is what defined by policy. But even this doesn't work, as drives got full. To make an offsite backup im using script that backups same data as onsite backup script.
  6. Hello people. I currently experiencing issues with Retrospect in terms of backup drives got full. In example: Total size of data to backup is 4.6TB "onsite media set" consists of two drive and has in total 9TB of storage, it holds up to 6 months of backups "offsite backup" drives A and B are 8TB rotated every couple days and it got filled like immediately during a week despite the fact that it should hold only 1 backup (drive A) , drive B still has 1.2TB available Grooming is not helping, attempted to verify catalog on media set. The reason I'm here is because Retrospect spammed yesterday my email (~1300+ emails, last 400 came in less then 1min), plus today over night 500+ arrived more. Yesterday Retrospect engine was restarting itself, but after I turned off proactive backup script it allowed me to start verification of the media set. After verification got these errors: !Generated MD5 digest for file "/Volumes/Boot RAID/Library/Server/Wiki/Database.xpg/Cluster.pg/pg_xlog/archive_status/00000001000000180000003A.done" does not match stored MD5 digest. Additional error information for Disk Backup Set member "1-New Home Backup", Can't read to file /Volumes/New Home Backup 1/Retrospect/New Home Backup/1-New Home Backup/AA007994.rdb, error -1101 (file/directory not found) Additional error information for Disk Backup Set member "1-New Home Backup", Can't read to file /Volumes/New Home Backup 1/Retrospect/New Home Backup/1-New Home Backup/AA008000.rdb, error -1101 (file/directory not found) !Generated MD5 digest for file "/Volumes/Boot RAID/Library/Server/Wiki/Database.xpg/Cluster.pg/pg_xlog/archive_status/000000010000001C00000017.done" does not match stored MD5 digest. !Generated MD5 digest for file "/Volumes/Boot RAID/Library/Server/Wiki/PostgresSocket/.xpg.skt.lock" does not match stored MD5 digest. Additional error information for Disk Backup Set member "2-New Home Backup", Can't read to file /Volumes/New Home Backup 2/Retrospect/New Home Backup/2-New Home Backup/AA012574.rdb - AA014055.rdb , error -1101 (file/directory not found) Any ideas on what might happening and how to release space? Even if I will start backup from scratch and will delete catalog file, is there any chance to inherit previous backups to continue work with them? Or just in case for future restores? PS: sorry for grammar and thank you for assistance. Regards
×