[nemo@localhost calendar]$ syncevolution --restore /home/nemo/.cache/syncevolution/google_+calendar@google_+calendar-2014-02-05-13-50/  --before

No configuration name specified

# the peer which is used by default in some frontends, like the sync-UI
# defaultPeer =

# Explicitly selects a certain safe password storage.
# Depending on how SyncEvolution was compiled and installed
# the following values are possible:
#
# GNOME
#   GNOME Keyring
# KDE
#   KWallet
# yes/true/1
#   pick one automatically
# no/false/0
#   store passwords in SyncEvolution config files
#
# If unset, the default is to pick one automatically if support
# for any kind of password storage was enabled and use the config files
# otherwise. When choosing automatically, GNOME keyring is tried
# first because distinguishing between KDE and GNOME sessions
# automatically is tricky.
#
# Note that using this option applies to *all* passwords in
# a configuration and that the --keyring command line option
# is merely an alias for setting the global property, so setting
# a single password as follows sets both `keyring` and
# `proxyPasswords`, and also moves the other passwords into the
# keyring, even if they were not stored there already:
#
#      --keyring --configure proxyPassword=foo
#
# When passwords were stored in a safe storage, their value is set to a single
# hyphen ("-") in the configuration. This means that when running a
# synchronization without using the storage, the password has to be
# entered interactively. The --print-config output always shows "-" instead
# of retrieving the password from the keyring.
# keyring = no

syncevolution --restore /home/nemo/.cache/syncevolution/google_+calendar@google_+calendar-2014-02-05-13-50/  --before google-calendar calendar

syncevolution --print-sessions google-calendar