Of course new backups can be made while existing save sets will be cloned - in general. However, some limitations 'by nature' exist. So you can only use a tape device/media for reading OR writing at the same time.
Without any further details about your configuration, nobody can point you directly to what has been setup wrong. The workflow details/log info will tell you the reason why the backup has not taken place. Just double-click the appropriate line(s). Worst case, check the daemon.raw file with
nsr_render_log [-S (start_time)]
Obvious issues are
- wrong storage node defined
- wrong pool/pool type defined
- device defined but no appendable media is available.
May I suggest that you disable the clone action and look that you backups will run successfully first. The reasons areobvious:
bingo.1
2.4K Posts
0
February 5th, 2020 23:00
Of course new backups can be made while existing save sets will be cloned - in general. However, some limitations 'by nature' exist. So you can only use a tape device/media for reading OR writing at the same time.
Without any further details about your configuration, nobody can point you directly to what has been setup wrong. The workflow details/log info will tell you the reason why the backup has not taken place. Just double-click the appropriate line(s). Worst case, check the daemon.raw file with
nsr_render_log [-S (start_time)]
Obvious issues are
- wrong storage node defined
- wrong pool/pool type defined
- device defined but no appendable media is available.
May I suggest that you disable the clone action and look that you backups will run successfully first. The reasons areobvious:
- you can only clone an existing backup.
- you can manually clone any time later.