I set up 4 snapshots so that 002 - 004 do not overlap, and each cover a 3 hour 59 minute window.
I have two issues:
1) The drop-list to select the snapshot for local backup shows no entries (Maintenance/Backup/Local Backup/Snapshot). Why?
Also, if I try to backup without any snapshot selected why does a message pop up saying:
"No snapshot choosed.
Backup can be made only from snapshots with no create- and remove-time assigned."
2) Only the active snapshot actually contains files, the other 3 are empty and designated as "unused"
My goal is to have multiple restore points available concurrently. Is this possible?
It would appear that placing an end time on a snapshot causes it to write to the mail volume and "empty" itself. While this is fine, it is not what I need for my implementation.
The obvious solution is to not put end-times on snapshots, which would cause them to persist for 24 hours until refreshed at the next start time. Sounds great, but when you have more than one snapshot in this mode, I need to know how they interact with each other with respect to writes to the main volume. All the questions I asked previously about interaction still apply.
1)
You must set a Snapshot with no begin and no end time. Then create the snapshot in Maintenance / Snapshot this will set it in manual mode to allow you to select from the Maintenance / Backup.
Please read the instructions on how this is done or read the cut that I have provided.
Function “Local backup”
This function allows you to backup shares into tar-gziped files. Available choices:
Source lv:
Please choose logical volume from which shares will be backed up. It is possible
to backup shares from one logical volumes at once.
When you change source lv, avaliable shares and snapshot will also
change.
Snapshot:
Backup is performed from snapshot to provide data integrity.
You can choose only from snapshots with no create- and remove-time
assigned.
2)
You can have multiple snapshots to provide multiple restore points. Please set your Snapshots appropriate to the scheduled or with no end time for file recovery purposes. It would be best if you can test which Snapshot functions would best fit your needs for this, as every environment is different.
I think I understand snapshots well enough now to know that I want to have no end times in order to preserve restorable data. This gives me snapshots that are refreshed at create time every day. Cool.
The only issue I have now is with backups. You've confirmed that backups can only function on snapshots that have no start or end time. That means no automatically scheduled snapshot can be backed up at all, -only manually created ones.
This is the function of Local Backup. Backup is performed from snapshot to provide data integrity. So you need to have this setup for manual mode for backup and the other Snapshots can be used for quick file retrieval. This is explained in the manual as well.
Simple Question: Is it possible to have more than one snapshot contain data at one time?
Originally I had snap002 - 005 set with create and delete dates, but found that if I wanted to go to their contents *outside* that time range I would find them "unused" and therefore empty.
I cleared the delete time so that they would retain their contents until they are (re)created the next day, but what I am finding is that snap002 gets created and the rest of the snapshots remain "unused."
My goals seem simple enough to me: Multiple CONCURRENT snapshot restore points and a scheduled local backup.
I have already given up on the scheduled local backup because it depends on a manual snapshot creation. Do I also have to give up on the idea of having several snapshot restore points to choose from?
Ironically, I just found out my local backup is working the way I would like; right off the logical volume rather than a snapshot. The UI confused me by putting both drop lists in there and having the snapshot one fail if the snapshot is scheduled.
I am not sure that the backups are actually happening though, as my dynamic volume is full. Is there a cull or overwrite mechanism in place that I can't find?
You are saying that if I manually create snapshots, multiple snapshots can stick around as long as I like, but only one automatic/scheduled snapshot can exist at one time?
Snapshot is a manual restore process. Not sure if we are miss communicating to each other.
Try to provide me in detail what steps you have taken and what are the detail results. These functions are very simple and are easy to test. In future releases we will add more functionality but no time frame is set and details. Thanks for your patients in this matter.
My Goal: Multiple, snapshots available for restore at the same time with these snapshots being created through your scheduling process.
Restore is indeed a manual process, but so far I have only figured out how to have 1 scheduled snapshot contain data to restore at any given time.
I have created them with begin and end dates, and I have created them with only begin dates. In both cases, only one of these automatically created snapshots contains data at a given time.
For me, the value of snapshots is dramatically lessened if I have to create them manually. I would like them to get created on a schedule, and if I need a restore, I pick whichever one is appropriate and perform the restore.
Thanks for *your* patience, I am sure I must be driving you mad with this line of inquiry.
Reply With Quote
