You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is it possible to add the option to provide a name for the snapshot? Currently, it's blank. Is there a way to also provide an intermental number when snapshots are in daemon mode?
Example: Test_20151014_01, Test_20151014_02, Test_20151014_03, Test_20151015_01, Test_20151015_02 (Something like --snapshot-name Test_$date_$increment_value)
Also - Is there a way to specify the log-file inside a .conf file as opposed to a command line parameter? I want to be able to log what happens automatically through the daemon and have a location where the logs are saved.
AWESOME TOOL! Love it! and THANK YOU!!!!!
The text was updated successfully, but these errors were encountered:
Snapshots are hard to associate with an EBS in EC2 control panel because as far as I can see you can't name/tag your snapshots. If you could name it something like "YYYY-MM-DD HH:ii - vol-xxxxxxx" you could easily see which snaps apply to which volume and which date each one was taken. (If I'm missing something and you can get this info already, sorry!)
Is it possible to add the option to provide a name for the snapshot? Currently, it's blank. Is there a way to also provide an intermental number when snapshots are in daemon mode?
Example: Test_20151014_01, Test_20151014_02, Test_20151014_03, Test_20151015_01, Test_20151015_02 (Something like --snapshot-name Test_$date_$increment_value)
Also - Is there a way to specify the log-file inside a .conf file as opposed to a command line parameter? I want to be able to log what happens automatically through the daemon and have a location where the logs are saved.
AWESOME TOOL! Love it! and THANK YOU!!!!!
The text was updated successfully, but these errors were encountered: